Hide Forgot
Description of problem: The following kernel commandline: Kernel command line: BOOT_IMAGE=/ovirt-node-ng-4.0.0-0.0.master.20160211.0.el7+1/vmlinuz-3.10.0-327.4.5.el7.x86_64 root=/dev/onn/ovirt-node-ng-4.0.0-0.0.master.20160211.0.el7+1 ro crashkernel=auto rd.lvm.lv=onn/ovirt-node-ng-4.0.0-0.0.master.20160211.0.el7+1 rd.lvm.lv=onn/swap rhgb quiet LANG=en_US.UTF-8 img.bootid=ovirt-node-ng-4.0.0-0.0.master.20160211.0.el7+1 Causes the following error message: Feb 11 14:47:46 localhost systemd[1]: Cannot add dependency dev-onn-ovirt\x2dnode\x2dng\x2d4.0.0\x2d0.0.master.20160211.0.el7+1.device to initrd.target, ignoring: Invalid argument By swithcing to the following root= argument the error goes away: root=UUID=2c1392eb-4132-4b2f-b5f1-2dc49564278c Version-Release number of selected component (if applicable): RHEl 7.2 # rpm -q systemd kernel dracut systemd-219-19.el7.x86_64 kernel-3.10.0-327.4.5.el7.x86_64 dracut-033-360.el7_2.x86_64 How reproducible: Always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
If you still have a reproducer, could you add rd.break to command line and post here content of /etc/systemd/system/initrd.target.wants?
It only has dev-centos_installed-swap.device
Anything else I can help with?
I installed the scratch build and tried the following: 1. Installed the new build 2. Reboot 3. dracut -f … 4. Reboot After 2: Error msg is still shown After 4: Error msg is still shown. I can not observer any change in behavior
might be a dracut bug creating the device unit name.
Ping?
please also search in /run and /usr # grep -R . /{run,etc,usr/lib}/systemd/system/initrd.target.wants/*.device
# grep -R . /{run,etc,usr/lib}/systemd/system/initrd.target.want grep: /run/systemd/system/initrd.target.wants/*.device: No such file or directory grep: /etc/systemd/system/initrd.target.wants/*.device: No such file or directory grep: /usr/lib/systemd/system/initrd.target.wants/*.device: No such file or directory # find /{run,etc,usr/lib}/systemd/system/ | grep initrd /usr/lib/systemd/system/initrd-switch-root.target.wants /usr/lib/systemd/system/initrd-switch-root.target.wants/plymouth-start.service /usr/lib/systemd/system/initrd-switch-root.target.wants/plymouth-switch-root.service /usr/lib/systemd/system/initrd.target.wants /usr/lib/systemd/system/initrd.target.wants/dracut-cmdline.service /usr/lib/systemd/system/initrd.target.wants/dracut-initqueue.service /usr/lib/systemd/system/initrd.target.wants/dracut-mount.service /usr/lib/systemd/system/initrd.target.wants/dracut-pre-mount.service /usr/lib/systemd/system/initrd.target.wants/dracut-pre-pivot.service /usr/lib/systemd/system/initrd.target.wants/dracut-pre-trigger.service /usr/lib/systemd/system/initrd.target.wants/dracut-pre-udev.service /usr/lib/systemd/system/initrd.target /usr/lib/systemd/system/initrd-cleanup.service /usr/lib/systemd/system/initrd-fs.target /usr/lib/systemd/system/initrd-parse-etc.service /usr/lib/systemd/system/initrd-root-fs.target /usr/lib/systemd/system/initrd-switch-root.service /usr/lib/systemd/system/initrd-switch-root.target /usr/lib/systemd/system/initrd-udevadm-cleanup-db.service
# journalctl -b | egrep "Cannot|witch Ro" Jul 22 13:45:09 localhost systemd[1]: Cannot add dependency dev-r4b_slot\x2d6c-rhvh\x2d4.0\x2d0.20160714.3+1.device to initrd.target, ignoring: Invalid argument Jul 22 13:45:09 localhost systemd[1]: Cannot add dependency job for unit multipathd.service, ignoring: Unit blk-availability.service failed to load: No such file or directory. Jul 22 13:45:11 localhost systemd[1]: Reached target Switch Root. Jul 22 13:45:11 localhost systemd[1]: Starting Switch Root. Jul 22 13:45:11 localhost systemd[1]: Starting Switch Root... To give an idea where/when it is happening
We are still seeing this, in production now - any news?
Still around in 7.3
I am really sory for late answer. I have backported couple of patch that should improve how dracut mangle device names
https://github.com/lnykryn/dracut/commits/bz1306640
devel-ack for merging patches from https://github.com/lnykryn/dracut/commits/bz1306640
Lukas, what patches exactly would be merged?
https://github.com/lnykryn/dracut/commit/66ef103af98ab0809b5a5effa444e1bf79076c65 https://github.com/lnykryn/dracut/commit/297517a274f57188dff670597be4338ad7c5f333 https://github.com/lnykryn/dracut/commit/27efa37e91701d8e9ce07672ea33fd5e88299cd0https://github.com/lnykryn/dracut/commit/5513ea9ad0821c16a8cef527f22211bd33e0c764
Hi Fabian, I'm not able to reproduce this problem, tested on RHEL-7.2 and RHEL-7.4, system booted correctly in both cases. The kernel command line was: [root@localhost ~]# dmesg | grep "Kernel command line" [ 0.000000] Kernel command line: BOOT_IMAGE=/ovirt-node-ng-4.0.0-0.0.master.20160211.0.el7+1/vmlinuz-3.10.0-327.el7.x86_64 root=/dev/rhel/ovirt-node-ng-4.0.0-0.0.master.20160211.0.el7+1 ro crashkernel=auto rd.lvm.lv=rhel/ovirt-node-ng-4.0.0-0.0.master.20160211.0.el7+1 rd.lvm.lv=rhel/swap console=ttyS0 LANG=en_US.UTF-8 [root@localhost ~]# Would you help with verification of this bug once there is a fix, please?
Let me redirect this to Ryan - as this was seen on RHVH
This is definitely still reproducible, and it looks like a UTF8 encoding bug, Jan. [ 0.964269] systemd[1]: Cannot add dependency dev-rhvh-rhvh\x2d4.2.1.2\x2d0.20180126.0+1.device to initrd.target, ignoring: Invalid argument The actual LV is rhvh-4.2.1.2-0.20180126.0+1. The hyphens in the LV name should be `-`, not \x2d
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:0964