Hi,
I get this each day. Is there a guide to how to fix it? The raid 5 is fine.
/etc/cron.daily/openmediavault-mdadm:
mdadm: DeviceDisappeared event detected on md device /dev/md/md0
mdadm: NewArray event detected on md device /dev/md0
Daily email [NL-40.internal] Anacron job 'cron.daily' on NL-40
-
votdev
Approved the thread. -
-
-
Yes this is a known OMV/mdadm issue and doesn't necessarily mean your RAID5 is failing.
If /proc/mdstat shows the array as healthy then it's probably just the /dev/md/md0 vs /dev/md0 naming issue. I would check:
cat /proc/mdstatmdadm --detail /dev/md0 eplfeedback
Both look healthy so you can check the mdadm/udev configuration without building/making changes to the RAID.
-
Yes this is a known OMV/mdadm issue and doesn't necessarily mean your RAID5 is failing.
Are you a bot? This isn't a known issue. The array really is in auto read only.
-
To fix the "spares missing" notification issue:
1. Edit /etc/mdadm/mdadm.conf.
2. Look for spares=1 and change it to spares=0. Be careful not to alter anything else.
3. Run update-initramfs -u.
4. Reboot.
5. (Optional) Check the health of your array with cat /proc/mdstat and/or cat /etc/mdadm/mdadm.conf to verify it still says spares=0.
6. There should be no more notifications now.
-
-
Display More
To fix the "spares missing" notification issue:
1. Edit /etc/mdadm/mdadm.conf.
2. Look for spares=1 and change it to spares=0. Be careful not to alter anything else.
3. Run update-initramfs -u.
4. Reboot.
5. (Optional) Check the health of your array with cat /proc/mdstat and/or cat /etc/mdadm/mdadm.conf to verify it still says spares=0.
6. There should be no more notifications now.
All fixed. Thanks.
Participate now!
Don’t have an account yet? Register yourself now and be a part of our community!