Error messages about mdadm --incremental failing

[Laurent Bonnaud]

Hi,

this system has a mdadm RAID volume:

$ cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md1 : active raid5 sde1[3] sdf1[5] sdd1[2] sdc1[1] sdb1[0]
      15627542528 blocks super 1.2 level 5, 512k chunk, algorithm 2 [5/5] [UUUUU]
      bitmap: 0/30 pages [0KB], 65536KB chunk

It is working well, but when the system boots, I see several error messages in journalctl:

$ journalctl |grep mdadm
Apr 08 20:23:50 xeelee systemd-udevd[473]: Process '/sbin/mdadm --incremental /dev/sde1 --offroot' failed with exit code 1.
Apr 08 20:23:50 xeelee systemd-udevd[477]: Process '/sbin/mdadm --incremental /dev/sdf1 --offroot' failed with exit code 1.
Apr 08 20:23:50 xeelee systemd-udevd[483]: Process '/sbin/mdadm --incremental /dev/sdb1 --offroot' failed with exit code 1.
Apr 08 20:23:50 xeelee systemd-udevd[472]: Process '/sbin/mdadm --incremental /dev/sdc1 --offroot' failed with exit code 1.
Apr 08 20:23:50 xeelee systemd-udevd[476]: Process '/sbin/mdadm --incremental /dev/sdd1 --offroot' failed with exit code 1.
Apr 08 20:24:42 xeelee mdadm[845]: * Starting MD monitoring service mdadm --monitor
Apr 08 20:24:42 xeelee mdadm[845]: ...done.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: udev 229-4ubuntu1
Uname: Linux 4.5.0-040500-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CurrentDesktop: KDE
CustomUdevRuleFiles: 60-ssd-scheduler.rules
Date: Fri Apr 8 20:51:27 2016
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.5.0-040500-lowlatency root=UUID=347d095b-3b19-412b-841e-acfd162e2c53 ro quiet splash nomdmonddf nomdmonisw vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to xenial on 2016-03-31 (8 days ago)
dmi.bios.date: 03/25/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.50
dmi.board.name: HM77-HT
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd03/25/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM77-HT:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Laurent Bonnaud (laurent-bonnaud)]

This bug seems to be fixed in yakkety with mdadm 3.4-4.

Thanks!

[Alex R (abr28)]

Is a fix planned for Xenial as well?

I have this too on 16.04.1 with latest mdadm as of this writing.

[jhansonxi (jhansonxi)]

Same for me on Xenial with mdadm 3.3 (amd64).

Bug #1582191 may be related.

[Ivaylo (ivaylo-str82dhead)]

Same for me - 16.04 with mdadm 3.3.2.
Will be there a patch for this anytime soon?

[Jean-Pierre van Riel (jpvr)]

Similar mdadm error for me when I resume from suspend on 16.04.2 LTS.

> This bug seems to be fixed in yakkety with mdadm 3.4-4.

Note that while v4.4 was released early 2016, Xenial shipped with v3.3 (which is sane given one wouldn't want to ship with v4.4 just a few mere months after it was released) .

However, what seems a bit tardy to me is that v3.3.4 release was published 03 Aug-2015, so why did/does Xenial ship with a v3.3.2 version and miss two minor releases worth of fixes/updates from upstream (or have to back port them)?

```
$ mdadm --version
mdadm - v3.3 - 3rd September 2013
$ dpkg-query --show mdadm
mdadm 3.3-2ubuntu7.2
```

Of course, there are back-ported patches from v3.4...

https://launchpad.net/ubuntu/+source/mdadm/+changelog

[Jean-Pierre van Riel (jpvr)]

Sorry correction, meant to say v3.4 (not 4.4).

[pgnd (pgnd)]

On Xenial

 lsb_release -rd
  Description: Ubuntu 16.04.2 LTS
  Release: 16.04

I've still got

 dmesg | grep fail
  [ 5.304662] systemd-udevd[146]: Process '/sbin/lvm pvscan --cache --activate ay --major 9 --minor 1' failed with exit code 5.
  [ 13.284345] systemd-udevd[362]: Process '/sbin/mdadm --incremental /dev/sdb2 --offroot' failed with exit code 1.
  [ 13.287567] systemd-udevd[361]: Process '/sbin/mdadm --incremental /dev/sdb1 --offroot' failed with exit code 1.
  [ 13.884875] systemd-udevd[365]: Process '/sbin/mdadm --incremental /dev/sda1 --offroot' failed with exit code 1.
  [ 16.434847] systemd-udevd[368]: Process '/sbin/mdadm --incremental /dev/sda2 --offroot' failed with exit code 1.

where

 mdadm --version
  mdadm - v3.3 - 3rd September 2013
 dpkg-query --show mdadm
  mdadm 3.3-2ubuntu7.2
 apt-get upgrade mdadm
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  mdadm is already the newest version (3.3-2ubuntu7.2).
  Calculating upgrade... Done
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

(Where) is there a fix available for Xenial?

[Risto H. Kurppa (risto.kurppa)]

Has anyone found any solution other than upgrading to a newer *buntu version? Are there newer mdadm packages available for Xenial?

This bug report seems to have similar error messages, is it the same bug? https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1587142

[Andreas Hasenack (ahasenack)]

Is this bug just an annoyance in terms of noise in the logs, or is there something else that's wrong? FWIW I can confirm the log messages happen in xenial, but that's all.