Hello everybody,
my NAS with OMV 5 worked fine for years, now it was time to update it to V6.
Everything about the upgrade worked fine, except this:
I have a boot drive 120 gb SSD (usb - its a terramaster nas and device /dev/sdc) and a raid 1 created with OMV 5 on /dev/md0.
After Upgrade to 6 i see /dev/md0 in Storage - Software Raid: Its clean, healthy and made of /dev/sda and /dev/sdb
In File Systems i only see Partition /dev/sdc3 (there are my docker containers on it) , but nothing else, no sdc (the boot drive), no sda, sdb or md0.
So its also not possible to create Samba file shares or else, because only sdc3 is visible for omv.
Tried it with installed webmin, shares with samba can be created and working, but they are of course gone when OMV overwrites the smb.conf.
I have been read most everything in the forum and google and also tested most every hint about this, but no success.
I know that there maybe an issue with OMVs Database, that these drives are not seen, but i dont know how i can fix this..
Do you have any ideas ? Thanks a lot for any help..... with OMV5 all worked fine in this configuration.
~# cat /proc/mdstat
Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10]
md0 : active raid1 sda[0] sdb[1]
3906886464 blocks super 1.2 [2/2] [UU]
bitmap: 0/30 pages [0KB], 65536KB chunk
unused devices: <none>
:~# blkid
/dev/sda: UUID="8ec9a44c-a3f6-51fc-01e5-b1d4c3f8229a" UUID_SUB="372921da-bf4a-8c76-f328-1f31321a910e" LABEL="omv5nas:data" TYPE="linux_raid_member"
/dev/sdb: UUID="8ec9a44c-a3f6-51fc-01e5-b1d4c3f8229a" UUID_SUB="addaeafd-255a-c299-5dab-07733aed1c7f" LABEL="omv5nas:data" TYPE="linux_raid_member"
/dev/md0: UUID="0de3ebb0-b8bf-4303-b628-5dbe98153e4a" TYPE="crypto_LUKS"
/dev/sdc1: UUID="af318bcf-adc8-452d-8671-8b60031e6d43" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="2815dfe4-01"
/dev/sdc3: LABEL="docker" UUID="5a341348-c332-4d73-9b40-7122e52dfb37" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="2815dfe4-03"
/dev/sdc5: UUID="3bf9f84e-9a79-4fde-822b-d16f76c1aeba" TYPE="swap" PARTUUID="2815dfe4-05"
/dev/sdd1: UUID="3F83-90B4" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="89687d8f-01"
/dev/mapper/crypt_hdd1: UUID="dbaf88f0-983b-48aa-8829-a22b7433215b" BLOCK_SIZE="4096" TYPE="ext4"
# fdisk -l | grep "Disk "
Disk /dev/sda: 3,64 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: ST4000VX007-2DT1
Disk /dev/sdb: 3,64 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: ST4000VX007-2DT1
Disk /dev/md0: 3,64 TiB, 4000651739136 bytes, 7813772928 sectors
Disk /dev/sdc: 111,78 GiB, 120024203264 bytes, 234422272 sectors
Disk model: 2115
Disk identifier: 0x2815dfe4
Disk /dev/sdd: 7,38 GiB, 7927234560 bytes, 15482880 sectors
Disk model: Basic Line
Disk identifier: 0x89687d8f
Disk /dev/mapper/crypt_hdd1: 3,64 TiB, 4000634961920 bytes, 7813740160 sectors
:~# cat /etc/mdadm/mdadm.conf
# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.
# 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>
# instruct the monitoring daemon where to send mail alerts
MAILADDR dings@wwww.com
MAILFROM root
# definitions of existing MD arrays
ARRAY /dev/md0 metadata=1.2 name=omv5nas:data UUID=8ec9a44c:a3f651fc:01e5b1d4:c3 f8229a
:~# mdadm --detail --scan --verbose
ARRAY /dev/md0 level=raid1 num-devices=2 metadata=1.2 name=omv5nas:data UUID=8ec9a44c:a3f651fc:01e5b1d4:c3f8229a
devices=/dev/sda,/dev/sdb