Kernel 4.4.1-1 fails to boot - root volume “does not exist” - 3.10.0.327 and 4.3.3-1 both continue to...












0















I'm trying to install and boot kernel-ml (currently 4.4.1-1) on RHEL 7.2 following the instructions here: http://linuxg.net/install-kernel-4-x-on-enterprise-linux-7-centos-7-and-rhel-7/



Install works fine and on reboot I can choose the new kernel from the grub menu - however it fails midway through booting up.



When it fails, I can see multiple instances of the following:



dracut-initqueue[632]: Warning: dracut-initqueue timeout - starting timeout scripts


Followed by this:



dracut-initqueue[632]: Warning: Could not boot.
dracut-initqueue[632]: Warning: /dev/mapper/vg_root-lv_root does not exist
dracut-initqueue[632]: Warning: /dev/vg_root/lv_root does not exist
Starting Dracut emergency shell...


I can still boot into the previously working old kernel, and to another 4.x (4.3.3-1) without issue, but 4.4.1-1 fails at this point every time. SO far I've tried the following with no success (some of the iseda come from https://askubuntu.com/questions/567730/gave-up-waiting-for-root-device-ubuntu-vg-root-doesnt-exist which looked like a similar error):



Exiting the dracut emergency shell - boot does not progress any further



Specifying root volume by UUID in the grub config - still not found



Checking if lvm2 is installed - it is



ls /dev/mapper - all I see under here is "control"



Added all_generic_ide boot parameter - no change



Rebuilt the initramfs for the broken kernel - no change



Removed rhgb and quiet from boot params



listing disks with lvm pvdisplay / lvm lvdisplay / lvm vgdisplay - none found, blank output



I'm not sure what else I can try here or what to do next - any pointers appreciated










share|improve this question

























  • Did you find a way out? I'm having exactly the same problem.

    – chirag1992m
    Jun 16 '17 at 21:22


















0















I'm trying to install and boot kernel-ml (currently 4.4.1-1) on RHEL 7.2 following the instructions here: http://linuxg.net/install-kernel-4-x-on-enterprise-linux-7-centos-7-and-rhel-7/



Install works fine and on reboot I can choose the new kernel from the grub menu - however it fails midway through booting up.



When it fails, I can see multiple instances of the following:



dracut-initqueue[632]: Warning: dracut-initqueue timeout - starting timeout scripts


Followed by this:



dracut-initqueue[632]: Warning: Could not boot.
dracut-initqueue[632]: Warning: /dev/mapper/vg_root-lv_root does not exist
dracut-initqueue[632]: Warning: /dev/vg_root/lv_root does not exist
Starting Dracut emergency shell...


I can still boot into the previously working old kernel, and to another 4.x (4.3.3-1) without issue, but 4.4.1-1 fails at this point every time. SO far I've tried the following with no success (some of the iseda come from https://askubuntu.com/questions/567730/gave-up-waiting-for-root-device-ubuntu-vg-root-doesnt-exist which looked like a similar error):



Exiting the dracut emergency shell - boot does not progress any further



Specifying root volume by UUID in the grub config - still not found



Checking if lvm2 is installed - it is



ls /dev/mapper - all I see under here is "control"



Added all_generic_ide boot parameter - no change



Rebuilt the initramfs for the broken kernel - no change



Removed rhgb and quiet from boot params



listing disks with lvm pvdisplay / lvm lvdisplay / lvm vgdisplay - none found, blank output



I'm not sure what else I can try here or what to do next - any pointers appreciated










share|improve this question

























  • Did you find a way out? I'm having exactly the same problem.

    – chirag1992m
    Jun 16 '17 at 21:22
















0












0








0








I'm trying to install and boot kernel-ml (currently 4.4.1-1) on RHEL 7.2 following the instructions here: http://linuxg.net/install-kernel-4-x-on-enterprise-linux-7-centos-7-and-rhel-7/



Install works fine and on reboot I can choose the new kernel from the grub menu - however it fails midway through booting up.



When it fails, I can see multiple instances of the following:



dracut-initqueue[632]: Warning: dracut-initqueue timeout - starting timeout scripts


Followed by this:



dracut-initqueue[632]: Warning: Could not boot.
dracut-initqueue[632]: Warning: /dev/mapper/vg_root-lv_root does not exist
dracut-initqueue[632]: Warning: /dev/vg_root/lv_root does not exist
Starting Dracut emergency shell...


I can still boot into the previously working old kernel, and to another 4.x (4.3.3-1) without issue, but 4.4.1-1 fails at this point every time. SO far I've tried the following with no success (some of the iseda come from https://askubuntu.com/questions/567730/gave-up-waiting-for-root-device-ubuntu-vg-root-doesnt-exist which looked like a similar error):



Exiting the dracut emergency shell - boot does not progress any further



Specifying root volume by UUID in the grub config - still not found



Checking if lvm2 is installed - it is



ls /dev/mapper - all I see under here is "control"



Added all_generic_ide boot parameter - no change



Rebuilt the initramfs for the broken kernel - no change



Removed rhgb and quiet from boot params



listing disks with lvm pvdisplay / lvm lvdisplay / lvm vgdisplay - none found, blank output



I'm not sure what else I can try here or what to do next - any pointers appreciated










share|improve this question
















I'm trying to install and boot kernel-ml (currently 4.4.1-1) on RHEL 7.2 following the instructions here: http://linuxg.net/install-kernel-4-x-on-enterprise-linux-7-centos-7-and-rhel-7/



Install works fine and on reboot I can choose the new kernel from the grub menu - however it fails midway through booting up.



When it fails, I can see multiple instances of the following:



dracut-initqueue[632]: Warning: dracut-initqueue timeout - starting timeout scripts


Followed by this:



dracut-initqueue[632]: Warning: Could not boot.
dracut-initqueue[632]: Warning: /dev/mapper/vg_root-lv_root does not exist
dracut-initqueue[632]: Warning: /dev/vg_root/lv_root does not exist
Starting Dracut emergency shell...


I can still boot into the previously working old kernel, and to another 4.x (4.3.3-1) without issue, but 4.4.1-1 fails at this point every time. SO far I've tried the following with no success (some of the iseda come from https://askubuntu.com/questions/567730/gave-up-waiting-for-root-device-ubuntu-vg-root-doesnt-exist which looked like a similar error):



Exiting the dracut emergency shell - boot does not progress any further



Specifying root volume by UUID in the grub config - still not found



Checking if lvm2 is installed - it is



ls /dev/mapper - all I see under here is "control"



Added all_generic_ide boot parameter - no change



Rebuilt the initramfs for the broken kernel - no change



Removed rhgb and quiet from boot params



listing disks with lvm pvdisplay / lvm lvdisplay / lvm vgdisplay - none found, blank output



I'm not sure what else I can try here or what to do next - any pointers appreciated







linux-kernel redhat-enterprise-linux dracut






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Apr 13 '17 at 12:22









Community

1




1










asked Feb 3 '16 at 12:02









Ian FrazerIan Frazer

111




111













  • Did you find a way out? I'm having exactly the same problem.

    – chirag1992m
    Jun 16 '17 at 21:22





















  • Did you find a way out? I'm having exactly the same problem.

    – chirag1992m
    Jun 16 '17 at 21:22



















Did you find a way out? I'm having exactly the same problem.

– chirag1992m
Jun 16 '17 at 21:22







Did you find a way out? I'm having exactly the same problem.

– chirag1992m
Jun 16 '17 at 21:22












1 Answer
1






active

oldest

votes


















0














I encountered this same problem on Ubuntu, the same scenario: 4.3.3 works but 4.4.x+ does not. The same thing was happening that no drives were found at all under /dev/mapper.



In my case, the problem wasn't with lvm (although I thought that was the issue as well), but that my computer uses a NVMe solid state drive (a Dell XPS 9550). According to Arch Linux Wiki, the location of the "nvm" driver was moved in between kernel 4.3 and 4.4. Some OSes have yet to update their initramfs to accommodate for the new location (including Arch and Ubuntu), causing the kernel to build without it.



See this bug in the Ubuntu queue: nvm extension is not properly loaded in initramfs.



The Arch Wiki suggests:




Edit your /etc/mkinitcpio.conf file:




...
MODULES="... nvme"
...



Then update the bootloader.




# mkinitcpio -p linux


But as Ubuntu doesn't have mkinitcpio to fix the problem as recommended in the Arch Wiki, I loaded the nvm extension in /etc/initramfs-tools/modules:



sudo bash -c "echo '
nvme' >> /etc/initramfs-tools/modules"
sudo update-initramfs -u -k all


If you have an NVM drive, you may also be running a Skylake chipset. If so, you should also download the i915 drivers and add the i915 extension to this same file, as recommended in https://askubuntu.com/questions/717338/installing-4-4-rc7-kernel-yields-i915-module-not-available






share|improve this answer

























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "3"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1035083%2fkernel-4-4-1-1-fails-to-boot-root-volume-does-not-exist-3-10-0-327-and-4-3%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    I encountered this same problem on Ubuntu, the same scenario: 4.3.3 works but 4.4.x+ does not. The same thing was happening that no drives were found at all under /dev/mapper.



    In my case, the problem wasn't with lvm (although I thought that was the issue as well), but that my computer uses a NVMe solid state drive (a Dell XPS 9550). According to Arch Linux Wiki, the location of the "nvm" driver was moved in between kernel 4.3 and 4.4. Some OSes have yet to update their initramfs to accommodate for the new location (including Arch and Ubuntu), causing the kernel to build without it.



    See this bug in the Ubuntu queue: nvm extension is not properly loaded in initramfs.



    The Arch Wiki suggests:




    Edit your /etc/mkinitcpio.conf file:




    ...
    MODULES="... nvme"
    ...



    Then update the bootloader.




    # mkinitcpio -p linux


    But as Ubuntu doesn't have mkinitcpio to fix the problem as recommended in the Arch Wiki, I loaded the nvm extension in /etc/initramfs-tools/modules:



    sudo bash -c "echo '
    nvme' >> /etc/initramfs-tools/modules"
    sudo update-initramfs -u -k all


    If you have an NVM drive, you may also be running a Skylake chipset. If so, you should also download the i915 drivers and add the i915 extension to this same file, as recommended in https://askubuntu.com/questions/717338/installing-4-4-rc7-kernel-yields-i915-module-not-available






    share|improve this answer






























      0














      I encountered this same problem on Ubuntu, the same scenario: 4.3.3 works but 4.4.x+ does not. The same thing was happening that no drives were found at all under /dev/mapper.



      In my case, the problem wasn't with lvm (although I thought that was the issue as well), but that my computer uses a NVMe solid state drive (a Dell XPS 9550). According to Arch Linux Wiki, the location of the "nvm" driver was moved in between kernel 4.3 and 4.4. Some OSes have yet to update their initramfs to accommodate for the new location (including Arch and Ubuntu), causing the kernel to build without it.



      See this bug in the Ubuntu queue: nvm extension is not properly loaded in initramfs.



      The Arch Wiki suggests:




      Edit your /etc/mkinitcpio.conf file:




      ...
      MODULES="... nvme"
      ...



      Then update the bootloader.




      # mkinitcpio -p linux


      But as Ubuntu doesn't have mkinitcpio to fix the problem as recommended in the Arch Wiki, I loaded the nvm extension in /etc/initramfs-tools/modules:



      sudo bash -c "echo '
      nvme' >> /etc/initramfs-tools/modules"
      sudo update-initramfs -u -k all


      If you have an NVM drive, you may also be running a Skylake chipset. If so, you should also download the i915 drivers and add the i915 extension to this same file, as recommended in https://askubuntu.com/questions/717338/installing-4-4-rc7-kernel-yields-i915-module-not-available






      share|improve this answer




























        0












        0








        0







        I encountered this same problem on Ubuntu, the same scenario: 4.3.3 works but 4.4.x+ does not. The same thing was happening that no drives were found at all under /dev/mapper.



        In my case, the problem wasn't with lvm (although I thought that was the issue as well), but that my computer uses a NVMe solid state drive (a Dell XPS 9550). According to Arch Linux Wiki, the location of the "nvm" driver was moved in between kernel 4.3 and 4.4. Some OSes have yet to update their initramfs to accommodate for the new location (including Arch and Ubuntu), causing the kernel to build without it.



        See this bug in the Ubuntu queue: nvm extension is not properly loaded in initramfs.



        The Arch Wiki suggests:




        Edit your /etc/mkinitcpio.conf file:




        ...
        MODULES="... nvme"
        ...



        Then update the bootloader.




        # mkinitcpio -p linux


        But as Ubuntu doesn't have mkinitcpio to fix the problem as recommended in the Arch Wiki, I loaded the nvm extension in /etc/initramfs-tools/modules:



        sudo bash -c "echo '
        nvme' >> /etc/initramfs-tools/modules"
        sudo update-initramfs -u -k all


        If you have an NVM drive, you may also be running a Skylake chipset. If so, you should also download the i915 drivers and add the i915 extension to this same file, as recommended in https://askubuntu.com/questions/717338/installing-4-4-rc7-kernel-yields-i915-module-not-available






        share|improve this answer















        I encountered this same problem on Ubuntu, the same scenario: 4.3.3 works but 4.4.x+ does not. The same thing was happening that no drives were found at all under /dev/mapper.



        In my case, the problem wasn't with lvm (although I thought that was the issue as well), but that my computer uses a NVMe solid state drive (a Dell XPS 9550). According to Arch Linux Wiki, the location of the "nvm" driver was moved in between kernel 4.3 and 4.4. Some OSes have yet to update their initramfs to accommodate for the new location (including Arch and Ubuntu), causing the kernel to build without it.



        See this bug in the Ubuntu queue: nvm extension is not properly loaded in initramfs.



        The Arch Wiki suggests:




        Edit your /etc/mkinitcpio.conf file:




        ...
        MODULES="... nvme"
        ...



        Then update the bootloader.




        # mkinitcpio -p linux


        But as Ubuntu doesn't have mkinitcpio to fix the problem as recommended in the Arch Wiki, I loaded the nvm extension in /etc/initramfs-tools/modules:



        sudo bash -c "echo '
        nvme' >> /etc/initramfs-tools/modules"
        sudo update-initramfs -u -k all


        If you have an NVM drive, you may also be running a Skylake chipset. If so, you should also download the i915 drivers and add the i915 extension to this same file, as recommended in https://askubuntu.com/questions/717338/installing-4-4-rc7-kernel-yields-i915-module-not-available







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Apr 13 '17 at 12:22









        Community

        1




        1










        answered Mar 12 '16 at 22:27









        Nate LamptonNate Lampton

        1011




        1011






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Super User!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1035083%2fkernel-4-4-1-1-fails-to-boot-root-volume-does-not-exist-3-10-0-327-and-4-3%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            How to reconfigure Docker Trusted Registry 2.x.x to use CEPH FS mount instead of NFS and other traditional...

            is 'sed' thread safe

            How to make a Squid Proxy server?