From owner-freebsd-current Sun Nov 21 11: 5:21 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 542) id C697B14DD9; Sun, 21 Nov 1999 11:05:19 -0800 (PST) Date: Sun, 21 Nov 1999 11:05:19 -0800 From: "Andrey A. Chernov" To: Mike Smith Cc: sthaug@nethelp.no, current@FreeBSD.ORG Subject: Re: Root mount failed:22 ??? Message-ID: <19991121110519.A38340@freebsd.org> References: <102.943174393@verdi.nethelp.no> <199911210851.AAA03911@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199911210851.AAA03911@dingo.cdrom.com>; from mike@smith.net.au on Sun, Nov 21, 1999 at 12:51:59AM -0800 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Nov 21, 1999 at 12:51:59AM -0800, Mike Smith wrote: > You're not using the loader, so nothing gets to read /etc/fstab and set > vfs.root.mountfrom. Thus the kernel can't use it to find the root > filesystem. I should probably emit a diagnostic to the effect that it > wasn't set, since in many cases to come that will be fatal for the boot > process. I just rebuild/reinstall -current /kernel and /sys/boot and update bootblocks via disklabel, as result diagnostic in question gone, but I _not_ see vfs.root.mountfrom variable in my sysctl -a output. -- Andrey A. Chernov http://nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message