From owner-freebsd-current Wed May 23 6:37:56 2001 Delivered-To: freebsd-current@freebsd.org Received: from enigma.whacky.net (enigma.whacky.net [194.109.204.120]) by hub.freebsd.org (Postfix) with ESMTP id 2777137B424 for ; Wed, 23 May 2001 06:37:45 -0700 (PDT) (envelope-from stephanb@whacky.net) Received: (from root@localhost) by enigma.whacky.net (8.11.3/8.11.3) id f4NDbqT01315 for current@freebsd.org; Wed, 23 May 2001 15:37:52 +0200 (CEST) (envelope-from stephanb) Received: (from stephanb@localhost) by enigma.whacky.net (8.11.3/8.11.3) id f4NDbnD01307 for current@freebsd.org; Wed, 23 May 2001 15:37:49 +0200 (CEST) (envelope-from stephanb) Date: Wed, 23 May 2001 15:37:49 +0200 From: Stephan van Beerschoten To: current@freebsd.org Subject: harddisk faillure or kernel problem ? Message-ID: <20010523153749.A1257@enigma.whacky.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Virus-Scanned: by enigma.whacky.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG For a while now I keep having the following logentries in my messages file: May 23 13:59:40 enigma /kernel: ad0s1a: UDMA ICRC error reading fsbn 1704031 of 720912-720913 (ad0s1 bn 17040 31; cn 1803 tn 3 sn 7) retrying May 23 13:59:40 enigma /kernel: ad0s1a: UDMA ICRC error reading fsbn 2857979 of 1297886-1297887 (ad0s1 bn 285 7979; cn 3024 tn 4 sn 47) retrying May 23 13:59:40 enigma /kernel: ad0s1a: UDMA ICRC error reading fsbn 3689535 of 1713664-1713677 (ad0s1 bn 368 9535; cn 3904 tn 4 sn 3) retrying May 23 13:59:40 enigma /kernel: ad0s1a: UDMA ICRC error reading fsbn 4198463 of 1968128-1968129 (ad0s1 bn 419 8463; cn 4442 tn 12 sn 17) retrying May 23 13:59:40 enigma /kernel: ad0s1a: UDMA ICRC error reading fsbn 4607039 of 2172416-2172419 (ad0s1 bn 460 7039; cn 4875 tn 2 sn 38) retrying Is this because of some UDMA option in my kernel that I have or may have missed, or is this really hardware ? I've had this for months now and never actually bothered because it never gave me any problems, at least not noticable ones. I use the machine remotely mainly, so harddisk speeds that may have dropped because of this are hardly noticable if you're just doing commandline work. Diagnoses: Do I need to replace hardware here, or not ? FreeBSD xxxx.xx.xxx.xx.xx 4.3-STABLE FreeBSD 4.3-STABLE #3: Tue May 15 20:23:48 CEST 2001 root@xxxx.xx.xxx.xx.xx:/usr/obj/usr/src/sys/ENIGMA i386 Thanks, Stephan -- Stephan van Beerschoten [SVB21-RIPE] stephanb@whacky.net PGP fingerprint: 4557 9761 B212 FB4C 778D 3529 C42A 2D27 "To err is human, to forgive is Not Company Policy" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message