RAID1 not found after updating to OMV 5.3.9-1 (Usul)

SS113 · Apr 2nd 2020

Hello,

Tonight I saw there was a new update to OMV (5.3.9-1 (Usul)) and I went ahead and updated it (I was on 5.x.x already before the update). Everything went fine and since I did this just after a new boot, my RAID1 wasn't mounted yet. I went to File Systems menu and noticed the raid file system status is not "Missing".

If I try to create a new file system I can pick the RAID1 but that will wipe all data on it which I can't afford to do. I also noticed it's now set to be coming from /dev/md127 instead of what it used to be /dev/disk/by-label/RAID1

Not too sure what to do at this point and any help would be appreciated.

For more info I also got 2 emails on this from OMV upon restart:

Code

Host:        \NAS.local
Date:        Wed, 01 Apr 2020 23:42:54
Service:     mountpoint_srv_dev-disk-by-label-RAID1
Event:       Status failed
Description: status failed (1) -- /srv/dev-disk-by-label-RAID1 is not a mountpoint


Host:        \NAS.local
Date:        Wed, 01 Apr 2020 23:42:24
Service:     filesystem_srv_dev-disk-by-label-RAID1
Event:       Does not exist
Description: unable to read filesystem '/srv/dev-disk-by-label-RAID1' state

Display More

Here is the output from fdisk -l

Code

root@NAS:~# fdisk -l

Disk /dev/sda: 7.3 TiB, 8001563222016 bytes, 15628053168 sectors
Disk model: WDC WD8001FFWX-6
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/sdb: 7.3 TiB, 8001563222016 bytes, 15628053168 sectors
Disk model: WDC WD8001FFWX-6
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/md127: 7.3 TiB, 8001428979712 bytes, 15627790976 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/sdc: 114.6 GiB, 123010547712 bytes, 240254976 sectors
Disk model: Ultra Fit
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 2E228E89-B923-46F8-8FCF-8A595AC6235F


Device         Start       End   Sectors   Size Type
/dev/sdc1       2048   1050623   1048576   512M EFI System
/dev/sdc2    1050624 232089599 231038976 110.2G Linux filesystem
/dev/sdc3  232089600 240252927   8163328   3.9G Linux swap

Display More

and blkid /dev/md*

Code

root@NAS:~# blkid /dev/md*
/dev/md127: UUID="f408fd50-d1eb-41bf-be1d-a75ad820cb23" TYPE="crypto_LUKS"

If you need to look at anything else please let me know.

Thank you!

SS113 · Apr 2nd 2020

So I found my problem

In older version before this update, after a new boot, I'd have to mount the RAID1 file system first and then enter my passcode to decrypt LUKS. With this new one, I have to decrypt it first and then mount it.

Glad it's working and I have my data again!

RAID1 not found after updating to OMV 5.3.9-1 (Usul)

votdev Apr 2nd 2020

votdev Apr 2nd 2020

Participate now!