Red Hat Bugzilla – Bug 1280103
Failed to mount /sysroot: mount.nfs: Failed to resolve server live: Name or service not known
Last modified: 2016-12-20 10:39:31 EST
Description of problem:
Attempting to boot a live booted Fedora 23 over http location or torrent file fails after the rootfs has been retrieved successfully:
[ OK ] Reached target Remote File Systems (Pre).
[ OK ] Reached target Remote File Systems.
[FAILED] Failed to mount /sysroot.
See 'systemctl status sysroot.mount' for details.
[DEPEND] Dependency failed for Initrd Root File System.
[DEPEND] Dependency failed for Reload Configuration from the Real Root.
[ OK ] Stopped dracut pre-pivot and cleanup hook.
:/# systemctl status sysroot.mount -l
● sysroot.mount - /sysroot
Loaded: loaded (/proc/cmdline)
Active: failed (Result: exit-code) since Tue 2015-11-10 22:54:27 UTC; 1min 56s ago
Process: 900 ExecMount=/usr/bin/mount live:http://hostname/rootfs.img /sysroot -o ro (code=exited, status=32)
Nov 10 22:54:27 hostname systemd: Mounting /sysroot...
Nov 10 22:54:27 hostname mount: mount.nfs: Failed to resolve server live: Name or service not known
Nov 10 22:54:27 hostname systemd: sysroot.mount: Mount process exited, code=exited status=32
Nov 10 22:54:27 hostname systemd: Failed to mount /sysroot.
Nov 10 22:54:27 hostname systemd: sysroot.mount: Unit entered failed state.
Warning: sysroot.mount changed on disk. Run 'systemctl daemon-reload' to reload units.
Version-Release number of selected component (if applicable):
Fedora 23 updated as of Nov 10, 2015
Should be fairly reproducible using liveboot over http
Steps to Reproduce:
Using pxe, boot the vmlinuz, initrd with the following options kernel params.
root=live:http://hostname/rootfs.img rootflags="" ip=10.24.104.40::10.24.104.1:255.255.252.0:hostname:ens9f1:none nameserver=184.108.40.206 nomodeset rd.live.debug=1 rd.writable.fsimg rd.shell enforcing=1 modprobe.blacklist=mei_me console=ttyS4,115200n8 8250.nr_uarts=5
Failure after rootfs has been downloaded, OS is unable to boot into RAM from there.
Should boot image from live http or torrent successfully. This is has been working great in Fedora 22.
Similar issue, but not sure if it takes into affect live booted over http/torrent, looks like F23 has dracut-043:
Moving to correct component.
Another previously resolved issue that appears related for more context:
No, this was caused by a patch for systemd-fstab-generator.
So, the proper solution for this is to add a systemd generator for the livenet dracut module to handle the root=live:<URL> case.
I made a pull request towards dracut master here:
This seems to allow live booted URLs to work again. This patch uses systemd's generator arg to generate an early sysroot.mount that preempts systemd-fstab-generator similiar to the dmsquash-generator. I'm not sure if that's the exact approach you're looking for but I have verified it does work and generates the early sysroot.mount for systemd.
Thanks for the merge, is this something we could get backported into F23?
yeah, will do, thanks!
Hey Harald, has this been backported into F23 yet? Thanks!
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 23 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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
Thank you for reporting this bug and we are sorry it could not be fixed.