as part of https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1722491 there is currently mdadm update available from xenial-proposed and zesty-proposed that might resolve this issue.
To test that solution please perform the following: 1) Install mdadm from xenial-proposed/zesty-proposed - See https://wiki.ubuntu.com/Testing/EnableProposed - Or download & install packages from xenial https://launchpad.net/ubuntu/+source/mdadm/3.4-4ubuntu0.1/+build/13596415 zesty https://launchpad.net/ubuntu/+source/mdadm/3.3-2ubuntu7.5/+build/13596431 2) $ sudo apt install dracut-core 3) $ sudo systemctl enable mdadm-shutdown.service 4) $ sudo systemctl start mdadm-shutdown.service After this the expectation is for shutdown/reboots to perform clean a shutdown, maintaining the raid array in a synced state, such that it comes up clean. Please let me know if above resolves shutdown/reboot issues for you. Regards, Dimitri. ** Changed in: mdadm (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: mdadm (Ubuntu Xenial) Status: Confirmed => Fix Committed ** Changed in: mdadm (Ubuntu Yakkety) Status: Confirmed => Won't Fix ** Changed in: mdadm (Ubuntu Zesty) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1608495 Title: IMSM fakeraid handled by mdadm: unclean mounted volumes on shutdown/reboot Status in mdadm package in Ubuntu: Fix Committed Status in mdadm source package in Xenial: Fix Committed Status in mdadm source package in Yakkety: Won't Fix Status in mdadm source package in Zesty: Fix Committed Bug description: Opening this report for Xenial and later as this problem does surface again due to moving to systemd. Background: mdadm is used to create md raid volumes based on Intel Matrix Storage Manager fakeraid metadata. The setup usually consists of a container set that contains one or more raid volumes. Which is the reason that those fakeraid volume are more affected by timing issues on shutdown/reboot. In my specific setup I am using one of the IMSM raid volumes as a LVM PV and one LV of that is mounted as /home. The problem is that unmounting /home on shutdown/reboot will update the filesystem superblock which causes the raid state to become dirty for a small period of time. For that reason with sysvinit scripts there is a mdadm-waitidle script which *must* be run after the umountroot (or for /home at least after umountfs) script has run. With Xenial both umountroot and umountfs are softlinks to /dev/null in /lib/systemd/system, so I am not sure they are good to cause the mdadm-waitidle to be delayed *after* all filesystems are unmounted. Practically I see that if /home is mounted on shutdown/reboot, the raid set will go into a full resync the next time I boot (additional pain but different problem: the resync appears to be much more aggressive than in the past, delaying boot a lot and rendering the system barely usable until it finishes). If I manually unmount /home before the reboot, the raid set is good. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1608495/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : [email protected] Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
