Pretty new here, but I'll try to make this as clear as I can... (sorry, it's long.)
OMV6 on AMD x64 KeyScan KSNAS120 (4-bay). / is on a 1TB spinner. 4 bays each have a 4TB drive, with the plan to have 2x data, 1x parity, 1x backup. I just installed and had everything almost set up how I wanted a few weeks ago. Even did my first checks in SnapRAID. Then the system wouldn't boot. Something happened to GRUB. I tried most of the fixes, nothing worked, so I just re-installed. I didn't yet have a backup, so this was fresh.
When I re-installed The drives and tried to reconfigure the filesystems and shares, I couldn't get the second data drive (dev/sdb1) to work. Looking into it, it appeared that somehow, it had 'assumed' the same UUID as the boot drive in fstab.
root@minion:~# lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINT
sda
├─sda1 vfat FAT32 110E-BF08 510.8M 0% /boot/efi
├─sda2 ext4 1.0 c6c18332-957f-4f69-b04e-b691d24c6036 87.8G 3% /
├─sda3 swap 1 dd8c7faf-5da9-4c2a-9231-c504dba77920 [SWAP]
└─sda4 ext4 1.0 04af4f70-aea3-4ef2-b84b-6f6ccc2ff0dc
sdb
└─sdb1 ext4 1.0 c6c18332-957f-4f69-b04e-b691d24c6036 **NOTE: NO mount point information for sdb1, and UUID is same as sda2**
sdc
└─sdc1 ext4 1.0 001518ec-ad92-4ff9-b845-9985be241372 2T 45% /srv/dev-disk-by-uuid-001518ec-ad92-4ff9-b845-9985be241372
sdd
└─sdd1 ext4 1.0 291de9c4-0262-4e47-b3f6-e1522edb931e 1.9T 46% /srv/dev-disk-by-uuid-291de9c4-0262-4e47-b3f6-e1522edb931e
sde
└─sde1 ext4 1.0 40ca4384-b937-44e2-8aff-e2a80c4a9ff0 2T 45% /srv/dev-disk-by-uuid-40ca4384-b937-44e2-8aff-e2a80c4a9ff0
/etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda2 during installation
UUID=c6c18332-957f-4f69-b04e-b691d24c6036 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sda1 during installation
UUID=110E-BF08 /boot/efi vfat umask=0077 0 1
# swap was on /dev/sda3 during installation
UUID=dd8c7faf-5da9-4c2a-9231-c504dba77920 none swap sw 0 0
# >>> [openmediavault]
/dev/disk/by-uuid/c6c18332-957f-4f69-b04e-b691d24c6036 /srv/dev-disk-by-uuid-c6c18332-957f-4f69-b04e-b691d24c6036 ext4 defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota>
/dev/disk/by-uuid/001518ec-ad92-4ff9-b845-9985be241372 /srv/dev-disk-by-uuid-001518ec-ad92-4ff9-b845-9985be241372 ext4 defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota>
/dev/disk/by-uuid/291de9c4-0262-4e47-b3f6-e1522edb931e /srv/dev-disk-by-uuid-291de9c4-0262-4e47-b3f6-e1522edb931e ext4 defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota>
/dev/disk/by-uuid/40ca4384-b937-44e2-8aff-e2a80c4a9ff0 /srv/dev-disk-by-uuid-40ca4384-b937-44e2-8aff-e2a80c4a9ff0 ext4 defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota>
/dev/disk/by-uuid/4feee735-58c5-4c11-beb0-c3ed6470442e /srv/dev-disk-by-uuid-4feee735-58c5-4c11-beb0-c3ed6470442e ext4 defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota>
/dev/disk/by-uuid/2132aca3-ac90-46f5-995a-4df087469214 /srv/dev-disk-by-uuid-2132aca3-ac90-46f5-995a-4df087469214 ext4 defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota>
# <<< [openmediavault]
The original FS UUID (...6470442e) for dev/sdb1 was still in fstab, but wasn't being associated with the filesystem any longer. I tried several different things found in these forums and elsewhere to try and fix it, but nothing worked. So I just wiped the drive, recreated the filesystem, and remounted it in the GUI. All of that worked fine, but when I got the Configuration change prompt, I get an error that I can't get around. It looks like the system is still trying to find the original mountpoints, and I don't know how to fix it.
From the syslog output, it continues to try and mount ...c6036 (the incorrect duplicate) and ...70442e (the previous FS) (...469214 also, but that was a flash drive and I'm hoping that your help to fix the others will fix that one too).
Also included output of latest omv-salt deploy run fstab.
Please let me know if you need anything else to help clarify the problem. TIA for your time.