Too many uncorrectable read errors with atang
martines at rochester.rr.com
Fri Nov 7 12:07:49 PST 2003
If you are running -CURRENT, you can check the SMART status of the
drives with the port sysutils/smartmontools. If the drive supports >
ATA-3 commands, you should be able to see if there are errors being
reported by the drive itself.
On Fri, 2003-11-07 at 13:33, Soren Schmidt wrote:
> It seems Kris Kennaway wrote:
> -- Start of PGP signed section.
> > Since upgrading the bento package machines to -current I am getting
> > a lot of the following errors:
> > ad0: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=40<UNCORRECTABLE>
> That does look like a valid error condition from the drive...
> > 1) All my drives have performed mass suicide at once
> You know, with deathstar's you cant really rule that out :)
> > 2) ATAng is detecting errors that the ATAog did not
> That is true, the error detection is better in ATAng.
> > 3) ATAng is not trying as hard as ATAog to recover from the errors
> > from the crappy drives
> Neither ATAog nor ATAnr retried uncorrectable errors...
> > 4) ATAng has a bug on this hardware.
> That we cant rule out, and it probably likely..
> > Furthermore, I'd like to know why the panic occurred above.
> Is this on a brand new -current ? lots of things that could
> cause this has been fixed...
> freebsd-current at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
Eduard Martinescu <martines at rochester.rr.com>
More information about the freebsd-current