dracut-initqueue timeout

[AMjuni]

After rebook, the 460c machine is stuck in following: 

[  OK  ] Started udev Kernel Device Manager.
         Starting udev Coldplug all Devices...
         Mounting Configuration File System...
[  OK  ] Mounted Configuration File System.
[  OK  ] Started udev Coldplug all Devices.
         Starting Show Plymouth Boot Screen...
[  OK  ] Reached target System Initialization.
         Starting dracut initqueue hook...
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Reached target Paths.
[  OK  ] Reached target Basic System.
[  126.538177] dracut-initqueue[542]: Warning: dracut-initqueue timeout - starting timeout scripts
[  127.051466] dracut-initqueue[542]: Warning: dracut-initqueue timeout - starting timeout scripts
[  127.559858] dracut-initqueue[542]: Warning: dracut-initqueue timeout - starting timeout scripts
[  128.067571] dracut-initqueue[542]: Warning: dracut-initqueue timeout - starting timeout scripts
[  128.575591] dracut-initqueue[542]: Warning: dracut-initqueue timeout - starting timeout scripts
[  129.083598] dracut-initqueue[542]: Warning: dracut-initqueue timeout - starting timeout scripts
[  129.591389] dracut-initqueue[542]: Warning: dracut-initqueue timeout - starting timeout scripts
[  130.099355] dracut-initqueue[542]: Warning: dracut-initqueue timeout - starting timeout scripts
[  130.607137] dracut-initqueue[542]: Warning: dracut-initqueue timeout - starting timeout scripts
[  131.115329] dracut-initqueue[542]: Warning: dracut-initqueue timeout - starting timeout scripts
[  131.623045] dracut-initqueue[542]: Warning: dracut-initqueue timeout - starting timeout scripts

[  186.519793] dracut-initqueue[542]: Warning: dracut-initqueue timeout - starting timeout scripts
[  187.028486] dracut-initqueue[542]: Warning: dracut-initqueue timeout - sWarning: /dev/mapper/vg00-root does not exist
Warning: /dev/vg00/root does not exist
Warning: /dev/vg00/swap does not exist

Generating "/run/initramfs/rdsosreport.txt"


Entering emergency mode. Exit the shell to continue.
Type "journalctl" to view system logs.
You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot
after mounting them and attach it to a bug report.

[avd437]

These issues are sometimes related to a modification in the Logical Volumes of the system, but the config files weren't all updated to reflect the changes. Specifically the rd.lvm.lv kernel parameters in /etc/default/grub file were not updated. The below steps can be ran after booting from a previous kernel that still boots, or the server will need to be booted from an installation media and enter rescue mode.

List the logical volumes on your system:

# lvs -o vg_name,lv_name

Verify that the rd.lvm.lv= parameter values match the list of logical volumes on the system:

# grep GRUB_CMDLINE_LINUX /etc/default/grub