Page 2 of 2 FirstFirst 12
Results 11 to 16 of 16

Thread: Clean install boot fails - Gave up waiting for root device

  1. #11
    Join Date
    Oct 2005
    Beans
    131

    Re: Clean install boot fails - Gave up waiting for root device

    I am having this problem on an old laptop with a Promise controller.

    Worked fine with 11.10 but a new install of 12.04 lost both the drive and the touchpad. (multiple monitors on the laptop also doesn't work, neither does the all-in-one HP fax)

    One suggestion I have seen is to add the module name needed to /etc/initramfs-toos/modules and then run update-initramfs - I had problems with that probably because of the dev, proc, and sys binding so will have to give it another shot.

    thanks for the bug link. Precise is looking to be quite a regression for me at this point. (but I learn a lot trying to figure these things out!)

  2. #12
    Join Date
    Apr 2012
    Location
    Phoenix, Arizona
    Beans
    166
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: Clean install boot fails - Gave up waiting for root device

    I used the workarounds from the bug report to get up and running on 12.04; it took a bit of work but now everything works smoothly for me. Hopefully it will be the same for you.

  3. #13
    Join Date
    May 2012
    Beans
    3

    Re: Clean install boot fails - Gave up waiting for root device

    I may be having the same issue as you, but when I attempted to perform the fix by editing /usr/share/initramfs-tools/scripts/local-top/dmraid, I get down to the scripts directory and find no directory within named local-top.

    Did dmraid move in 12.04?

  4. #14
    Join Date
    Apr 2012
    Location
    Phoenix, Arizona
    Beans
    166
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: Clean install boot fails - Gave up waiting for root device

    I don't know. It was still there when I resolved the problem on 12.04 beta 2, and I've installed all the updates so I should be running code pretty much identical to 12.04 release. Here is the contents of my scripts directory:
    Code:
    root@reptoid:/usr/share/initramfs-tools/scripts# ls
    functions    init-premount  local         local-premount  nfs      panic
    init-bottom  init-top       local-bottom  local-top       nfs-top
    root@reptoid:/usr/share/initramfs-tools/scripts# uname -a
    Linux reptoid 3.2.0-24-generic #37-Ubuntu SMP Wed Apr 25 08:43:22 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
    root@reptoid:/usr/share/initramfs-tools/scripts#
    When you fall into the initramfs shell, can you recover by typing
    Code:
    dmraid -ay
    followed by 'exit'? You might be having more severe problems than what I experienced.

  5. #15
    Join Date
    Mar 2013
    Beans
    13

    Re: Clean install boot fails - Gave up waiting for root device

    I was having this same problem, but only on computers with 2 hard drives. If the computer only had 1 hard drive there was no problem.

    I figured out, mostly by luck, that if I installed 10.04 and then did an in place upgrade to 12.04 the problem went away. I don't know why, but it did.

    Source: http://www.itfromscratch.com/ubuntu-...or-workaround/

  6. #16
    Join Date
    Apr 2013
    Beans
    1

    Re: Clean install boot fails - Gave up waiting for root device

    I had a similar problem last night when I upgraded to 12.04 LTS. Specifically, it said:
    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/mapper/isw_cafgghefcf_Volume01 does not exist. Dropping to a shell!
    The /dev/mapper directory had new device names for the old system partitions (Volume01 changed to Volume0p1!). Some of the other posts I ran across here helped me get an idea about how to solve it.

    Here's what I did:
    In the emergency shell, create a /mnt directory and mount the old root:
    $:> mount /dev/mapper/isw_cafgghefcf_Volume0p1 /mnt

    Then mount the virtual system directories:
    $:> mount --bind /proc /mnt/proc
    $:> mount --bind /dev /mnt/dev
    $:> mount --bind /sys /mnt/sys

    And change to your real system:
    $:> chroot /mnt

    (Here you can back up your files if you're worried and haven't done that yet)

    Fix the boot issue:
    $:> vi /boot/grub/menu.lst

    In menu.lst, change the occurrences of the missing volumes to be the actual volumes found in /dev/mapper for both the root and the swap partitions.

    $:> exit
    $:> umount /mnt/sys
    $:> umount /mnt/dev
    $:> umount /mnt/proc
    $:> umount /mnt

    Reboot the system and you're back up and running!

    If you aren't going to do anything but change the devices in menu.lst you don't have to go through the mounting of the system directories or the chroot, just mount your root filesystem and edit the menu.lst file (you won't have vi though unless you chroot).
    Last edited by Homechicken; April 5th, 2013 at 06:11 PM.

Page 2 of 2 FirstFirst 12

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •