Every time i replace a drive mdadm doesnt see my raid and i have to stop and forcefully rebuild via console

Darkyputz · Dec 7th 2025

Hello everyone.

I am in the process of making my raid bigger while.keeping the data, so i replace all my 1 tb drives one by one with 3 tb drives and rebuild the degraded raid. But to do so i always have to stop my md127 mdadm and restart in the console otherwise it is not showing any raid, only the drives and smart values.

Is there a trick, fix or so? Or as i just saw, is 7 already obsolete and i should move on to 8 in hope that it is fixed? I have 7.x with all updates installed on a readynas pro6 bak with the biggest intel cpu that this board supports.

Thx for any help

votdev · Dec 7th 2025

This is no bug, this is how mdadm works. You can try to add the new disk as hotspare before removing the disk that is to be replaced. To keep it short, the mdadm support in OMV does not do any magic for you.

Darkyputz · Dec 8th 2025

ok, i am just used to other systems where it would see a degraded raid after reboot and ask to get a new drive. Wasnt expecting that it does not even see the raid at all. Especially when only one out of 6 drives got swapped.

But good to know. At least i was able to find the answer in google

votdev · Dec 8th 2025

OMV does not store any data in its database about the RAID. All data that is displayed is extracted from userland apps and procfs. If the RAID is gone, mdadm does not show any info in /proc/mdstat, so in the end OMV can not display anything as well.

Darkyputz · Dec 8th 2025

th alot for the clarification. Solves my question.

dsm1212 · Dec 28th 2025

Md127 is your swap and you likely have it configured raid0. If any disk fails raid0 fails. If you must use swap it should be at least raid1 or a disk failure can cause the kernel to panic if swap was in use.

Every time i replace a drive mdadm doesnt see my raid and i have to stop and forcefully rebuild via console

Darkyputz Dec 8th 2025

Participate now!