Re: smartctl test error

[Kevin Ross <kevin@familyross.net>]

 On 8/17/2010 10:26 PM, vishnuvardhan wrote:
> *I have run the following command and it is showing the following 
> error for all the disks [ hda, hda1, hda2, hda5 ]* :
> # smartctl -l selftest /dev/hda
>
> === 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  Short offline       Completed without error       00%     
> 15730         -
> # 2  Extended offline    Aborted by host               90%     
> 11081         -
> # 3  Short offline       Completed without error       00%     
> 11080         -

That isn't showing an "error" as you say.  It's showing the result of 
the last few self-tests.

> *And when I run the following command nothing happens and I did check 
> syslog for message. Do I have to look elsewhere ?*
>
> # smartctl -t short /dev/hda

Run the command you gave above to see the results.

> *The output of my hard drive #  smartctl -a /dev/hda :*
>
> <trim>
> 196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   
> Always       -       132

A reallocated event count of 132 doesn't look good.

> SMART Error Log Version: 1
> ATA Error Count: 191 (device log contains only the most recent five 
> errors)
>     CR = Command Register [HEX]
>     FR = Features Register [HEX]
>     SC = Sector Count Register [HEX]
>     SN = Sector Number Register [HEX]
>     CL = Cylinder Low Register [HEX]
>     CH = Cylinder High Register [HEX]
>     DH = Device/Head Register [HEX]
>     DC = Device Command Register [HEX]
>     ER = Error register [HEX]
>     ST = Status register [HEX]
> Powered_Up_Time is measured from power on, and printed as
> DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
> SS=sec, and sss=millisec. It "wraps" after 49.710 days.
>
> Error 191 occurred at disk power-on lifetime: 10995 hours (458 days + 
> 3 hours)
>   When the command that caused the error occurred, the device was 
> active or idle.
>
>   After command completion occurred, registers were:
>   ER ST SC SN CL CH DH
>   -- -- -- -- -- -- --
>   40 51 01 59 bf 7f e0  Error: UNC at LBA = 0x007fbf59 = 8372057
>
>   Commands leading to the command that caused the error were:
>   CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
>   -- -- -- -- -- -- -- --  ----------------  --------------------
>   40 00 01 59 bf 7f e0 00      00:09:22.600  READ VERIFY SECTOR(S)
>   c8 00 01 d0 98 86 e1 00      00:09:22.600  READ DMA
>   40 00 02 59 bf 7f e0 00      00:09:18.500  READ VERIFY SECTOR(S)
>   c8 00 01 70 7b e6 e0 00      00:09:18.500  READ DMA
>   40 00 02 57 bf 7f e0 00      00:09:18.500  READ VERIFY SECTOR(S)
>
> Error 190 occurred at disk power-on lifetime: 10995 hours (458 days + 
> 3 hours)
>   When the command that caused the error occurred, the device was 
> active or idle.
>
>   After command completion occurred, registers were:
>   ER ST SC SN CL CH DH
>   -- -- -- -- -- -- --
>   40 51 02 59 bf 7f e0  Error: UNC at LBA = 0x007fbf59 = 8372057
>
>   Commands leading to the command that caused the error were:
>   CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
>   -- -- -- -- -- -- -- --  ----------------  --------------------
>   40 00 02 59 bf 7f e0 00      00:09:18.500  READ VERIFY SECTOR(S)
>   c8 00 01 70 7b e6 e0 00      00:09:18.500  READ DMA
>   40 00 02 57 bf 7f e0 00      00:09:18.500  READ VERIFY SECTOR(S)
>   c8 00 01 00 00 00 e0 00      00:09:18.500  READ DMA
>   40 00 04 5b bf 7f e0 00      00:09:18.500  READ VERIFY SECTOR(S)
>
> Error 189 occurred at disk power-on lifetime: 10995 hours (458 days + 
> 3 hours)
>   When the command that caused the error occurred, the device was 
> active or idle.
>
>   After command completion occurred, registers were:
>   ER ST SC SN CL CH DH
>   -- -- -- -- -- -- --
>   40 51 02 59 bf 7f e0  Error: UNC at LBA = 0x007fbf59 = 8372057
>
>   Commands leading to the command that caused the error were:
>   CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
>   -- -- -- -- -- -- -- --  ----------------  --------------------
>   40 00 04 57 bf 7f e0 00      00:09:14.300  READ VERIFY SECTOR(S)
>   c8 00 01 00 00 00 e0 00      00:09:14.300  READ DMA
>   40 00 08 57 bf 7f e0 00      00:09:10.200  READ VERIFY SECTOR(S)
>   c8 00 01 d0 98 86 e1 00      00:09:10.200  READ DMA
>   40 00 08 4f bf 7f e0 00      00:09:10.200  READ VERIFY SECTOR(S)
>
> Error 188 occurred at disk power-on lifetime: 10995 hours (458 days + 
> 3 hours)
>   When the command that caused the error occurred, the device was 
> active or idle.
>
>   After command completion occurred, registers were:
>   ER ST SC SN CL CH DH
>   -- -- -- -- -- -- --
>   40 51 06 59 bf 7f e0  Error: UNC at LBA = 0x007fbf59 = 8372057
>
>   Commands leading to the command that caused the error were:
>   CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
>   -- -- -- -- -- -- -- --  ----------------  --------------------
>   40 00 08 57 bf 7f e0 00      00:09:10.200  READ VERIFY SECTOR(S)
>   c8 00 01 d0 98 86 e1 00      00:09:10.200  READ DMA
>   40 00 08 4f bf 7f e0 00      00:09:10.200  READ VERIFY SECTOR(S)
>   c8 00 01 70 7b e6 e0 00      00:09:10.200  READ DMA
>   40 00 10 4f bf 7f e0 00      00:09:06.000  READ VERIFY SECTOR(S)
>
> Error 187 occurred at disk power-on lifetime: 10995 hours (458 days + 
> 3 hours)
>   When the command that caused the error occurred, the device was 
> active or idle.
>
>   After command completion occurred, registers were:
>   ER ST SC SN CL CH DH
>   -- -- -- -- -- -- --
>   40 51 06 59 bf 7f e0  Error: UNC at LBA = 0x007fbf59 = 8372057
>
>   Commands leading to the command that caused the error were:
>   CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
>   -- -- -- -- -- -- -- --  ----------------  --------------------
>   40 00 10 4f bf 7f e0 00      00:09:06.000  READ VERIFY SECTOR(S)
>   c8 00 01 00 00 00 e0 00      00:09:06.000  READ DMA
>   40 00 10 3f bf 7f e0 00      00:09:06.000  READ VERIFY SECTOR(S)
>   c8 00 01 00 00 00 e0 00      00:09:06.000  READ DMA
>   40 00 20 5f bf 7f e0 00      00:09:06.000  READ VERIFY SECTOR(S)

This is showing a sector that it couldn't correct the errors on, and 
would have been reported back to the operating system as an I/O error.

You've never completed an extended offline test, try "smartctl -t long 
/dev/hda", and check the results after 30 minutes with "smartctl -a 
/dev/hda".  At the beginning of the output, you can see if the test has 
completed yet next to the "Self-test execution status" field.  After the 
test completes, the results will be near the end of the output, under 
"SMART Self-test log".**