"mdadm: DeviceDisappeared event detected on md device /dev/md/md0" since upgrade to OMV8

Hi folks, first post here. Hoping to write down good enough info to receive hints of support.

Not that noob, but really not skilled linux user, so I'm gonna be quite rough on the edges on understanding some suggestions.

I recently updated my nas box (repurpoused HP desktop computer, 2x 2tb WD RED drives for RAID1 + 128gb Corsair BX500 as system disk); I added to the system tailscale as a package, plus some plugins. If necessary I can list them here. System has been updated this morning.

Since the upgrade to OMV 8 every day I receive an email message with this output.

Quote

mdadm: DeviceDisappeared event detected on md device /dev/md/md0

mdadm: NewArray event detected on md device /dev/md0

which roughly seems to me the output of mdadm --monitor --scan --oneshot

System is working, I can access it from HTTPS, SMB, SSH (which are the mostly common used way to interact with)

Hoping to deliver useful info:

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 ##redacted##
MAILFROM root


# definitions of existing MD arrays
ARRAY /dev/md0 metadata=1.2 UUID=67117265:66ed20fd:913b6886:90dfdfc5

 cat /etc/sysctl.d/99-openmediavault-mdadm.conf

# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.
#
# Default values:
# dev.raid.speed_limit_min = 1000
dev.raid.speed_limit_min = 10000

mdadm --export --detail /dev/md0

MD_LEVEL=raid1
MD_DEVICES=2
MD_METADATA=1.2
MD_UUID=67117265:66ed20fd:913b6886:90dfdfc5
MD_NAME=safeboat:wdred
MD_DEVICE_dev_sdc_ROLE=0
MD_DEVICE_dev_sdc_DEV=/dev/sdc
MD_DEVICE_dev_sdb_ROLE=1
MD_DEVICE_dev_sdb_DEV=/dev/sdb

My guess is that somewhere the md UUID is not the one that is being found in the system, so any hint on which file look for/edit it will be golden to me.

Thanks in advance for everyone will share inputs.

Thanks for the hint, however the suggested modification did not solve the issue for the OP.

Maybe moderators could merge the two topics?

Update on this "issue" is present here, waiting for tomorrow morning if something changes.

Updated Kernel, and now md0 is... /dev/md127. Which is "fine", i'm not attached in any way to the array name but i find it somewhat... strange.

Nothing to report. Therefore... Problem solved

votdev thanks for sharing the info, I was not aware.