Bugzilla – Bug 556953
can not boot with / on RAID10
Last modified: 2013-09-30 08:09:15 UTC
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.1.23) Gecko/20090912 SUSE/1.1.18-1.2 SeaMonkey/1.1.18 Because of https://features.opensuse.org/305343 it is now possible to install openSUSE on RAID6 and RAID10, but a system with / on RAID10 will not boot after installation. Reproducible: Always Steps to Reproduce: 1. boot openSUSE-11.2-DVD-i586.iso 2. create 4 partitions with type FD=Linux RAID autodetect (2 partitions might suffice) 3. create RAID10 mounted on root (/) partition 4. use a non-raid or RAID1 for /boot 5. finish install Actual Results: on first boot, system stops in initrd: http://www.zq1.de/bernhard/temp/raid10-boot-fail.png Expected Results: should boot up as an equivalent RAID6 setup does Probable cause is that raid10.ko is missing from initrd.
Hello, I have the same problem with a raid1 config of /. I can mount it without problems in the rescue system. And the system boots, if I start an installation, abort it and boot the installed system from the text installer. On the screen there are the following console messages: ... Waiting for device /dev/md1 to appear: ok rootfs: major=9 minor=1 devn=2305 Mounting root /dev/md1 Usage: mount [-r] [-w] [-o options] [-t type] device directory umount2: Device or resource busy Kernel panic - not syncing: Attempted to kill init! Booting from the raid worked in 11.1 without problem. Maybe this is related: The rescue system does not assemble my raids any more, as it did in 11.1. But it works without any problem, if I do it manually. I cannot attribute the problem to the fact, that initrd does not contain the raid1 module. I unpacked it and verified, that the module is in the initrd. Regards, Dieter
Assigned to mkinitrd maintainer.
I found that in 11.3 there is now "raid10" added to /lib/mkinitrd/scripts/boot-md.sh Any chance to get this to 11.2, too? Is this a matter for maintenance at opensuse.org ?
openSUSE <= 12.1 is no longer active. If you still can reproduce the problem with openSUSE 12.3 or Factory, please reopen the bug and change the product field accordingly. Sorry that I did not have time to address this bug.