Date: Sat, 8 Sep 2001 08:54:53 -0400 (EDT) From: Erik Rothwell <erothwell@callgtn.com> To: ian j hart <ianjhart@ntlworld.com> Cc: Erik Rothwell <erothwell@callgtn.com>, <freebsd-stable@FreeBSD.ORG> Subject: Re: ad2s1e: UDMA ICRC error reading fsbn... Message-ID: <20010908084943.J35840-100000@endymion> In-Reply-To: <3B6F2974.98C2D37B@ntlworld.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 7 Aug 2001, ian j hart wrote: > Erik Rothwell wrote: > > > > On Sun, 5 Aug 2001, Carl Drougge wrote: > > > > > I would say the cable. Or using UDMA66/UDMA100 on a 40 pin cable. > > > (ICRC should be the CRC of the tranfer, if I guess correctly, which means > > > the disk transfered the data correctly, but it didn't reach the controller > > > correctly. Try forcing it to use a slower mode (not that I know how..).) > > > > The disk _appears_ to work correctly in PIO4 mode... but 16MB/s isn't > > anything to scream about. I was using an 80-conductor, 40-pin cable on my > > bootdisk (ad0, 20GB), but, I switched the cables originally so that the > > ATA66/100 cable is on the 40GB drive. > > > > Everything works beautifully in PIO4, but, that's sort of a hollow victory > > considering how slow that works... and, what's strange is that even with > > the plethora of errors I reported-- the read/writes still complete & the > > data is all there. > > > > Is there any way to rule out if it is the disk or the software? My BIOS is > > set to LBA mode, UDMA is enabled for ata1-master there (if it matters)... > Sorry for the late follow-up... I got this working a while back but I've been away. > Did you try the Seagate UATA100.EXE tool yet? > > -- > ian j hart Yes: It seems if I sent the mode down to UDMA/33, the errors disappeared. UDMA/66 would generate errors on the secondary chain. However, I moved the drive from the secondary chain to the primary, set the drive down to UDMA/66 (100 isn't supported by my controller) and everything was fine. The drive is set to UDMA/100 by default, which still produces read errors on either controller (which doesn't surprise me)... so, in any event... all's working now :) Thanks for your help everyone. Erik. -- E. L. Rothwell PGP Public Key at http://www.keyserver.net/ 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?20010908084943.J35840-100000>