Gave up waiting for root device on Ubuntu












7















I've just installed Ubuntu 12.10 to dual boot with Windows 8, but every time I choose Ubuntu from grub menu, it always get stuck at this error and won't boot:



Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait long enough?)
- Check root= (did the system wait for the right device?)
- Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/disk/by-uuid/920903aa-762f-40d2-8126-87f4b0e6f975 does not exist. Dropping to a shell!

BusyBox v1.19.3 (Ubuntu 1:1.10.3-7ubuntu1.1) built-in shell (ash)
Enter 'help' for a lost of built-in commands.
(initramfs)


I tried with boot-repair, but it doesn't help, here is the log generated it.










share|improve this question

























  • Not going to "waste" an answer just as if trying hard fishing for rep points. The following +50 answer may already get some of you guys you out of your misery: askubuntu.com/questions/361886/… For those with "exotic" hardware, note the 6th pitfall, which I've just added recently to Braiam's great post. (i e. either missing linux-image-extra, or it got "destroyed" when upgrading kernel)

    – syntaxerror
    Feb 10 '16 at 2:29


















7















I've just installed Ubuntu 12.10 to dual boot with Windows 8, but every time I choose Ubuntu from grub menu, it always get stuck at this error and won't boot:



Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait long enough?)
- Check root= (did the system wait for the right device?)
- Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/disk/by-uuid/920903aa-762f-40d2-8126-87f4b0e6f975 does not exist. Dropping to a shell!

BusyBox v1.19.3 (Ubuntu 1:1.10.3-7ubuntu1.1) built-in shell (ash)
Enter 'help' for a lost of built-in commands.
(initramfs)


I tried with boot-repair, but it doesn't help, here is the log generated it.










share|improve this question

























  • Not going to "waste" an answer just as if trying hard fishing for rep points. The following +50 answer may already get some of you guys you out of your misery: askubuntu.com/questions/361886/… For those with "exotic" hardware, note the 6th pitfall, which I've just added recently to Braiam's great post. (i e. either missing linux-image-extra, or it got "destroyed" when upgrading kernel)

    – syntaxerror
    Feb 10 '16 at 2:29
















7












7








7


3






I've just installed Ubuntu 12.10 to dual boot with Windows 8, but every time I choose Ubuntu from grub menu, it always get stuck at this error and won't boot:



Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait long enough?)
- Check root= (did the system wait for the right device?)
- Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/disk/by-uuid/920903aa-762f-40d2-8126-87f4b0e6f975 does not exist. Dropping to a shell!

BusyBox v1.19.3 (Ubuntu 1:1.10.3-7ubuntu1.1) built-in shell (ash)
Enter 'help' for a lost of built-in commands.
(initramfs)


I tried with boot-repair, but it doesn't help, here is the log generated it.










share|improve this question
















I've just installed Ubuntu 12.10 to dual boot with Windows 8, but every time I choose Ubuntu from grub menu, it always get stuck at this error and won't boot:



Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait long enough?)
- Check root= (did the system wait for the right device?)
- Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/disk/by-uuid/920903aa-762f-40d2-8126-87f4b0e6f975 does not exist. Dropping to a shell!

BusyBox v1.19.3 (Ubuntu 1:1.10.3-7ubuntu1.1) built-in shell (ash)
Enter 'help' for a lost of built-in commands.
(initramfs)


I tried with boot-repair, but it doesn't help, here is the log generated it.







boot






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Feb 21 '14 at 3:50









Braiam

51.8k20136221




51.8k20136221










asked Jan 25 '13 at 16:42









winter_windwinter_wind

36113




36113













  • Not going to "waste" an answer just as if trying hard fishing for rep points. The following +50 answer may already get some of you guys you out of your misery: askubuntu.com/questions/361886/… For those with "exotic" hardware, note the 6th pitfall, which I've just added recently to Braiam's great post. (i e. either missing linux-image-extra, or it got "destroyed" when upgrading kernel)

    – syntaxerror
    Feb 10 '16 at 2:29





















  • Not going to "waste" an answer just as if trying hard fishing for rep points. The following +50 answer may already get some of you guys you out of your misery: askubuntu.com/questions/361886/… For those with "exotic" hardware, note the 6th pitfall, which I've just added recently to Braiam's great post. (i e. either missing linux-image-extra, or it got "destroyed" when upgrading kernel)

    – syntaxerror
    Feb 10 '16 at 2:29



















Not going to "waste" an answer just as if trying hard fishing for rep points. The following +50 answer may already get some of you guys you out of your misery: askubuntu.com/questions/361886/… For those with "exotic" hardware, note the 6th pitfall, which I've just added recently to Braiam's great post. (i e. either missing linux-image-extra, or it got "destroyed" when upgrading kernel)

– syntaxerror
Feb 10 '16 at 2:29







Not going to "waste" an answer just as if trying hard fishing for rep points. The following +50 answer may already get some of you guys you out of your misery: askubuntu.com/questions/361886/… For those with "exotic" hardware, note the 6th pitfall, which I've just added recently to Braiam's great post. (i e. either missing linux-image-extra, or it got "destroyed" when upgrading kernel)

– syntaxerror
Feb 10 '16 at 2:29












4 Answers
4






active

oldest

votes


















3














If you installed Ubuntu Desktop onto a partition/hard drive which is part of a RAID array, or an encrypted disk, or on Windows ME, it will likely fail to boot. Installing Ubuntu Desktop onto one of these sources is not supported.



If you have installed Ubuntu Desktop to one of the above sources, and it won't boot:




  1. Uninstall Ubuntu.

  2. Install Ubuntu to a hard drive or partition which is not part of a RAID array, not encrypted, and not on Windows ME, and it should boot up just fine.






share|improve this answer


























  • Why do you assume this is Wubi on RAID?

    – Oli
    Aug 29 '13 at 14:53











  • hes probably not assuming, just telling you not to.

    – Lorenzo Von Matterhorn
    Sep 20 '13 at 17:48



















1














I also occurred same problem but I can solve it using following link



http://blog.wittchen.biz.pl/ubuntu-system-boot-problem/



Attempt #1



First, I tried to change rootdelay as error message said. I opened file /etc/default/grub
I found there the following line:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
and changed it to:
GRUB_CMDLINE_LINUX_DEFAULT="rootdelay=90 quiet splash"
rootdelay became longer, but unfortunately it didn’t fix the problem in my case.



Attempt #2



I edited /etc/fstab file. I executed the following command in terminal: sudo gedit /etc/fstab and edited fstab file in gedit. In the beginning my file looked like that:



# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda1 during installation
UUID=96889309-5f73-4688-8354-e64cd1bb158f / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=480cc3f7-a39d-4d0f-93d5-49fc8df1a392 none swap sw 0 0


Then, I commented one line and added another one describing /dev/sda1 disk device. Now, my file looks as follows:



# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda1 during installation
UUID=/dev/sda1 / ext4 errors=remount-ro 0 1
# UUID=96889309-5f73-4688-8354-e64cd1bb158f / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=480cc3f7-a39d-4d0f-93d5-49fc8df1a392 none swap sw 0 0


Problem still existed, so I tried another attempt to solve it.



Attempt #3



I opened terminal and typed the following command:



sudo grub-install /dev/sda


and then I typed another command to update grub:



sudo update-grub


After all of this, I rebooted computer and finally, error disappeared and problem was fixed!






share|improve this answer

































    0














    I just randomly started typing stuff... try:



    (initramfs) blkid
    (initramfs) blockdev --rereadpt /dev/sda
    (initramfs) blkid
    (initramfs) exit


    This at least gets you to the desktop where you can begin trouble shooting your problem which is probably due to a proprietary driver or something






    share|improve this answer































      0














      I have got same issue while i'm doing patched for entire system which includes kernel. unfortunately package broken which leads kernel was partially upgrade and corrected.



      I was scared about issue since where mail server was hosted and data also reside in the same machine.



      I google it. tried all possible concepts as below.



      1. Booting with live cd
      2. doing fsck for / partition and /boot
      3. grub-install on /dev/sda(which is default root filesystem)
      4. check fstab


      And following solve make happy to get boot server.



      --> note in my case boot is mounted on /boot which is /dev/sda3 where as /dev/sda1

      / file system.



      Simple solution to fix the issue(but to cross all module which are install on kernel level




      1. copy /boot of other server complete /boot excluding grub.cfg to external flash disk


      2. boot with live cd


      3. find out root file system with following command
        fdisk -l /dev/sda


      4. mount / file system on /mnt
        mount /dev/sdXY /mnt


      5. mkdir directory to mount external data
        mkdir -p /mnt/pd


      6. mount flash disk data to /mnt/pd


      7. now it is time to do chages on root file system with chroot command(Please care while doing chages)


      8. chroot /mnt


      9. now copy of entire /mnt/pd/boot/ to /mnt


      10. exit


      11. now unmout /mnt/pd


      12. create new folder mkdir -p /mnt/test



      13. mount /boot on /mnt/test



        mount /dev/sdXY /mnt/test



      14. now /boot is mounted on /mnt/test/


      15. again do chroot /mnt


      16. rename all file which contains /mnt/test/


      17. now copy /mnt/boot (which we have copied from pd) to /mnt/test/


      18. make sure your using original grub.cfg /mnt/test/boot/grub/grub.cfg


      19. exit


      20. reboot


      21. you will be successfully boot to the server without any issues.







      share|improve this answer








      New contributor




      Ramu Nakerikanti is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.




















        Your Answer








        StackExchange.ready(function() {
        var channelOptions = {
        tags: "".split(" "),
        id: "89"
        };
        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%2faskubuntu.com%2fquestions%2f247541%2fgave-up-waiting-for-root-device-on-ubuntu%23new-answer', 'question_page');
        }
        );

        Post as a guest















        Required, but never shown

























        4 Answers
        4






        active

        oldest

        votes








        4 Answers
        4






        active

        oldest

        votes









        active

        oldest

        votes






        active

        oldest

        votes









        3














        If you installed Ubuntu Desktop onto a partition/hard drive which is part of a RAID array, or an encrypted disk, or on Windows ME, it will likely fail to boot. Installing Ubuntu Desktop onto one of these sources is not supported.



        If you have installed Ubuntu Desktop to one of the above sources, and it won't boot:




        1. Uninstall Ubuntu.

        2. Install Ubuntu to a hard drive or partition which is not part of a RAID array, not encrypted, and not on Windows ME, and it should boot up just fine.






        share|improve this answer


























        • Why do you assume this is Wubi on RAID?

          – Oli
          Aug 29 '13 at 14:53











        • hes probably not assuming, just telling you not to.

          – Lorenzo Von Matterhorn
          Sep 20 '13 at 17:48
















        3














        If you installed Ubuntu Desktop onto a partition/hard drive which is part of a RAID array, or an encrypted disk, or on Windows ME, it will likely fail to boot. Installing Ubuntu Desktop onto one of these sources is not supported.



        If you have installed Ubuntu Desktop to one of the above sources, and it won't boot:




        1. Uninstall Ubuntu.

        2. Install Ubuntu to a hard drive or partition which is not part of a RAID array, not encrypted, and not on Windows ME, and it should boot up just fine.






        share|improve this answer


























        • Why do you assume this is Wubi on RAID?

          – Oli
          Aug 29 '13 at 14:53











        • hes probably not assuming, just telling you not to.

          – Lorenzo Von Matterhorn
          Sep 20 '13 at 17:48














        3












        3








        3







        If you installed Ubuntu Desktop onto a partition/hard drive which is part of a RAID array, or an encrypted disk, or on Windows ME, it will likely fail to boot. Installing Ubuntu Desktop onto one of these sources is not supported.



        If you have installed Ubuntu Desktop to one of the above sources, and it won't boot:




        1. Uninstall Ubuntu.

        2. Install Ubuntu to a hard drive or partition which is not part of a RAID array, not encrypted, and not on Windows ME, and it should boot up just fine.






        share|improve this answer















        If you installed Ubuntu Desktop onto a partition/hard drive which is part of a RAID array, or an encrypted disk, or on Windows ME, it will likely fail to boot. Installing Ubuntu Desktop onto one of these sources is not supported.



        If you have installed Ubuntu Desktop to one of the above sources, and it won't boot:




        1. Uninstall Ubuntu.

        2. Install Ubuntu to a hard drive or partition which is not part of a RAID array, not encrypted, and not on Windows ME, and it should boot up just fine.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Aug 15 '13 at 16:40

























        answered May 2 '13 at 19:50









        Lemmings19Lemmings19

        1315




        1315













        • Why do you assume this is Wubi on RAID?

          – Oli
          Aug 29 '13 at 14:53











        • hes probably not assuming, just telling you not to.

          – Lorenzo Von Matterhorn
          Sep 20 '13 at 17:48



















        • Why do you assume this is Wubi on RAID?

          – Oli
          Aug 29 '13 at 14:53











        • hes probably not assuming, just telling you not to.

          – Lorenzo Von Matterhorn
          Sep 20 '13 at 17:48

















        Why do you assume this is Wubi on RAID?

        – Oli
        Aug 29 '13 at 14:53





        Why do you assume this is Wubi on RAID?

        – Oli
        Aug 29 '13 at 14:53













        hes probably not assuming, just telling you not to.

        – Lorenzo Von Matterhorn
        Sep 20 '13 at 17:48





        hes probably not assuming, just telling you not to.

        – Lorenzo Von Matterhorn
        Sep 20 '13 at 17:48













        1














        I also occurred same problem but I can solve it using following link



        http://blog.wittchen.biz.pl/ubuntu-system-boot-problem/



        Attempt #1



        First, I tried to change rootdelay as error message said. I opened file /etc/default/grub
        I found there the following line:
        GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
        and changed it to:
        GRUB_CMDLINE_LINUX_DEFAULT="rootdelay=90 quiet splash"
        rootdelay became longer, but unfortunately it didn’t fix the problem in my case.



        Attempt #2



        I edited /etc/fstab file. I executed the following command in terminal: sudo gedit /etc/fstab and edited fstab file in gedit. In the beginning my file looked like that:



        # /etc/fstab: static file system information.
        #
        # Use 'blkid' to print the universally unique identifier for a
        # device; this may be used with UUID= as a more robust way to name devices
        # that works even if disks are added and removed. See fstab(5).
        #
        # <file system> <mount point> <type> <options> <dump> <pass>
        # / was on /dev/sda1 during installation
        UUID=96889309-5f73-4688-8354-e64cd1bb158f / ext4 errors=remount-ro 0 1
        # swap was on /dev/sda5 during installation
        UUID=480cc3f7-a39d-4d0f-93d5-49fc8df1a392 none swap sw 0 0


        Then, I commented one line and added another one describing /dev/sda1 disk device. Now, my file looks as follows:



        # /etc/fstab: static file system information.
        #
        # Use 'blkid' to print the universally unique identifier for a
        # device; this may be used with UUID= as a more robust way to name devices
        # that works even if disks are added and removed. See fstab(5).
        #
        # <file system> <mount point> <type> <options> <dump> <pass>
        # / was on /dev/sda1 during installation
        UUID=/dev/sda1 / ext4 errors=remount-ro 0 1
        # UUID=96889309-5f73-4688-8354-e64cd1bb158f / ext4 errors=remount-ro 0 1
        # swap was on /dev/sda5 during installation
        UUID=480cc3f7-a39d-4d0f-93d5-49fc8df1a392 none swap sw 0 0


        Problem still existed, so I tried another attempt to solve it.



        Attempt #3



        I opened terminal and typed the following command:



        sudo grub-install /dev/sda


        and then I typed another command to update grub:



        sudo update-grub


        After all of this, I rebooted computer and finally, error disappeared and problem was fixed!






        share|improve this answer






























          1














          I also occurred same problem but I can solve it using following link



          http://blog.wittchen.biz.pl/ubuntu-system-boot-problem/



          Attempt #1



          First, I tried to change rootdelay as error message said. I opened file /etc/default/grub
          I found there the following line:
          GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
          and changed it to:
          GRUB_CMDLINE_LINUX_DEFAULT="rootdelay=90 quiet splash"
          rootdelay became longer, but unfortunately it didn’t fix the problem in my case.



          Attempt #2



          I edited /etc/fstab file. I executed the following command in terminal: sudo gedit /etc/fstab and edited fstab file in gedit. In the beginning my file looked like that:



          # /etc/fstab: static file system information.
          #
          # Use 'blkid' to print the universally unique identifier for a
          # device; this may be used with UUID= as a more robust way to name devices
          # that works even if disks are added and removed. See fstab(5).
          #
          # <file system> <mount point> <type> <options> <dump> <pass>
          # / was on /dev/sda1 during installation
          UUID=96889309-5f73-4688-8354-e64cd1bb158f / ext4 errors=remount-ro 0 1
          # swap was on /dev/sda5 during installation
          UUID=480cc3f7-a39d-4d0f-93d5-49fc8df1a392 none swap sw 0 0


          Then, I commented one line and added another one describing /dev/sda1 disk device. Now, my file looks as follows:



          # /etc/fstab: static file system information.
          #
          # Use 'blkid' to print the universally unique identifier for a
          # device; this may be used with UUID= as a more robust way to name devices
          # that works even if disks are added and removed. See fstab(5).
          #
          # <file system> <mount point> <type> <options> <dump> <pass>
          # / was on /dev/sda1 during installation
          UUID=/dev/sda1 / ext4 errors=remount-ro 0 1
          # UUID=96889309-5f73-4688-8354-e64cd1bb158f / ext4 errors=remount-ro 0 1
          # swap was on /dev/sda5 during installation
          UUID=480cc3f7-a39d-4d0f-93d5-49fc8df1a392 none swap sw 0 0


          Problem still existed, so I tried another attempt to solve it.



          Attempt #3



          I opened terminal and typed the following command:



          sudo grub-install /dev/sda


          and then I typed another command to update grub:



          sudo update-grub


          After all of this, I rebooted computer and finally, error disappeared and problem was fixed!






          share|improve this answer




























            1












            1








            1







            I also occurred same problem but I can solve it using following link



            http://blog.wittchen.biz.pl/ubuntu-system-boot-problem/



            Attempt #1



            First, I tried to change rootdelay as error message said. I opened file /etc/default/grub
            I found there the following line:
            GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
            and changed it to:
            GRUB_CMDLINE_LINUX_DEFAULT="rootdelay=90 quiet splash"
            rootdelay became longer, but unfortunately it didn’t fix the problem in my case.



            Attempt #2



            I edited /etc/fstab file. I executed the following command in terminal: sudo gedit /etc/fstab and edited fstab file in gedit. In the beginning my file looked like that:



            # /etc/fstab: static file system information.
            #
            # Use 'blkid' to print the universally unique identifier for a
            # device; this may be used with UUID= as a more robust way to name devices
            # that works even if disks are added and removed. See fstab(5).
            #
            # <file system> <mount point> <type> <options> <dump> <pass>
            # / was on /dev/sda1 during installation
            UUID=96889309-5f73-4688-8354-e64cd1bb158f / ext4 errors=remount-ro 0 1
            # swap was on /dev/sda5 during installation
            UUID=480cc3f7-a39d-4d0f-93d5-49fc8df1a392 none swap sw 0 0


            Then, I commented one line and added another one describing /dev/sda1 disk device. Now, my file looks as follows:



            # /etc/fstab: static file system information.
            #
            # Use 'blkid' to print the universally unique identifier for a
            # device; this may be used with UUID= as a more robust way to name devices
            # that works even if disks are added and removed. See fstab(5).
            #
            # <file system> <mount point> <type> <options> <dump> <pass>
            # / was on /dev/sda1 during installation
            UUID=/dev/sda1 / ext4 errors=remount-ro 0 1
            # UUID=96889309-5f73-4688-8354-e64cd1bb158f / ext4 errors=remount-ro 0 1
            # swap was on /dev/sda5 during installation
            UUID=480cc3f7-a39d-4d0f-93d5-49fc8df1a392 none swap sw 0 0


            Problem still existed, so I tried another attempt to solve it.



            Attempt #3



            I opened terminal and typed the following command:



            sudo grub-install /dev/sda


            and then I typed another command to update grub:



            sudo update-grub


            After all of this, I rebooted computer and finally, error disappeared and problem was fixed!






            share|improve this answer















            I also occurred same problem but I can solve it using following link



            http://blog.wittchen.biz.pl/ubuntu-system-boot-problem/



            Attempt #1



            First, I tried to change rootdelay as error message said. I opened file /etc/default/grub
            I found there the following line:
            GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
            and changed it to:
            GRUB_CMDLINE_LINUX_DEFAULT="rootdelay=90 quiet splash"
            rootdelay became longer, but unfortunately it didn’t fix the problem in my case.



            Attempt #2



            I edited /etc/fstab file. I executed the following command in terminal: sudo gedit /etc/fstab and edited fstab file in gedit. In the beginning my file looked like that:



            # /etc/fstab: static file system information.
            #
            # Use 'blkid' to print the universally unique identifier for a
            # device; this may be used with UUID= as a more robust way to name devices
            # that works even if disks are added and removed. See fstab(5).
            #
            # <file system> <mount point> <type> <options> <dump> <pass>
            # / was on /dev/sda1 during installation
            UUID=96889309-5f73-4688-8354-e64cd1bb158f / ext4 errors=remount-ro 0 1
            # swap was on /dev/sda5 during installation
            UUID=480cc3f7-a39d-4d0f-93d5-49fc8df1a392 none swap sw 0 0


            Then, I commented one line and added another one describing /dev/sda1 disk device. Now, my file looks as follows:



            # /etc/fstab: static file system information.
            #
            # Use 'blkid' to print the universally unique identifier for a
            # device; this may be used with UUID= as a more robust way to name devices
            # that works even if disks are added and removed. See fstab(5).
            #
            # <file system> <mount point> <type> <options> <dump> <pass>
            # / was on /dev/sda1 during installation
            UUID=/dev/sda1 / ext4 errors=remount-ro 0 1
            # UUID=96889309-5f73-4688-8354-e64cd1bb158f / ext4 errors=remount-ro 0 1
            # swap was on /dev/sda5 during installation
            UUID=480cc3f7-a39d-4d0f-93d5-49fc8df1a392 none swap sw 0 0


            Problem still existed, so I tried another attempt to solve it.



            Attempt #3



            I opened terminal and typed the following command:



            sudo grub-install /dev/sda


            and then I typed another command to update grub:



            sudo update-grub


            After all of this, I rebooted computer and finally, error disappeared and problem was fixed!







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Apr 28 '15 at 13:47

























            answered Apr 28 '15 at 13:38









            user3441273user3441273

            313




            313























                0














                I just randomly started typing stuff... try:



                (initramfs) blkid
                (initramfs) blockdev --rereadpt /dev/sda
                (initramfs) blkid
                (initramfs) exit


                This at least gets you to the desktop where you can begin trouble shooting your problem which is probably due to a proprietary driver or something






                share|improve this answer




























                  0














                  I just randomly started typing stuff... try:



                  (initramfs) blkid
                  (initramfs) blockdev --rereadpt /dev/sda
                  (initramfs) blkid
                  (initramfs) exit


                  This at least gets you to the desktop where you can begin trouble shooting your problem which is probably due to a proprietary driver or something






                  share|improve this answer


























                    0












                    0








                    0







                    I just randomly started typing stuff... try:



                    (initramfs) blkid
                    (initramfs) blockdev --rereadpt /dev/sda
                    (initramfs) blkid
                    (initramfs) exit


                    This at least gets you to the desktop where you can begin trouble shooting your problem which is probably due to a proprietary driver or something






                    share|improve this answer













                    I just randomly started typing stuff... try:



                    (initramfs) blkid
                    (initramfs) blockdev --rereadpt /dev/sda
                    (initramfs) blkid
                    (initramfs) exit


                    This at least gets you to the desktop where you can begin trouble shooting your problem which is probably due to a proprietary driver or something







                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered Mar 16 '13 at 7:35









                    user140700user140700

                    191




                    191























                        0














                        I have got same issue while i'm doing patched for entire system which includes kernel. unfortunately package broken which leads kernel was partially upgrade and corrected.



                        I was scared about issue since where mail server was hosted and data also reside in the same machine.



                        I google it. tried all possible concepts as below.



                        1. Booting with live cd
                        2. doing fsck for / partition and /boot
                        3. grub-install on /dev/sda(which is default root filesystem)
                        4. check fstab


                        And following solve make happy to get boot server.



                        --> note in my case boot is mounted on /boot which is /dev/sda3 where as /dev/sda1

                        / file system.



                        Simple solution to fix the issue(but to cross all module which are install on kernel level




                        1. copy /boot of other server complete /boot excluding grub.cfg to external flash disk


                        2. boot with live cd


                        3. find out root file system with following command
                          fdisk -l /dev/sda


                        4. mount / file system on /mnt
                          mount /dev/sdXY /mnt


                        5. mkdir directory to mount external data
                          mkdir -p /mnt/pd


                        6. mount flash disk data to /mnt/pd


                        7. now it is time to do chages on root file system with chroot command(Please care while doing chages)


                        8. chroot /mnt


                        9. now copy of entire /mnt/pd/boot/ to /mnt


                        10. exit


                        11. now unmout /mnt/pd


                        12. create new folder mkdir -p /mnt/test



                        13. mount /boot on /mnt/test



                          mount /dev/sdXY /mnt/test



                        14. now /boot is mounted on /mnt/test/


                        15. again do chroot /mnt


                        16. rename all file which contains /mnt/test/


                        17. now copy /mnt/boot (which we have copied from pd) to /mnt/test/


                        18. make sure your using original grub.cfg /mnt/test/boot/grub/grub.cfg


                        19. exit


                        20. reboot


                        21. you will be successfully boot to the server without any issues.







                        share|improve this answer








                        New contributor




                        Ramu Nakerikanti is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                        Check out our Code of Conduct.

























                          0














                          I have got same issue while i'm doing patched for entire system which includes kernel. unfortunately package broken which leads kernel was partially upgrade and corrected.



                          I was scared about issue since where mail server was hosted and data also reside in the same machine.



                          I google it. tried all possible concepts as below.



                          1. Booting with live cd
                          2. doing fsck for / partition and /boot
                          3. grub-install on /dev/sda(which is default root filesystem)
                          4. check fstab


                          And following solve make happy to get boot server.



                          --> note in my case boot is mounted on /boot which is /dev/sda3 where as /dev/sda1

                          / file system.



                          Simple solution to fix the issue(but to cross all module which are install on kernel level




                          1. copy /boot of other server complete /boot excluding grub.cfg to external flash disk


                          2. boot with live cd


                          3. find out root file system with following command
                            fdisk -l /dev/sda


                          4. mount / file system on /mnt
                            mount /dev/sdXY /mnt


                          5. mkdir directory to mount external data
                            mkdir -p /mnt/pd


                          6. mount flash disk data to /mnt/pd


                          7. now it is time to do chages on root file system with chroot command(Please care while doing chages)


                          8. chroot /mnt


                          9. now copy of entire /mnt/pd/boot/ to /mnt


                          10. exit


                          11. now unmout /mnt/pd


                          12. create new folder mkdir -p /mnt/test



                          13. mount /boot on /mnt/test



                            mount /dev/sdXY /mnt/test



                          14. now /boot is mounted on /mnt/test/


                          15. again do chroot /mnt


                          16. rename all file which contains /mnt/test/


                          17. now copy /mnt/boot (which we have copied from pd) to /mnt/test/


                          18. make sure your using original grub.cfg /mnt/test/boot/grub/grub.cfg


                          19. exit


                          20. reboot


                          21. you will be successfully boot to the server without any issues.







                          share|improve this answer








                          New contributor




                          Ramu Nakerikanti is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                          Check out our Code of Conduct.























                            0












                            0








                            0







                            I have got same issue while i'm doing patched for entire system which includes kernel. unfortunately package broken which leads kernel was partially upgrade and corrected.



                            I was scared about issue since where mail server was hosted and data also reside in the same machine.



                            I google it. tried all possible concepts as below.



                            1. Booting with live cd
                            2. doing fsck for / partition and /boot
                            3. grub-install on /dev/sda(which is default root filesystem)
                            4. check fstab


                            And following solve make happy to get boot server.



                            --> note in my case boot is mounted on /boot which is /dev/sda3 where as /dev/sda1

                            / file system.



                            Simple solution to fix the issue(but to cross all module which are install on kernel level




                            1. copy /boot of other server complete /boot excluding grub.cfg to external flash disk


                            2. boot with live cd


                            3. find out root file system with following command
                              fdisk -l /dev/sda


                            4. mount / file system on /mnt
                              mount /dev/sdXY /mnt


                            5. mkdir directory to mount external data
                              mkdir -p /mnt/pd


                            6. mount flash disk data to /mnt/pd


                            7. now it is time to do chages on root file system with chroot command(Please care while doing chages)


                            8. chroot /mnt


                            9. now copy of entire /mnt/pd/boot/ to /mnt


                            10. exit


                            11. now unmout /mnt/pd


                            12. create new folder mkdir -p /mnt/test



                            13. mount /boot on /mnt/test



                              mount /dev/sdXY /mnt/test



                            14. now /boot is mounted on /mnt/test/


                            15. again do chroot /mnt


                            16. rename all file which contains /mnt/test/


                            17. now copy /mnt/boot (which we have copied from pd) to /mnt/test/


                            18. make sure your using original grub.cfg /mnt/test/boot/grub/grub.cfg


                            19. exit


                            20. reboot


                            21. you will be successfully boot to the server without any issues.







                            share|improve this answer








                            New contributor




                            Ramu Nakerikanti is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                            Check out our Code of Conduct.










                            I have got same issue while i'm doing patched for entire system which includes kernel. unfortunately package broken which leads kernel was partially upgrade and corrected.



                            I was scared about issue since where mail server was hosted and data also reside in the same machine.



                            I google it. tried all possible concepts as below.



                            1. Booting with live cd
                            2. doing fsck for / partition and /boot
                            3. grub-install on /dev/sda(which is default root filesystem)
                            4. check fstab


                            And following solve make happy to get boot server.



                            --> note in my case boot is mounted on /boot which is /dev/sda3 where as /dev/sda1

                            / file system.



                            Simple solution to fix the issue(but to cross all module which are install on kernel level




                            1. copy /boot of other server complete /boot excluding grub.cfg to external flash disk


                            2. boot with live cd


                            3. find out root file system with following command
                              fdisk -l /dev/sda


                            4. mount / file system on /mnt
                              mount /dev/sdXY /mnt


                            5. mkdir directory to mount external data
                              mkdir -p /mnt/pd


                            6. mount flash disk data to /mnt/pd


                            7. now it is time to do chages on root file system with chroot command(Please care while doing chages)


                            8. chroot /mnt


                            9. now copy of entire /mnt/pd/boot/ to /mnt


                            10. exit


                            11. now unmout /mnt/pd


                            12. create new folder mkdir -p /mnt/test



                            13. mount /boot on /mnt/test



                              mount /dev/sdXY /mnt/test



                            14. now /boot is mounted on /mnt/test/


                            15. again do chroot /mnt


                            16. rename all file which contains /mnt/test/


                            17. now copy /mnt/boot (which we have copied from pd) to /mnt/test/


                            18. make sure your using original grub.cfg /mnt/test/boot/grub/grub.cfg


                            19. exit


                            20. reboot


                            21. you will be successfully boot to the server without any issues.








                            share|improve this answer








                            New contributor




                            Ramu Nakerikanti is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                            Check out our Code of Conduct.









                            share|improve this answer



                            share|improve this answer






                            New contributor




                            Ramu Nakerikanti is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                            Check out our Code of Conduct.









                            answered yesterday









                            Ramu NakerikantiRamu Nakerikanti

                            1




                            1




                            New contributor




                            Ramu Nakerikanti is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                            Check out our Code of Conduct.





                            New contributor





                            Ramu Nakerikanti is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                            Check out our Code of Conduct.






                            Ramu Nakerikanti is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                            Check out our Code of Conduct.






























                                draft saved

                                draft discarded




















































                                Thanks for contributing an answer to Ask Ubuntu!


                                • 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%2faskubuntu.com%2fquestions%2f247541%2fgave-up-waiting-for-root-device-on-ubuntu%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

                                數位音樂下載

                                When can things happen in Etherscan, such as the picture below?

                                格利澤436b