Created attachment 1034048 [details] a screen image from a failure to boot Description of problem: The last kernel which boots without any issues is 4.1.0-0.rc4.git1.1.fc23.x86_64. For kernels 4.1.0-0.rc5.git0.1.fc23.x86_64 and 4.1.0-0.rc6.git0.1.fc23.x86_64 a boot ends up in an emergency shell because systemd-fsck-root.service failed on a root file system (specified by label). It says "Exit the shell to continue" but if one tries that then it responds with "Failed to start default target. Transaction is destructive" and gets stuck. A picture of a screen with a failed boot is attached. Asking for a status of systemd-fsck-root.service results in the following: ● systemd-fsck-root.service - File System Check on /dev/disk/by-label/\x2f1 Loaded: loaded (/run/systemd/generator/systemd-fsck-root.service) Active: failed (Result: exit-code) since Tue 2015-06-02 22:44:43 UTC; 7min ago Docs: man:systemd-fsck-root.service(8) Process: 291 ExecStart=/usr/lib/systemd/systemd-fsck /dev/disk/by-label//1 (code=exited, status=1/FAILURE) Main PID: 291 (code=exited, status=1/FAILURE) Jun 02 22:44:43 YYY systemd[1]: Starting File System Check on /dev/disk/by-label/\x2f1... Jun 02 22:44:43 YYY systemd-fsck[291]: Failed to stat /dev/disk/by-label//1: No such file or directory Jun 02 22:44:43 YYY systemd[1]: systemd-fsck-root.service: Main process exited, code=exited, status=1/FAILURE Jun 02 22:44:43 YYY systemd[1]: Failed to start File System Check on /dev/disk/by-label/\x2f1. Jun 02 22:44:43 YYY systemd[1]: systemd-fsck-root.service: Unit entered failed state. Jun 02 22:44:43 YYY systemd[1]: systemd-fsck-root.service: Failed with result 'exit-code'. OTOH a direct fsck on that "Failed to start File System Check on /dev/disk/by-label/\x2f1" runs without any issues. Moreover an attached rdsosreport.txt was saved on this "non-existing" file system after it got manually mounted. Version-Release number of selected component (if applicable): dracut-041-10.git20150219.fc23.x86_64 How reproducible: always Steps to Reproduce: 1. try to boot with a newer kernel Additional info: Recently systemd was updated to systemd-220-3.fc23.x86_64. Only that initramfs-4.1.0-0.rc5.git0.1.fc23.x86_64.img was created _before_ systemd was updated and initramfs for 4.1.0-0.rc4.git1.1.fc23.x86_64 luckily still boots. Maybe kernel changes are too blame? I do not really know. The whole boot mechanism becomes a maze-like.
Created attachment 1034050 [details] dracut generated rdsosreport.txt for 4.1.0-0.rc6.git0.1.fc23.x86_64 kernel
Replacing in a boot command "root=LABEL=/1" with "root=UUID=..." allows me to boot again. No idea what is screwing up but this is a nasty bug.
/dev/disk/by-label: total 0 lrwxrwxrwx 1 root 0 10 Jun 2 22:44 \x2f1 So, it seems /dev/disk/by-label/\x2f1 exists, but systemd unescapes it to /dev/disk/by-label//1 Reassigning to systemd.
https://github.com/systemd/systemd/issues/50
(In reply to Harald Hoyer from comment #3) > > So, it seems /dev/disk/by-label/\x2f1 exists, but systemd unescapes it to > /dev/disk/by-label//1 It seemed to me originally that both initramfs-4.1.0-0.rc4.git1.1.fc23.x86_64.img (booting) and initramfs-4.1.0-0.rc5.git0.1.fc23.x86_64.img (failing to boot) were made with the same version of systemd. It looks that I was mistaken and the older initramfs was created with systemd-219-12.fc23 and the next one, which failed to boot, with systemd-220-1.fc23. The current one installed is systemd-220-3.fc23.
This should now be fixed upstream with commit fa05e97257. Could you give that a try?
(In reply to Daniel Mack from comment #6) > This should now be fixed upstream with commit fa05e97257. Could you give > that a try? Is there any way to see that particular commit without cloning the whole repository from github? Nothing strikes me as "obvious". Not even if github is a place I really should be looking at.
https://github.com/systemd/systemd/commit/fa05e972.diff
(In reply to Daniel Mack from comment #6) > This should now be fixed upstream with commit fa05e97257. Could you give > that a try? Yes, indeed, with this change there are no more troubles with systemd-fsck-root.service and a root file system specified by label. With a new initramfs my machine boots. Only that fa05e97257.diff is not a form acceptable to systemd.spec. Once hacked around that an over three hours recompilation time is deep into a ridiculous territory. It is good that I had to go somewhere while this compilation was running or I would be convinced a long time ago that something went haywire. 1.4G of disk space taken by this compilation does not help very much. You should have warn me.
A just updated systemd-220-5.fc23 sports this bug too.
Created attachment 1036469 [details] git fa05e972 v2 for rawhide 202-5
systemd-220-8.fc23 does not seem to suffer from that affliction anymore.
I have the same problem in Fedora 22 with versions: kernel-4.0.8-300.fc22.i686 and kernel-4.1.2-200.fc22.i686 systemd-219-19.fc22.i686 The workaround in comment 2 (changing the root parameter in boot command line) works for me.
*** Bug 1313463 has been marked as a duplicate of this bug. ***