I operate mostly in the GUI of OMV, but understand some concepts of linux, so an answer doesn't have to be hand-holding (but don't intentionally obfuscate, ya sadist!). I have a basic question with an elaborate backstory.
The basic question: When editing the parameters/arguments of a unionfs (mergerfs?), where is that information stored? How do I go about editing that from CLI? You can stop here, you don't have to read the below.....
Elaboration: I went and pseudo-blindly followed some internet advise that suggested adding
to the unionfs options (irrelevant details why below). To the unionfs plugin's one merged filesystem, I added 3 of these so that (as I assumed) my three disks in the merged fs would have their mount points available before continuing with the rest of the boot process. My system disk is NOT included in this. I added exactly:
Aaaand after a reboot, OMV webgui will not launch. From the CLI, if I try to log into the omv admin user, I get:
No directory, logging in with HOME=/
This account is currently not available
Checking the log, it looks like it sees the drives:
OMV systemd: Mounting /srv/dev-disk-by-label-Z...
-- The start-up result is done.
(for each of the drives)
sidenote, relevant line:
OMV Kernel: EXT4-fs (sdb): mounted filesystem with ordered data mode. Opts: user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,ac1
The first failure I see here is for each non-system disk, it's looking for aquota.group and aquota.user and failing. Dunno what this is, but i assume its not necessary. Including just in case.
As it starts to bring up interfaces and whatnot, I get a few more failures: "Cleanup monit state file", "Enable File System Quotas", "Update UTMP about System Boot/Shutdown", but thing is, I don't know what's expected here. I've never bothered to look at the logs when it worked!
How do I undo what I did? I just want to get back to those parameters and remove that bit that I added. I don't care about the why, I just wanna boot back up and return to my original migraine of an issue.
Below are just general, disorganized notes and errors.
anacron service fails
liblogging-stdlog "read-only file system"
fan.controlservice "failed to start fan speed regulator" god this pisses me off so much
First, i think unique, failure is samba:
OMV sh: /sbin/dhclient-script: 46: /etc/hdcp/dhclient-enter-hooks.d/samba: cannot create /etc/samba/dhcp.conf.new: Read-only file system
OMV systemd: failed to start Samba SMB Daemon
...and a whole bunch of other complaints: "Failed to start Generate the prelogin message" "Failed to start Samba NMB Daemon." "rrdcached plugin: Failed to connect to RRDCacheD at unix:/var/run/rrdcached.sock: Unable to connect to rrdcached: No such file or directory (status=2) with a giant failure later:
OMV systemd: Failed to start Docker Application Container Engine.
Failed to start A high performance web server and a reverse proxy server.
pretty much everything points to "Read-only file system"
The "why" was because I was having issues with permissions on the mount points in my dockers. I pointed one container to the /srv/[mergerfsid] path and it worked great. I pointed another to the same, and it couldn't create a folder. I had already tried a lot of other standard troubleshooting steps. This was a trial-and-error attempt. I had assumed "well since my system drive isn't a part of these, it won't prevent the system from booting if this argument is wrong!" Wow. Wow. just.... wow.