Arch Linux

$p00ky

Member

Registered: 2010-03-23

Posts: 7

Re: Grub can't find root device after system update today (12/30)

Dear all,

I have a similar problem installing ArchLinux on my USB.

The booting fails on "Waiting 10 seconds for device /dev/disk/by-uuid/4b8c3014-beaa-4f29-a30d-8c460e448b88"

My /boot/menu.lst is as follows:

timeout   5
default   0
color light-blue/black light-cyan/blue

# (0) Arch Linux 
title  ArchBang Linux
#root   (hd0,0)
kernel /vmlinuz26 root=/dev/disk/by-uuid/4b8c3014-beaa-4f29-a30d-8c460e448b88 ro
initrd /kernel26.img

# (1) Arch Linux
title  ArchBang Linux Fallback
#root   (hd0,0)
kernel /vmlinuz26 root=/dev/disk/by-uuid/4b8c3014-beaa-4f29-a30d-8c460e448b88 ro
initrd /kernel26-fallback.img

/etc/fstab:

unionfs                /             unionfs   noauto              0      0
none                   /dev/pts      devpts    defaults            0      0
none                   /dev/shm      tmpfs     defaults            0      0
tmpfs               /tmp         tmpfs     defaults           0      0

auto,noatime,users,suid,dev,exec,quiet,umask=0,check=s,shortname=mixed 0 0 # AutoUpdate
UUID=2e73ef45-e04b-4233-bc88-e19374f968b1 /home ext4 defaults 0 1
UUID=4b8c3014-beaa-4f29-a30d-8c460e448b88 / ext4 defaults 0 1
UUID=4dd44191-3505-423e-a346-01033dfccac9 swap swap defaults 0 0
UUID=c51b4939-25eb-46ae-be8b-637cab37d0c0 /boot ext2 defaults 0 1

After the 10 seconds waiting, a command prompt shows up.
I can see only "/dev/sdaX" is mounted, which is my local hard drive.
The USB key has not been mounted so the boot cannot work.

When I boot on my local hard drive (Fedora  12 x64) I can see the UUID is right:

# blkid
/dev/sdb1: UUID="c51b4939-25eb-46ae-be8b-637cab37d0c0" TYPE="ext2" 
/dev/sda1: LABEL="System Reserved" UUID="F0B0148FB0145F02" TYPE="ntfs" 
/dev/sda2: LABEL="" UUID="780416DE04169EE6" TYPE="ntfs" 
/dev/sda3: UUID="502b2e9b-f938-4dda-bdad-ded9ddb32dc0" TYPE="ext4" 
/dev/sda5: UUID="TB5gFN-95Lx-xIr5-NbI7-CIYC-89hs-jSX8Ez" TYPE="LVM2_member" 
/dev/mapper/VolGroup-lv_root: LABEL="Fedora-12-x86_64" UUID="8bbb446f-4304-4b7e-8daf-1dc28f219113" TYPE="ext4" 
/dev/mapper/VolGroup-lv_swap: UUID="b026521e-cf5b-4689-ad06-a66ec08003f6" TYPE="swap" 
/dev/sdb2: UUID="4dd44191-3505-423e-a346-01033dfccac9" TYPE="swap" 
/dev/sdb3: UUID="4b8c3014-beaa-4f29-a30d-8c460e448b88" TYPE="ext4" 
/dev/sdb4: UUID="2e73ef45-e04b-4233-bc88-e19374f968b1" TYPE="ext4"

Do you have an idea where is the problem from?

I noticed that my USB keyboard is not mounted anymore after starting the boot  whereas it works fine when I am in the boot selection menu....
I'm wondering if 10 seconds is not just too short to wait for the USB key to be mounted.
Is it possible that a longer timeout can make it work? If so, how can I tell it to wait longer, let say 20 seconds?

(I had a timeout problem booting on the live-usb (archbang), it didn't work when I was waiting 5 seconds, but it worked when I put 15 seconds)

Last edited by $p00ky (2010-03-23 09:31:14)

$p00ky

Member

Registered: 2010-03-23

Posts: 7

Re: Grub can't find root device after system update today (12/30)

Picture of the problem:

Last edited by $p00ky (2010-03-30 06:08:29)

Kaso_Da_Zmok

Member

Registered: 2007-11-01

Posts: 19

Re: Grub can't find root device after system update today (12/30)

i got the same problem after upgrading to 2.6.34 from testing today.

The resolution was to remove autodetect from HOOKS and regenerate the initrd which will generate the full image.

boot your system with fallback kernel if possible, if not boot with install CD or USB and chroot to your system, edit the

 /etc/mkinitcpio.conf

and remove the
autodetect
from the HOOKS

HOOKS="base udev pata scsi sata filesystems"
\

and

mkinitcpio -p kernel26

reboot and let me know if it worked.

$p00ky

Member

Registered: 2010-03-23

Posts: 7

Re: Grub can't find root device after system update today (12/30)

Thank you for your reply.

Unfortunately, I don't have the system on the USB key anymore (I quit and installed on local hard drive).
I'm kind of busy recently but I'll do the steps again and tell you if your fix works.