Artur Linhart - Linux communication
2007-May-29 18:45 UTC
[Xen-users] Problem with xen boot if DOM0 is on the LVM, which is on RAID
Hello,
I have problems with booting with the new Xen (used the binary
tarball) v. 3.1.0.
I have installed following system:
One small raid partition with Ext3 fs with the boot directorz and grub
installed
Two large and one small mirrored raid1 partitions managed by mdadm and used
as 3 physical volumes for LVM, all 3 joined into one volume group.
Planned dom0 system is installed on the logical volume, which is striped
over md1 and md3 raid phzsical volumes. It is Ubuntu server 7.04.
The Ubuntu system self boots ad behaves normally.
If booting Xen, the boot process comes to the point where the raid arrays
are beeing initialized. The RAID arrays itself are initialized and activated
correctly. After it happens, the system hangs for some minutes and then the
message comes:
Check root= bootarg cat /proc/cmdline
or missing modules, devices: cat /proc/modules ls /dev
ALERT! /dev/mapper/VG_HIGHLAND_SYSTEM-LV_DOM0 does not exist. Dropping to
shell!
... and the sh is invoked, the tty cannot be accessed, so the job control is
turned off.
I looked into /devúmapper and really, thre is no VG_HIGHLAND_SYSTEM volume
group, which appears there if booting the Ubuntu server.
I am not very skilled in the work with LVM, so the only thing what came into
my mind was - it looks like if the default binary tarball of Xen 3.1.0 has
not turned on the LVM support in the kernel, but I think this is not
possible, because LVM is normally used.
Or would it be the solution to configure and compile the kernel from source?
Does somebody some other idea, why the volume group is not recogized and
cannot be found in /dev/mapper ?
The logical partitions also are invisible in the result of cat
/proc/partitions
Thank You very much in advance for any advice or
help...
With best regards, Archie
P.S. In
http://groups.google.cz/group/linux.debian.bugs.dist/browse_thread/thread/ea
fa7a66782c206e/630c5180caa580dd?lnk=st
<http://groups.google.cz/group/linux.debian.bugs.dist/browse_thread/thread/e
afa7a66782c206e/630c5180caa580dd?lnk=st&q=ALERT!+%2Fdev%2Fmapper%2FVG+does+n
ot+exist.+Dropping+to+shell!&rnum=1&hl=cs#630c5180caa580dd>
&q=ALERT!+%2Fdev%2Fmapper%2FVG+does+not+exist.+Dropping+to+shell!&rnum=1&hlcs#630c5180caa580dd
I found the idea this is some error in GRUB script, but I do not know if it
is my case - GRUB configuration file "menu.lst" looks like:
title Xen 3.1.0, kernel 2.6.18-xen /dev/sda1
root (hd0,0)
kernel /xen-3.1.0.gz dom0_mem=192M
module /vmlinuz-2.6.18-xen root=/dev/mapper/VG_HIGHLAND_SYSTEM-LV_DOM0 ro
max_loop=255 console=tty0
module /initrd.img-2.6.18-xen
and the working Ubuntu server boot-configuration looks like
title Ubuntu 7.04 server, kernel 2.6.20-15-server /dev/sda1
root (hd0,0)
kernel /vmlinuz-2.6.20-15-server
root=/dev/mapper/VG_HIGHLAND_SYSTEM-LV_DOM0 ro console=tty0
initrd /initrd.img-2.6.20-15-server ro splash
Unfortunatelly I cannot get to the log because there is nothing written to
the logfiles because the system partition cannot be mounted... etc.
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Vladislav Kurz
2007-May-30 08:08 UTC
Re: [Xen-users] Problem with xen boot if DOM0 is on the LVM, which is on RAID
On Tuesday 29 May 2007 20:45, Artur Linhart - Linux communication wrote:> Hello, > > > > I have problems with booting with the new Xen (used the binary > tarball) v. 3.1.0. > > > > I have installed following system: > > One small raid partition with Ext3 fs with the boot directorz and grub > installed > > Two large and one small mirrored raid1 partitions managed by mdadm and used > as 3 physical volumes for LVM, all 3 joined into one volume group. > > Planned dom0 system is installed on the logical volume, which is striped > over md1 and md3 raid phzsical volumes. It is Ubuntu server 7.04. > > The Ubuntu system self boots ad behaves normally. >I have similar configuration without any problems: Debian etch + xen 3.0.3 /boot of dom0 on (hardware) raid1 + ext3 root of dom0 & everything else on raid1 + lvm + ext3 I use xen kernel provided by debian> > If booting Xen, the boot process comes to the point where the raid arrays > are beeing initialized. The RAID arrays itself are initialized and > activated correctly. After it happens, the system hangs for some minutes > and then the message comes: > > > > Check root= bootarg cat /proc/cmdline > > or missing modules, devices: cat /proc/modules ls /dev > > ALERT! /dev/mapper/VG_HIGHLAND_SYSTEM-LV_DOM0 does not exist. Dropping to > shell! > > > > > ... and the sh is invoked, the tty cannot be accessed, so the job control > is turned off. > > I looked into /devúmapper and really, thre is no VG_HIGHLAND_SYSTEM volume > group, which appears there if booting the Ubuntu server. >Check if there is something else in /dev/mapper> > > I am not very skilled in the work with LVM, so the only thing what came > into my mind was - it looks like if the default binary tarball of Xen > 3.1.0 has not turned on the LVM support in the kernel, but I think this is > not possible, because LVM is normally used. > > Or would it be the solution to configure and compile the kernel from > source?before compiling your own, compare the configuration of ubuntu ditstro kernel, and xen kernel, expecially CONFIG_MD_* and CONFIG_DM_* options, to find if there is support for LVM. If the support for LVM is in your xen kernel, then check the contents of initrd if there are scripts that activate the logical volume i.e. /sbin/vgchange, /scripts/*/lvm Anyway even if you compile your own kernel you might need initrd to activate LVM.> I found the idea this is some error in GRUB script, but I do not know if it > is my case - GRUB configuration file "menu.lst" looks like: > > > > title Xen 3.1.0, kernel 2.6.18-xen /dev/sda1 > root (hd0,0) > kernel /xen-3.1.0.gz dom0_mem=192M > module /vmlinuz-2.6.18-xen root=/dev/mapper/VG_HIGHLAND_SYSTEM-LV_DOM0 > ro max_loop=255 console=tty0 > module /initrd.img-2.6.18-xen >This is OK, I have similar config -- Regards Vladislav Kurz _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Artur Linhart - Linux communication
2007-May-30 14:44 UTC
RE: [Xen-users] Problem with xen boot if DOM0 is on the LVM, which is on RAID
Hello, Thanks for response :-) I verified the kernel configurations, they are different - sure - but in the area of the MD/LVM this is very similar (the only difference is, the Xen kernel has for CONFIG_BLK_DEV_MD the value "y", by the Ubuntu default kernel it is the value "m"), so it''s looks for me like this is rather not the problem I have... Or what do You think? In the /dev/mapper directory is only 1 character device with the name "control" After the system comes in the state described below, there is such a " prompt" (initramfs) And the cursor is blinking there, I can use some shell commands of the xen. If I start lvm, I can by lvdisplay, vgdisplay, pvdisplay see the given entities like I have defined it and used in Ubuntu direct, but that is all - it looks like the device in /dev/mapper just would not be created and I do not have any Idea why or what should I do... With best regards, Archie. P.S. The section dedicated to RAID/LVM in the kernel configurations: ***** config-2.6.18-xen # # Multi-device support (RAID and LVM) # CONFIG_MD=y CONFIG_BLK_DEV_MD=y CONFIG_MD_LINEAR=m CONFIG_MD_RAID0=m CONFIG_MD_RAID1=m CONFIG_MD_RAID10=m CONFIG_MD_RAID456=m CONFIG_MD_RAID5_RESHAPE=y CONFIG_MD_MULTIPATH=m CONFIG_MD_FAULTY=m CONFIG_BLK_DEV_DM=m CONFIG_DM_CRYPT=m CONFIG_DM_SNAPSHOT=m CONFIG_DM_MIRROR=m CONFIG_DM_ZERO=m CONFIG_DM_MULTIPATH=m CONFIG_DM_MULTIPATH_EMC=m ***** CONFIG-2.6.20-15-SERVER # # Multi-device support (RAID and LVM) # CONFIG_MD=y CONFIG_BLK_DEV_MD=m CONFIG_MD_LINEAR=m CONFIG_MD_RAID0=m CONFIG_MD_RAID1=m CONFIG_MD_RAID10=m CONFIG_MD_RAID456=m CONFIG_MD_RAID5_RESHAPE=y CONFIG_MD_MULTIPATH=m CONFIG_MD_FAULTY=m CONFIG_BLK_DEV_DM=m # CONFIG_DM_DEBUG is not set CONFIG_DM_CRYPT=m CONFIG_DM_SNAPSHOT=m CONFIG_DM_MIRROR=m CONFIG_DM_ZERO=m CONFIG_DM_MULTIPATH=m CONFIG_DM_MULTIPATH_EMC=m -----Original Message----- From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Vladislav Kurz Sent: Wednesday, May 30, 2007 10:08 AM To: xen-users@lists.xensource.com Subject: Re: [Xen-users] Problem with xen boot if DOM0 is on the LVM,which is on RAID On Tuesday 29 May 2007 20:45, Artur Linhart - Linux communication wrote:> Hello, > > > > I have problems with booting with the new Xen (used the binary > tarball) v. 3.1.0. > > > > I have installed following system: > > One small raid partition with Ext3 fs with the boot directorz and grub > installed > > Two large and one small mirrored raid1 partitions managed by mdadm andused> as 3 physical volumes for LVM, all 3 joined into one volume group. > > Planned dom0 system is installed on the logical volume, which is striped > over md1 and md3 raid phzsical volumes. It is Ubuntu server 7.04. > > The Ubuntu system self boots ad behaves normally. >I have similar configuration without any problems: Debian etch + xen 3.0.3 /boot of dom0 on (hardware) raid1 + ext3 root of dom0 & everything else on raid1 + lvm + ext3 I use xen kernel provided by debian> > If booting Xen, the boot process comes to the point where the raid arrays > are beeing initialized. The RAID arrays itself are initialized and > activated correctly. After it happens, the system hangs for some minutes > and then the message comes: > > > > Check root= bootarg cat /proc/cmdline > > or missing modules, devices: cat /proc/modules ls /dev > > ALERT! /dev/mapper/VG_HIGHLAND_SYSTEM-LV_DOM0 does not exist. Dropping to > shell! > > > > > ... and the sh is invoked, the tty cannot be accessed, so the job control > is turned off. > > I looked into /devúmapper and really, thre is no VG_HIGHLAND_SYSTEM volume > group, which appears there if booting the Ubuntu server. >Check if there is something else in /dev/mapper> > > I am not very skilled in the work with LVM, so the only thing what came > into my mind was - it looks like if the default binary tarball of Xen > 3.1.0 has not turned on the LVM support in the kernel, but I think this is > not possible, because LVM is normally used. > > Or would it be the solution to configure and compile the kernel from > source?before compiling your own, compare the configuration of ubuntu ditstro kernel, and xen kernel, expecially CONFIG_MD_* and CONFIG_DM_* options, to find if there is support for LVM. If the support for LVM is in your xen kernel, then check the contents of initrd if there are scripts that activate the logical volume i.e. /sbin/vgchange, /scripts/*/lvm Anyway even if you compile your own kernel you might need initrd to activate LVM.> I found the idea this is some error in GRUB script, but I do not know ifit> is my case - GRUB configuration file "menu.lst" looks like: > > > > title Xen 3.1.0, kernel 2.6.18-xen /dev/sda1 > root (hd0,0) > kernel /xen-3.1.0.gz dom0_mem=192M > module /vmlinuz-2.6.18-xen root=/dev/mapper/VG_HIGHLAND_SYSTEM-LV_DOM0 > ro max_loop=255 console=tty0 > module /initrd.img-2.6.18-xen >This is OK, I have similar config -- Regards Vladislav Kurz _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users __________ Informace od NOD32 2296 (20070529) __________ Tato zprava byla proverena antivirovym systemem NOD32. http://www.nod32.cz _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Vladislav Kurz
2007-May-30 15:19 UTC
Re: [Xen-users] Problem with xen boot if DOM0 is on the LVM, which is on RAID
On Wednesday 30 May 2007 16:44, Artur Linhart - Linux communication wrote:> Hello, > > Thanks for response :-) > > I verified the kernel configurations, they are different - sure - but in > the area of the MD/LVM this is very similar (the only difference is, the > Xen kernel has for CONFIG_BLK_DEV_MD the value "y", by the Ubuntu default > kernel it is the value "m"), so it''s looks for me like this is rather not > the problem I have... Or what do You think?I think this should not be a problem.> In the /dev/mapper directory is only 1 character device with the name > "control" > After the system comes in the state described below, there is such a " > prompt" > (initramfs) > And the cursor is blinking there, I can use some shell commands of the xen. > If I start lvm, I can by lvdisplay, vgdisplay, pvdisplay see the given > entities like I have defined it and used in Ubuntu direct, but that is all > - it looks like the device in /dev/mapper just would not be created and I > do not have any Idea why or what should I do...Try this (in initramfs shell): vgchange -a y this should bring up all volume groups It seems that there is no script to bring up lvm in your initrd. Check the contents of /script (in initramfs) or /usr/share/initramfs-tools/scripts if there is a script "lvm". Maybe regenerating the initrd might help. Try this (on normally booted system): update-initramfs -u -k 2.6.18-xen (At least this should work on debian, I expect ubuntu to be similar) -- Regards Vladislav Kurz _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Artur Linhart - Linux communication
2007-May-30 18:34 UTC
RE: [Xen-users] Problem with xen boot if DOM0 is on the LVM, which is on RAID
Hello, vgchange -a y works good - the 4 currently allocated volumes are found and than also can be found in /dev/mapper/ folder. In initramfs scripts I rallz doid not find anz scripts which would initiate the lvm. Is this a bug of initramfs from Ubuntu? The update of the ramfs brings nothing new - the error is still the same. But one thing is interesting, after I start update-initramfs, there comes more times the error message: find: /lib/firmware/2.6.18-xen : No such file or directory - could this mean something from Your point of view? The same messages came also at the time I have created the first ramfs. Do You have any idea what to do now? Is there any other tool for the creation of the ramfs which could be used? In the previous version I used yaird, but with Ubuntu 7.04 it reports some strange errors... Thank You very much for Your help, Diky Vladimire :-) Archie -----Original Message----- From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Vladislav Kurz Sent: Wednesday, May 30, 2007 5:20 PM To: xen-users@lists.xensource.com Subject: Re: [Xen-users] Problem with xen boot if DOM0 is on the LVM,which is on RAID On Wednesday 30 May 2007 16:44, Artur Linhart - Linux communication wrote:> Hello, > > Thanks for response :-) > > I verified the kernel configurations, they are different - sure - but in > the area of the MD/LVM this is very similar (the only difference is, the > Xen kernel has for CONFIG_BLK_DEV_MD the value "y", by the Ubuntu default > kernel it is the value "m"), so it''s looks for me like this is rather not > the problem I have... Or what do You think?I think this should not be a problem.> In the /dev/mapper directory is only 1 character device with the name > "control" > After the system comes in the state described below, there is such a " > prompt" > (initramfs) > And the cursor is blinking there, I can use some shell commands of thexen.> If I start lvm, I can by lvdisplay, vgdisplay, pvdisplay see the given > entities like I have defined it and used in Ubuntu direct, but that is all > - it looks like the device in /dev/mapper just would not be created and I > do not have any Idea why or what should I do...Try this (in initramfs shell): vgchange -a y this should bring up all volume groups It seems that there is no script to bring up lvm in your initrd. Check the contents of /script (in initramfs) or /usr/share/initramfs-tools/scripts if there is a script "lvm". Maybe regenerating the initrd might help. Try this (on normally booted system): update-initramfs -u -k 2.6.18-xen (At least this should work on debian, I expect ubuntu to be similar) -- Regards Vladislav Kurz _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users __________ Informace od NOD32 2298 (20070530) __________ Tato zprava byla proverena antivirovym systemem NOD32. http://www.nod32.cz _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Octavian Teodorescu
2007-May-30 21:08 UTC
RE: [Xen-users] Problem with xen boot if DOM0 is on the LVM, which is on RAID
Hi, If I understood correctly your guest dom boot''s up until some point were you get the error: find: /lib/firmware/2.6.18-xen : No such file or directory If this is the error you have to: -shutdown the guest dom; -mount the lvm partition on to a folder on the dom0, and then copy from dom0 the /lib/firmware/"2.6.18-xen" directory to /mounted_lvm/lib/firmware/"2.6.18-xen" -umount the partition, and everthing should be ok know. Best regards.>> Hello, >> >> vgchange -a y >> >> works good - the 4 currently allocated volumes are found and than >> also can be found in /dev/mapper/ folder. >> In initramfs scripts I rallz doid not find anz scripts which would >> initiate the lvm. Is this a bug of initramfs from Ubuntu? >> The update of the ramfs brings nothing new - the error is still the >> same. But one thing is interesting, after I start update-initramfs, there >> comes more times the error message: >> >> find: /lib/firmware/2.6.18-xen : No such file or directory >> >> - could this mean something from Your point of view? The same >> messages came also at the time I have created the first ramfs. >> Do You have any idea what to do now? Is there any other tool for the >> creation of the ramfs which could be used? In the previous version I used >> yaird, but with Ubuntu 7.04 it reports some strange errors... >> >> Thank You very much for Your help, Diky Vladimire :-) >> >> Archie >> >> -----Original Message----- >> From: xen-users-bounces@lists.xensource.com >> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Vladislav Kurz >> Sent: Wednesday, May 30, 2007 5:20 PM >> To: xen-users@lists.xensource.com >> Subject: Re: [Xen-users] Problem with xen boot if DOM0 is on the LVM,which >> is on RAID >> >> On Wednesday 30 May 2007 16:44, Artur Linhart - Linux communication wrote: >>> Hello, >>> >>> Thanks for response :-) >>> >>> I verified the kernel configurations, they are different - sure - but in >>> the area of the MD/LVM this is very similar (the only difference is, the >>> Xen kernel has for CONFIG_BLK_DEV_MD the value "y", by the Ubuntu >>> default >>> kernel it is the value "m"), so it''s looks for me like this is rather >>> not >>> the problem I have... Or what do You think? >> >> I think this should not be a problem. >> >>> In the /dev/mapper directory is only 1 character device with the name >>> "control" >>> After the system comes in the state described below, there is such a " >>> prompt" >>> (initramfs) >>> And the cursor is blinking there, I can use some shell commands of the >> xen. >>> If I start lvm, I can by lvdisplay, vgdisplay, pvdisplay see the given >>> entities like I have defined it and used in Ubuntu direct, but that is >>> all >>> - it looks like the device in /dev/mapper just would not be created and >>> I >>> do not have any Idea why or what should I do... >> >> Try this (in initramfs shell): >> >> vgchange -a y >> >> this should bring up all volume groups >> >> It seems that there is no script to bring up lvm in your initrd. Check the >> contents of /script (in initramfs) or /usr/share/initramfs-tools/scripts >> if >> there is a script "lvm". Maybe regenerating the initrd might help. Try >> this >> (on normally booted system): >> >> update-initramfs -u -k 2.6.18-xen >> >> (At least this should work on debian, I expect ubuntu to be similar) >> >> -- >> Regards >> Vladislav Kurz >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> >> __________ Informace od NOD32 2298 (20070530) __________ >> >> Tato zprava byla proverena antivirovym systemem NOD32. >> http://www.nod32.cz >> >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >>_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Vladislav Kurz
2007-May-31 15:00 UTC
Re: [Xen-users] Problem with xen boot if DOM0 is on the LVM, which is on RAID
On Wednesday 30 May 2007 20:34, you wrote:> Hello, > > vgchange -a y > > works good - the 4 currently allocated volumes are found and than > also can be found in /dev/mapper/ folder. > In initramfs scripts I rallz doid not find anz scripts which would > initiate the lvm. Is this a bug of initramfs from Ubuntu?Perhaps missing package lvm-common it contains file /usr/share/initramfs-tools/hooks/lvm which should do the job. update-initramfs shoudl copy stuff from /usr/share/initramfs-tools/ into initrd. Or you could add your own script or hook to /etc/initramfs-tools/, that would do vgchange -a y. But RTFM of initramfs-tolls for more info where exactly the script should be placed. -- Regards Vladislav Kurz _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Vladislav Kurz
2007-Jun-01 09:59 UTC
Re: [Xen-users] Problem with xen boot if DOM0 is on the LVM, which is on RAID
On Friday 01 June 2007 11:47, you wrote:> Hello, > > Lvm-common is there, in the hooks folder are also the scripts lvm > and lvm2 are there. > > But I looked into the /etc/udev/rules.d - in the (initramfs) shell > - and there are more initialization scripts - bot also following two files > with the same number i the start: > > 85-mdadm.rules > 85-lvm.rules > > - the script 85-lvm.rules contains the calling of vgchange... Is it > correct both of this scripts have the number 85? Should this not be unique? > How can be there figured out what is the execution order of the scripts? I > think the numbers should be unique in this directory, isn''t it?Execution order is alphabetic, so lvm comes befor mdadm, which is wrong. You need to execute mdadm first to set up raid, and after that you can stat lvm. So, renumber them.> I could imagine, the 85-mdadm-rules is called, then the higher number is > searched and therefore 85-lvm.rules is ignored... > > I have tried to mount the rdimage to try to modify the names so, they are > uique but i was not successfull - the rdimage cannot be mounted, the mount > command does not recognize the file system on it :-(Initrd is either cramfs which is read-olny, or compressed cpio archive. But to modify the initrd its safer to modify the scripts in /etc/initamfs-tools, /usr/share/initramfs-tools, or whatever else gets copied from normal system into initramfs and the use update-initrd. If you manage to modify initrd by hand, then you risk losing your modifications when you upgrade kernel or initramfs-tools (postinst scripts run update-initrd) Anyway we are getting a bit off-topic. What is weird that initrd for distro kernel has the scripts in correct order, but not for xen kernel... Regards Vladki> > With best regards > > Artur > > P.S. chtel jsem napsat Vlado, ale pak jsem si rekl jestli nejsem moc > familierni a tak jsem pak jmeno spletl - omlouvam se :-) ach ta hlava...Personal P.S. in czech. Nic se nedeje. Koukam ze sme oba sklerotici a neposilame kopie do konfery at z toho maji uzitek i ostatni. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Artur Linhart - Linux communication
2007-Jun-01 16:25 UTC
RE: [Xen-users] Problem with xen boot if DOM0 is on the LVM, which is on RAID
Hello, It really looks so, the script for LVM initialization installed by Xen 3.1.0 has a wrong name 85-lvm.rules, what causes this is called earlier than the script 85-mdadm.rules. But also if I rename this script to 86-lvm.rules, rebuild the ramdisk and restart the system, it again hangs after the raid initialization and the error Check root= bootarg cat /proc/cmdline or missing modules, devices: cat /proc/modules ls /dev ALERT! /dev/mapper/VG_HIGHLAND_SYSTEM-LV_DOM0 does not exist. Dropping to shell! Is shown on the display, in the shell the volume group can be initialized... :-(... Any other ideas? With best regards, Artur -----Original Message----- From: Vladislav Kurz [mailto:vladislav.kurz@webstep.net] Sent: Friday, June 01, 2007 11:59 AM To: Artur Linhart Cc: xen-users@lists.xensource.com Subject: Re: [Xen-users] Problem with xen boot if DOM0 is on the LVM,which is on RAID On Friday 01 June 2007 11:47, you wrote:> Hello, > > Lvm-common is there, in the hooks folder are also the scripts lvm > and lvm2 are there. > > But I looked into the /etc/udev/rules.d - in the (initramfs) shell > - and there are more initialization scripts - bot also following two files > with the same number i the start: > > 85-mdadm.rules > 85-lvm.rules > > - the script 85-lvm.rules contains the calling of vgchange... Is it > correct both of this scripts have the number 85? Should this not beunique?> How can be there figured out what is the execution order of the scripts? I > think the numbers should be unique in this directory, isn''t it?Execution order is alphabetic, so lvm comes befor mdadm, which is wrong. You need to execute mdadm first to set up raid, and after that you can stat lvm. So, renumber them.> I could imagine, the 85-mdadm-rules is called, then the higher number is > searched and therefore 85-lvm.rules is ignored... > > I have tried to mount the rdimage to try to modify the names so, they are > uique but i was not successfull - the rdimage cannot be mounted, the mount > command does not recognize the file system on it :-(Initrd is either cramfs which is read-olny, or compressed cpio archive. But to modify the initrd its safer to modify the scripts in /etc/initamfs-tools, /usr/share/initramfs-tools, or whatever else gets copied from normal system into initramfs and the use update-initrd. If you manage to modify initrd by hand, then you risk losing your modifications when you upgrade kernel or initramfs-tools (postinst scripts run update-initrd) Anyway we are getting a bit off-topic. What is weird that initrd for distro kernel has the scripts in correct order, but not for xen kernel... Regards Vladki> > With best regards > > Artur > > P.S. chtel jsem napsat Vlado, ale pak jsem si rekl jestli nejsem moc > familierni a tak jsem pak jmeno spletl - omlouvam se :-) ach ta hlava...Personal P.S. in czech. Nic se nedeje. Koukam ze sme oba sklerotici a neposilame kopie do konfery at z toho maji uzitek i ostatni. __________ Informace od NOD32 2303 (20070601) __________ Tato zprava byla proverena antivirovym systemem NOD32. http://www.nod32.cz _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users