From owner-freebsd-questions Wed Oct 17 20:18:31 2001 Delivered-To: freebsd-questions@freebsd.org Received: from nyc.rr.com (nycsmtp2fb.rdc-nyc.rr.com [24.29.99.78]) by hub.freebsd.org (Postfix) with ESMTP id D0EAF37B407 for ; Wed, 17 Oct 2001 20:18:28 -0700 (PDT) Received: from scott1.nyc.rr.com ([24.168.25.8]) by nyc.rr.com with Microsoft SMTPSVC(5.5.1877.357.35); Wed, 17 Oct 2001 23:18:26 -0400 Message-Id: <5.1.0.14.0.20011017231222.00c0c158@pop-server.nyc.rr.com> X-Sender: scottro@pop-server.nyc.rr.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Wed, 17 Oct 2001 23:15:30 -0400 To: freebsd-questions@freebsd.org From: Scott Subject: re: UDMA errors Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed 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 Hi, I saw the original post on another machine, so might have broken the thread with this post, for which I apologize. At any rate, having gotten similar errors, I've done some searching in this list's archives and deja, and it seems that the three typical culprits are cables, motherboards and hard drives. I'm having the same problem with new, albeit relatively cheap hard drives (Swapping boxes and cables didn't help, so I'm assuming it's the drives--putting a better drive in one box, and reinstalling allowed me to boot without the errors. I'll be following this one to see if you get a better solution. The drives show no problems with MS O/S's or various flavors of Linux. Scott Robbins To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message