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@xxxxxxxxxxx]
Sent: Friday, June 01, 2007 11:59 AM
To: Artur Linhart
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
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 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.
__________ Informace od NOD32 2303 (20070601) __________
Tato zprava byla proverena antivirovym systemem NOD32.
http://www.nod32.cz
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home