"mdadm: Unknown keyword INACTIVE-ARRAY" after Upgrade OMV5 > OMV6

I have finally updated my omv5 to omv6. Everything seems to be working normally. However, I get the following message in my email:

/etc/cron.daily/openmediavault-mdadm:

mdadm: Unknown keyword INACTIVE-ARRAY

mdadm: Unknown keyword INACTIVE-ARRAY

some infos:

--------------

root@omv:~# cat /proc/mdstat

Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [ra id10]

md0 : active raid1 sdc[1] sdd[0]

2930135360 blocks super 1.2 [2/2] [UU]

unused devices: <none>

--------------

root@omv:~# blkid

/dev/sdb1: UUID="ce2da1ef-7948-445e-98fc-fd6c73baff70" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="0de79efb-2be5-4b38-9d11-2a795c81f365"

/dev/sda1: LABEL="Tosh1" UUID="fb1e45f4-ea1c-4de9-b916-189ef60fe594" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="629f2b40-044e-4a27-aef4-ba1a56ac30ee"

/dev/sde1: UUID="afcb2e95-3261-4ee7-aca5-2a0b59efecbb" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="ee989c28-01"

/dev/sde5: UUID="a0b829ac-79ae-4476-bda4-b94f0cf6ab14" TYPE="swap" PARTUUID="ee989c28-05"

/dev/sdd: UUID="71753bdb-548e-a668-3af6-83b631435b44" UUID_SUB="f2fde8d8-06e3-ff69-742e-15d805966938" LABEL="OMV:0" TYPE="linux_raid_member"

/dev/sdc: UUID="71753bdb-548e-a668-3af6-83b631435b44" UUID_SUB="d3568d19-04d9-bab2-ccc0-811a8c2c27da" LABEL="OMV:0" TYPE="linux_raid_member"

/dev/md0: LABEL="Server" UUID="ea51eaa0-83a4-4fd9-8ff9-63fd17095186" BLOCK_SIZE="4096" TYPE="ext4"

--------------

root@omv:~# fdisk -l | grep "Disk "

Disk /dev/sdb: 2,73 TiB, 3000592982016 bytes, 5860533168 sectors

Disk model: WDC WD30EFRX-68E

Disk identifier: 22AE76A3-E787-4F5F-9503-3946B592E5EC

Disk /dev/sda: 2,73 TiB, 3000592982016 bytes, 5860533168 sectors

Disk model: WDC WD30EFRX-68E

Disk identifier: ED39D5EE-12DD-4D03-BBF0-E95D91579DC8

Disk /dev/sde: 111,79 GiB, 120034123776 bytes, 234441648 sectors

Disk model: KINGSTON SA400S3

Disk identifier: 0xee989c28

Disk /dev/sdd: 2,73 TiB, 3000592982016 bytes, 5860533168 sectors

Disk model: WDC WD30EFRX-68E

Disk /dev/sdc: 2,73 TiB, 3000592982016 bytes, 5860533168 sectors

Disk model: WDC WD30EFRX-68E

Disk /dev/md0: 2,73 TiB, 3000458608640 bytes, 5860270720 sectors

--------------

root@omv:~# cat /etc/mdadm/mdadm.conf

# This file is auto-generated by openmediavault (https://www.openmediavault.org)

# WARNING: Do not edit this file, your changes will get lost.

# mdadm.conf

#

# Please refer to mdadm.conf(5) for information about this file.

#

# by default, scan all partitions (/proc/partitions) for MD superblocks.

# alternatively, specify devices to scan, using wildcards if desired.

# Note, if no DEVICE line is present, then "DEVICE partitions" is assumed.

# To avoid the auto-assembly of RAID devices a pattern that CAN'T match is

# used if no RAID devices are configured.

DEVICE partitions

# auto-create devices with Debian standard permissions

CREATE owner=root group=disk mode=0660 auto=yes

# automatically tag new arrays as belonging to the local system

HOMEHOST <system>

# instruct the monitoring daemon where to send mail alerts

MAILADDR xxxxxxxx@xxx.de

MAILFROM root

# definitions of existing MD arrays

ARRAY /dev/md/OMV:0 metadata=1.2 name=OMV:0 UUID=71753bdb:548ea668:3af683b6:31435b44

INACTIVE-ARRAY /dev/md127 metadata=1.1 name=NAS-SYNC-1:1 UUID=b4c741a8:a463898b:cf1c72ea:f540dd7f

INACTIVE-ARRAY /dev/md126 metadata=1.1 name=ix4-300d:0 UUID=5f2c2150:a36b9e26:f980de9f:84d7fff4

--------------

root@omv:~# mdadm --detail --scan --verbose

mdadm: Unknown keyword INACTIVE-ARRAY

mdadm: Unknown keyword INACTIVE-ARRAY

ARRAY /dev/md/OMV:0 level=raid1 num-devices=2 metadata=1.2 name=OMV:0 UUID=71753bdb:548ea668:3af683b6:31435b44

devices=/dev/sdc,/dev/sdd

what do i have to do ?

greetings

mirada

I have 2 hard drives in Raid 1 and 2 other hard drives (4x 3TB WD) on which I currently only save files to the first one and will later set up an rsync to the second hard drive. I already had that before the upgrade.

I will submit the output of "omv-salt deploy run mdadm initramfs" later.

I think it looks good ...

The message at the top of the field " Storage I Software RAID I Details " (mdadm: Unknown keyword INACTIVE-ARRAY) - now it's gone!

I'll keep an eye on the whole thing and give you feedback.

Output :

root@omv:~# omv-salt deploy run mdadm initramfs

debian:

----------

ID: remove_cron_daily_mdadm

Function: file.absent

Name: /etc/cron.daily/mdadm

Result: True

Comment: File /etc/cron.daily/mdadm is not present

Started: 01:07:20.063148

Duration: 0.864 ms

Changes:

----------

ID: divert_cron_daily_mdadm

Function: omv_dpkg.divert_add

Name: /etc/cron.daily/mdadm

Result: True

Comment: Leaving 'local diversion of /etc/cron.daily/mdadm to /etc/cron.dai ly/mdadm.distrib'

Started: 01:07:20.064662

Duration: 13.07 ms

Changes:

----------

ID: configure_default_mdadm

Function: file.managed

Name: /etc/default/mdadm

Result: True

Comment: File /etc/default/mdadm updated

Started: 01:07:20.078009

Duration: 117.321 ms

Changes:

----------

diff:

---

+++

@@ -1,20 +1,21 @@

-# mdadm Debian configuration

-#

-# You can run 'dpkg-reconfigure mdadm' to modify the values i n this file, if

-# you want. You can also change the values here and changes w ill be preserved.

-# Do note that only the values are preserved; the rest of the file is

-# rewritten.

-#

+# This file is auto-generated by openmediavault (https://www. openmediavault.org)

+# WARNING: Do not edit this file, your changes will get lost.

+

+# INITRDSTART:

+# list of arrays (or 'all') to start automatically when the initial ramdisk

+# loads. This list *must* include the array holding your ro ot filesystem. Use

+# 'none' to prevent any array from being started from the i nitial ramdisk.

+#INITRDSTART='none'

+

+# AUTOSTART:

+# should mdadm start arrays listed in /etc/mdadm/mdadm.conf automatically

+# during boot?

+AUTOSTART=true

# AUTOCHECK:

# should mdadm run periodic redundancy checks over your arr ays? See

# /etc/cron.d/mdadm.

AUTOCHECK=true

-

-# AUTOSCAN:

-# should mdadm check once a day for degraded arrays? See

-# /etc/cron.daily/mdadm.

-AUTOSCAN=true

# START_DAEMON:

# should mdadm start the MD monitoring daemon during boot?

----------

ID: configure_mdadm_conf

Function: file.managed

Name: /etc/mdadm/mdadm.conf

Result: True

Comment: File /etc/mdadm/mdadm.conf updated

Started: 01:07:20.195451

Duration: 118.061 ms

Changes:

----------

diff:

---

+++

@@ -23,6 +23,3 @@

MAILFROM root

# definitions of existing MD arrays

-ARRAY /dev/md/OMV:0 metadata=1.2 name=OMV:0 UUID=71753bdb:548 ea668:3af683b6:31435b44

-INACTIVE-ARRAY /dev/md127 metadata=1.1 name=NAS-SYNC-1:1 UUID =b4c741a8:a463898b:cf1c72ea:f540dd7f

-INACTIVE-ARRAY /dev/md126 metadata=1.1 name=ix4-300d:0 UUID=5 f2c2150:a36b9e26:f980de9f:84d7fff4

----------

ID: mdadm_save_config

Function: cmd.run

Name: mdadm --detail --scan >> /etc/mdadm/mdadm.conf

Result: True

Comment: Command "mdadm --detail --scan >> /etc/mdadm/mdadm.conf" run

Started: 01:07:20.314772

Duration: 8.977 ms

Changes:

----------

pid:

8139

retcode:

0

stderr:

stdout:

----------

ID: update_initramfs_nop

Function: test.nop

Result: True

Comment: Success!

Started: 01:07:20.325250

Duration: 0.605 ms

Changes:

----------

ID: update_initramfs

Function: cmd.run

Name: update-initramfs -u

Result: True

Comment: Command "update-initramfs -u" run

Started: 01:07:20.325957

Duration: 20986.984 ms

Changes:

----------

pid:

8141

retcode:

0

stderr:

stdout:

update-initramfs: Generating /boot/initrd.img-6.1.0-0.deb11.21 -amd64

Summary for debian

------------

Succeeded: 7 (changed=4)

Failed: 0

------------

Total states run: 7

Total run time: 21.246 s