I have a hard drive that is starting to fail (see here for details and links: http://linux.overshoot.tv/ticket/64 )
I have a specific question about e2fsck:
What am I supposed to reply to this question? Ignore error <y>?
I searched and many people seem to reply yes to all such question (they even use the -y flag to automatically reply yes).
But what does it do? What are the consequences of replying either way? What is safe? What difference does it make?
As I said in the above ticket, man e2fsck didn't help much.
Other people seem to recommend using badblocks(8).
How are those two tools related? Should I run one then the other?
Also, be aware that I am documenting everything I find here, as I go along:
http://linux.overshoot.tv/wiki/hardw...ing_hard_drive
so that we have a permanent record of the best practice (preparedness, troubleshooting and repair).
If you know of other tutorials, HOWTOs, documentation and wikis addressing the same issue, let me know. Generally speaking, I do my best to link http://linux.overshoot.tv/ to the best available documentation (no need to reinvent the wheel). For example: http://linux.overshoot.tv/wiki/external_documentation
I have a specific question about e2fsck:
Code:
# e2fsck /dev/sdc1 /dev/sdc1 contains a file system with errors, check forced. Pass 1: Checking inodes, blocks, and sizes Error reading block 162824194 (Attempt to read block from filesystem resulted in short read) while getting next inode from scan. Ignore error<y>?
I searched and many people seem to reply yes to all such question (they even use the -y flag to automatically reply yes).
But what does it do? What are the consequences of replying either way? What is safe? What difference does it make?
As I said in the above ticket, man e2fsck didn't help much.
Other people seem to recommend using badblocks(8).
How are those two tools related? Should I run one then the other?
Also, be aware that I am documenting everything I find here, as I go along:
http://linux.overshoot.tv/wiki/hardw...ing_hard_drive
so that we have a permanent record of the best practice (preparedness, troubleshooting and repair).
If you know of other tutorials, HOWTOs, documentation and wikis addressing the same issue, let me know. Generally speaking, I do my best to link http://linux.overshoot.tv/ to the best available documentation (no need to reinvent the wheel). For example: http://linux.overshoot.tv/wiki/external_documentation
Comment