From owner-freebsd-hackers Sat Sep 15 4: 3:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gatekeeper.radio-do.de (gatekeeper.Radio-do.de [193.101.164.1]) by hub.freebsd.org (Postfix) with ESMTP id E7D9C37B409 for ; Sat, 15 Sep 2001 04:03:16 -0700 (PDT) Received: from ibook (ibook.Radio-do.de [193.101.164.23]) by gatekeeper.radio-do.de (Postfix) with ESMTP id E225A16F96; Sat, 15 Sep 2001 13:03:00 +0200 (CEST) Date: Sat, 15 Sep 2001 13:03:00 +0200 From: Frank Nobis Content-Type: text/plain; format=flowed; charset=us-ascii Subject: Re: PIO mode Cc: "Dan" , To: "Stephen Hurd" X-Mailer: Apple Mail (2.388) In-Reply-To: Mime-Version: 1.0 (Apple Message framework v388) Content-Transfer-Encoding: 7bit Message-Id: <20010915110300.E225A16F96@gatekeeper.radio-do.de> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Am Samstag, 15. September 2001 um 07:33 schrieb Stephen Hurd: >> ad0s1a: UDMA ICRC error reading fsbn 191 of 64-79 (ad0s1 bn 191; cn 0 tn >> 3 >> sn 2) retrying > > Actually, the ICRC error IS a bit frigtening... I always got read timeouts > when it was a bad HD/controller combo... I'd like to revise my opinion to > say > "Get your data off now while you still can!" But maybe dig through the ata > source... there's probobly helpful comments in that bit. > I had those problems once with a HPT370 controller. The problem was at last bad cable. After trying three different 80 wire types I had success. I had no more ICRC errors since then. Frank -- Frank Nobis Landgrafenstr. 130 44139 Dortmund To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message