On 05/05/2014 03:13 PM, Marcelo Cavalcante wrote:
Well,
By the logs we can see that it has a "few" sectors with problems.
For now, do you know which file system is used on this partition/disk?
First of all, I would try to map the badblocks. Something like:
$ sudo badblocks -v /dev/sdb1 > bad-blocks
You can also mak e aread/write test:
$ sudo badblocks -wsv /dev/sdb1
It will generate a file (bad-blocks) with a list of the badblocks
identified. After that, you can try to use:
$ sudo fsck -t ext3 -l bad-blocks /dev/sdb1
I´m using ext3 here supposing that you´re using ext3 on this disk.
It will try to pass this file to the fsck command to record these bad blocks.
If you can access the partition but not see the files, you can try a
few specific "recovering" tools, but it will depends on what file
system you´re using.. that´s why it´s important to tell us.
Best,
===================================================
[...]
2014-05-05 16:01 GMT-03:00 Patricia Campbell <[email protected]>:
Hello All,
Someone has come to me with an hdd that is borked, kernel msgs
attached. He cannot afford to pay to have it recovered: I do know
about the guy in NDG but that is out of the question. So anybody out
there have a favourite recovery program or two ??
Hello,
Before any fsck or badblock, please, _PLEASE_, use ddrescure and make a
copy of what you have on that disk. Any further action should be done on
the image created with ddrescure and NOT on the failing HDD. Depending
on the filesystem, then you can use specific tools to try to
repair/recover data.
--
Best Regards,
Sorin Toma
_______________________________________________
mlug mailing list
[email protected]
https://listes.koumbit.net/cgi-bin/mailman/listinfo/mlug-listserv.mlug.ca
