>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
On 3/10/00, 9:51:06 AM, R Joseph Wright <[EMAIL PROTECTED]> wrote
regarding single user mode problem:
> This has been going on for awhile, and I've looked everywhere for a
> solution. When I boot single user, the / filesystem gets mounted on
> wd0s4a even though /dev does not even have such an entry nor does
> /etc/fstab, since these have all been updated.
> This is not really such a problem until I try to exit from single user
> mode. Then, it tries to remount / on ad0s4a and can't find it.
Dear Joseph,
as I have recently written, I met an analogous problem while upgrading
to CURRENT: the "wdNsMa syndrome" appeared when I rebooted in s.u.m.
with the shining gleaming roaring freshly-made 4.0-CURRENT kernel in
order to (somehow) make installworld. Well, I did NOT care about it
and I went ahead ruthlessly ...
By the way, I made another kernel at the end of the process ("by the
book"). I suppose (?) this cleared the problem. In fact, I was able to
boot with no weird messages: all my filesystems were correctly
identified as adNsM (e.g. ad1s2a, ad1s2e ...)
HTH,
Salvo
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
