https://bugzilla.novell.com/show_bug.cgi?id=720919
https://bugzilla.novell.com/show_bug.cgi?id=720919#c13
Neil Brown changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution| |INVALID
--- Comment #13 from Neil Brown 2012-01-12 05:57:07 UTC ---
"mdadm --examine" is meant to be applied to the member devices, not the arrays.
So that fact that "no superblock" is reported when it is run on an array is not
a concern.
The mdadm.conf files look correct ... but then it all seems to be working now
so I'm not sure what that tells us.
mdadm will assign md devices like md127 and md126 when it isn't sure that the
the array really belongs to "this" machine. That is determined by the
'homehost' which e.g. "mdadm --examine /d/ev/sdb3" will report.
If it finds correct details in /etc/mdadm.conf it should not worry about
'homehost' but should trust the arrays and given them there 'proper' names.
Maybe there is some sort of ordering problem with systemd - it would need to
start LVM after 'mdadm' has assembled the arrays ... or udev would need to give
the devices to LVM as they appear ... I'm not sure if it does that.
If you still have problems I suggest trying to boot with sysvinit rather than
systemd.
According to http://www.novell.com/linux/releasenotes/x86_64/openSUSE/12.1/#12
this is achieved by pressing 'F5'.
If this makes a difference, consider filing a bug against systemd.
Thanks.
--
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.