I have been running OMV 3 on an RPi 2 for some time, and today it suddenly misbehaved. Initially the web interface didn't work, then after reboot it goes into emergency mode and from there into "raising network interfaces" which runs forever with no limit. My conclusion - the SD card is fried (checks confirm this is very likely).
I need to recover the files on the Raid disks if possible (2 x 1TB). When I cut a new OMV 3 SD card and reboot, "Physical disks" can see them as sda and sdb, but "File systems" cannot. This means I cannot mount them from the web interface to retrieve the files or rebuild a more robust OMV setup. If I try to mount them myself, this fails. See below result of lsblk and attempted mount:
root@raspberrypi:~# lsblk -f
NAME FSTYPE LABEL UUID MOUNTPOINT
sdb linux_ra raspberrypi:Raid1Mirror
66243d3d-07e1-5847-606e-f191a34992a9
zram3 swap 651c5e00-c9e0-401a-8ac0-6c520247b927 [SWAP]
zram1 swap dd347844-695b-4769-9972-e739b62b7370 [SWAP]
sda linux_ra raspberrypi:Raid1Mirror
66243d3d-07e1-5847-606e-f191a34992a9
zram2 swap cddd0ffa-9b66-46b4-a564-8a8e0ec6bec0 [SWAP]
zram0 swap 46667f81-5744-480e-bfe4-bc07f6565dac [SWAP]
mmcblk0
├─mmcblk0p2 ext4 ae708a4d-982a-4a20-965c-01ec7e1f32b3 /
├─mmcblk0p3
└─mmcblk0p1 vfat boot CE83-8CE1 /boot
root@raspberrypi:~# mount -U 66243d3d-07e1-5847-606e-f191a34992a9 /media/66243d3d-07e1-5847-606e-f191a34992a9
mount: unknown filesystem type 'linux_raid_member'
Alles anzeigen
As I use OMV for domestic backups, my plan is to move to 2 x RPi3 OMV 3 implementations with SSD for OMV itself plus 1 of the 2 x 1TB HDD used for backups now. Therefore if I can get help to mount the existing RAID initially so I can get the data copied somewhere else, or remove the Raid SAFELY so I can mount one of them as ext4 that would be very helpful.