https://bugzilla.novell.com/show_bug.cgi?id=821366
https://bugzilla.novell.com/show_bug.cgi?id=821366#c2
--- Comment #2 from Klaus Braun 2013-05-29 11:47:51 UTC ---
For me it looks curious. On a test machine I tried to change something in
the boot.md script like
MDADM_DEVICE_TIMEOUT=480
Then after the next reboot I see different situations concerning mdmon:
- one time I have a job like
"mdmon md127"
maybe coming from initrd ?
- the other time I see
@/sbin/mdmon -all --takeover --offroot
coming from boot.md
- but most times after a second and third reboot without any further change
of boot.md mdmon isn't running at all.
Furthermore I tried to create a softraid with mdadm --create. This works fine,
even if mdon is not running after reboot. May be mdmon isn't necessary in
this case, this is something I don't know.
Creating an imsm based fake raid using mdadm --create --metadata=imsm I get
the same problem as before: If mdmon isn't running the raid hangs.
For me it looks like in most of the cases when I reboot my machine the raid
isn't
ready if systemd wants to start mdmon. In some rare cases mdmon could be
started,
but I don't see what should be done to reproduce this.
--
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.