So I solved this. Turns out I'm using pi login instead of omv default login, which I assume dont have enough right, hence the botched dashboard. All good now.
I just installed OMV on my pi 4 and to my surprise, it was OMV 6. I know it's beta, and that's fine for now. The first hurdle is the completely empty dashboard which can't be filled, or so it seems.
I am greeted with "The dashboard has not yet been configured. To personalize it, please go to the settings page."
Well, on the settings page, there is just an empty box titled "Enabled widgets". And I don't see any way to add any widgets or anything else.
Is this a common issue? Is it worth playing around with OMV 6 or is it not in a useable state?
tldr: OMV 6 is running but empty.
What if my docker is on my sd card? I am following the default path in the OMV docker settings. Is that a bad idea?
My OS is on the SD card, where I assume all the services will run from, is not delayed. Only the data harddisk that combined in the unionfs is delayed. Will that be a problem, and if is, what kind of service are affected by this?
Probably the Radxa hat. I have one too. https://wiki.radxa.com/Dual_Quad_SATA_HAT
yeah this is correct. The solution is here if anyone else facing the same issue:
Nvm, this is solved. Im using sata hat that is using its proprietary driver, which doesnt load when the drive being mounted. Solved it by editing disabling automount in fstab, and add them in rc.local.
Nope, not using LUKS.
I have been stuck, uninstalling and reinstalling OMV on my new pi 4 multiple time in the past couple of days, and narrow the problem down to unionfs plugin. Once I installed and pool my 3 drives together, next reboot will stuck at the "root account is locked". The server only become bootable again, once I edit in the cmdline.txt in the sd card, edited the fstab to remove the line added by the unionfs plugin.
Below is the error message from the boot screen:
This is the line I need to remove from my fstab in order to get it bootable again.
/srv/dev-disk-by-uuid-1cbb3ff5-a3ef-4b26-8cf9-0d8c16a9716f:/srv/dev-disk-by-uuid-565a0e37-55b6-4651-9503-a138d8f43285:/srv/dev-disk-by-uuid-c1cd54fb-889f-4008-9a61-11a96855616b /srv/ccb605bf-522c-4215-b959-1a4d830da0df fuse.mergerfs defaults,allow_other,cache.files=off,use_ino,category.create=mfs,minfreespace=4G,fsname=omvunion:ccb605bf-522c-4215-b959-1a4d830da0df,x-systemd.requires=/srv/dev-disk-by-uuid-1cbb3ff5-a3ef-4b26-8cf9-0d8c16a9716f,x-systemd.requires=/srv/dev-disk-by-uuid-565a0e37-55b6-4651-9503-a138d8f43285,x-systemd.requires=/srv/dev-disk-by-uuid-c1cd54fb-889f-4008-9a61-11a96855616b 0 0
I am novice in linux, so any help to assist me me running unionFS in my OMV is greatly appreciated.