I've failed to do this in the past and royally regretted it! I consider rule #1 in these situations as to avoid reading from or writing to a suspected faulty drive, to avoid further data loss or complete drive failure. Unmount and cease all interactions with the filesystem, except for the following steps.If I were in your shoes, and if the drive had important stuff on it, I would do the following, in order: You could maybe use that to determine if the drive - or at least the area of the drive on which the filesystem stands - has bad sectors/blocks, but do not run this tool on a mounted filesystem doing so itself can cause corruption, even if you mount the filesystem as read-only. There's a program called `badblocks`, which seems to work on EXT4 filesystems. I agree with Kadaitcha Man that SMART is should be used as a guide alongside other information, not alone to be taken as gospel. Is your drive really slow, lately? That's a sign of a hardware fault I've noticed in the past. Do you get I/O errors? That's a common sign of corruption and/or faulty hardware.
0 Comments
Leave a Reply. |