Hello Georg, Please let's try to keep CC to the bug report, so others can see.
2011/8/24 Georg Gast <schorsch...@gmx.de>: > Am 23.08.2011 21:53, schrieb Hector Oron: >> >> Hello Georg, >> >> 2011/8/23 Georg Gast<schorsch...@gmx.de>: >> >>> linux-image-2.6.38-bpo2-amd64 is able to boot from my VG >>> "/dev/Desktop/root" >>> but linux-image-3.0.0-1-amd64 is not able to boot from this VG. >>> >>> I upgraded today my squeeze to wheezy and let the 2.6.38 kernel >>> installed. >>> >>> grub 1.99 >> >> Could you please provide more information? Error message or some way >> to reproduce this behaviour. Why do you think is lvm2 related? >> >> With best regards, > > Hello Hector, > today i tried a fresh installation of wheezy in a kvm. I named my VG Desktop > and made a minimal debian system installation. The kvm system did boot in > this constellation. > > All i know for sure (until now) is, that linux 3.0.0-1-amd64 is not able to > boot from my VG and 2.6.38-bpo is able to boot from the very same > hardware/installation. The grub2 parameters are the same (except the kernel > name). > > Error message with linux 3.0.0: > > -------------- > Begin: waiting for root file system ... done > 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/Desktop-root does not exist. Dropping to a shell! > -------------- > > Yes, the system did wait long enough. > Yes, the module 3w_9xxx is present in the initrd (cat /proc/modules) > Yes, the device is present (ls /dev/sda1) > Yes, the root device name is right (/dev/mapper/Desktop-root) > > The commandline for the kernel was: > BOOT_IMAGE=/vmlinuz-3.0.0-1-amd64 root=/dev/mapper/Desktop-root ro single This line hints your root filesystem was booting into read-only single mode. Likely root filesystem needed fsck. > Things to note: > The difference between the two scenarios seems to me, that my "real hard > disk VG" is relativly old and was originally installed with lenny. I think > it might be a problem with migration from the "old lenny/squeeze" VG to the > new wheezy VG. > > Dont know what happened: Today after the second try to boot the linux-3.0.0 > it did finally work. So, it's the problem away? can we close the bug? > I made a photo of the error message and attached it. > > Best regards > Georg Gast > > > > -- Héctor Orón -.. . -... .. .- -. -.. . ...- . .-.. --- .--. . .-. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org