Sigh...
The command "cat /proc/mdstat" confirms that md127 is no more present:
root@DIYNAS-OMV:~# cat /proc/mdstat
Personalities : [raid0] [raid6] [raid5] [raid4] [linear] [multipath] [raid1] [raid10]
md0 : active raid5 sdb[2] sda[3] sdf[0] sde[1] sdc[4]
23441567744 blocks super 1.2 level 5, 512k chunk, algorithm 2 [5/5] [UUUUU]
bitmap: 0/44 pages [0KB], 65536KB chunk...but the "grow" fails again (but with different message) 
The answer is in the message, the current array is performing a resync/recovery, what's the output if mdadm --detail /dev/md0
root@DIYNAS-OMV:~# mdadm --detail /dev/md0
mdadm: ARRAY line /dev/md/ddf0 has no identity information.
/dev/md0:
Version : 1.2
Creation Time : Mon Jun 15 23:04:23 2020
Raid Level : raid5
Array Size : 23441575936 (22355.63 GiB 24004.17 GB)
Used Dev Size : 5860393984 (5588.91 GiB 6001.04 GB)
Raid Devices : 5
Total Devices : 6
Persistence : Superblock is persistent
Intent Bitmap : Internal
Update Time : Wed May 26 22:32:21 2021
State : clean
Active Devices : 5
Working Devices : 6
Failed Devices : 0
Spare Devices : 1
Layout : left-symmetric
Chunk Size : 512K
Consistency Policy : bitmap
Name : DIYNAS-OMV:RAID5 (local to host DIYNAS-OMV)
UUID : add77410:4af984b4:4a1bf4c9:a53296ae
Events : 94109
Number Major Minor RaidDevice State
0 8 80 0 active sync /dev/sdf
1 8 64 1 active sync /dev/sde
2 8 16 2 active sync /dev/sdb
3 8 0 3 active sync /dev/sda
4 8 32 4 active sync /dev/sdc
5 8 48 - spare /dev/sdd
root@DIYNAS-OMV:~# I noticed that "/dev/sdd" is now present in the RAID Array list, but as a spare disk:
it's been added as a spare, try mdadm --grow --raid-devices=6 /dev/md0
This is the output:
root@DIYNAS-OMV:~# mdadm --grow --raid-devices=6 /dev/md0
mdadm: ARRAY line /dev/md/ddf0 has no identity information.And this is what appears in GUI:
I suppose we've to wait a lot... 
I suppose we've to wait a lot...
Yes
This doesn't make sense;
mdadm: ARRAY line /dev/md/ddf0 has no identity information.
post the output of cat /etc/mdadm/mdadm.conf
That explains that error, I wonder where that came from, cos that doesn't look like an OMV setup but it could be OMV picked up some metadata from a drive/s
That explains that error, I wonder where that came from, cos that doesn't look like an OMV setup but it could be OMV picked up some metadata from a drive/s
What does that means?
And what do I have to do to eventually solve (without risks)?
What does that means
Pass, sorry
And what do I have to do to eventually solve (without risks)
Pass again, seen this once before when a user was having an issue with a Raid50, it was never really looked at, it's there, it's doing nothing and will not affect your system
BTW you have now moved into what I call 'squeaky bum' territory, 6 drives in a Raid5 
'rule of thumb' is, once you get over 4 drives move to Raid6 especially when using larger drives.
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!
