From owner-freebsd-questions Sat Nov 17 12: 2: 5 2001 Delivered-To: freebsd-questions@freebsd.org Received: from mcqueen.wolfsburg.de (pns.wobline.de [212.68.68.5]) by hub.freebsd.org (Postfix) with ESMTP id 3685737B419 for ; Sat, 17 Nov 2001 12:02:02 -0800 (PST) Received: from colt.ncptiddische.net (ppp-158.wobline.de [212.68.69.166]) by mcqueen.wolfsburg.de (8.11.3/8.11.3/tw-20010821) with ESMTP id fAHK1rO30762; Sat, 17 Nov 2001 21:01:53 +0100 Received: from jodie.ncptiddische.net (jodie.ncptiddische.net [192.168.0.2]) by colt.ncptiddische.net (8.11.6/8.11.6) with ESMTP id fAHK2Jt07684; Sat, 17 Nov 2001 21:02:19 +0100 (CET) (envelope-from nils@tisys.org) Received: from jodie.ncptiddische.net (jodie.ncptiddische.net [192.168.0.2]) by jodie.ncptiddische.net (8.11.6/8.11.6) with ESMTP id fAHK2dg37940; Sat, 17 Nov 2001 21:02:39 +0100 (CET) (envelope-from nils@tisys.org) Date: Sat, 17 Nov 2001 21:02:39 +0100 (CET) From: Nils Holland To: David Loszewski Cc: freebsd-questions@FreeBSD.ORG Subject: Re: harddrive error In-Reply-To: <001401c16f9f$d6311a70$3000a8c0@sickness> Message-ID: <20011117205613.R37932-100000@jodie.ncptiddische.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 17 Nov 2001, David Loszewski wrote: > Does this error mean that my harddrive is going? Or just that it has a > few bad sectors? What can I do to fix it? > > Nov 17 15:35:55 suicidal /kernel: ad0s1a: UDMA ICRC error writing fsbn > 1183935 of 67648-67659 (ad0s1 bn 1183935 > ; cn 73 tn 177 sn 39) retrying This *could* mean that your data gets currupted while it tavels from your HD to your computer. Most likely cause: A problem with your IDE cable. Are you using a 80-pin cable? For UDMA66 and up, this is neccessary. Also, there's only one drive formally allowed to operate in UDMA66 (or 100) mode on any given cable (although I have heard about cases where two devices actually worked). Keep in mind that this is just my guess. It could well also be a fault with your HDD itself. The easiest way to find out if this is the case is to try your HDD with a different cable, and if that fails, in a different machine (or at least with a different mainboard). If your drive still produces these errors in a different machine using a different IDE cable, it looks as if your drive has a serious problem. If that is the case, backup your data as far as possible, and get a new drive (or send your current drive in for warranty service, if still applicable). Greetings Nils Nils Holland Ti Systems - FreeBSD in Tiddische, Germany http://www.tisys.org * nils@tisys.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message