From: <lxn...@gm...> - 2012-11-17 15:35:37
|
Please point me straight I have a drive showing 2 bad blocks I want to find the files associated with these blocks I have read "Bad block HOWTO for smartmontools" but am still confused The first lba 333161989705 is greater than 1465144064 # fdisk -l /dev/sda Disk /dev/sda: 750.2 GB, 750156374016 bytes 255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x0009a6c9 Device Boot Start End Blocks Id System /dev/sda1 63 208844 104391 83 Linux /dev/sda2 208845 16996769 8393962+ 82 Linux swap / Solaris /dev/sda3 16996770 48468104 15735667+ 83 Linux /dev/sda4 48468105 1465144064 708337980 83 Linux # smartctl -x /dev/sda Error 2 [1] occurred at disk power-on lifetime: 27064 hours (1127 days + 16 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 08 00 4d 92 00 86 49 e0 00 Error: UNC 8 sectors at LBA = 0x4d92008649 = 333161989705 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 25 00 00 00 08 00 4d 92 00 86 49 e0 08 39d+22:53:19.132 READ DMA EXT ca 00 00 00 08 00 01 cd 00 2f b2 e1 08 39d+22:53:19.132 WRITE DMA ea 00 00 00 00 00 01 cd 00 2f b1 e0 08 39d+22:53:19.092 FLUSH CACHE EXT ca 00 00 00 10 00 01 cd 00 2f a2 e1 08 39d+22:53:19.092 WRITE DMA ca 00 00 00 08 00 01 83 00 a8 d2 e1 08 39d+22:53:19.091 WRITE DMA Error 1 [0] occurred at disk power-on lifetime: 27064 hours (1127 days + 16 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 01 a0 00 4d 90 00 86 f1 e0 00 Error: UNC 416 sectors at LBA = 0x4d900086f1 = 333128435441 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 25 00 00 01 a0 00 4d 90 00 86 f1 e0 08 39d+22:53:01.661 READ DMA EXT 35 00 00 00 10 00 4d 90 00 83 99 e0 08 39d+22:53:01.661 WRITE DMA EXT 35 00 00 00 08 00 17 97 00 ff 19 e0 08 39d+22:53:01.661 WRITE DMA EXT 35 00 00 00 08 00 51 90 00 d3 a1 e0 08 39d+22:53:01.660 WRITE DMA EXT ea 00 00 00 00 00 4c 90 00 e3 e8 e0 08 39d+22:53:01.620 FLUSH CACHE EXT |
From: Alex S. <ml...@os...> - 2012-11-17 18:32:45
|
On 11/17/2012 04:35 PM, lxn...@gm... wrote: > Please point me straight > I have a drive showing 2 bad blocks > I want to find the files associated with these blocks > I have read "Bad block HOWTO for smartmontools" but am still confused > The first lba 333161989705 is greater than 1465144064 > I had similar problem. My workaround was to run long test and get correct sector number from the -l selftest. Also you could look on dmesg to find failed sector. > > > # smartctl -x /dev/sda > > Error 2 [1] occurred at disk power-on lifetime: 27064 hours (1127 days + 16 hours) > When the command that caused the error occurred, the device was active or idle. > > After command completion occurred, registers were: > ER -- ST COUNT LBA_48 LH LM LL DV DC > -- -- -- == -- == == == -- -- -- -- -- > 40 -- 51 00 08 00 4d 92 00 86 49 e0 00 Error: UNC 8 sectors at LBA = 0x4d92008649 = 333161989705 > > Commands leading to the command that caused the error were: > CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name > -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- > 25 00 00 00 08 00 4d 92 00 86 49 e0 08 39d+22:53:19.132 READ DMA EXT > ca 00 00 00 08 00 01 cd 00 2f b2 e1 08 39d+22:53:19.132 WRITE DMA > ea 00 00 00 00 00 01 cd 00 2f b1 e0 08 39d+22:53:19.092 FLUSH CACHE EXT > ca 00 00 00 10 00 01 cd 00 2f a2 e1 08 39d+22:53:19.092 WRITE DMA > ca 00 00 00 08 00 01 83 00 a8 d2 e1 08 39d+22:53:19.091 WRITE DMA > > Error 1 [0] occurred at disk power-on lifetime: 27064 hours (1127 days + 16 hours) > When the command that caused the error occurred, the device was active or idle. > > After command completion occurred, registers were: > ER -- ST COUNT LBA_48 LH LM LL DV DC > -- -- -- == -- == == == -- -- -- -- -- > 40 -- 51 01 a0 00 4d 90 00 86 f1 e0 00 Error: UNC 416 sectors at LBA = 0x4d900086f1 = 333128435441 > > Commands leading to the command that caused the error were: > CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name > -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- > 25 00 00 01 a0 00 4d 90 00 86 f1 e0 08 39d+22:53:01.661 READ DMA EXT > 35 00 00 00 10 00 4d 90 00 83 99 e0 08 39d+22:53:01.661 WRITE DMA EXT > 35 00 00 00 08 00 17 97 00 ff 19 e0 08 39d+22:53:01.661 WRITE DMA EXT > 35 00 00 00 08 00 51 90 00 d3 a1 e0 08 39d+22:53:01.660 WRITE DMA EXT > ea 00 00 00 00 00 4c 90 00 e3 e8 e0 08 39d+22:53:01.620 FLUSH CACHE EXT > |
From: Christian F. <Chr...@t-...> - 2012-11-17 18:47:11
|
lxnf98mm at gmail.com wrote: > Please point me straight > I have a drive showing 2 bad blocks > I want to find the files associated with these blocks > I have read "Bad block HOWTO for smartmontools" but am still confused > The first lba 333161989705 is greater than 1465144064 > > > # fdisk -l /dev/sda > > Disk /dev/sda: 750.2 GB, 750156374016 bytes > 255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors > ... > > # smartctl -x /dev/sda > > Error 2 [1] occurred at disk power-on lifetime: 27064 hours (1127 days + 16 hours) > When the command that caused the error occurred, the device was active or idle. > > After command completion occurred, registers were: > ER -- ST COUNT LBA_48 LH LM LL DV DC > -- -- -- == -- == == == -- -- -- -- -- > 40 -- 51 00 08 00 4d 92 00 86 49 e0 00 Error: UNC 8 sectors at LBA = 0x4d92008649 = 333161989705 Unfortunately some disk firmware author did not read the ATA standard carefully: The byte order of the "LBA field" (previously "LBA Low/Mid/High registers") is not correct. The standard uses the old (ATA-6/7) LBA register ordering, the drive likely uses little endian ordering. Smartctl 6.0 adds a new option "-F xerrorlba" to fix this. When this option is specified, the output should change to a more reasonable LBA value: LBA_48 LH LM LL == == == -- -- -- 00 4d 92 00 86 49 ... 0x4d92008649 = 333161989705 | | | | 00 00 4d 86 92 49 ... 0x004d869249 = 1300664905 Please provide a full "smartctl -x -q noserial" output for this drive as an attachment. Then I could add the -F xerrorlba option to its drive database entry. Thanks, Christian |
From: <lxn...@gm...> - 2012-11-17 19:01:44
Attachments:
smartctl_sda
|
On Sat, 17 Nov 2012, Christian Franke wrote: > lxnf98mm at gmail.com wrote: >> Please point me straight >> I have a drive showing 2 bad blocks >> I want to find the files associated with these blocks >> I have read "Bad block HOWTO for smartmontools" but am still confused >> The first lba 333161989705 is greater than 1465144064 >> >> >> # fdisk -l /dev/sda >> >> Disk /dev/sda: 750.2 GB, 750156374016 bytes >> 255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors >> ... >> >> # smartctl -x /dev/sda >> >> Error 2 [1] occurred at disk power-on lifetime: 27064 hours (1127 days + >> 16 hours) >> When the command that caused the error occurred, the device was active >> or idle. >> >> After command completion occurred, registers were: >> ER -- ST COUNT LBA_48 LH LM LL DV DC >> -- -- -- == -- == == == -- -- -- -- -- >> 40 -- 51 00 08 00 4d 92 00 86 49 e0 00 Error: UNC 8 sectors at LBA = >> 0x4d92008649 = 333161989705 > > Unfortunately some disk firmware author did not read the ATA standard > carefully: The byte order of the "LBA field" (previously "LBA Low/Mid/High > registers") is not correct. The standard uses the old (ATA-6/7) LBA register > ordering, the drive likely uses little endian ordering. > > Smartctl 6.0 adds a new option "-F xerrorlba" to fix this. When this option > is specified, the output should change to a more reasonable LBA value: > > LBA_48 LH LM LL > == == == -- -- -- > 00 4d 92 00 86 49 ... 0x4d92008649 = 333161989705 > | | > | | > 00 00 4d 86 92 49 ... 0x004d869249 = 1300664905 > > Please provide a full "smartctl -x -q noserial" output for this drive as an > attachment. Then I could add the -F xerrorlba option to its drive database > entry. > > Thanks, > Christian > Attached |
From: <lxn...@gm...> - 2012-11-17 18:55:26
|
On Sat, 17 Nov 2012, Alex Samorukov wrote: > > On 11/17/2012 04:35 PM, lxn...@gm... wrote: >> Please point me straight >> I have a drive showing 2 bad blocks >> I want to find the files associated with these blocks >> I have read "Bad block HOWTO for smartmontools" but am still confused >> The first lba 333161989705 is greater than 1465144064 >> > I had similar problem. My workaround was to run long test and get correct > sector number from the -l selftest. Also you could look on dmesg to find > failed sector. I ran a long test after I found this SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 27220 - >> >> >> # smartctl -x /dev/sda >> >> Error 2 [1] occurred at disk power-on lifetime: 27064 hours (1127 days + >> 16 hours) >> When the command that caused the error occurred, the device was active >> or idle. >> >> After command completion occurred, registers were: >> ER -- ST COUNT LBA_48 LH LM LL DV DC >> -- -- -- == -- == == == -- -- -- -- -- >> 40 -- 51 00 08 00 4d 92 00 86 49 e0 00 Error: UNC 8 sectors at LBA = >> 0x4d92008649 = 333161989705 >> >> Commands leading to the command that caused the error were: >> CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time >> Command/Feature_Name >> -- == -- == -- == == == -- -- -- -- -- --------------- >> -------------------- >> 25 00 00 00 08 00 4d 92 00 86 49 e0 08 39d+22:53:19.132 READ DMA EXT >> ca 00 00 00 08 00 01 cd 00 2f b2 e1 08 39d+22:53:19.132 WRITE DMA >> ea 00 00 00 00 00 01 cd 00 2f b1 e0 08 39d+22:53:19.092 FLUSH CACHE >> EXT >> ca 00 00 00 10 00 01 cd 00 2f a2 e1 08 39d+22:53:19.092 WRITE DMA >> ca 00 00 00 08 00 01 83 00 a8 d2 e1 08 39d+22:53:19.091 WRITE DMA >> >> Error 1 [0] occurred at disk power-on lifetime: 27064 hours (1127 days + >> 16 hours) >> When the command that caused the error occurred, the device was active >> or idle. >> >> After command completion occurred, registers were: >> ER -- ST COUNT LBA_48 LH LM LL DV DC >> -- -- -- == -- == == == -- -- -- -- -- >> 40 -- 51 01 a0 00 4d 90 00 86 f1 e0 00 Error: UNC 416 sectors at LBA >> = 0x4d900086f1 = 333128435441 >> >> Commands leading to the command that caused the error were: >> CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time >> Command/Feature_Name >> -- == -- == -- == == == -- -- -- -- -- --------------- >> -------------------- >> 25 00 00 01 a0 00 4d 90 00 86 f1 e0 08 39d+22:53:01.661 READ DMA EXT >> 35 00 00 00 10 00 4d 90 00 83 99 e0 08 39d+22:53:01.661 WRITE DMA EXT >> 35 00 00 00 08 00 17 97 00 ff 19 e0 08 39d+22:53:01.661 WRITE DMA EXT >> 35 00 00 00 08 00 51 90 00 d3 a1 e0 08 39d+22:53:01.660 WRITE DMA EXT >> ea 00 00 00 00 00 4c 90 00 e3 e8 e0 08 39d+22:53:01.620 FLUSH CACHE >> EXT >> > -- |
From: Christian F. <Chr...@t-...> - 2012-11-17 19:00:07
|
lxn...@gm... wrote: > On Sat, 17 Nov 2012, Alex Samorukov wrote: > >> On 11/17/2012 04:35 PM, lxn...@gm... wrote: >>> Please point me straight >>> I have a drive showing 2 bad blocks >>> I want to find the files associated with these blocks >>> I have read "Bad block HOWTO for smartmontools" but am still confused >>> The first lba 333161989705 is greater than 1465144064 >>> >> I had similar problem. My workaround was to run long test and get correct >> sector number from the -l selftest. Also you could look on dmesg to find >> failed sector. > I ran a long test after I found this > > SMART Extended Self-test Log Version: 1 (1 sectors) > Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error > # 1 Extended offline Completed without error 00% 27220 > - Then the reported errors were transient or the bad blocks have been reallocated. |
From: <lxn...@gm...> - 2012-11-17 19:04:18
|
On Sat, 17 Nov 2012, Christian Franke wrote: > lxn...@gm... wrote: >> On Sat, 17 Nov 2012, Alex Samorukov wrote: >> >> > On 11/17/2012 04:35 PM, lxn...@gm... wrote: >> > > Please point me straight >> > > I have a drive showing 2 bad blocks >> > > I want to find the files associated with these blocks >> > > I have read "Bad block HOWTO for smartmontools" but am still >> > > confused >> > > The first lba 333161989705 is greater than 1465144064 >> > > >> > I had similar problem. My workaround was to run long test and get >> > correct >> > sector number from the -l selftest. Also you could look on dmesg to find >> > failed sector. >> I ran a long test after I found this >> >> SMART Extended Self-test Log Version: 1 (1 sectors) >> Num Test_Description Status Remaining >> LifeTime(hours) LBA_of_first_error >> # 1 Extended offline Completed without error 00% 27220 >> - > > Then the reported errors were transient or the bad blocks have been > reallocated. > > I still show 2 current pending sectors Should I ignore this I had hoped to find the affected files Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-K 200 200 051 - 0 3 Spin_Up_Time POS--K 104 103 021 - 7783 4 Start_Stop_Count -O--CK 100 100 000 - 41 5 Reallocated_Sector_Ct PO--CK 200 200 140 - 0 7 Seek_Error_Rate -OSR-K 100 253 000 - 0 9 Power_On_Hours -O--CK 063 063 000 - 27249 10 Spin_Retry_Count -O--CK 100 253 000 - 0 11 Calibration_Retry_Count -O--CK 100 253 000 - 0 12 Power_Cycle_Count -O--CK 100 100 000 - 39 192 Power-Off_Retract_Count -O--CK 200 200 000 - 18 193 Load_Cycle_Count -O--CK 001 001 000 - 2619243 194 Temperature_Celsius -O---K 109 096 000 - 38 196 Reallocated_Event_Count -O--CK 200 200 000 - 0 197 Current_Pending_Sector -O--CK 200 200 000 - 2 198 Offline_Uncorrectable ----CK 200 200 000 - 0 199 UDMA_CRC_Error_Count -O--CK 200 200 000 - 0 200 Multi_Zone_Error_Rate ---R-- 200 165 000 - 0 |
From: Christian F. <Chr...@t-...> - 2012-11-18 20:56:11
|
lxn...@gm... wrote: > On Sat, 17 Nov 2012, Christian Franke wrote: > >> lxn...@gm... wrote: >>> >>> I ran a long test after I found this >>> >>> SMART Extended Self-test Log Version: 1 (1 sectors) >>> Num Test_Description Status Remaining >>> LifeTime(hours) LBA_of_first_error >>> # 1 Extended offline Completed without error 00% 27220 >>> - >> Then the reported errors were transient or the bad blocks have been >> reallocated. >> >> > I still show 2 current pending sectors Pending sectors count may not be reset until the recorded sectors are written. > Should I ignore this Yes, if no further messages appear. The last error message is ~200 hours old. Thanks, Christian |