Quantcast

Getting rid of an uncorrectable error

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Getting rid of an uncorrectable error

Joachim Breitner
Hi,

two days ago, I got an uncorrectable error:

$ smartctl --all /dev/hda|grep -i uncorrect
198 Offline_Uncorrectable   0x0030   100   100   000    Old_age   Offline      -       1

This corresponds with these errors in the dmesg output:

[2746522.212124] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
[2746522.215737] hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=72206605, sector=72206605
[2746522.215782] ide: failed opcode was: unknown
[2746522.215802] end_request: I/O error, dev hda, sector 72206605
[2746522.215825] Buffer I/O error on device dm-2, logical block 1042560
[2746522.216149] EXT3-fs error (device dm-2): ext3_readdir: directory #508100 contains a hole at offset 77824
[2746528.461763] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
[2746528.461763] hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=72206605, sector=72206605
[2746528.461763] ide: failed opcode was: unknown
[2746528.461763] end_request: I/O error, dev hda, sector 72206605
[2746528.461763] EXT3-fs error (device dm-2): ext3_readdir: directory #508100 contains a hole at offset 77824

All SMART tests run though, though:
SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%     33000         -
# 2  Short offline       Completed without error       00%     32978         -
# 3  Extended offline    Completed without error       00%     32959         -
# 4  Extended offline    Completed without error       00%     32955         -
# 5  Short offline       Completed without error       00%     32953         -
# 6  Short offline       Completed without error       00%     32933         -
[..]

I could read sector 72206605 just fine, and I wrote it back using ddl,
following the BadBlockHowto. Still, I get daily mails from smartd that I
have this error.

How can I find out if and where there still is an error, and if there is
none, how can I make the drive forget about it.

Drive information:

=== START OF INFORMATION SECTION ===
Device Model:     SAMSUNG SP0802N
Serial Number:    S00JJ10XC74544
Firmware Version: TK200-04
User Capacity:    80.060.424.192 bytes
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   7
ATA Standard is:  ATA/ATAPI-7 T13 1532D revision 0
Local Time is:    Mon Apr 20 18:29:19 2009 CEST


Thanks,
Joachim
--
Joachim "nomeata" Breitner
  mail: [hidden email] | ICQ# 74513189 | GPG-Key: 4743206C
  JID: [hidden email] | http://www.joachim-breitner.de/
  Debian Developer: [hidden email]

------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today.
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
Smartmontools-support mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/smartmontools-support

signature.asc (204 bytes) Download Attachment
Loading...