<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: dracut-initqueue timeout in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/dracut-initqueue-timeout/m-p/7074805#M59037</link>
    <description>&lt;P&gt;&lt;SPAN&gt;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&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;rd.lvm.lv&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;kernel parameters in&amp;nbsp;/etc/default/grub&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;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.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;List the logical volumes on your system:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;# lvs -o vg_name,lv_name&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Verify that the&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;rd.lvm.lv=&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;parameter values match the list of logical volumes on the system:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;# grep GRUB_CMDLINE_LINUX /etc/default/grub&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 06 Jan 2020 12:49:04 GMT</pubDate>
    <dc:creator>avd437</dc:creator>
    <dc:date>2020-01-06T12:49:04Z</dc:date>
    <item>
      <title>dracut-initqueue timeout</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dracut-initqueue-timeout/m-p/7074450#M59036</link>
      <description>&lt;P&gt;After rebook, the 460c machine is stuck in following:&amp;nbsp;&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;OK&amp;nbsp;&amp;nbsp;] Started udev Kernel Device Manager.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Starting udev Coldplug all Devices...&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Mounting Configuration File System...&lt;BR /&gt;[&amp;nbsp;&amp;nbsp;OK&amp;nbsp;&amp;nbsp;] Mounted Configuration File System.&lt;BR /&gt;[&amp;nbsp;&amp;nbsp;OK&amp;nbsp;&amp;nbsp;] Started udev Coldplug all Devices.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Starting Show Plymouth Boot Screen...&lt;BR /&gt;[&amp;nbsp;&amp;nbsp;OK&amp;nbsp;&amp;nbsp;] Reached target System Initialization.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Starting dracut initqueue hook...&lt;BR /&gt;[&amp;nbsp;&amp;nbsp;OK&amp;nbsp;&amp;nbsp;] Started Show Plymouth Boot Screen.&lt;BR /&gt;[&amp;nbsp;&amp;nbsp;OK&amp;nbsp;&amp;nbsp;] Reached target Paths.&lt;BR /&gt;[&amp;nbsp;&amp;nbsp;OK&amp;nbsp;&amp;nbsp;] Reached target Basic System.&lt;BR /&gt;[&amp;nbsp;&amp;nbsp;126.538177] dracut-initqueue[542]: Warning: dracut-initqueue timeout - starting timeout scripts&lt;BR /&gt;[&amp;nbsp;&amp;nbsp;127.051466] dracut-initqueue[542]: Warning: dracut-initqueue timeout - starting timeout scripts&lt;BR /&gt;[&amp;nbsp;&amp;nbsp;127.559858] dracut-initqueue[542]: Warning: dracut-initqueue timeout - starting timeout scripts&lt;BR /&gt;[&amp;nbsp;&amp;nbsp;128.067571] dracut-initqueue[542]: Warning: dracut-initqueue timeout - starting timeout scripts&lt;BR /&gt;[&amp;nbsp;&amp;nbsp;128.575591] dracut-initqueue[542]: Warning: dracut-initqueue timeout - starting timeout scripts&lt;BR /&gt;[&amp;nbsp;&amp;nbsp;129.083598] dracut-initqueue[542]: Warning: dracut-initqueue timeout - starting timeout scripts&lt;BR /&gt;[&amp;nbsp;&amp;nbsp;129.591389] dracut-initqueue[542]: Warning: dracut-initqueue timeout - starting timeout scripts&lt;BR /&gt;[&amp;nbsp;&amp;nbsp;130.099355] dracut-initqueue[542]: Warning: dracut-initqueue timeout - starting timeout scripts&lt;BR /&gt;[&amp;nbsp;&amp;nbsp;130.607137] dracut-initqueue[542]: Warning: dracut-initqueue timeout - starting timeout scripts&lt;BR /&gt;[&amp;nbsp;&amp;nbsp;131.115329] dracut-initqueue[542]: Warning: dracut-initqueue timeout - starting timeout scripts&lt;BR /&gt;[&amp;nbsp;&amp;nbsp;131.623045] dracut-initqueue[542]: Warning: dracut-initqueue timeout - starting timeout scripts&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;[&amp;nbsp;&amp;nbsp;186.519793] dracut-initqueue[542]: Warning: dracut-initqueue timeout - starting timeout scripts&lt;BR /&gt;[&amp;nbsp;&amp;nbsp;187.028486] dracut-initqueue[542]: Warning: dracut-initqueue timeout - sWarning: /dev/mapper/vg00-root does not exist&lt;BR /&gt;Warning: /dev/vg00/root does not exist&lt;BR /&gt;Warning: /dev/vg00/swap does not exist&lt;BR /&gt;&lt;BR /&gt;Generating "/run/initramfs/rdsosreport.txt"&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Entering emergency mode. Exit the shell to continue.&lt;BR /&gt;Type "journalctl" to view system logs.&lt;BR /&gt;You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot&lt;BR /&gt;after mounting them and attach it to a bug report.&lt;/P&gt;</description>
      <pubDate>Wed, 01 Jan 2020 10:45:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dracut-initqueue-timeout/m-p/7074450#M59036</guid>
      <dc:creator>AMjuni</dc:creator>
      <dc:date>2020-01-01T10:45:47Z</dc:date>
    </item>
    <item>
      <title>Re: dracut-initqueue timeout</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dracut-initqueue-timeout/m-p/7074805#M59037</link>
      <description>&lt;P&gt;&lt;SPAN&gt;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&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;rd.lvm.lv&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;kernel parameters in&amp;nbsp;/etc/default/grub&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;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.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;List the logical volumes on your system:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;# lvs -o vg_name,lv_name&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Verify that the&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;rd.lvm.lv=&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;parameter values match the list of logical volumes on the system:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;# grep GRUB_CMDLINE_LINUX /etc/default/grub&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 06 Jan 2020 12:49:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dracut-initqueue-timeout/m-p/7074805#M59037</guid>
      <dc:creator>avd437</dc:creator>
      <dc:date>2020-01-06T12:49:04Z</dc:date>
    </item>
  </channel>
</rss>

