From owner-freebsd-questions Sat May 13 6:16:50 2000 Delivered-To: freebsd-questions@freebsd.org Received: from reftech.refnet.co.uk (reftech.refnet.co.uk [195.74.101.39]) by hub.freebsd.org (Postfix) with ESMTP id 0289137BE13 for ; Sat, 13 May 2000 06:16:37 -0700 (PDT) (envelope-from simon@reftech.co.uk) Received: from reftech.co.uk (smtp.ref000000.enta.net [195.74.117.157]) by reftech.refnet.co.uk (8.9.3/8.9.1) with ESMTP id OAA22664 for ; Sat, 13 May 2000 14:16:33 +0100 (BST) (envelope-from simon@reftech.co.uk) Received: from vaio [10.0.0.35] by reftech.co.uk (FTGate 2, 2, 0, 1); Sat, 13 May 00 14:13:26 +0100 From: "Simon Clayton" To: Subject: ATA66 IDE hard disk problems Date: Sat, 13 May 2000 14:13:24 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 In-Reply-To: <391B398E.B0B6FCA6@ican.net> Importance: Normal Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have seen quite a few questions relating to this topic but never any answers so I will try myself. One of the machines I have running FreeBSD is my desktop machine running an Athlon 600 with FIC SD-11 motherboard. I have now tried two different IDE hard disks, I have tried disabling the 32bit transfers and setting the mode down to 0 but with no effect. The problem is that the system reports lots of errors like /kernel: ad0: UDMA ICRC WRITE ERROR blk# 3062797 retrying or /kernel: ad0: UDMA ICRC WRITE ERROR blk#2400383ata0-master: WARNING: WAIT_READY active=ATA_ACTIVE_ATA Then eventually /kernel: falling back to PIO mode This happens from the time of startup until the system falls back to PIO mode. Unfortunately, lately the machine has started locking solid when running X and needs a hard reboot to sort it out - I suspect that if there have been lots of these write errors over time it will screw the file system (technical term!). I have only had to do an fsck manually a few times but don't really want to re-build everything until I know how to sort the disk problem. Is there anyway to force the machine to start up in PIO mode? does anyone know if this might cure the problem? Thanks in advance Simon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message