Hello! Low-res pictures are on <http://www.thomas.schwinge.homeip.net/tmp/xen/>. Sorry, I don't have anything better at the moment, but I'll explain them below. On Tue, Oct 27, 2009 at 11:55:33PM +0100, Bastian Blank wrote: > On Tue, Oct 27, 2009 at 11:15:13PM +0100, Thomas Schwinge wrote: > > At this point, nothing is mounted on /root -- it's supposed to be an ext3 > > filesystem based on a LVM LV. And the very strange thing is that > > /dev/mapper/ does contain only one LV device, and that is the swap LV > > (254,0), but not the root filessystem one. > > Please provide the complete log and the bootloader config. GRUB2: menuentry "Xen 3.4, Debian GNU/Linux, Linux 2.6.31-1-xen-amd64" { insmod lvm insmod ext2 set root=(vg0-boole-root) search --no-floppy --fs-uuid --set 54ccee0d-3455-43dc-af2e-e2bb3940776a multiboot /boot/xen-3.4-amd64.gz noreboot module /boot/vmlinuz-2.6.31-1-xen-amd64 root=/dev/mapper/vg0-boole--root ro module /boot/initrd.img-2.6.31-1-xen-amd64 } 03.jpg, 07.jpg: Dropped into the BusyBox shell. 08.jpg, 09.jpg: mount output (nothing on /root); ls -l /dev/mapper/ (only control and vg0-boole--swap (254,0)); lvm vgchange -ay; ls -l /dev/mapper/ (control, vg0-boole--data (254,2), vg0-boole--root (254,1), vg0-boole--swap (254,0). > > If I manually run ``lvm > > vgchange -ay'' the missing LVs appear, root (254,1) and data (254,2). > > How would I manually resume the booting process from here? > > mount $dev /root > CTRL-D > > should do it. 10.jpg: fstype vg0-boole-root (ext3); mount /dev/mapper/vg0-boole--root /root (failed -- no such file or directory?!). > > The exactly same arrangement boots without any problems with a non-Xen > > kernel. This is a up-to-date Debian testing, by the way. Help? > > I doubt that. 11.jpg: successful boot without Xen; here the device number are different: vg0-boole--data (254,2), vg0-boole--root (254,0), vg0-boole--swap (254,1) -- root has minor zero instead of one, and swap vice versa?! Regards, Thomas
Attachment:
signature.asc
Description: Digital signature