Red Hat Bugzilla – Bug 133635
Initscripts 7.84-1 does not like non initrd kernels
Last modified: 2014-03-16 22:48:42 EDT
After upgrading to Initscripts 7.84-1 and udev-032, I now get this
message upon booting with a non-Fedora or other kernel not built with
Welcome to Fedora Core
Press 'I' to enter interactive startup.
Mounting... tmpfs at /dev/: mount: wrong fs type, bad option, bad
or too many mounted file systems
Making extra nodes: ln: creating symbolic link `/dev//fd' to
ln: creating symbolic link `/dev//stdin' to `/proc/self/fd/0': Read-
only file sm
ln: creating symbolic link `/dev//stdout' to `/proc/self/fd/1': Read-
only file m
ln: creating symbolic link `/dev//stderr' to `/proc/self/fd/2': Read-
only file m
ln: creating symbolic link `/dev//core' to `/proc/kcore': Read-only
MAKEDEV: error making /dev/fd1: Read-only file system
ln: creating symbolic link `/dev/MAKEDEV' to `/sbin/MAKEDEV': Read-
only file sym
Starting udev: rm: cannot remove `/dev//.udev.tdb': Read-only file
Initializing hardware... storage network audio done[ OK ]
This is because udev is now started much earlier on in the boot
sequence - too early, in so far as it now starts before a rw
filesystem is mounted on /dev.
It comes down to either building with an initrd, or using a Fedora
kernel as a non-initrd kernel will not boot without this message. It
also screws up the operation of udev, which expects to have MAKEDEV
and also the abovementioned devices available on boot.
To accomodate this, perhaps the initscripts could check for the
presence of a rw /dev, and if not, either delay the udev start till
after the filesystems have been mounted rw, or else mount a rw tmpfs
on /dev so that start_udev can run without error ?
The udev script already does mount /dev if needed. I suspect you're
running into a different bug.
*** This bug has been marked as a duplicate of 133465 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.