> > This suggests you may have an old loader, or the loader's parsing of
> > your /etc/fstab file may be failing. I probably need to add a
> > diagnostic to it to help us track this down.
>
> Okay, here's another one. I have 3.3-STABLE on wd0s1a, and -current
> (from 18. November) on wd0s1d. I boot this by pressing the space bar
> so I get the "boot: " prompt, and then typing "wd(0,d)kernel". This
> works fine, except I get the "Root mount failed" error message:
You should be using the loader to load the kernel. wd(0,d)/boot/loader
would be correct.
> With the commit you just did to vfs_conf.c I guess it'll be silent
> after the next time I've cvsup'ed and built world - I'm just wondering
> why this happens now.
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.
--
\\ Give a man a fish, and you feed him for a day. \\ Mike Smith
\\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED]
\\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
