WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

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

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] xen on suse 9.3 and software raid
From: Robbie Dinn <robbie@xxxxxxxxxxxx>
Date: Fri, 29 Apr 2005 09:42:41 +0100
Cc: "John M. Johnson III" <johnsonj@xxxxxxxxx>
Delivery-date: Fri, 29 Apr 2005 08:42:23 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <Pine.LNX.4.58.0504262344130.23086@xxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <Pine.LNX.4.58.0504262344130.23086@xxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040906
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-2.6.11.4-20a-xen | 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 2.6.11.4-20a-default
                                                         ^^^^^^^
drwxr-xr-x  3 root root 4096 Apr 29 09:36 2.6.11.4-20a-xen
paradox:/tmp/initrd-tree # grep -r raid1 init
echo "Loading /lib/modules/2.6.11.4-20a-default/kernel/drivers/md/raid1.ko"
insmod /lib/modules/2.6.11.4-20a-default/kernel/drivers/md/raid1.ko
                                   ^^^^^^^
echo "Loading kernel/drivers/md/raid1.ko"
insmod /lib/modules/2.6.11.4-20a-xen/kernel/drivers/md/raid1.ko
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
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users