From owner-freebsd-hardware Fri Apr 21 21:51:50 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from web107.yahoomail.com (web107.yahoomail.com [205.180.60.74]) by hub.freebsd.org (Postfix) with SMTP id B785337B8F0 for ; Fri, 21 Apr 2000 21:51:38 -0700 (PDT) (envelope-from eaglez69@yahoo.com) Received: (qmail 14861 invoked by uid 60001); 22 Apr 2000 04:51:38 -0000 Message-ID: <20000422045138.14860.qmail@web107.yahoomail.com> Received: from [130.65.210.24] by web107.yahoomail.com; Fri, 21 Apr 2000 21:51:38 PDT Date: Fri, 21 Apr 2000 21:51:38 -0700 (PDT) From: Eaglez Subject: Re: Write errors on UDMA drives To: AG Cc: freebsd-hardware@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org No offense, but I think that's because they're >Maxtor< drives. Those are notoriously stupid. They even tried to sell a bootloader with some of their old ones, that would put a new format on the disk, and make it so nothing could read it. I think this is something like how a lot of 100baseTX cards can't really do full 100baseTX. Like maybe not enough buffer. I couldn't say for sure. The point is, Maxtor is somewhat low-end (they're cheep for a reason), and if you're going to be doing massive reads/writes, i'd advise saving up for something slightly better. (I've had NO problems with IBM drives...) -Jesse --- AG wrote: > > > ---------- Forwarded message ---------- > Date: Sat, 22 Apr 2000 05:13:10 -0400 (EDT) > From: AG > To: freebsd-questions@freebsd.org > Subject: Write errors on UDMA drives > > Hello, > > I am running FreeBSD 4.0 with two UDMA drives. One > is a 8 gig Maxtor > running at UDMA/33 and the other is a 40 gig Maxtor > running at > UDMA/66. When I try to do large writes to either > drive, gunzip'ing a large > file, sorting a large file, or any other type of > intensive writing to the > drive, I get the following errors repeatedly: > > Apr 22 05:02:40 37 /kernel: ad0: UDMA ICRC WRITE > ERROR blk# 13597744 > retrying > > On the 8 gig drive, this will continue without any > real effects, but on > the 40 gig drive, it will go so far as to > halt/reboot my machine. The > blk# changes, and it appears to be a worse condition > on the 40 gig, > rather then the 8 gig. I have checked dmesg, and > there doesn't appear to > be any IRQ conflicts. Has anyone else run across > this, or possibly know > what is going on? Any help will be appreciated. > > Thanks, > > AG > > p.s. I am also getting this error occasionaly: > > Apr 22 10:05:55 37 /kernel: invalid state: 0x1 > Apr 22 10:05:56 37 /kernel: invalid state: 0x1 > > I'm not sure this relates, but I thought I would > just include it anyways. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of > the message > __________________________________________________ Do You Yahoo!? Send online invitations with Yahoo! Invites. http://invites.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message