Currently unreadable sectors problem??
Praveen <praveen9 <at> gmail.com>
2004-11-04 09:53:54 GMT
Hi,
I have a Maxtor 6Y160P0 drive, with one fat32 and one
reiserfs partition. Recently i realised (after some compilation errors
which always used to hang the system - i was using kdecvs-build
program) that syslog showed two specific SMART messages regarding the
maxtor drive
1. Device: /dev/hda, 137 Offline uncorrectable sectors
2. Device: /dev/hda, 138 Currently unreadable (pending) sectors.
I then ran a long test using smartctl -t long which
showed status "Completed:Read failure" and listed the LBA of first
error. I then ran 'badblocks' on each of the partition to verify if
there are any bad sectors but it showed nothing. I again ran the
badblocks program with -n option which does a non-destructive write
test and it showed lot of errors on the fat32 partition like
Nov 3 15:58:37 hda: dma_intr: error=0x40 { UncorrectableError },
LBAsect=146560385, high=8, low=12342657, sector=146560291
Nov 3 15:58:37 end_request: I/O error, dev hda, sector 146560291.
After running this all smartctl tests now pass with status "Completed
without error". The syslog message from smartctl now only indicates
1. Device: /dev/hda, 138 Currently unreadable (pending) sectors.
I am not sure what just happened with the drive, did 'badblocks' force
the drive to remap bad sectors . What does the "currently unreadable
sectors" signify and why does the smart test now pass without errors.
Should i do a low level format of the drive? The errors only occured
for the fat32 partition not the reiserfs partition. Why did the system
hang when compiling in reiserfs partition when the errors were found
(Continue reading)