Re: ad0 errors on 6.0-RC1

From: Mike Tancsa (mike_at_sentex.net)
Date: 10/13/05

  • Next message: Bjoern A. Zeeb: "Re: NO_TOOLCHAIN broken in -current ?"
    Date: Wed, 12 Oct 2005 23:09:46 -0400
    To: "Dan Langille" <dan@langille.org>
    
    

    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

    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"


  • Next message: Bjoern A. Zeeb: "Re: NO_TOOLCHAIN broken in -current ?"

    Relevant Pages

    • Re: Problem with WSH Shell Exec StdOut
      ... catch its StdOut stream in real time. ... then almost immediately I get a command window displaying the following: ... You have to abort the script by ending the ...
      (microsoft.public.scripting.vbscript)
    • Re: Problem with WSH Shell Exec StdOut
      ... catch its StdOut stream in real time. ... NeroCmd.exe is a command line utility included ... Here is the script I'm currently using: ...
      (microsoft.public.scripting.vbscript)
    • Re: Problem with WSH Shell Exec StdOut
      ... catch its StdOut stream in real time. ... then almost immediately I get a command window displaying the following: ... Here is the script I'm currently using: ...
      (microsoft.public.scripting.vbscript)
    • Re: need help, will pay
      ... Windows XP, willing to pay $100 for the solution. ... output of command is sent back to browser in real time (this is ...
      (comp.lang.perl.misc)
    • Problem with WSH Shell Exec StdOut
      ... I'm trying to Use WSH Shell Exec to run a 'command line' program and catch ... The batch file runs differently if Shell Exec'ed. ... and to read and display the exec method's StdOut stream in real ... this indicates that I am not getting StdOut in real time; ...
      (microsoft.public.scripting.vbscript)