https://bugzilla.novell.com/show_bug.cgi?id=793954
https://bugzilla.novell.com/show_bug.cgi?id=793954#c13
Neil Brown changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |NEEDINFO
InfoProvider| |suse-beta@cboltz.de
--- Comment #13 from Neil Brown 2013-02-27 06:44:15 UTC ---
The messages from mdadm would appear in the output of
journalctl -b
but I can see that it didn't wait at all from the lack of any delay between
"md: md1 stopped" and "md: bind <sda3>". So it didn't wait and give up - it
just didn't see sdb3 at all.
Could you add "-vv" to the mdadm command in /etc/init.d/boot.md
Both
$mdadm_BIN -IRs
$mdadm_BIN -A -s -c $mdadm_CONFIG
could have "-vv" added at the end.
Then when it happens again,
journalctl -b | grep mdadm
and see what it says.
I've tried it mayself with the latest Factory and I cannot reproduce the
problem, but then it is quite possibly dependent on exact timing, and that will
vary with different hardware.
Am I correct in thinking that this never happens to the "root" array, only to
other arrays what would be assembled once the system has booted?
--
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.