http://bugzilla.novell.com/show_bug.cgi?id=586837
http://bugzilla.novell.com/show_bug.cgi?id=586837#c0
Summary: YaST installs on partitioned MD devices, but the
"initrd" does not activate nor use the MD device after
reboot.
Classification: openSUSE
Product: openSUSE 11.3
Version: Milestone 3
Platform: x86-64
OS/Version: openSUSE 11.3
Status: NEW
Severity: Major
Priority: P5 - None
Component: YaST2
AssignedTo: bnc-team-screening@forge.provo.novell.com
ReportedBy: DOlsson@WEB.de
QAContact: jsrain@novell.com
Found By: ---
Blocker: ---
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.18)
Gecko/2010020400 SUSE/3.0.18-0.1.2 Firefox/3.0.18
After having manually created a partitioned MD RAID1 device using unpartitioned
disks:
mdadm --create /dev/md/raid1 --name="raid1" --homehost="Loke" --level="raid1"
--metadata="1.0" --auto=part3 -v -n 2 /dev/sda /dev/sdb
fdisk /dev/md/raid1
p1 <default> +512M type 83
p2 <default> +5G type 82
p3 /dev/raid1/root (ext4)
=> /dev/raid1/pagingp50 (swap)
=> /dev/raid1/usr (ext4)
The installation setup seems to work, except that the "Booting" entry complains
about:
It was not possible to determine the exact order of disks for device map.
The order of disks can be changed in "Boot Loader Installation Details".
As the order listed under the entry was
"Order of Hard Disks: /dev/md127 /dev/sdb"
I found no reasons for changing anything.
After reboot the MD device is *not* activated nor is it used, instead the
system runs as if it had been installed on "/dev/sda[123]"!!
Having tried to debug the problem, it turns out that the MD device is *not*
activated in the "initrd" at all!!
Reproducible: Always
Steps to Reproduce:
1. Create a partitioned MD device by hand.
2. Boot openSUSE 11.3 DVD and start installation.
3. Configure file systems using the MD partitions.
4. Start installation.
5. After system having rebooted, notice that the MD device is *not* started
during the "initrd" startup, just as it is not in usage at all in the running
kernel.
Actual Results:
Although YaST installs openSUSE 11.3 on the assigned partitioned MD device, the
system is *not* setup to make use of the partitioned MD device has having been
rebooted.
In fact, the MD device is not activated *at all* during the loading and setting
up of the "initrd".
Expected Results:
After system reboot, the "initrd" is supposed to setup and activate the
partitioned MD device and make use of it in the started up kernel.
The issue reported here, may be related to the issues reported in Bugzilla
#463033.
--
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.