https://bugzilla.novell.com/show_bug.cgi?id=684291
https://bugzilla.novell.com/show_bug.cgi?id=684291#c10
Neil Brown changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
CC| |mmarek@novell.com
--- Comment #10 from Neil Brown 2011-06-09 06:42:39 UTC ---
OK, I've figured out what happened.
Under 11.3 you were using mdadm to manage your platform-RAID arrays.
When you upgraded to 11.4, something went wrong and the mkinitrd setup script
for md didn't recognise your array. So it didn't install the md modules or
tools in the initrd, so the initrd couldn't assembly your RAID array.
You thought that dmraid had been managing the arrays so built an initrd with
dmraid support and it assembled the arrays but gave them a different name than
the name that mdadm gave them, so you were a little closer but it still didn't
work. You had to edit /etc/fstab etc to use the new names, and now it works.
I'm a bit confused as to why the setup script didn't put any md stuff in the
initrd, but it clearly didn't. In any case if it had it wouldn't have worked.
It seems that when I "fixed" the udev rules to avoid a race condition, I also
"broken" them so that partitions weren't handled properly. So had it assembled
the md arrays, it wouldn't have created the 'partXX' devices in /dev/disk/...
and it wouldn't have worked anyway.
I'm guess that part of the install process involved telling udev to recreate
all links, and that make it remove the partition links in /dev/disk. Then
when mkinitrd ran the md setup script it couldn't find the like, got confused
and gave up.
So I'll fix the udev rules file to do the right thing.
You can just leave things as they are if you like, or we could convert back to
using mdadm just to make sure it works. If you would like to try converting
back, let me know and I'll see if I can work out the easiest way to do it.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.