ad0 errors on 6.0-RC1

Mike Tancsa mike at sentex.net
Wed Oct 12 20:09:33 PDT 2005


At 10:55 PM 12/10/2005, Dan Langille wrote:

>We did that yesterday.  I don't know enough about the output to
>judge, but it seems ok.  Also posted to http://pastebin.com/391872
>
>   Commands leading to the command that caused the error were:
>   CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
>   -- -- -- -- -- -- -- --  ----------------  --------------------
>   c8 00 37 38 1f a2 e0 08      00:06:15.120  READ DMA
>   c8 00 09 2f 1f a2 e0 08      00:06:15.120  READ DMA
>   c8 00 36 f9 1e a2 e0 08      00:06:15.120  READ DMA
>   c8 00 0a ef 1e a2 e0 08      00:06:15.120  READ DMA
>   c8 00 35 ba 1e a2 e0 08      00:06:15.120  READ DMA
>
>Error 3 occurred at disk power-on lifetime: 3332 hours (138 days + 20
>hours)
>   When the command that caused the error occurred, the device was in
>an unknown state.
>
>   After command completion occurred, registers were:
>   ER ST SC SN CL CH DH
>   -- -- -- -- -- -- --
>   84 51 00 ba 1e a2 e0  Error: ICRC, ABRT at LBA = 0x00a21eba =
>10624698
>
>   Commands leading to the command that caused the error were:
>   CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
>   -- -- -- -- -- -- -- --  ----------------  --------------------
>   c8 00 35 ba 1e a2 e0 08      00:06:15.056  READ DMA
>   c8 00 0b af 1e a2 e0 08      00:06:15.056  READ DMA
>   c8 00 34 7b 1e a2 e0 08      00:06:15.056  READ DMA
>   c8 00 0c 6f 1e a2 e0 08      00:06:15.056  READ DMA
>   c8 00 02 6f 1e a2 e0 08      00:06:15.056  READ DMA

I think the drive itself is seeing the errors as well.  Watch some of 
the counters and see how they increment over time.  Run smartd, and 
it will record it in real time as well and log it for you.

         ---Mike 



More information about the freebsd-current mailing list