http://bugzilla.novell.com/show_bug.cgi?id=525237 User piotrek.juzwiak@gmail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=525237#c1 --- Comment #1 from Piotrek Juzwiak 2009-07-24 22:11:49 MDT --- Message when installing this way: Device md0 not handled Script /lib/mkinitrd/setup/72-block.sh failed! -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=525237 Piotrek Juzwiak changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Component|Kernel |Installation QAContact|qa@suse.de |jsrain@novell.com -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=525237 shuang qiu changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sqiu@novell.com AssignedTo|bnc-team-screening@forge.pr |duwe@novell.com |ovo.novell.com | -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=525237 User pgnet.dev@gmail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=525237#c5 --- Comment #5 from pgnet Dev 2009-08-11 17:04:10 MDT --- since 'mkinitrd -v' doesn't seem to be any more verbose than just 'mkinitrd', here's the (relevant?) output with "set -x", .. ++ blockminor=1 +++ block_driver 9 +++ sed -n '/^Block devices:/{n;: n;s/^[ ]*9 \(.*\)/\1/p;n;b n}' ++ blockdriver=md ++ '[' '!' md ']' ++ '[' md = device-mapper ']' ++ false +++ majorminor2blockdev 9 1 +++ local major=9 minor=1 +++ '[' '!' 1 ']' +++ '[' 9 -lt 0 ']' ++++ cat /proc/partitions ++++ egrep '^[ ]*9[ ]*1 ' +++ local 'retval= 9 1 243987048 md1' +++ echo /dev/md1 ++ blkpart=/dev/md1 ++ '[' /dev/md1 ']' +++ echo md1 +++ sed 's./.!.g' ++ blkpart=md1 +++ echo md1 +++ sed 's/\([a-z]\)[0-9]*$/\1/;s/p$//' ++ blkdev=md ++ '[' -d /sys/block/md/md1 ']' +++ update_list /dev/md1 +++ local elem=/dev/md1 +++ shift +++ case " $@ " in +++ echo ' /dev/md1' ++ blockpart_blockdev=' /dev/md1' ++ blockdev=' /dev/md1' + '[' 0 -ne 0 ']' + for setupfile in '$INITRD_PATH/setup/*.sh' + '[' -d /dev/shm/mkinitramfs.53DRvf/mnt ']' + cd /dev/shm/mkinitramfs.53DRvf/mnt + '[' '!' -d /lib/mkinitrd/setup/72-block.sh ']' + curscript=block.sh + source /lib/mkinitrd/setup/72-block.sh ++ '[' '' ']' ++ all_libata_modules_included=0 ++ for bd in '$blockdev' ++ case $bd in ++ update_blockdev /dev/md1 ++ local curblockdev=/dev/md1 ++ '[' /dev/md1 ']' ++ '[' /dev/md1 ']' ++ blockmajor=-1 ++ blockminor=-1 ++ '[' -e /dev/md1 ']' +++ devnumber /dev/md1 ++++ ls -lL /dev/md1 +++ set -- brw-rw---- 1 root disk 9, 1 2009-03-17 16:21 /dev/md1 +++ mkdevn 9 1 +++ local major=9 minor=1 +++ echo 9437185 ++ blockdevn=9437185 +++ devmajor 9437185 +++ local devn=9437185 +++ echo 9 ++ blockmajor=9 ++ '[' '!' 9 ']' +++ devminor 9437185 +++ local devn=9437185 +++ echo 1 ++ blockminor=1 +++ block_driver 9 +++ sed -n '/^Block devices:/{n;: n;s/^[ ]*9 \(.*\)/\1/p;n;b n}' ++ blockdriver=md ++ '[' '!' md ']' ++ '[' md = device-mapper ']' ++ false ++ get_devmodule md1 curmodule ++ local result= +++ echo md1 +++ sed 's./.!.g' ++ local blkdev=md1 ++ '[' '!' -d /sys/block/md1 ']' ++ case "$blkdev" in ++ '[' '!' -d /sys/block/md1/device ']' ++ echo 'Device md1 not handled' Device md1 not handled ++ return 1 ++ '[' 1 -eq 0 ']' ++ return 1 + '[' 1 -ne 0 ']' + oops 1 'Script /lib/mkinitrd/setup/72-block.sh failed!' + echo 'Script /lib/mkinitrd/setup/72-block.sh failed!' Script /lib/mkinitrd/setup/72-block.sh failed! + cleanup + rm -f /dev/shm/mkinitramfs.53DRvf/initrd /dev/shm/mkinitramfs.53DRvf/initrd.gz + '[' -d /dev/shm/mkinitramfs.53DRvf/mnt ']' + rm -rf /dev/shm/mkinitramfs.53DRvf/mnt + initrd_bins=() + exit_code=1 + exit 1 + exit_code=1 + '[' -e /dev/shm/mkinitramfs.53DRvf/error ']' + (( i++ )) + (( 1<2 )) + echo .. ++ echo 'Device md1 not handled' Device md1 not handled ++ return 1 ++ '[' 1 -eq 0 ']' ++ return 1 + '[' 1 -ne 0 ']' + oops 1 'Script /lib/mkinitrd/setup/72-block.sh failed!' + echo 'Script /lib/mkinitrd/setup/72-block.sh failed!' Script /lib/mkinitrd/setup/72-block.sh failed! + cleanup + rm -f /dev/shm/mkinitramfs.53DRvf/initrd /dev/shm/mkinitramfs.53DRvf/initrd.gz + '[' -d /dev/shm/mkinitramfs.53DRvf/mnt ']' + rm -rf /dev/shm/mkinitramfs.53DRvf/mnt + initrd_bins=() + exit_code=1 + exit 1 + exit_code=1 + '[' -e /dev/shm/mkinitramfs.53DRvf/error ']' + (( i++ )) + (( 2<2 )) + cleanup_finish + umount_proc + '[' '' ']' + mounted_proc= + '[' '' ']' + mounted_sys= + '[' '' ']' + mounted_usr= + '[' -d /dev/shm/mkinitramfs.53DRvf ']' + rm -rf /dev/shm/mkinitramfs.53DRvf + '[' '!' -x /sbin/update-bootloader ']' + '[' 1 -eq 0 ']' + exit 1 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=525237 User pgnet.dev@gmail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=525237#c7 --- Comment #7 from pgnet Dev 2009-08-11 17:42:20 MDT --- just fyi, upgrading mkinitrd to, http://download.opensuse.org/repositories/home:/thomasbiege:/branches:/Base:... does NOT solve the problem ... -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=525237 User pgnet.dev@gmail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=525237#c9 pgnet Dev changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Major |Blocker --- Comment #9 from pgnet Dev 2009-08-12 07:41:07 MDT --- (In reply to comment #8)

Please read http://en.opensuse.org/Bugs/Definitions#Blocker

I *DID* read it: "Blocker * Prevents developers or testers from performing their jobs. Impacts the development process. " we ARE doing 'development or testing' -- not just _of_ Factory , but of our own products/services. this bug, and the inability to boot as a result, DOES prevent our folks from doing their jobs, and DOES impact the development process. the *specific* examples given for 'Blocker' severity are, * Unable to login * Unable to perform certification tests * Unable to update system all three of which are tru in in this case. if you have different definitions of the criteria, or suggest that it's only relevant for *suse's developers/tester, then that should be clearly stated in the docs you reference. in the meantime ... -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=525237 User juhliarik@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=525237#c11 Jozef Uhliarik changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |juhliarik@novell.com Info Provider| |piotrek.juzwiak@gmail.com --- Comment #11 from Jozef Uhliarik 2009-08-13 06:45:03 MDT --- The first please attach YaST logs. Next if you play with md raid it is possible boot only from MBR. There is problem with kernel caching and it is not possible boot from /boot (or "/") partition if it is on md raid. I mean scenario (which doesn't work): * write generic boot code to MBR * set boot flag on /boot (or "/") partition on md raid * write GRUB stage1 to /boot (or "/") partition on md raid I am sure that if you use only md raid yast propose boot from MBR (resp. write GRUB to MBR) I am not sure about LVM on md raid but I see same problem like only with md raid and finally if you want to use LVM you HAVE TO separate /boot partition out of LVM and in this case out of md raid! -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=525237 User piotrek.juzwiak@gmail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=525237#c13 --- Comment #13 from Piotrek Juzwiak 2009-08-13 07:49:59 MDT --- Nevermind, i will test both M4 and M5 with that scenario. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=525237 User piotrek.juzwiak@gmail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=525237#c15 --- Comment #15 from Piotrek Juzwiak 2009-08-13 08:29:48 MDT --- Well to be honest you misinterpreted my bug report. I reported that the system fails to build initrd when the / is on on an LVM which is on a RAID-0. From what i've heard /boot on RAID-1 is fine but not on RAID-0. My scenario involves creating a RAID-0 stripe with separate /boot partition and on top of that RAID-0 stripe (which is not formatted as suggested normally) is a LVM group in which i create / root partition. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=525237 User juhliarik@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=525237#c17 --- Comment #17 from Jozef Uhliarik 2009-08-14 02:51:45 MDT --- Piotrek, thanks for yast logs. I know there is little bit misunderstanding of terminology. I am sorry for it. I try to use complete desription of boot settings instead of names of checkbox from y2-bootloader. ;-) OK lets start: comment#12: ========== * Please take a fact that GRUB doesn't know to boot from LVM you need separate /boot partition out of LVM (yast2-storage should warning you during creating LVM that you need separate /boot partition) * Boot from raid0 is not possible if it is software raid. GRUB works with physical partitions not with sw raid partitions and in this case it is not possible use physical partitions because raid0 doesn't dulicate(mirroring) data on physical partitions but use only part from each physical partition. It means GRUB hasn't chance to read from (for example) /dev/sda1 (/dev/sda1 is one of physical partition from raid0) content of /boot directory. But basic problem is that GRUB has not code for using software raids and it means it doesn't know to use software raid partitions. comment#14: ========== I am sorry I wrote it wrong. You can have /boot partition or if you haven't separate /boot partition you can have "/" and there /boot directory on md raid (but only raid1) Next it is mandatory to write GRUB in to MBR other scenarios where is uses "write generic boot code" to MBR doesn't work as I wrote it before (comment#11). Yes your link is valid but for older openSUSE somebody change kernel caching and it doesn't allow to use other scenario of booting than write GRUB to MBR. y2-bootloader propose write GRUB to MBR during installation. Please doesn't ask me about details. It is kernel problem. comment#15: ========== I see in bugzilla problem with mkinitrd and LVM maybe it is solved now. The bug will be reassign to maintainer of mkinitrd. Finally: ======== I hope that now it is clear for everybody how GRUB works with md raids and LVM -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=525237 User piotrek.juzwiak@gmail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=525237#c19 Piotrek Juzwiak changed: What |Removed |Added ---------------------------------------------------------------------------- Platform|x86-64 |All --- Comment #19 from Piotrek Juzwiak 2009-08-14 03:02:54 MDT --- Jozef, i am aware that GRUB can't boot from /boot which is on RAID-0 thus this /boot was "separate" and NOT on this RAID stripe. It was simple primary partition. I created three partitions, one primary for /boot and two for RAID-0. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=525237 User anniyka@wandersmann.net added comment http://bugzilla.novell.com/show_bug.cgi?id=525237#c22 --- Comment #22 from Anniyka Wandersmann 2009-09-25 07:32:58 MDT --- Hello, my scenario: 1) /boot on md0 RAID1, yes, it works!! I use this system for servel years now and if you say it is not working for grub, thats not true. Nonetheless I startet this years ago with lilo. It may be that it is not possible to install suche a soulution now, But for upgraded systems it is definitvly a blocker since it takes upgraded systems into an unbootable state. 2) / on lvm2 on md1 To say so: linux:/ # mkinitrd Kernel image: /boot/vmlinuz-2.6.31-rc9-7-default Initrd image: /boot/initrd-2.6.31-rc9-7-default Root device: /dev/vg00/root (mounted on / as xfs) Device md1 not handled Script /lib/mkinitrd/setup/72-block.sh failed! Kernel image: /boot/vmlinuz-2.6.31-rc9-7-trace Initrd image: /boot/initrd-2.6.31-rc9-7-trace Root device: /dev/vg00/root (mounted on / as xfs) Device md1 not handled Script /lib/mkinitrd/setup/72-block.sh failed! I tried the workaround with rootdev I found in the mailinglist, but then the only thing that happens is: linux:/ # mkinitrd -d /dev/md1 Kernel image: /boot/vmlinuz-2.6.31-rc9-7-default Initrd image: /boot/initrd-2.6.31-rc9-7-default node name not found Could not find the filesystem type for root device /dev/md1 Currently available -d parameters are: Block devices /dev/<device> NFS <server>:<path> URL <protocol>://<path> Ok, hear is what I discoverd: linux:/ # diff /lib/mkinitrd/setup/62-dm.sh /lib/mkinitrd/setup/62-lvm2.sh linux:/ # linux:/ # ls -l /lib/mkinitrd/setup/62-dm.sh /lib/mkinitrd/setup/62-lvm2.sh lrwxrwxrwx 1 root root 22 Sep 25 16:53 /lib/mkinitrd/setup/62-dm.sh -> ./scripts/setup-dm.sh lrwxrwxrwx 1 root root 24 Sep 25 16:53 /lib/mkinitrd/setup/62-lvm2.sh -> ./scripts/setup-lvm2.sh linux:/ # I certainly think that this is an error. ../scripts/setup-lvm2.sh is just a copy of ../scripts/setup-dm.sh. Therfor /md1 (in my case) is not handled as lvm2. I also think that this is an error because of this: http://www.novell.com/products/linuxpackages/opensuse/mkinitrd.html 848 Sep 19 14:28 /lib/mkinitrd/scripts/setup-dm.sh 1093 Sep 19 14:28 /lib/mkinitrd/scripts/setup-lvm2.sh Sometimes between 10.3 and now someone seems to have copied ./scripts/setup-dm.sh over ../scripts/setup-lvm2.sh. The other side is this: http://www.novell.com/products/linuxpackages/opensuse11.1/mkinitrd.html There are no such scripts noticed. Well, a) It is back again b) It's leftover from old installations If its back again, than it seems to be a package error If it is a leftover, than it seems such also, because it was not deleted and is now interfering with the new package I bootet into the livefilesystem opensuse 11.2 factory, mounted all needed filesystemsm copied /dev to /mnt/dev, mountet sys, devpts and proc and did a chroot. Thats my rescuebasis at the moment. regards, anniyka -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=525237 User anniyka@googlemail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=525237#c24 --- Comment #24 from Anniyka Wandersmann 2009-09-26 07:15:25 MDT --- linux:~/cpio # find | grep -e dm -e lvm -e md | grep -v amd /lib/udev/collect_lvm /lib/udev/rules.d/64-md-raid.rules /lib/udev/rules.d/64-lvm2.rules /lib/udev/idedma.sh /lib/modules/2.6.31-rc9-7-default/kernel/drivers/md /lib/modules/2.6.31-rc9-7-default/kernel/drivers/md/raid6_pq.ko /lib/modules/2.6.31-rc9-7-default/kernel/drivers/md/raid456.ko /lib/modules/2.6.31-rc9-7-default/kernel/drivers/md/raid1.ko /lib/modules/2.6.31-rc9-7-default/kernel/drivers/md/dm-snapshot.ko /lib/modules/2.6.31-rc9-7-default/kernel/drivers/md/dm-mod.ko /boot/03-lvm2.sh /boot/03-dm.sh /config/dm.sh /config/lvm2.sh /sbin/lvm /sbin/udevadm /sbin/dmsetup linux:~/cpio # diff ./config/dm.sh ./config/lvm2.sh linux:~/cpio # Shoulden`t there something to set up MDs or LVs? Well, if the scripts (notet in previous comment) are the same maybe thats the reason? ... -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=525237 User jsj@jsj.dyndns.org added comment http://bugzilla.novell.com/show_bug.cgi?id=525237#c26 Stefan Schmidt changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |REOPENED Resolution|NORESPONSE | --- Comment #26 from Stefan Schmidt 2009-09-28 03:49:31 MDT --- I am not really sure, why this bug has been close, allthough there is no solution in sight. Can someone please clarify? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=525237 User wmerriam@yahoo.com added comment http://bugzilla.novell.com/show_bug.cgi?id=525237#c28 Bill Merriam changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wmerriam@yahoo.com --- Comment #28 from Bill Merriam 2009-09-28 19:02:35 MDT --- I copied /lib/mkinitrd/scripts/setup-lvm2.sh and /lib/mkinitrd/scripts/ boot-lvm2.sh from an 11.1 system to my 11.2M7 system and it fixed this problem. You need to send the bug to the maintainer of the lvm2 rpm. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=525237 User anniyka@googlemail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=525237#c29 --- Comment #29 from Anniyka Wandersmann 2009-09-29 03:21:34 MDT --- Tried this to but it didn't worked. It's always the same as in my last comment in Bug 505670 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=525237 User blackhole999@gmail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=525237#c31 --- Comment #31 from Ray Sutton 2009-10-01 20:02:20 MDT --- I'm having a similar problem, tried copying setup-lvm.sh/boot-lvm2.sh as outlined above - no joy! my configuration is LVM2 on top of software raid1, /boot is /dev/md0 (raid1/ext3) and / is a lvm2 partition on top of /dev/md1(raid1/PV). I don't claim to understand the initrd process but tracing linuxrc it looks as if this may be a sequencing problem looking at the run_all.sh script on the generated initrd it executes 02-start 03-dm 03-rtc 03-storage 04-udev ....... 51-md 61-lvm2 udev times out waiting for the root device but as yet the md and lvm2 initialization hasn't occurred so the root device is not visible. Also in the initial install of 11.2M7 failed during initrd creatation in 72-block.sh as md* isn't recognized as a block device. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=525237 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- Flag| |SHIP_STOPPER+ -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=525237 User blackhole999@gmail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=525237#c34 --- Comment #34 from Ray Sutton 2009-10-03 15:49:50 MDT --- I was able to get the system to boot using the following procedure Unpack initrd to a directory edit run_all.sh before the call to 03-lvm as follows: define (mknod) sda,sda1,sda2,sdb,sdb1,sdb2,md0,md1 manually assemble raid devices md0/md1 manually vgchange to bring the lvm devices online. repack initrd & reboot. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=525237 User coolo@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=525237#c36 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jblunck@novell.com --- Comment #36 from Stephan Kulow 2009-10-12 02:10:09 MDT --- *** Bug 546022 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=546022 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=525237 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P3 - Medium |P1 - Urgent Severity|Major |Critical -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=525237 User xwhu@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=525237#c41 --- Comment #41 from Xinwei Hu 2009-10-12 03:30:53 MDT --- (In reply to comment #40)

I can confirm the solution from Petri Asikainen from Bug 540522, but the lvm2 package from 11.2M8 differs greatly from the one from factory - which Petri used and modified. The factory lvm2 seems to be more like the one from 11.1.

Can we have the lvm2 from factory with the trivial fix for 11.2?

I've submitted the related patch to factory already. pending for acceptance now -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=525237 User anniyka@googlemail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=525237#c43 --- Comment #43 from Anniyka Wandersmann 2009-10-13 06:48:25 MDT --- Well: linux:/lib/mkinitrd/setup # for i in 01-prepare.sh 01-splashy.sh 02-start.sh 03-udev.sh 03-usb.sh 11-storage.sh 21-luks.sh 31-lvm2.sh ; do grep -H sysconfig $i; done | grep -v "#" 02-start.sh: . $root_dir/etc/sysconfig/kernel 02-start.sh: . $root_dir/etc/sysconfig/kernel 31-lvm2.sh: cp -a /etc/sysconfig/lvm $tmp_mnt/etc/sysconfig Without a directory sysconfig ... -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=525237 User anniyka@googlemail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=525237#c45 --- Comment #45 from Anniyka Wandersmann 2009-10-13 07:05:36 MDT --- Well, you can check this patch if you could still need it. With this I could build my initrd: linux:/lib/mkinitrd/scripts # diff -cB setup-prepare.sh setup-prepare.sh~ *** setup-prepare.sh Tue Oct 13 16:51:59 2009 --- setup-prepare.sh~ Tue Aug 11 11:59:50 2009 *************** *** 137,143 **** cp $INITRD_PATH/bin/linuxrc $linuxrc mkdir "$tmp_mnt/boot" ! mkdir -p $tmp_mnt/{sbin,bin,etc,dev,proc,sys,root,config,etc/sysconfig} mkdir -p -m 4777 $tmp_mnt/tmp --- 137,143 ---- cp $INITRD_PATH/bin/linuxrc $linuxrc mkdir "$tmp_mnt/boot" ! mkdir -p $tmp_mnt/{sbin,bin,etc,dev,proc,sys,root,config} mkdir -p -m 4777 $tmp_mnt/tmp -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=525237 User coolo@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=525237#c47 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #47 from Stephan Kulow 2009-10-13 09:00:25 MDT --- I just did a test installation of Build327 with LVM and mkinitrd works fine. I hope it's ok to close the bug -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=525237 User rccj@ricreig.com added comment http://bugzilla.novell.com/show_bug.cgi?id=525237#c49 Richard Creighton changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |rccj@ricreig.com Resolution|FIXED | --- Comment #49 from Richard Creighton 2009-10-13 20:05:15 MDT --- I hope you do NOT. I had no problems with M8, did a factory zyp dup to what appears to be labled RC1 and it would not boot...Fortunately, Grub had saved M8 and I could get it to boot from there. It was waiting on MD0. My system has a separate /boot on a separate partition, / is on a Software raid MD0 which is 20G and excludes /home and a couple of other directories like /srv /home and /srv are on a LVM across 4 drives grabbing bits and pieces of otherwise unused space totalling about 700G. This works, works well in M8, with NO changes other than the upgrade mentioned, RC1 fails during boot while waiting for MD0, falls back to MD0 and waits until I reset the machine. Remember, this is a separate PRIMARY partion for the /boot, 2 identical drives with primary partitions dedicated to a RAID1 MD0 and the rest of the drive partitions are allocated to the LVM for home, etc. This worked fine in M5 on to 8. Prior to that, I didn't use RAID or LVM as I wasn't testing that aspect yet on that machine. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=525237 User coolo@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=525237#c51 --- Comment #51 from Stephan Kulow 2009-10-14 07:12:07 MDT --- we need more data than what Richard's setup. Is the new package working for everyone else? (please remember to call mkinitrd explicitly if you do zypper dup). -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=525237 User rccj@ricreig.com added comment http://bugzilla.novell.com/show_bug.cgi?id=525237#c54 --- Comment #54 from Richard Creighton 2009-10-14 10:27:21 MDT --- What, if any additional information would you need from me? I believe this bug came closest to describing the problem I experienced, ie, it is not about LVM,or RAID specifically, it is about mkinitrd when either or both of those are used to store all or part of the root of the file system. In my case, / is on a RAID 1, but /boot is on a normal primary partition, not part of either a LVM or a RAId, but directories needed for building a new module or load image certainly reside on (in my case) a RAID or LVM or possibly both in my case because /usr is on the LVM for instance, however, at the time things are being updated or being built, this tree is (or should be) fully available as the system hasn't been rebooted yet as it is still being updated by the update scripts and fwiw, the failure also fails when run from YAST as opposed to zypper dup. Previous updates have not failed using YAST (update all with newer) (only factory enabled) (from M8 to RC1) and with zypper dup as an effort to repair the failure as a last resort with no positive effect. I hope this does not become a pissing match about technicalities about raid version or lvm vs raid, It is a failure of mkinitrd when using one or both of those in some or any combination that causes a failure that needs to be identified and I will do my best to help identify the cause if you remember, I am NOT a technical person (anymore), I am a stroke victim that USED to be a systems engineer/programmer that hasn't programmed in 'modern' low level languages in many years. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=525237 User anniyka@googlemail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=525237#c56 --- Comment #56 from Anniyka Wandersmann 2009-10-14 14:28:13 MDT --- :-/ ... Did zypper dup just a minute ago (well, it finished a minute ago): anniys:~ # mkinitrd Kernel image: /boot/vmlinuz-2.6.31.3-1-default Initrd image: /boot/initrd-2.6.31.3-1-default Root device: /dev/vg00/root (mounted on / as xfs) Resume device: /dev/disk/by-id/ata-SAMSUNG_SP2014N_S088J10L405647-part1 (/dev/hda1) setup-md.sh: md1 found multiple times Kernel Modules: thermal_sys processor thermal fan exportfs xfs xor async_tx async_memcpy async_xor raid6_pq raid456 cdrom sr_mod ide-core amd74xx pata_amd sata_nv ata_generic sg ide-gd_mod ide-cd_mod ide-pci-generic dm-mod edd raid1 dm-snapshot pata_acpi raid0 linear Features: dm block usb md lvm2 resume.userspace resume.kernel Bootsplash: openSUSE (1280x1024) 30689 blocks Kernel image: /boot/vmlinuz-2.6.31.3-1-trace Initrd image: /boot/initrd-2.6.31.3-1-trace Root device: /dev/vg00/root (mounted on / as xfs) Resume device: /dev/disk/by-id/ata-SAMSUNG_SP2014N_S088J10L405647-part1 (/dev/hda1) setup-md.sh: md1 found multiple times Kernel Modules: thermal_sys processor thermal fan exportfs xfs xor async_tx async_memcpy async_xor raid6_pq raid456 cdrom sr_mod ide-core amd74xx pata_amd sata_nv ata_generic sg ide-gd_mod ide-cd_mod ide-pci-generic dm-mod edd raid1 dm-snapshot pata_acpi raid0 linear Features: dm block usb md lvm2 resume.userspace resume.kernel Bootsplash: openSUSE (1280x1024) 31048 blocks What the heck is this: setup-md.sh: md1 found multiple times At least it build the initrd, I will try if it boots up ... -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=525237 User lnussel@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=525237#c58 --- Comment #58 from Ludwig Nussel 2009-10-15 03:10:06 MDT --- Suppose the volume group of the root volume is called 'system'. What should be the output of the following command? # vgs --noheadings --options pv_name system For lvm on top of raid it's /dev/md0 on 11.1 and /dev/dm-0 on 11.2 AFAICT. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=525237 User lnussel@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=525237#c60 --- Comment #60 from Ludwig Nussel 2009-10-15 06:14:00 MDT --- Created an attachment (id=322652) --> (http://bugzilla.novell.com/attachment.cgi?id=322652) disk layout with root on lvm on raid and boot on raid works with Build0334 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=525237 User blackhole999@gmail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=525237#c62 --- Comment #62 from Ray Sutton 2009-10-15 19:06:43 MDT --- Mostly works for me :-) Configuration /boot on /dev/md0 (raid1/ext4) / on /dev/sys/dom0 (ext4 on LVM2 on raid1) RC1 (Build 334 X86_64) installed no problem, reboot fine after install to desktop mode, rebooting to dom0 under xen failed on switching to runlevel 5 (system locked) Regenerated initrd as a test, reported the missing scsi_config file but this didn't prevent initrd being recreated. On reboot desktop mode worked fine but xen-dom0 crapped out switching to run level 5, this time I was able to recover to runlevel 3. The initrd problem is resolved for me, I just need to go beat up (gently of course) the x-windows or xen guys (probably the latter). Thanks to everybody who had time to work this problem! -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=525237 User rccj@ricreig.com added comment http://bugzilla.novell.com/show_bug.cgi?id=525237#c64 --- Comment #64 from Richard Creighton 2009-10-16 00:13:33 MDT --- My comment associated with attachment of comment 63 didn't seem to take: I downloaded the ISO for RC1 and created the DVD and installed it as an update successfully on the test machine using the configuration as shown in the above attachment. It installed successfully with the exception that GRUB did not update properly. It left the old RC1, the non-bootable version marked as the default even though it added the new kernel into the menu but did not mark it as the default and when it rebooted, of course, it went into the old waiting game for MD1, which of course never occured. When I rebooted manually, I noticed the menu was not 'right' in that the default was the 2nd set of RC1 choices, so I manually selected the top set of RC1 default flavor and it booted. I then went into grub and selected that first (top) menu item as default, deleted the bottom two items from the menu (the old pae flavor) and then rebooted just to be sure it would do so without intervention from a power off reboot, and it did. I would say that aside from grub messing up, the initrd problem with LVM and RAID is fixed and this bug from my perspective at least could be marked as closed. Richard -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=525237 User hawke@hawkenterprising.com added comment http://bugzilla.novell.com/show_bug.cgi?id=525237#c66 --- Comment #66 from Hawke Robinson 2009-10-16 14:26:16 MDT --- I see that 11.2 RC1 is now out. I am downloading that, and will see how that behaves with the same setup on the same system. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=525237 User xwhu@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=525237#c68 Xinwei Hu changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |CLOSED Resolution| |FIXED --- Comment #68 from Xinwei Hu 2009-10-18 21:02:34 MDT --- So closing it again as reports indicate that bug is fixed in RC1. Thank you all for participating in testing and resolving this issue! -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.