Just had an interesting experience, while configuring MergerFS and then testing it on reboot, I found my system to no longer mount root read-write. Swap wouldn't mount either and that was my first warning sign as the kernel finished up initializing.
I noticed that /etc/fstab.bak existed from MergerFS backing it up prior to modifying it, so I copied the current fstab to fstab.mergerfs and then cp'd fstab.bak back. I rebooted and the system worked fine. I then copied fstab.mergfs back to fstab and ran mount -av which insanely reported that the filesystem in question mounted successfully (mount -fav also actually executes MergerFS mount, so it doesn't fake it like it's supposed to). A reboot yielded failure again and still requires a mount -o remount,rw / to be able to modify anything on the filesystem.
The line that MergerFS added to my /etc/fstab is:
/mnt/bay_1:/mnt/bay_2:/mnt/bay_3:/mnt/bay_4:/mnt/bay_5:/mnt/bay_6 /srv/1fd5adb1-3581-4d14-9856-5c288aa699ff fuse.mergerfs defaults,allow_other,cache.files=off,use_ino,category.create=mfs,minfreespace=275G,fsname=tank:1fd5adb1-3581-4d14-9856-5c288aa699ff,x-systemd.requires=/mnt/bay_1,x-systemd.requires=/mnt/bay_2,x-systemd.requires=/mnt/bay_3,x-systemd.requires=/mnt/bay_4,x-systemd.requires=/mnt/bay_5,x-systemd.requires=/mnt/bay_6 0 0
I'm going to break this down into segments where each space has a new line for readability:
The GUI seems to show nothing remarkable:
Any thoughts on what the problem is?
I'm still digging through this, but I thought I should at least document this so far and in case I don't find anything someone else may have some experience with this situation.