From: <mk-...@em...> - 2005-07-15 22:54:24
|
Hi, great tool! Thanks for the good FAQ and HOWTOs to overcome the problem of bad blocks. It had been proven to be very valuable for me, since I have been able to repair quite a bit of one of my drives. Though I ran into a strange thing: I understood that I need to force the drive to write on bad blocks to let it reallocate them to another physical spot on the disc. So, when I noticed that extended offline tests ("-t long") failed on my drive repeatedly --- === START OF READ SMART DATA SECTION === SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed: read failure 00% 31 18800160 # 2 Short offline Completed without error 00% 31 - # 3 Extended offline Completed: read failure 00% 31 18800161 # 4 Short offline Completed without error 00% 31 - # 5 Extended offline Completed: read failure 00% 30 18800162 # 6 Extended offline Completed: read failure 00% 30 18800161 # 7 Short offline Completed without error 00% 30 - # 8 Extended offline Completed: read failure 00% 30 18800161 # 9 Extended offline Completed: read failure 00% 30 18800161 #10 Extended offline Completed: read failure 00% 29 18800160 #11 Short offline Completed without error 00% 29 - #12 Extended offline Completed: read failure 00% 29 18800160 #13 Extended offline Completed: read failure 00% 29 18800160 #14 Extended offline Completed: read failure 00% 28 18800160 #15 Short offline Completed without error 00% 28 - #16 Short offline Completed without error 00% 25 - #17 Short offline Completed without error 00% 22 - #18 Short offline Completed without error 00% 21 - #19 Extended offline Completed without error 00% 21 - #20 Abort offline test Aborted by host 80% 20 - #21 Extended offline Completed without error 00% 20 - --- I forced it to reallocate the wrong sectors by overwriting the corresponding area (using "dd" and also "badblocks" in write mode): --- dd if=/dev/zero of=/dev/hde6 bs=4096 count=1 seek=635073 ; sync --- badblocks -w -v -b 512 /dev/hde 18800163 18800160 ; sync --- (Surprisingly the call of badblocks above didn't show the presence of bad blocks 18800160-18800162, although the SMART test DOES.) BUT, looking at the drive's attributes (after those writes) I saw they showed NO sign of pending sectors. The reallocated blocks and uncorrectables shown below stem from events later in the past and didn't change during the operations listed above: --- 196 Reallocated_Event_Count 0x0032 099 099 000 Old_age Always - 4 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 099 099 000 Old_age Offline - 4 --- And eventually the "extended offline tests" still fail... Writes using dd and badblocks happened somewhere around #6, but the error in that sector area persists. WHAT DOES THIS MEAN? Is this area uncorrectable by writing on it? Something must be wrong in my understanding of the situation, I guess... Here is my hardware: === START OF INFORMATION SECTION === Device Model: SAMSUNG SP0812N Serial Number: S00MJ10XC20460 Firmware Version: TK100-30 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: Sat Jul 16 00:25:41 2005 CEST SMART support is: Available - device has SMART capability. SMART support is: Enabled Disk /dev/hde: 80.0 GB, 80060424192 bytes 255 heads, 63 sectors/track, 9733 cylinders, total 156368016 sectors Units = sectors of 1 * 512 = 512 bytes Here is the relevant part of my partitioning of that hd: --- Device Boot Start End Blocks Id System /dev/hde1 63 10490444 5245191 c W95 FAT32 (LBA) /dev/hde2 10490445 12594959 1052257+ 82 Linux swap / Solaris /dev/hde3 12594960 12691349 48195 83 Linux /dev/hde4 12691350 156344579 71826615 f W95 Ext'd (LBA) /dev/hde5 12691413 13719509 514048+ 83 Linux /dev/hde6 13719573 24209954 5245191 83 Linux ... --- where hde6 is the partition with the read error in it. There is a second drive on the udma port, which didn't show any problems up to now, except that it's presence somehow seems to disturb the first drive, because when I inserted the Maxtor below, suddenly the Samsung had it's first UDMA_CRC_Error_Count, which hadn't happened ever before: === START OF INFORMATION SECTION === Device Model: Maxtor 4R080J0 Serial Number: R20Z97QE Firmware Version: RAMB1TU0 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: Sat Jul 16 00:26:08 2005 CEST SMART support is: Available - device has SMART capability. SMART support is: Enabled Any idea what's going on here??? Regards, Marko |
From: Marko <mk-...@em...> - 2005-08-01 01:46:24
|
Hi, I still keep having these errors from time to time. What's going on? Perhaps the error occurs rarely during writing on that spot of the HD, but happens more often during reads?! And so I get read errors, but no self-correction during writes. Is that possible? Marko |