Hi!
First off, English is not my main language, but I hope it's not to bad
I have an HP Microserver gen8 with two HGST 4Tb drives in raid1 and a single WD red 2Tb drive. I had OMV 3 (something) installed to a USB drive and the system became corrupt so i did an new install of OMV 5 to an SSD. But in order to boot from the SSD i had to move the HGST (raid1) from "port ?" 1 and 2 two 2 and 3, if it affects this?
The installation went fine and i can see all the drives i disks, i can see the raid1 in raid management, both the single WD red and the raid1 show up in file systems, but i´m only able to mount the single WD red, the mount button on the raid1 is grayed out.
After searching around in the forums, and om other sites on the internet i did find 1 thread i the OMV forum whit an similar case, but i´m an toddler (noob) to this so i thought it was better to be safe than sorry.
1 "cat /proc/mdstat"
root@SkumNas:~# cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md127 : active (auto-read-only) raid1 sdc[0] sdb[1]
3906887360 blocks super 1.2 [2/2] [UU]
unused devices: <none>
2 "blkid"
root@SkumNas:~# blkid
/dev/sda1: UUID="f152ef00-0891-4829-b464-200d28baac07" TYPE="ext4" PARTUUID="ec79dd45-01"
/dev/sda5: UUID="1e9c93f8-f8b1-4fa6-98ed-21c41c2e5e9f" TYPE="swap" PARTUUID="ec79dd45-05"
/dev/sdb: UUID="01f45529-b1e1-dce3-650a-a77f14b74d20" UUID_SUB="640a5833-0897-e5a3-33b3-40b751d37187" LABEL="SkumNAS:SkumNAS" TYPE="linux_raid_member"
/dev/sdc: UUID="01f45529-b1e1-dce3-650a-a77f14b74d20" UUID_SUB="367468af-9c33-d4b5-9c51-63dcbada9bf5" LABEL="SkumNAS:SkumNAS" TYPE="linux_raid_member"
/dev/sdd1: LABEL="SkumRASK" UUID="b7f06a91-c410-406c-bda1-ef791575058a" TYPE="ext4" PARTUUID="0044af10-61d8-4b5a-9098-d41b3c9f478a"
3 "fdisk -l | grep "Disk ""
root@SkumNas:~# fdisk -l | grep "Disk "
The primary GPT table is corrupt, but the backup appears OK, so that will be used.Disk /dev/sda: 111.8 GiB, 120034123776 bytes, 234441648 sectors
Disk model: GIGABYTE GP-GSTF
Disk identifier: 0xec79dd45
The primary GPT table is corrupt, but the backup appears OK, so that will be used.
Disk /dev/sdb: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: HGST HDN724040AL
Disk identifier: 228F371D-6878-4EF2-9053-703F24F61CEB
Disk /dev/md127: 3.7 TiB, 4000652656640 bytes, 7813774720 sectors
Disk /dev/sdc: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: HGST HDN724040AL
Disk identifier: DC419BEB-303A-47BA-8F05-1F47C2EEDD35
Disk /dev/sdd: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: WDC WD20EFRX-68E
Disk identifier: 7CF39CA4-5B1E-4DEB-9C69-010A38B6F629
4 "cat /etc/mdadm/mdadm.conf"
root@SkumNas:~# cat /etc/mdadm/mdadm.conf
# mdadm.conf
#
# !NB! Run update-initramfs -u after updating this file.
# !NB! This will ensure that initramfs has an uptodate copy.
#
# Please refer to mdadm.conf(5) for information about this file.
#
# by default (built-in), scan all partitions (/proc/partitions) and all
# containers for MD superblocks. alternatively, specify devices to scan, using
# wildcards if desired.
#DEVICE partitions containers
# automatically tag new arrays as belonging to the local system
HOMEHOST <system>
# instruct the monitoring daemon where to send mail alerts
MAILADDR root
# definitions of existing MD arrays
# This configuration was auto-generated on Fri, 16 Aug 2019 07:12:16 +0000 by mkconf
5 "mdadm --detail --scan --verbose"
root@SkumNas:~# mdadm --detail --scan --verbose
ARRAY /dev/md/SkumNAS level=raid1 num-devices=2 metadata=1.2 name=SkumNAS:SkumNAS UUID=01f45529:b1e1dce3:650aa77f:14b74d20
devices=/dev/sdb,/dev/sdc