Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 08 Sep 2001 19:55:05 +0100
From:      ian j hart <ianjhart@ntlworld.com>
To:        Dave Uhring <duhring@charter.net>
Cc:        "stable@FreeBSD.ORG" <stable@FreeBSD.ORG>
Subject:   Re: UDMA ICRC error reading fsb (?)
Message-ID:  <3B9A6989.1715D8DC@ntlworld.com>
References:  <20010906204356.A4116@nc.rr.com> <auto-000013329585@dc-mx03.cluster1.charter.net> <3B9A1DF4.1FEC670B@ntlworld.com> <auto-000026431550@dc-mx08.cluster1.charter.net>

next in thread | previous in thread | raw e-mail | index | archive | help
Dave Uhring wrote:
> 
> On Saturday 08 September 2001 08:32 am, ian j hart wrote:
> > Dave Uhring wrote:
> > > On Friday 07 September 2001 11:48 pm, Marius Strom wrote:
> > > > FWIW, I had this error and assumed it was cabling.  I've spent
> > > > the last few hours copying data of what is now a dead disk and
> > > > putting it back on a new disk.  YMMV.
> > > >
> > > > On Fri, Sep 07, 2001 at 11:45:28PM +0100, ian j hart wrote:
> > > > > Dave Uhring wrote:
> > > > > > On Friday 07 September 2001 17:04, Randall Hopper wrote:
> > > > > > > Dave Uhring:
> > > > > > >  |On Thursday 06 September 2001 07:43 pm, Randall Hopper
> wrote:
> > > > > > >  |>      What do these messages mean?  Are CRCs done by the
> > > > > > >  |> IDE controller on DMA transfers and they're coming up
> > > > > > >  |> wrong?
> > > > > > >  |>
> > > > > > >  |> ad0s2a: UDMA ICRC error writing fsbn 3283483 of
> > > > > > >  |> 396704-396713 (ad0s2 bn 3283483; cn 204 tn 98 sn 49)
> > > > > > >  |> retrying
> > > > > > >  |
> > > > > > >  |Your drive is dying.  Back it up and replace it.
> > > > >
> > > > > I think you are being a tad premature.
> > > > >
> > > > > There have been plenty of posts on this subject, both on stable
> > > > > and hardware. IIRC none of them were bad disks.
> > > > >
> > > > > Randall,
> > > > > 1) post a copy of dmesg so we can see what hardware you have.
> > > > > 2) measure the cable - M/B to drive.
> > > > >
> > > > > > > Ok, thanks.  But what do these messages "mean" on a
> > > > > > > technical level?
> > > > > > >
> > > > > > > And could these just as well indicate a marginal cable, bad
> > > > > > > connector, loose connector, or the other hard drive on the
> > > > > > > controller being a bit flakey?
> > > > > > >
> > > > > > > Randall
> > > > > >
> > > > > > CRC's (16 bit cyclic redundancy check characters) have been
> > > > > > done on controllers since we had to use floppies.  The first
> > > > > > Winchester drive interface I ever designed back in 1979 had a
> > > > > > Fairchild 9401 (IIRC) CRC generator chip on it.  The writes
> > > > > > are failing.  You "may" have marginal cabling or loose or
> > > > > > corroded connectors.
> > > > > >
> > > > > > If you wish to keep using the drive, replace the cable and in
> > > > > > doing so your contacts will also wipe clean.
> > > > >
> > > > > --
> > > > > ian j hart
> > >
> > > IDE cables which are somewhat too long can cause many problems with
> > > data transfer.  However, the cable certainly didn't grow in length
> > > overnight.
> >
> > It's a new disk, which may be the problem as some hardware
> > combinations have problems. It's also possible the cable was replaced
> > at the same time.
> > I found the problem was load related (at least at first). Maybe the
> > system is now under a heavier load.
> >
> > >Sudden onset of the described problems "may" be due to
> > > corrosion of the cable contacts, but it is most likely due to a
> > > drive failure.  Most modern drives support S.M.A.R.T. and it would
> > > be nice if FreeBSD had a utility to detect the drive's complaints.
> > > Perhaps it is in the ports, but my weak eyes have failed to see it.
> >
> > "most likely": Would your opinion change if it turns out to be a VIA
> > chipset M/B?
> >
> > See also the Lazarus like Re: ad2s1e: UDMA ICRC error reading fsbn...
> 
> "most likely"? No, I use one myself (MSI K7T Pro2 A) with no problems
> whatsoever.  Both IDE drives are IBM-DTLA.  But I don't use a SB Live,
> either ;)

IIRC that's an 82C686 - different bug to the 82C586B.
There seems to be a reluctance to provide dmesg output, which doesn't
help.

Off on a tangent here - does tagged queuing work?

-- 
ian j hart

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3B9A6989.1715D8DC>