The following happens:
Writing to one of the log files in /var/adm/. produces
a "hardware error: MEDIUM ERROR -- cannot write to block XYZ"
(something like this) in the syslog and a harsh sound from
my SCSI-hd.
OK, reboot with boot - floppy and
e2fsck -c /dev/<sda2>
to check everything for not useable blocks. This SHOULD also include
defect blocks into the badblock inode.
Again the sound nasty soudn a the same block was reported being defect.
I - thought - this was the repair of my problems. But:
Again running
e2fsck /dev/sda2
Produces the same read error from the same bad block and the same sound.
Hmmm...
I thought the -c option and the entry
of the badblock would avoid further reading?!
Is there something wrong with the hadnling of bad blocks?
Am I totally wrong in this case?
And -- if so -- how can I avoid further reading from this defect block, possibly
WITHOUT reformatting the disk, cause it is my root device and therefore
the prrof of Murphy's law.
Thank you very much for any help!
KEEP HACKING!
Meino
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/