Date: Wed, 28 Feb 2001 11:32:02 +0000 From: Josef Karthauser <joe@tao.org.uk> To: John Baldwin <jhb@FreeBSD.org> Cc: hackers@FreeBSD.org Subject: Re: rootdev problems with /boot/loader. Message-ID: <20010228113202.A32458@tao.org.uk> In-Reply-To: <XFMail.010227144404.jhb@FreeBSD.org>; from jhb@FreeBSD.org on Tue, Feb 27, 2001 at 02:44:04PM -0800 References: <20010227214100.A850@tao.org.uk> <XFMail.010227144404.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --]
On Tue, Feb 27, 2001 at 02:44:04PM -0800, John Baldwin wrote:
>
> On 27-Feb-01 Josef Karthauser wrote:
> > I've got a bootable filesystem that although it's installed in the first
> > slice on a disk the kernel/bootloader tries to mount /dev/ad0s2a as the
> > root filesystem. I'm scratching my head as to why. Any ideas?
> > It should be mounting /dev/ad0s1a automatically.
> >
> > The following are set by /boot/loader:
> > rootdev=disk1s1a
> > currdev=disk1s1a:
> >
> > Joe.
> >
> > p.s. This image is being booted via /dev/md0 in vmware. What I'm
> > trying to work out is whether it's a bug in either of these parts.
>
> What does 'lsdev' show.
Here's what lsdev shows:
disk @ 0xf3e4
disk0: BIOS drive A:
disk1: BIOS drive C:
disk1s1a: FFS
So why is it trying to book disk1s2a at mount time. /me's confused.
Joe
p.s. It's not devfs. It does the same thing with static dev nodes in
/dev.
[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (FreeBSD)
Comment: For info see http://www.gnupg.org
iEYEARECAAYFAjqc4bEACgkQXVIcjOaxUBZkPwCgxSDp2q7BJ0x934DCqfa4/GAg
dcUAn0GUp/o3ICCNL8rKLy8wmI/zyxX7
=gTkO
-----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010228113202.A32458>