After an energy shortage (coincidence, I now think), the disks on my Raspberry Pi 4 started to be mounted at a different location (“/media/pi/label” instead of “/srv/dev-disk-by-label-label”). I tried to reboot, but the error persisted.
Checking OMV5 web gui, I noticed that the "filesystems" tab was not working (kept "loading" indefinitely). Besides that, the system was giving me many "RPC something" errors that I couldn't understand.
So, I did a fresh install of everything, but, as I reconnected the HDDs, they kept being mounted at “/media/pi/label” and the OMV gui was acting the same way (the “filesystems” tab still wouldn't "load").
I, than, disconnected the two HDDs (they're connected via USB 3, and the dock has its own power source) and the web gui became responsive again, showing the “filesystems” tab. After that, I connected another two HDDs, and everything worked.
The only difference between the HDDs sets is that the problematic ones are formatted with BTRFS (the other two, that are working, are NTFS).
I've already verified the data on the BTRFS HDDs, and everything seems fine (I can access it as the disks are mounted on “/media/pi/label”; using SSH for that).
I tried to include the disks manually on “config.xml” (and ran "omv-salt deploy run fstab"), but didn't work (I copied the UUID and set the mount point at “/srv/dev-disk-by-label-label”, as it was before the problem started).
I really don't know what changed on the system, because it was working flawlessly (the USB 3 dock I use had a problem with some sort of linux driver regarding UASP, but I solved it black listing its load at boot - including the "usb-storage.quirks=aaaa:bbbb:u" at "/boot/cmdline.txt"). Besides, as I mentioned, I can access the data no problem; it's OMV5 that seems to not to.
What am I doing wrong? Is it not possible to reconnect a BTRFS formatted HDD on another installation?