I replaced one disk and in Raid Management and after that - the entry was dissapeared from OMV Gui
How did you replace the drive
power off machine and swapped the one disk with other. After that my Raid entry dissapeared from GUI (it was visible via command line as inactive)
That's the correct behavior, madadm (software raid) is not hot swappable like a hardware raid controller
Expected behavior is that necessary steps to recover RAID will be available on GUI.
It is;
To replace a failing drive;
Raid Management, select the array, on the menu click delete, from the dialog select the failing drive, click OK, the drive will be failed and removed from the array.
Then;
Shutdown the machine, removed the failed drive and install new one, restart.
Storage -> Disks, select the new drive on the menu click wipe, then short, wait until completed.
Raid Management, select the array (which should display as clean/degraded), on the menu click Recover, from the dialog select the drive that has been added and wiped, click OK
The array should now rebuild.
If an array displays as clean/degraded then mdadm has failed the drive and remove it from the array, in that case you shutdown and replace the failed drive.
I replaced one disk and in Raid Management and after that - the entry was dissapeared from OMV Gui.
In that case /proc/mdstat did not contain any data that OMV can use to display in the UI.
You can add/recover a RAID via UI
Здравствуйте, у меня создан REID 1. Зеркало. Один диск посыпался, хочу его заменить, мне просто выключить накопитель снять старый, поставить новый и включить? Что то надо делать еще??? Помогите пожалуйста боюсь потерять данные, а диск надо сдавать по гарантии, а то он так и будет сыпаться. Спасибо
It is;
To replace a failing drive;
Raid Management, select the array, on the menu click delete, from the dialog select the failing drive, click OK, the drive will be failed and removed from the array.
Is there a way to identify the physical drive?
I'f a RAID6 with 6 Drives where two of them start to get bad sectors; time to replace I think. But I use a 19" 12-bay case where also a 2nd Mirror-set and plain drives are exist.
So I have no idea which one are the two to slide out... (one by one obvious...)
Any hint?
Is there a way to identify the physical drive
Yes, create an Excel spreadsheet, take a screenshot of storage disks, this will give you the model and serial number.
Shutdown the server, pull each drive one by one making a note of it's position in the server, transfer the information of each drive to the spreadsheet, you'll then have the information you need to replace the necessary drives.
Simples 
shure... Simple as hell 
My Q point more in a technical way. I know that must be possible to let the DriveLED blink or switch off. I have seen that on an other system.
But ok... For now your way will do it also 
My Q point more in a technical way.
we don't do technical only KIS
Raid Management, select the array (which should display as clean/degraded), on the menu click Recover, from the dialog select the drive that has been added and wiped, click OK
... tja ... fail ... Done the way you described before step by step but the RAID6 don't show up anymore!!!
SDB is the new one, A to F was the RAID6 but that doesn't shop up...
And now?!?
Ok go back to the CLI and run cat /proc/mdstat and blkid
... and now? What I have to do with this?
I see that the RAID6 named md126 is inactive... I have try to shutdown, plugin the old drive and fireup, but that don't change anything.
Now I have shutdown, plugin the new SDB and fireup, copy the result of what you telling me to do ...
root@SV-OMV-NAS:~# cat /proc/mdstat
Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10]
md126 : inactive sde[4](S) sdd[2](S) sda[0](S) sdc[3](S) sdf[5](S) sdg[6](S)
11720310288 blocks super 1.2
md127 : active raid1 sdj[1] sdi[0]
7813894464 blocks super 1.2 [2/2] [UU]
bitmap: 2/59 pages [8KB], 65536KB chunk
unused devices: <none>
root@SV-OMV-NAS:~# blkid
/dev/sdl1: UUID="b582676e-e6dc-4cf3-81f3-9aaaed9e08eb" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="b843e8a0-01"
/dev/sdl5: UUID="549e5698-dbad-42f5-9491-a423f2ee530b" TYPE="swap" PARTUUID="b843e8a0-05"
/dev/sda: UUID="a8a7fe8b-49af-179d-fbed-107b9af555a9" UUID_SUB="b98cf955-1869-3196-9816-a4d3c4f4356e" LABEL="SV-OMV-NAS.BUCHHOLZ:RAID6a" TYPE="linux_raid_member"
/dev/sde: UUID="a8a7fe8b-49af-179d-fbed-107b9af555a9" UUID_SUB="28baac2d-361e-55d2-7481-da7bbcd18ea2" LABEL="SV-OMV-NAS.BUCHHOLZ:RAID6a" TYPE="linux_raid_member"
/dev/sdj: UUID="cb4bd60b-28ed-16b8-d5b6-0d15fb3452b8" UUID_SUB="45a5aebd-f205-610c-43fb-f9d78bf7f9a7" LABEL="SV-OMV-NAS:2x8tb" TYPE="linux_raid_member"
/dev/sdg: UUID="a8a7fe8b-49af-179d-fbed-107b9af555a9" UUID_SUB="01aa4fa4-bc68-16a5-684d-56f54fa2210b" LABEL="SV-OMV-NAS.BUCHHOLZ:RAID6a" TYPE="linux_raid_member"
/dev/sdf: UUID="a8a7fe8b-49af-179d-fbed-107b9af555a9" UUID_SUB="4beb7d5c-1514-bdbd-2e00-331c6f180c80" LABEL="SV-OMV-NAS.BUCHHOLZ:RAID6a" TYPE="linux_raid_member"
/dev/sdc: UUID="a8a7fe8b-49af-179d-fbed-107b9af555a9" UUID_SUB="d43480d8-8483-b6eb-d2ad-a4bc347b4eb4" LABEL="SV-OMV-NAS.BUCHHOLZ:RAID6a" TYPE="linux_raid_member"
/dev/sdh2: LABEL="WD-RED-4TB-1" BLOCK_SIZE="512" UUID="60746FA2746F79A4" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="63110a97-0a51-42fc-aece-3f0ca4d6e8e3"
/dev/sdd: UUID="a8a7fe8b-49af-179d-fbed-107b9af555a9" UUID_SUB="e6caf7c1-9e9b-2f34-faa3-825759434703" LABEL="SV-OMV-NAS.BUCHHOLZ:RAID6a" TYPE="linux_raid_member"
/dev/sdi: UUID="cb4bd60b-28ed-16b8-d5b6-0d15fb3452b8" UUID_SUB="5f421642-05ea-b9bb-8a17-43bee29aea62" LABEL="SV-OMV-NAS:2x8tb" TYPE="linux_raid_member"
/dev/md127: LABEL="2x8tb" UUID="fd72314a-9b1a-4983-b5ef-02e1f0a797be" BLOCK_SIZE="4096" TYPE="ext4"
/dev/sdh1: PARTLABEL="Microsoft reserved partition" PARTUUID="adc2c666-abeb-446d-b69f-7c1b57c9feaa"
root@SV-OMV-NAS:~#mdadm --stop /dev/md126
mdadm --assemble --force --verbose /dev/md126 /dev/sd[acdefg]
... well done! You save my ass!
Now I have click repair, add the new drive and it just startet to recovering... Looks good!
The only what I see now is that the RAID6 catch the 7th drive also and I have no idea why... But that's not a problem. That was only a drive for the PVR- system via FTP what I can change later; no robbery in Town tonight I hope ;o)
well done!
You're welcome 
Ok... very bad things 
The restored RAID6 is empty!
If I take a look via SSH and open /srv/[uuid] there is not a single file 
How can that be?
The restored RAID6 is empty
That makes no sense....
Now I have click repair, add the new drive and it just startet to recovering... Looks good
When I read the above that was somewhat confusing, I'll explain;
The output of cat /proc/mdstat showed the array as inactive (there a few reasons why this happens) the output of blkid confirmed the 6 drives within that array /dev/sd[acdefg]
After running mdadm --stop the second mdadm command is just reassembling the array and there would have been some output and it would have confirmed that the array was reassembled and started with the 6 drives, likewise if there were any errors.
Don’t have an account yet? Register yourself now and be a part of our community!