Bugzilla – Bug 548642
root=LABEL=xyzzy boot configuration broken (initrd udev problem ?)
Last modified: 2009-10-26 16:27:54 UTC
after update from 11.1 to 11.2 RC2 via DVD the system does not boot correctly anymore. it tries "manual resume" which fails and then can't access the root file system and waits for the user pressing ENTER to continue boot :-( this is from boot.msg: <6>[ 104.101360] fuse init (API version 7.12) Kernel logging (ksyslog) stopped. Kernel log daemon terminating. Boot logging started on /dev/char/../tty1(/dev/console) at Wed Oct 21 02:26:33 2009 WARNING: All config files need .conf: /etc/modprobe.d/module-renames, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/peak, it will be ignored in a future release. 5 logical volume(s) in volume group "system" now active Trying manual resume from /dev/sda7 Invoking userspace resume from /dev/sda7 resume: libgcrypt version: 1.4.4 Trying manual resume from /dev/sda7 Invoking in-kernel resume from /dev/sda7 Waiting for device /dev/root to appear: ..............................Could not find /dev/root. Want me to fall back to /dev/block/253:4? (Y/n) Waiting for device /dev/block/253:4 to appear: ok fsck from util-linux-ng 2.16 [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/dm-4 root2: recovering journal root2: Clearing orphaned inode 534100 (uid=1000, gid=100, mode=0100600, size=0) root2: clean, 714656/1966080 files, 5784231/7864320 blocks fsck succeeded. Mounting root device read-write. Mounting root /dev/block/253:4 mount -o rw,acl,user_xattr -t ext3 /dev/block/253:4 /root Boot logging started on /dev/char/../tty1(/dev/console) at Wed Oct 21 08:27:33 2009 and here is the grub entry ###Don't change this comment - YaST2 identifier: Original name: linux### title Desktop -- openSUSE 11.2 RC 1 - 2.6.31.3-1 root (hd0,5) kernel /vmlinuz-2.6.31.3-1-desktop root=LABEL=root2 resume=/dev/sda7 splash=silent crashkernel=256M-:128M@16M showopts vga=0x37d initrd /initrd-2.6.31.3-1-desktop
11.2 breaks root=LABEL=xyzzy boot configuration :-( (In reply to comment #0) > it tries "manual resume" which fails and then can't access the root file system > and waits for the user pressing ENTER to continue boot :-( > > this is from boot.msg: > Waiting for device /dev/root to appear: ..............................Could not > find /dev/root. > Want me to fall back to /dev/block/253:4? (Y/n) last night I did a lot of initrd tracing, here more details: I use root=LABEL=root2 on boot command line (which works fine with 10.* to 11.1) which triggers the problem. with root=/dev/mapper/system-root2 11.2 RC1 boots fine. my rootfs is a LVM (thus /dev/mapper/system-root2) there is the "set -x" trace from initrd boot/03-storage.sh "working": +++ . /config/mount.sh ++++ '[' /dev/block/253:4 ']' ++++ '[' '' ']' ++++ rootfsck=/sbin/fsck.ext3 +++ '[' /dev/mapper/system-root2 ']' +++ rootdev=/dev/mapper/system-root2 +++ '[' '' ']' +++ '[' /dev/sda7 ']' +++ resumedev=/dev/sda7 +++ '[' '' ']' +++ case $rootdev in and "broken" with root=LABEL=root2 +++ . /config/mount.sh ++++ '[' /dev/block/253:4 ']' ++++ '[' '' ']' ++++ rootfsck=/sbin/fsck.ext3 +++ '[' LABEL=root2 ']' +++ rootdev=LABEL=root2 +++ '[' '' ']' +++ '[' /dev/sda7 ']' +++ resumedev=/dev/sda7 +++ '[' '' ']' +++ case $rootdev in +++ label=root2 +++ echo 'ENV{ID_FS_USAGE}=="filesystem|other", ENV{ID_FS_LABEL_SAFE}=="root2", SYMLINK+="root"' +++ rootdev=/dev/root so the real problem is that udev doesn't create the missing /dev/root symlink which boot/83-mount.sh is waiting for "forever". can you give me some hints how to debug this further and/or give more details ? I'm not very familar with udev, so I don't have a good clue right now...
What's the content of /dev/disk/by-label/ when it fails? Does a link with the expected label exist? If not, did it exist in older releases?
(In reply to comment #2) > What's the content of /dev/disk/by-label/ when it fails? Does a link with the > expected label exist? If not, did it exist in older releases? right now I only have the output of "ls -l" in 61-lvm2.sh in my logs which looks ok: /dev/disk/by-label: total 0 lrwxrwxrwx 1 root root 10 Oct 22 02:55 VMs -> ../../dm-3 lrwxrwxrwx 1 root root 10 Oct 22 02:55 boot -> ../../sda5 lrwxrwxrwx 1 root root 10 Oct 22 02:55 boot2 -> ../../sda6 lrwxrwxrwx 1 root root 10 Oct 22 02:55 root -> ../../dm-1 lrwxrwxrwx 1 root root 10 Oct 22 02:55 root2 -> ../../dm-4 lrwxrwxrwx 1 root root 10 Oct 22 02:55 swap -> ../../sda7 /dev/system/: total 0 lrwxrwxrwx 1 root root 23 Oct 22 02:55 home -> /dev/mapper/system-home lrwxrwxrwx 1 root root 25 Oct 22 02:55 iscsi1 -> /dev/mapper/system-iscsi1 lrwxrwxrwx 1 root root 25 Oct 22 02:55 iscsi2 -> /dev/mapper/system-iscsi2 lrwxrwxrwx 1 root root 23 Oct 22 02:55 root -> /dev/mapper/system-root lrwxrwxrwx 1 root root 24 Oct 22 02:55 root2 -> /dev/mapper/system-root2
ok, thanks. looks like an initramfs issue then.
Yes, a known problem. *** This bug has been marked as a duplicate of bug 483136 ***