From owner-freebsd-questions Fri Sep 1 14:13:19 2000 Delivered-To: freebsd-questions@freebsd.org Received: from brass.ftech.net (mrtg.ftech.net [195.200.0.119]) by hub.freebsd.org (Postfix) with ESMTP id 1A23B37B422 for ; Fri, 1 Sep 2000 14:13:15 -0700 (PDT) Received: from logger5.ftech.net ([195.200.0.64] helo=relay1.ftech.net) by brass.ftech.net with esmtp (Exim 3.12.ftech-p6 #2) id 13Uy7e-0000KF-00; Fri, 01 Sep 2000 22:13:14 +0100 Received: from dmg.ftech.co.uk ([195.200.9.208] helo=dmg.parse.net) by relay1.ftech.net with esmtp (Exim 3.16-ftechp6 #1) id 13Uy7c-0008L4-00; Fri, 01 Sep 2000 22:13:12 +0100 Received: from elf (elf.putney.parse.net [10.0.0.10]) by dmg.parse.net (8.9.3/8.9.3) with SMTP id WAA39234; Fri, 1 Sep 2000 22:12:31 +0100 (BST) (envelope-from goddard@acm.org) Message-Id: <3.0.3.32.20000901221333.008714f0@dmg.parse.net> X-Sender: dmg@dmg.parse.net (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Fri, 01 Sep 2000 22:13:33 +0100 To: Ruslan Ermilov From: David Goddard Subject: Re: /boot/loader issue (was Re: Machine-specific errors with top and uemacs) Cc: freebsd-questions@FreeBSD.ORG In-Reply-To: <20000901101737.A44758@sunbay.com> References: <3.0.3.32.20000831233833.0085ae90@dmg.parse.net> <3.0.3.32.20000828212409.007ee7e0@dmg.parse.net> <3.0.3.32.20000820105701.0085f100@dmg.parse.net> <3.0.3.32.20000820105701.0085f100@dmg.parse.net> <20000821123424.C91965@sunbay.com> <3.0.3.32.20000828212409.007ee7e0@dmg.parse.net> <20000829100542.B12568@sunbay.com> <3.0.3.32.20000831233833.0085ae90@dmg.parse.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:17 01/09/00 +0300, Ruslan Ermilov wrote: >On Thu, Aug 31, 2000 at 11:38:33PM +0100, David Goddard wrote: ... >> It looks like loader is mounting wd0s3a as / as opposed to ad0s3a, and >> consequently the boot fails with a "Specified device does not match mounted >> device" error when it goes through fstab (which of course refers to ad0s3a). >> >Loader(8) does not mount filesystems, though it passes a kernel the name of >root device. I'm still unsure where it's getting this from. >Do you see this problem without loader(8), i.e. when booting your /kernel >directly from boot blocks (the technique is described in boot(8) manpage). I can get the system booting OK if I bypass loader(8). >How does your default prompt look like: > >>> FreeBSD/i386 BOOT >Default: 0:ad(0,a)/kernel >boot: _ > >Do you see the `ad' or `wd' here? >If you see the `ad' then the problem is most probably with your >boot.config settings, perhaps you have a rootdev=foo there... I actually see: >> FreeBSD/i386 BOOT Default: 0:ad(0,a)/boot/loader boot: _ If I just hit return (kicking in loader), I get the wd0 as root problem. However, if I specify a kernel to boot, it uses ad0 as desired. I have no boot.config file and nothing in /boot points to wd0, so I still don't know where this has come from. The machine in question did formerly run an older version of FreeBSD using the wd* devices, but the current 4.x installation was done fresh (I deleted the old slices, but not the partitioning structure of the disk itself. I don't know if this has any bearing on it... Again, many thanks for your help... Dave To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message