The first button (looks like an arrow head or play symbol) is for mounting existing filesystems.
I have never seen that grayed out myself. If the drives show in the drives list and smart, the only reason I could see you not being able to mount them is if there is no filesystem on them or the filesystem is not compatible with OMV.
Were these mounted before as single drives?
What was the filesystem ued on them? If it was something like ZFS that needs to be installed.
If they were not single drives, how were they configured? mdadm raid, mergefs , etc?
mdadm raids easily remount with that little button that you say is greyed out. I have no experience with mergefs to guide you there.
If you are not sure on how they were formatted and configured, you can try looking at the output of blkid and lsblk to see what you have
look at the line in blkid that names the RAID device. It should be an MD###. That will tell you the file system used after TYPE
Mine looks like this as an example (xfs is the filesystem I used):
/dev/md127: LABEL="NASR5" UUID="4d26adbd-029a-4d74-a81f-c69bf193a099" BLOCK_SIZE="4096" TYPE="xfs"Your lsblk should look something like this. RO is read only, but the 0 under it means "no", while a 1 would mean "yes"
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdd 8:48 0 3.6T 0 disk
└─md127 9:127 0 18.2T 0 raid5 /srv/dev-disk-by-uuid-4d26adbd-029a-4d74-a81f-c69bf193a099
sde 8:64 0 3.6T 0 disk
└─md127 9:127 0 18.2T 0 raid5 /srv/dev-disk-by-uuid-4d26adbd-029a-4d74-a81f-c69bf193a099
sdf 8:80 0 3.6T 0 disk
└─md127 9:127 0 18.2T 0 raid5 /srv/dev-disk-by-uuid-4d26adbd-029a-4d74-a81f-c69bf193a099
sdg 8:96 0 3.6T 0 disk
└─md127 9:127 0 18.2T 0 raid5 /srv/dev-disk-by-uuid-4d26adbd-029a-4d74-a81f-c69bf193a099
sdh 8:112 0 3.6T 0 disk
└─md127 9:127 0 18.2T 0 raid5 /srv/dev-disk-by-uuid-4d26adbd-029a-4d74-a81f-c69bf193a099
sdi 8:128 0 3.6T 0 disk
└─md127 9:127 0 18.2T 0 raid5 /srv/dev-disk-by-uuid-4d26adbd-029a-4d74-a81f-c69bf193a099Here is a little lsblk tutorial
Linux lsblk Command Tutorial For Beginners
have a look at mdadm --detail /dev/md### replacing the ### with the md number of your array. This will tell you the number of drives and if all the drives are functioning.
Verify the number of devices in the total, active, working, failed, and spare make sense, make sure superblock is there.
It should look something like this when the array is working. Note mine is a RAID5:, Yours may be different. if you tried to do a RAID10, this could get very complicated sine you will have nested RAID levels.
/dev/md127:
Version : 1.2
Creation Time : Tue Nov 23 19:29:45 2021
Raid Level : raid5
Array Size : 19534430720 (18.19 TiB 20.00 TB)
Used Dev Size : 3906886144 (3.64 TiB 4.00 TB)
Raid Devices : 6
Total Devices : 6
Persistence : Superblock is persistent
Intent Bitmap : Internal
Update Time : Fri May 26 01:02:56 2023
State : active
Active Devices : 6
Working Devices : 6
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 512K
Consistency Policy : bitmap
Name : nas:NASR5 (local to host nas)
UUID : 9a94e451:1ea30c84:2f0405aa:2f4a75bc
Events : 144256
Number Major Minor RaidDevice State
0 8 48 0 active sync /dev/sdd
1 8 64 1 active sync /dev/sde
2 8 80 2 active sync /dev/sdf
3 8 96 3 active sync /dev/sdg
4 8 112 4 active sync /dev/sdh
5 8 128 5 active sync /dev/sdiIf you see any errors, it might help to post the full outputs of these commands.
I am not the forum's resident mdadm expert, so if you have to start manually assembling or reconstructing the array with mdadm, it might be best to ask geaves . If it was my own array, I would probably try to use UFS Explorer data recovery software I have access to, to assemble it and make sure I have a copy of everything important before trying any mdadm manipulations, and then I would spend a bit of time reading researching the commands to get it right, but he may be able to direct you quicker.
Reading the first post ssh into OMV and post the output of cat /proc/mdstat for some reason whilst OMV 'finds' the array after a clean install it doesn't always come up as active. Therefore no information is displayed in raid management and no filesystem is shown
I am assuming it is inactive
Yep,
mdadm --stop /dev/md127
mdadm --assemble --force --verbose /dev/md127 /dev/sd[abcdefghjk]
I think I have all the drive references, but double check
will that command run assemble all the drives consecutively.
Yes, it saves writing /dev/sda /dev/sdb /dev/sdc........and so on, you can do that if you want 
so this is producing an error, maybe that disk dead
It might be, do the same commands again as in #12 but leave out that drive and the array should come back as clean degraded
when i do that it says and the array is not showing up in filesystem
In filesystems select mount an existing filesystem, looks like a play icon
it still won't mount
AFAIK you click on mount a page opens with a dropdown to select what you want to mount, click save then apply
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!
