Matt Navarre wrote:
After a power outage last night I rebooted my computer and fsck
complained of the following :
ad1s2e: hard error reading fsbn 5103776 (ad1s2 bn 5103776; cn 317 tn
177 sn 20) status=59 error=40
Then goes on for a while giving the same error on blocks 5103776 -
5103807,
Matt Navarre [EMAIL PROTECTED] writes:
Now, on to the damaged sectors, how to recover the data? dd stops when
it hits bad blocks, so we can't use that to copy the slice. same with
dump(8) as far as I can tell. So. Download dd_rescue from
http://www.garlof.de/kurt/linux/ddrescue/
Just out of
Matt Navarre wrote:
Matt Navarre wrote:
After a power outage last night I rebooted my computer and fsck
complained of the following :
ad1s2e: hard error reading fsbn 5103776 (ad1s2 bn 5103776; cn 317 tn
177 sn 20) status=59 error=40
Then goes on for a while giving the same error on blocks
Lowell Gilbert wrote:
Matt Navarre [EMAIL PROTECTED] writes:
Now, on to the damaged sectors, how to recover the data? dd stops when
it hits bad blocks, so we can't use that to copy the slice. same with
dump(8) as far as I can tell. So. Download dd_rescue from
After a power outage last night I rebooted my computer and fsck
complained of the following :
ad1s2e: hard error reading fsbn 5103776 (ad1s2 bn 5103776; cn 317 tn
177 sn 20) status=59 error=40
Then goes on for a while giving the same error on blocks 5103776 -
5103807, except for block
orville weyrich wrote:
Before doing anything to your hard drive, check out
your computer's power supply -- if they go off
tolerance on voltages, you may start getting disk
errors -- often the first sign of power supply
problems.
Hmmm, Ok, I can see that. The errors are confined to one slice on
