From owner-freebsd-current Sun Dec 12 23: 5:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles516.castles.com [208.214.165.80]) by hub.freebsd.org (Postfix) with ESMTP id 93B7214D01 for ; Sun, 12 Dec 1999 23:05:42 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id XAA05626; Sun, 12 Dec 1999 23:08:24 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912130708.XAA05626@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Adam Wight Cc: current@freebsd.org Subject: Re: Among the ATA casualties... In-reply-to: Your message of "Sun, 12 Dec 1999 20:40:53 GMT." <19991212204053.A734@holonet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 12 Dec 1999 23:08:24 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > boot -v output using the wd driver follows: > > > > That's not very helpful; we know it works. How about some information on > > the problem? > > Well... I'd sure like to send a boot -v for a kernel using ata... I don't > have the right hardware here to use a serial console, however. That's more your problem than ours though. > Here are the relevant lines from the boot sequence (paraphrased, of course): > ad0: piomode=4 dmamode=2 udmamode=-1 cblid=0 > ad0: ATA-? disk at ata0 as master Eek. An old laptop drive. > ad0: 401MB (822016 sectors), 988 cyls, 16 heads, 52 S/T, 512 B/S > ad0: 16 secs/int, 1 depth queue, PIO > Creating DISK ad0 > Creating DISK wd0 > Mounting root from ufs:/dev/wd0s1a Ultimately you'll want to update /etc/fstab (obviously not yet!) > wd0: invalid primary partition table: no magic Ok. It looks like we need more verbose output from the 'ad' driver, since it believes that it's read the primary partition table, but obviously hasn't. This syncs to some degree with the 'wd' driver's complaining about the recal failing. > Root mount failed: 6 > Mounting root from ufs:wd0s1a > wd0: invalid primary partition table: no magic This destroys my original hypothesis (that the first command was being ignored). You'll need to take this up with Soren; I suspect though that the simplest answer for you is going to be to stick with 'wd' until you get yourself a less-broken disk, or manage to analyse the problem in greater depth. The latter would be greatly assisted if you were able to dig into the 'ad' code a little and see what, if anything, is actually failing. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message