Arch Linux

Full Null

Member

Registered: 2008-10-30

Posts: 6

Boot by UUID problem

Hi!
I'm have a problem with booting by UUID because symlink in /dev/disk/by-uuid to root device not created before/after booting. Symlinks to other partitions are exists.
Of course, while i'm trying to boot with root=/dev/disk/by-uuid i see "Kernel Panic. Can't find boot device /dev/disk/by-uuid/{UUID}". How to fix it?

Here are my configuration files /boot/grub/menu.lst and /etc/fstab

title  Arch Linux
root   (hd0,0)
kernel /boot/vmlinuz26 vga=795 root=/dev/sdb1 ro quiet
initrd /boot/kernel26.img

# <file system>        <dir>         <type>    <options>          <dump> <pass>
none                   /dev/pts      devpts    defaults            0      0
none                   /dev/shm      tmpfs     defaults            0      0


/dev/cdrom /media/cdrom   auto    ro,user,noauto,unhide   0      0
/dev/dvd /media/dvd   auto    ro,user,noauto,unhide   0      0
UUID=7fc76e01-7c0d-4725-8f2d-b642ad0bd514 / reiserfs defaults 0 1
/dev/sdb2 /home ext4 defaults 0 0

Sorry for my bad english

Wintervenom

Member

Registered: 2008-08-20

Posts: 1,011

Re: Boot by UUID problem

If you're booting off of a USB device, you might want to try adding rootdelay=5 to the kernel parameters, and see if that works.

If not, then does it work to mount it by label?  (If you haven't set a label, tune2fs -L whatever_you_want_to_name_it /dev/sdb1 (assuming you're using Ext[2-4]), then replace UUID=7fc76e01-7c0d-4725-8f2d-b642ad0bd514 with LABEL=whatever_you_named_it and root=/dev/sdb1 with root=/dev/disk/by-label/whatever_you_named_it.)  If that doesn't work, you probably need to check your mkinitcpio.conf and regenerate your initrd.

Last edited by Wintervenom (2009-01-09 00:36:02)

Full Null

Member

Registered: 2008-10-30

Posts: 6

Re: Boot by UUID problem

hmm i'm create label on /dev/sdb1 as "ROOTFS", set root device in grub, but directory /dev/disk/by-label not exists, even after system booting....
i'm think too what problem in initrd, even recreated it, but it not helps

It is my mkinitcpio.conf

MODULES=""
BINARIES=""
FILES=""
HOOKS="base autodetect udev scsi sata keymap filesystems"

Last edited by Full Null (2009-01-09 01:20:08)

.:B:.

Forum Fellow

Registered: 2006-11-26

Posts: 5,819

Website

Re: Boot by UUID problem

Your GRUB has to list the UUID, otherwise it's pretty much useless. You can't just update your fstab and leave your menu.lst untouched .

Also - if there is nothing in /dev/disk/by-uuid/, how did you get the value for your root partition then? It's kind of a catch 22...

---

Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy

Full Null

Member

Registered: 2008-10-30

Posts: 6

Re: Boot by UUID problem

Today i'm tried to reinstall GRUB and /dev/disk/by-label was created while booting the system. But in this directory not created symlink to root device, only to home. I'm think it's problem in GRUB?

Wintervenom

Member

Registered: 2008-08-20

Posts: 1,011

Re: Boot by UUID problem

hmm i'm create label on /dev/sdb1 as "ROOTFS", set root device in grub, but directory /dev/disk/by-label not exists, even after system booting....
i'm think too what problem in initrd, even recreated it, but it not helps

It is my mkinitcpio.conf

MODULES=""
BINARIES=""
FILES=""
HOOKS="base autodetect udev scsi sata keymap filesystems"

Try setting your HOOKS to:

HOOKS="base udev autodetect pata scsi sata keymap filesystems"

Last edited by Wintervenom (2009-01-09 18:33:24)

Full Null

Member

Registered: 2008-10-30

Posts: 6

Re: Boot by UUID problem

Try setting your HOOKS to:

HOOKS="base udev autodetect pata scsi sata keymap filesystems"

I'm tried but it not helps.
Today i'm converted root fs to ext4 and now i'm don't have problem
I'm think, problem was in reiserfs partition