Red Hat Bugzilla – Bug 985160
dracut ignores cmdline root= path
Last modified: 2014-06-17 23:55:45 EDT
Created attachment 774574 [details] screenshot Description of problem: RHEL7 decided it wanted to make a logical volume named "root" during install, which doesn't match my naming scheme at all. Post install I renamed the logical volume to lv_rhel7 and updated the cmdline in grub. Dracut doesn't seem to use care what root= value is passed on the cmdline and still look for the, now non-existent, root logical volume... What's the point of root=? Version-Release number of selected component (if applicable): rhel7 How reproducible: 100% Steps to Reproduce: 1. Rename your root logical volume 2. Update grub cmdline to reflect the new name 3. Attempt to reboot Actual results: See attached image Expected results: root= should override whatever path is embedded in the initrd. Additional info:
To get to the system again, boot with the rescue entry, change root=, run # dracut --regenerate-all -f And retry with the normal grub entry, with dracut-031-4.git20130731.el7, where this is hopefully fixed. # dracut -f
Created attachment 864198 [details] rdsosreport.txt Retested with dracut-033-124.el7, but system doesn't boot after changing LV name with rootfs: [root@localhost ~]# lvrename rhel root rhel7 Renamed "root" to "rhel7" in volume group "rhel" [root@localhost ~]# modifying kernel cmdline and reboot: dracut:/# cat /proc/cmdline BOOT_IMAGE=/vmlinuz-3.10.0-86.el7.x86_64 root=/dev/mapper/rhel-rhel7 ro rd.lvm.lv=rhel/rhel7 vconsole.font=latarcyrheb-sun16 rd.lvm.lv=rhel/swap vconsole.keymap=us crashkernel=auto rhgb quiet LANG=en_US.UTF-8 rd.debug console=ttyS0 dracut:/# lvm lvs LV VG Attr LSize Pool Origin Data% Move Log Cpy%Sync Convert rhel7 rhel -wi-a----- 17.51g swap rhel -wi-a----- 2.00g dracut:/# rdsosreport.txt is attached.
please retry with dracut-033-137.el7
Retested with dracut-033-137.el7, system booted correctly after changing root=, rd.lvm.lv= and updating /etc/fstab with the new LV name.
Retested with dracut-033-145.el7, this issue is fixed. Moving to VERIFIED.
This request was resolved in Red Hat Enterprise Linux 7.0. Contact your manager or support representative in case you have further questions about the request.