With Fedora 15 Kernel 2.6.38.6-27 some new problems arised. My /boot partition could not be mounted any more in the boot process. Later this was entirely possible. With the previous rc1 kernel, there was no such problem. Because of it, the boot process goes into emergency mode every time. The boot partition is reachable through a multipath dm device. So it's device is /dev/mapper/mpathap1. May be the mp device isn't ready, when systemd tries to mount it. Adding the _netdev mount option to fstab cures the problem, because it postpones the mount. Similar thing with a bind mount, but on shutdown. systemd hangs until it is removed, or the _netdev and nofail options are added to the mount options. Here are the non-working fstab entries: /home/tom /nfsexports/tom none bind,rw 0 0 and UUID=xxxxx-xxxxxx-xxxxxx... /boot ext4 defaults 1 2 Is it now necessary to use the _netdev option for such mounts?
In both cases, adding the _netdev option, causes the netfs.service to fail. Specifically the parts for checking the "network attached filesystems" and "Mounting other filesystems". The root cause is always, that one of the affected filesystems is already mounted. This also seems to include the devpts, shm and sysfs mounts. Apparently systemd mounts these by itself, very early in the boot process. Therefore all subsequent mounts by the fedora scripts must fail.
Please add "log_buf_len=1M systemd.log_level=debug systemd.log_target=kmsg" to your kernel command line and when you get to the emergency shell, save the output of the "dmesg" command and then attach it here. Thanks.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.