From owner-freebsd-hackers Wed Oct 18 8: 2:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sydney.worldwide.lemis.com (termroom.bsdcon.org [206.55.247.2]) by hub.freebsd.org (Postfix) with ESMTP id 0FC0E37B479 for ; Wed, 18 Oct 2000 08:02:08 -0700 (PDT) Received: (from grog@localhost) by sydney.worldwide.lemis.com (8.11.0/8.9.3) id e9I3IjB01467; Tue, 17 Oct 2000 20:18:45 -0700 (PDT) (envelope-from grog) Date: Tue, 17 Oct 2000 20:18:45 -0700 From: Greg Lehey To: Frank Nobis Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: UDMA ICRC WRITE ERROR Message-ID: <20001017201845.E1250@sydney.worldwide.lemis.com> References: <20001015135815.A5133@radio-do.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20001015135815.A5133@radio-do.de>; from fn@radio-do.de on Sun, Oct 15, 2000 at 01:58:15PM +0200 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday, 15 October 2000 at 13:58:15 +0200, Frank Nobis wrote: > Hi, > > I have a IDE drive spitting out this messages: > > ad3: UDMA ICRC WRITE ERROR blk# 48562489 retrying > ad3: UDMA ICRC READ ERROR blk# 24576329 retrying > ad3: UDMA ICRC WRITE ERROR blk# 69108025 retrying > ad3: UDMA ICRC WRITE ERROR blk# 73728313 retrying Is this always the same drive? >> From the boot messages: > > atapci0: port 0xd800-0xd80f at device 4.1 on pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > ad0: 8063MB [16383/16/63] at ata0-master using UDMA33 > ad1: 42934MB [87233/16/63] at ata0-slave using UDMA33 > ad2: 42934MB [87233/16/63] at ata1-master using UDMA33 > ad3: 42934MB [87233/16/63] at ata1-slave using UDMA33 > > Do I have to exchange the drive ? I think I should. You could try setting PIO mode first. > In the case of replacing is the best thing to do, that leads to the > question, how to replace this drive ? Shut the machine down. Replace drive, making sure the jumpers are set correctly. Reboot. > It is a part of a vinum raid5 volume. Is detach and attach the > right way ? No. Take a look at the description on http://www.vinumvm.org/. Sorry, I don't know the exact URL, and I'm currently off the net. One thing that occurs to me is that I suspect you're using ad[123] as your RAID-5 drive. That's seriously sub-optimal for performance, but it also means that ad2 and ad3 will frequently have transfers outstanding at the same time. That might be the real issue; you might find that if you swap ad1 and ad3 (which you can do without losing data on the volume), you will continue having problems with the new ad3. > PS. If someone want more information about the System (PRESMPNG) > dual PIII on an ASUS P2B-DS, just let me know. I want avoid spamming > the list with big config and dmesg output Right, we don't need them. Read http://www.vinumvm.org/how-to-debug.html for details regarding Vinum Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message