[Bug 1320402] Re: mdadm resyncs imsm raid in "Normal" state

[Roger Lawhorn]

Just a note for #12. Your change to sendsigs is broken, at least for mint 18.
The process mdmon will not be found.
It is actually /sbin/mdadm --monitor ....

I set OMITPIDS to OMITPIDS=`pidof /sbin/mdadm`
When using pidof the full path of the executable should be specified.

Your second sed expression gives off an error for me.

I just made this change and have to wait 4 hrs for my resync to finish
before I can reboot to test. I will repost the results.

I have done a lot of research on this and mdmon is the issue. It must
NOT be killed during a shutdown according to it's own docs.

#1. Edit /etc/init.d/sendsigs (to prevent mdmon from being killed on shutdown):
# OMITPIDS=`pidof mdmon | sed -e 's/ /,/g' -e 's/./-o \0'`

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to mdadm in Ubuntu.
https://bugs.launchpad.net/bugs/1320402

Title:
   mdadm resyncs imsm raid in "Normal" state

Status in mdadm package in Ubuntu:
  Confirmed

Bug description:
  Got an imsm raid1 which I don't boot from. Whenever bios reports the
  raid as being in "Normal" state, mdadm starts a resync of it after
  boot. If a resync already is underway (bios reports it as being in
  "Verify" state), it continues where it left off.

  This appears to be very similar to a problem in Fedora:
  https://bugzilla.redhat.com/show_bug.cgi?id=753335 It's apparently
  fixed there for some time now. (The workaround mentioned in comment 41
  in that ticket doesn't work in Ubuntu, but I guess that's due to
  distro differences in initramfs and systemd.)

  Using mdadm 3.2.5-5ubuntu4 in a fresh Trusty install.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1320402/+subscriptions