> > I see this:
> >
> > Root mount failed: 22
>
> 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:
ad0: <IBM-DTTA-351010/T56OA73A> ATA-4 disk at ata0 as master
ad0: 9671MB (19807200 sectors), 19650 cyls, 16 heads, 63 S/T, 512 B/S
ad0: 16 secs/int, 31 depth queue, UDMA33
Creating DISK ad0
Creating DISK wd0
...
Root mount failed: 22
Mounting root from ufs:wd0s1d
This is what my fstab for -current looks like:
# Device Mountpoint FStype Options Dump Pass#
/dev/wd0s1b none swap sw 0 0
/dev/wd0s1d / ufs rw 1 1
/dev/wd0s1f /usr ufs rw 2 2
/dev/wd0s1h /local ufs rw 2 2
proc /proc procfs rw 0 0
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.
Steinar Haug, Nethelp consulting, [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
