Hi all,
I am reinstalling OMV (latest version) onto an existing machine that was running an older version of OMV (version 5 or 6, not sure).
It is an HP Microserver Gen 7 which boots off a 2.5 inch SSD mounted in the ODD bay and has 2 x 2TB SATA hard drives in a RAID 1 in the first two caddy slots.
The machine was running fine but suffered a failure of the SSD and (obviously) stopped functioning, so I inserted a new SSD and installed OMV 7 to it.
Initially, I left the RAID drives out for safety until I had the installation complete and could prove the system functionality. Once that was done, I shut the machine down, inserted the RAID drives and rebooted.
After the system came up, the RAID did not appear in the dashboard. However, using a directly attached keyboard and screen I could see the RAID was there. I could manually mount it to /mnt and the contents were visible, so they RAID was not corrupted.
I thought it might be because the RAID was not detected at installation time, so I did the installation again, but with the RAID disks installed. During the partitioning selection process it offered a RAID1 array as a possible target, so the detection was successful. However, after the initial boot, the RAID manaagement option was still missing from the dashboard.
I researched this issue in the forum with no success, so I am embedding some printouts which seemed relevant in other cases
BR
Mick
root@odysseus:~# cat /proc/mdstat
Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10]
md0 : active raid1 sdb1[1] sdc1[0]
1953382400 blocks super 1.2 [2/2] [UU]
bitmap: 0/15 pages [0KB], 65536KB chunk
unused devices: <none>root@odysseus:~# mdadm --detail --scan --verbose
ARRAY /dev/md/0 level=raid1 num-devices=2 metadata=1.2 name=odysseus.internal.net:0 UUID=270a3820:d7386050:f7eaaaa7:d41c577a
devices=/dev/sdb1,/dev/sdc1The following mdadm.conf is unmodifed from the fresh install
root@odysseus:~# 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 Sat, 17 Feb 2024 11:39:02 +0000 by mkconfroot@odysseus:~# blkid
/dev/sdb1: UUID="270a3820-d738-6050-f7ea-aaa7d41c577a" UUID_SUB="f125f419-126f-766e-fca4-098a2c7073d1" LABEL="odysseus.internal.net:0" TYPE="linux_raid_member" PARTLABEL="primary" PARTUUID="0d9b0909-2c3a-48a3-9b51-cf38d57a04e3"
/dev/md0: UUID="58ef7588-5e20-43ea-ac6e-1e6a93767afb" BLOCK_SIZE="4096" TYPE="ext4"
/dev/sdc1: UUID="270a3820-d738-6050-f7ea-aaa7d41c577a" UUID_SUB="39e35f13-5503-77a6-b01b-6af1bf96bd5b" LABEL="odysseus.internal.net:0" TYPE="linux_raid_member" PARTLABEL="primary" PARTUUID="8a737892-d22e-4498-97ed-0a111844c64d"
/dev/sda5: UUID="be007ae5-52d5-4c5f-a987-b1120050c003" TYPE="swap" PARTUUID="675fc17e-05"
/dev/sda1: UUID="a4776153-5c42-440b-a59f-e64467189d58" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="675fc17e-01"
root@odysseus:~# fdisk -l | grep "Disk "
Disk /dev/sda: 232.89 GiB, 250059350016 bytes, 488397168 sectors
Disk model: Samsung SSD 870
Disk identifier: 0x675fc17e
Disk /dev/sdb: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: ST2000DM001-1CH1
Disk identifier: ED13D764-D033-4FED-B59B-F67222F46B38
Disk /dev/sdc: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: ST2000DM001-1CH1
Disk identifier: 61F2FE22-DA9D-4530-9CE3-B9005AF5CD59
Disk /dev/md0: 1.82 TiB, 2000263577600 bytes, 3906764800 sectors
