What happened:
I recently wanted to install OpenVPN to my OMV v4.1.23-1 and consulted a YouTube video of TechnoDadLife (Link follows). Anyways, after the first steps I had to reboot the system only to find that my Mirror RAID1 (it was encrypted using LUKS) was gone. It's also gone in the encryption section.
I have read through a couple of threads here, but was yet unable to mount even a single of the two disks, let alone the RAID. After having read these threads, I assume my manual edit of the config.xml and following omv-mkconf fstab was the reason for this error, though I'm clueless why. The exact procedure can be found at this timestamp of the video: https://youtu.be/nMthOobE-8g?t=172 - nothing really complicated especially up to this point.
When I try to create a new file system, OMV says it'll format the drive(s), which of course I do not want to happen.
I have already tried to reactivate the RAID by using mdadm -assemble, here's the output:
root@Serverlein:~# mdadm --assemble /dev/md0 /dev/sd[de]
mdadm: no recogniseable superblock on /dev/sdd
mdadm: /dev/sdd has no superblock - assembly abortedHere's the output to the Degraded or missing raid array questions
root@Serverlein:~# cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
unused devices: <none>
root@Serverlein:~# blkid
/dev/sda1: UUID="2101453d-5973-470f-b374-ca4b8ca56cf3" TYPE="ext4" PARTUUID="2ce08785-01"
/dev/sda5: UUID="262280ab-2e12-4a5f-9b81-86c45670afa6" TYPE="swap" PARTUUID="2ce08785-05"
/dev/sdb: UUID="7012eb61-0ef6-4c55-912a-1a8f524d26e5" TYPE="crypto_LUKS"
/dev/sdc: UUID="f9985f7e-c937-4873-bff9-4fcf41bef625" TYPE="crypto_LUKS"
/dev/mapper/sdb-crypt: LABEL="8TB1" UUID="3ce321fd-a407-4ddf-9fd7-0e7dc50bb461" TYPE="ext4"
/dev/mapper/sdc-crypt: LABEL="8TB2" UUID="55493042-ba3b-4ecf-8430-68bd435d849b" TYPE="ext4"
root@Serverlein:~# fdisk -l | grep "Disk "
Disk /dev/sda: 111.8 GiB, 120034123776 bytes, 234441648 sectors
Disk identifier: 0x2ce08785
Disk /dev/sdb: 7.3 TiB, 8001563222016 bytes, 15628053168 sectors
Disk /dev/sdd: 3.7 TiB, 4000753476096 bytes, 7813971633 sectors
Disk /dev/sde: 3.7 TiB, 4000753476096 bytes, 7813971633 sectors
Disk /dev/sdc: 7.3 TiB, 8001563222016 bytes, 15628053168 sectors
Disk /dev/mapper/sdb-crypt: 7.3 TiB, 8001561124864 bytes, 15628049072 sectors
Disk /dev/mapper/sdc-crypt: 7.3 TiB, 8001561124864 bytes, 15628049072 sectors
root@Serverlein:~# cat /etc/mdadm/mdadm.conf
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#
# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
# Note, if no DEVICE line is present, then "DEVICE partitions" is assumed.
# To avoid the auto-assembly of RAID devices a pattern that CAN'T match is
# used if no RAID devices are configured.
DEVICE partitions
# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes
# automatically tag new arrays as belonging to the local system
HOMEHOST <system>
# definitions of existing MD arrays
ARRAY /dev/md0 metadata=1.2 name=Serverlein:RAID4TB UUID=fff47ee3:74f5432a:863f8e22:11789248
# instruct the monitoring daemon where to send mail alerts
MAILADDR koenich@koenich.com
MAILFROM rootroot@Serverlein:~# mdadm --detail --scan --verbose
So the two drives for the RAID are /dev/sdd and /dev/sde, both with 4TB capacity (see screenshots below as well). And as said, encrypted using the LUKS / the encryption plugin. Worked perfectly well until this reboot...
Somehow I have the feeling that OMV "forgot" that these drives are encrypted and needs to be told and afterwards would be fine to recreate the RAID, but I do not know how.
Here's a screenshot of file systems with the missing RAID:
And here's one showing the 5 disks of my server. A 128GB SSD as system drive sda, two 8TB drives sdb & sdc (both LUKS encrypted as well) and the two 4TB drives sdd&sde which used to be the LUKS encrypted RAID:
