Oh … this is _another_ bug. We are dealing here with the situation that
mdmon controlling rootfs on RAID is not handled at all with Ubuntu
initrd, while this new CentOS issue is a bug in said handling in the
CentOS initrd …
The reference is valuable nevertheless … not least because I have
systems
Can we get any reaction from Ubuntu on this? Is the needed reworking of
the initrd about to happen for the LTS or is this a WONTFIX and root-on-
Intel-Matrix-RAID is simply not supported? It is clear what has to
happen to make things work again with systemd and mdadm/mdmon. Will it
happen?
--
Is anyone working on this? I see that the bug is assigned, but apart
from that only messages from affected users.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587142
Title:
Shutdown hangs in md
Well, of course effects are a pain. The sync is only 256G SSDs im my
case.
Main point is that the fix is known since many years and should
hopefully be quickly adaptible to Ubuntu. Or not … if it is really
necessary to switch to a return to the initrd like Fedora.
I wonder if 17.04 has this
So I got a simple fix for being able to reboot again:
```
udpate-rc.d mdadm disable
```
With that, the mdmon instance from the initrd persists (with @sbin/mdmon
as argv[0]) and is not killed by systemd. So systemd-reboot does not
hang. But: Since mdmon is not killed at all now, the array always
This very much looks like this ancient issue in RedHat:
https://bugzilla.redhat.com/show_bug.cgi?id=752593
It got fixed at some point in 2012 …
https://bugzilla.redhat.com/show_bug.cgi?id=785739
Is Ubuntu still running mdmon from inside the root fs and killing it
before r/o remount?
I am now
