Bug 1317966

Summary:	systemd update to 219-27.fc22 is causing failure to boot
Product:	[Fedora] Fedora	Reporter:	Michal Jaegermann <michal.jnn>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	22	CC:	johannbg, lnykryn, msekleta, muadda, s, systemd-maint, zbyszek
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-19 19:25:08 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Michal Jaegermann 2016-03-15 15:52:51 UTC

Description of problem:

As it happened I had 'root=LABEL=/FC0' in grub.cfg on the system in question.  Up to and including systemd-219-26.fc22 this was not an issue.  After an update to systemd-219-27.fc22 every initramfs build with this version exhibit the following behaviour:

.....
systemd[1]: Found device HDS724040KLSA80 /FC0.
systemd[1]: Starting File System Check on /dev/disk/by-label/\x2fFC0...
systemd-fsck[316]: Failed to stat '/dev/disk/by-label//FC0': No such file or directory
....
systemd[1]: systemd-fsck-root.service: main process exited, code=exited, status=1/FAILURE
systemd[1]: Failed to start File System Check on /dev/disk/by-label/\x2fFC0.
systemd[1]: Dependency failed for /sysroot.
systemd[1]: Dependency failed for Initrd Root File System.
systemd[1]: Dependency failed for Reload Configuration from the Real Root.
.....
systemd[1]: Reached target Remote File Systems.
systemd[1]: Starting Remote File Systems.
systemd[1]: Received SIGRTMIN+21 from PID 250 (plymouthd).

and I am dumped, rather quickly, into a "rescue mode" with not much to "rescue".  At this moment there is no problem in accessing or mounting this "No such file or directory" filesystem with a label /FC0.

A workaround is to boot with 'root=UUID=....' instead of 'root=LABEL=...'.  As it happens this is a local installation but if that would be a remote system I would be rather pissed by this regression.

Version-Release number of selected component (if applicable):
systemd-219-27.fc22

How reproducible:
always

Additional info:
systemd-222-14.fc23, as current for F23 installations, does not have this issue; systemd-229-6.fc25 from the current rawhide does not trip over this as well.

Comment 1 Fedora End Of Life 2016-07-19 19:25:08 UTC

Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.