[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] xen on suse 9.3 and software raid

John M. Johnson III wrote:
Has anyone had issues starting xen0 on a md? I have installed it a few times now w/ and w/o raid. Anytime I have a raid1 mirror, Xen panics on boot when trying to mount /.
It gets past waiting for /dev/md0 to appear.

Yes, I am seeing this too.

I believe the initrd is broken, or rather the /sbin/mkinitrd shell
script that generates /boot/initrd-xxxx is broken.

here is what I mean

Robbie's shell session>
paradox:~ # cd /tmp
paradox:/tmp # mkdir initrd-tree
paradox:/tmp # cd initrd-tree/
paradox:/tmp/initrd-tree # cat /boot/initrd- | gunzip | cpio -i
8668 blocks
paradox:/tmp/initrd-tree # ls
.   bin  etc     init  proc  run_init  sys  var
..  dev  events  lib   root  sbin      tmp
paradox:/tmp/initrd-tree # ls -l lib/modules/
total 16
drwxr-xr-x  4 root root 4096 Apr 29 09:36 .
drwxr-xr-x  4 root root 4096 Apr 29 09:36 ..
drwxr-xr-x  3 root root 4096 Apr 29 09:36
drwxr-xr-x  3 root root 4096 Apr 29 09:36
paradox:/tmp/initrd-tree # grep -r raid1 init
echo "Loading /lib/modules/"
insmod /lib/modules/
echo "Loading kernel/drivers/md/raid1.ko"
insmod /lib/modules/
paradox:/tmp/initrd-tree #

I see two trees of kernel modules for both the -default and -xen
kernels and it appears that the init shell script is loading up the
modules for the wrong kernel (i.e -xen kernel, -default modules !)

I don't know how to fix mkinitrd, but I am going to try to fix up
the initrd image by hand. delete the extraneous modules and edit
the init script to load just the -xen modules.

I'll reply when I find out if this helps or not.

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.