Hi all,
there was a thread in here in 2009 dealing with lvm2 initialisation on bootup:
http://www.mail-archive.com/[email protected]/msg52937.html
but we are running lvm2-2.02.84-3.25.5 now.
I am now preparing a SLES11 SP2 autoyast profile for initial server
installation using an LVM layout.
/dev/disk/by-path/ccw-0.0.0201-part1 to /boot
/dev/disk/by-path/ccw-0.0.0201-part2 is an lvm partition
/dev/rootvg1/homelv to /home
/dev/rootvg1/rootlv to /
/dev/rootvg1/tmplv to /tmp
/dev/rootvg1/varlv to /var
We are running this layout via autoyast installer on SLES 10 for years by now.
When installing via the yast interface everything is fine. When using the same
dasd layout via autoyast i am getting following messages:
Waiting for device /dev/rootvg1/rootlv to appear: . Reading all physical volume
s. This may take a while...
No volume groups found
Volume group "rootvg1" not found
Volume group "rootvg1" not found
. Reading all physical volumes. This may take a while...
No volume groups found
I modified init in initd by adding "set -x".
So i get follwing from the console for the autoyast installed server:
++ source boot/04-udev.sh
+++ '¬' -n '' '|'
+++ echo 'udev_log="error"'
+++ echo 'Creating device nodes with udev'
Creating device nodes with udev
+++ /sbin/udevd --daemon
+++ /sbin/udevadm trigger --action=add
+++ wait_for_events
+++ /sbin/udevadm settle --timeout=30
udev: starting version 147
++ '¬' '' '|'
++ '¬' '' '|'
++ '¬' -x /sbin/blogd '|'
++ '¬' '' '|'
++ source boot/05-blogd.sh
And for the manually installed server it looks like this:
++ source boot/04-udev.sh
+++ '¬' -n '' '|'
+++ echo 'udev_log="error"'
+++ echo 'Creating device nodes with udev'
Creating device nodes with udev
+++ /sbin/udevd --daemon
+++ /sbin/udevadm trigger --action=add
+++ wait_for_events
+++ /sbin/udevadm settle --timeout=30
udev: starting version 147
dasd-eckd.9e2b8e: 0.0.0201: New DASD 3390/0C (CU 3990/01) with 10016 cylinders,
15 heads, 224 sectors
dasd-eckd.79a145: 0.0.0201: DASD with 4 KB/block, 7211520 KB total size, 48 KB/t
rack, compatible disk layout
dasda:VOL1/ 0X0201: dasda1 dasda2
++ '¬' '' '|'
++ '¬' '' '|'
++ '¬' -x /sbin/blogd '|'
++ '¬' '' '|'
++ source boot/05-blogd.sh
Which is more reasonable to me.
Is this a known issue ?
Any help or ideas appreciated.
Kind regards,
Tobias Doerkes.
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
