Description of problem: Version-Release number of selected component (if applicable): systemd-22-1.fc15.x86_64 systemd-units-22-1.fc15.x86_64 How reproducible: yum update on Monday 4th April 15:00 CEST Steps to Reproduce: 1. boot fedora 15 beta 2. 3. Actual results: System hangs in boot with the message "Failed to mount /sys/fs/cgroup/systemd: No such file or directory" Expected results: Additional info: I tried to start with the following *) enforcing=0 *) 3 nomodeset *) removed all kms settings none of the actions solved my problem. Booting from CD and looking through the logs doesn't reveal any additional info.
yum downgrade to 20-1.fc15 (via chroot) fixed the boot problem in the meantime
apparently it seems to be a selinux problem with the new systemd. If I use selinux=0 as boot param all works well.
I also see this... The full boot errors are: Failed to load SELinux policy. Failed to set security context: system_u:object_r:sysfs_t:s0 for /sys: Invalid argument Failed to set security context: system_u:object_r:sysfs_t:s0 for /sys: Invalid argument Failed to mount /sys/fs/cgroup/systemd: No such file or directory # rpm -qa | grep systemd systemd-units-22-1.fc15.x86_64 systemd-22-1.fc15.x86_64 # rpm -qa | grep selinux-policy selinux-policy-3.9.16-11.fc15.noarch selinux-policy-targeted-3.9.16-11.fc15.noarch
same selinux versions over here (3.9.16-11.fc15)
Same as bug#692436 ?
systemd should be checking for enforcmode before failing. If SELinux is in permissive mode it should report the problem and continue. If it is disabled it should not try.
I have the following in /etc/sysconfig/selinux (which now a link to /etc/selinux/config): # This file controls the state of SELinux on the system. # SELINUX= can take one of these three values: # enforcing - SELinux security policy is enforced. # permissive - SELinux prints warnings instead of enforcing. # disabled - No SELinux policy is loaded. SELINUX=disabled # SELINUXTYPE= can take one of these two values: # targeted - Targeted processes are protected, # mls - Multi Level Security protection. SELINUXTYPE=targeted This bug still occurs though - so the only option at the moment is to boot with selinux=0 on the kernel line.
Tried booting with systemd.log_level=debug on the kernel line, however the first hint of any problem was the failure in my first post above. Can't add any value there.
(In reply to comment #7) > I have the following in /etc/sysconfig/selinux (which now a link to > /etc/selinux/config): ... > SELINUX=disabled You're seeing bug 692573.
same problem here, running with SELINUX=disabled
entering rescue mode and setting SELINUX=permissive works for now
*** This bug has been marked as a duplicate of bug 692573 ***