Bug 1774354

The OS comes with userspace tool mdadm installed by default.

What optional packages did you check off during installation?

>What optional packages did you check off during installation?

I didn't install additional optional packages during installation.

Besides, my test environment is a vm.

Mengyi

Hi 

Addition error log is outputted. The detail is as below:

~~~
/usr/lib/systemd/system/mdcheck_start.timer:12] Failed to parse calendar specification, ignoring: Sun *-*-1..7 1:00:00
~~~

# cat /usr/lib/systemd/system/mdcheck_start.timer
#  This file is part of mdadm.
#
#  mdadm is free software; you can redistribute it and/or modify it
#  under the terms of the GNU General Public License as published by
#  the Free Software Foundation; either version 2 of the License, or
#  (at your option) any later version.

[Unit]
Description=MD array scrubbing

[Timer]
OnCalendar=Sun *-*-1..7 1:00:00   <--- 

[Install]
WantedBy= mdmonitor.service

Thank you.

I’m getting the same issue downstream on CentOS 7.7 (see their issue https://bugs.centos.org/view.php?id=16665 )

As far as I can tell the problem is the systemd components included in the latest mdadm package are incompatible with the version of systemd included with RHEL/CentOS 7.

In my case I don’t just see these errors, but also can no longer automount my RAID array due to systemd ordering cycle problems.

Thanks

Failed to get exception for late RHEL7.8 fix.  Pushed to 7.9 (or zstream) for fix.

Need QA ack

Hi Mengyi

This should be fixed in mdadm-4.1-3.el7 already. 4.1-1 is old. So please ask customer to have a try
with the latest mdadm package (4.1-3)

Thanks
Xiao

Hi Xiao!

i have also this issue. I have patched our RHEL7 systems and i only get mdadm package 4.1-1. 
also, when i browse RHEL REPO, (....7.7/x86_64/os/Packages/m/) there are only these packages: mdadm-4.1-1.el7.x86_64.rpm, mdadm-4.1-rc1_2.el7.x86_64.rpm.

so please can you tell who to get mdadm-4.1-3

thanks
Michael

XiaoNi,

I too, am experiencing this same issue. The Red Hat Satellite server reports "No packages marked for update". Currently installed version is (mdadm.x86_64  4.1-1.el7 @RedHatEnterpriseLinux7ServerRPMs) Searches on rpmfind, etc only have version 4.1-1.el7. Please assist in where to find version 4.1-3.el7? This bug appears to be shutting down 3rd party syslog-ng. Please help.

Hi all

4.1-3.el7 is in rhel7.8. But it still has this problem. I've sent patch to upstream. I'll fix this in
4.1-4.el7

Thanks
Xiao

*** Bug 1763195 has been marked as a duplicate of this bug. ***

Hi All,

I think this problem has been sloved on mdadm-4.1-5.el7

[root@RHEL79-202004220 ~]# cat  /etc/redhat-release 
Red Hat Enterprise Linux Server release 7.9 Beta (Maipo)

[root@RHEL79-202004220 ~]# uname -a
Linux RHEL79-202004220.localdomain 3.10.0-1136.el7.x86_64 #1 SMP Fri Apr 17 11:40:59 EDT 2020 x86_64 x86_64 x86_64 GNU/Linux
[root@RHEL79-202004220 ~]# 


[root@RHEL79-202004220 ~]# rpm -q mdadm
package mdadm is not installed


[root@RHEL79-202004220 ~]# rpm -ivh /mnt/Packages/mdadm-4.1-5.el7.x86_64.rpm 
warning: /mnt/Packages/mdadm-4.1-5.el7.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID fd431d51: NOKEY
error: Failed dependencies:
	libreport-filesystem is needed by mdadm-4.1-5.el7.x86_64

[root@RHEL79-202004220 ~]# rpm -ivh  /mnt/Packages/libreport-filesystem-2.1.11-53.el7.x86_64.rpm 
warning: /mnt/Packages/libreport-filesystem-2.1.11-53.el7.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID fd431d51: NOKEY
Preparing...                          ################################# [100%]
Updating / installing...
   1:libreport-filesystem-2.1.11-53.el################################# [100%]
[root@RHEL79-202004220 ~]# rpm -ivh /mnt/Packages/mdadm-4.1-5.el7.x86_64.rpm 
warning: /mnt/Packages/mdadm-4.1-5.el7.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID fd431d51: NOKEY
Preparing...                          ################################# [100%]
Updating / installing...
   1:mdadm-4.1-5.el7                  ################################# [100%]
[root@RHEL79-202004220 ~]# 


[root@RHEL79-202004220 ~]# systemctl status mdcheck_continue.service
● mdcheck_continue.service - MD array scrubbing - continuation
   Loaded: loaded (/usr/lib/systemd/system/mdcheck_continue.service; static; vendor preset: disabled)
   Active: inactive (dead)
[root@RHEL79-202004220 ~]# reboot



[root@RHEL79-202004220 ~]# systemctl status mdcheck_continue.service -l
● mdcheck_continue.service - MD array scrubbing - continuation
   Loaded: loaded (/usr/lib/systemd/system/mdcheck_continue.service; static; vendor preset: disabled)
   Active: inactive (dead)
[root@RHEL79-202004220 ~]# 


[root@RHEL79-202004220 ~]# systemctl start mdcheck_continue.service
[root@RHEL79-202004220 ~]# 

BR
Fine

Now that mdcheck appears to run successfully via systemd, shouldn't the cron file be removed from the package?

>$ rpm -q mdadm
>mdadm-4.1-4.el7.x86_64

>$ rpm -ql mdadm | grep cron
>/etc/cron.d/raid-check

The errors can be fixed with the following changes:

Environment="MDADM_CHECK_DURATION=6 hours"
OnCalendar=Sun *-*-* 1:00:00

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (mdadm bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:3976