Hide Forgot
Created attachment 533158 [details] a jpg from cell phone of failed boot screen Description of problem: With the upgrade of systemd, boot will fail if /cgroup in fstab Version-Release number of selected component (if applicable): rpm -q systemd systemd-26-13.fc15.x86_64 How reproducible: Steps to Reproduce: 1.update systemd 2.reboot 3. Actual results: Starting /cgroup mount: none already mounted or /cgroup mounted cgroup.mount mount process exited, code=exited status=32 < then lots of dependency failures> Expected results: Additional info: With this upgrade of systemd, boot will fail if /cgroup is in fstab. I've attached a jpg of the failed boot screen. Fixed by commenting out the cgroup line in fstab: #none /cgroup cgroup defaults 0 0 Importantly, I don't think I added this line to fstab. I don't use cgroups. It's from some upgrade. So this line likely to be in lots of machines. As a general matter, it seems boot will fail if any of the entries in fstab can't be mounted. This causes a lot of trouble with remote systems. Shouldn't boot continue as long as / is available?
/cgroup was mounted by an init script in earlier releases, not from fstab. You are sure, you did not play around with containers or LXC, or anything like that? I would expect it was added it manually.
> With the upgrade of systemd, boot will fail if /cgroup in fstab > > Version-Release number of selected component (if applicable): > rpm -q systemd > systemd-26-13.fc15.x86_64 Did systemd-26-10.fc15 have no problem with the /cgroup line in fstab? Does that version still work if you downgrade to it and keep the line in fstab uncommented? systemd mounts cgroup controllers under /sys/fs/cgroup, but it's been doing since a long time ago, so I'm surprised why you started seeing the issue only now with the systemd-26-13.fc15 update. > #none /cgroup cgroup defaults 0 0 > > Importantly, I don't think I added this line to fstab. I don't use cgroups. > It's from some upgrade. So this line likely to be in lots of machines. I don't know if any script in Fedora adds this line. However, I found several websites where putting this line to fstab manually is suggested. They were all various LXC HOWTOs. Do you use LXC containers? > As a general matter, it seems boot will fail if any of the entries in fstab > can't be mounted. This causes a lot of trouble with remote systems. Shouldn't > boot continue as long as / is available? There's the "nofail" mount option that you can use in fstab to avoid this problem. But it's true that classic initscripts were more lenient in this regard.
>Did systemd-26-10.fc15 have no problem with the /cgroup line in fstab? systemd-26-10 had no problem. >Does that version still work if you downgrade to it and keep the line in fstab uncommented? I'll see if I can do that. This is a remote production box, so it's a little dicey. >I don't know if any script in Fedora adds this line. However, I found several websites where putting this line to fstab manually is suggested. They were all various LXC HOWTOs. Do you use LXC containers? No I haven't tried LXC containers. If none of the Fedora scripts added it, I must have, but I sure don't remember.
Do you experience this with the latest release?
Closing this bug dont hesitate to reopen it if this is still an issue with the latest release of systemd thanks.