I have manually edited my fstab file in a few different ways. Most of these changes are persistent, but it seems that one of my changes is automatically reverted (upon reboot, I assume). I have one non-system SSD and have chosen to remove the noexec argument, but I find that this option reasserts itself. Am I experiencing a bug, or is this working as intended? Either way, how do I prevent it?
noexec argument returns automatically
-
- gelöst
- OMV 4.x
- flvinny521
-
-
You can't manually edit /etc/fstab within the [openmediavault] stanzas and have the changes stick if what you are setting is a non-default value.
What you want to do is edit the /etc/default/openmediavault file and make the change in the appropriate OMV_FSTAB_MNTOPS environment variable, and then run:
omv-mkconf fstab
This will push the change into fstab and it will stick.
-
Changing the environment variable helps with new filesystems but you will need to change the mntent section of config.xml and then do omv-mkconf fstab to change existing filesystems.
-
To avoid messing with database (wrong closing tags or chars) use omv-confdbadm
https://openmediavault.readthe…ml#omv-confdbadm-database
If you changed several lines in between the tags of fstab, then all of those lines will get rewritten (not just one line) but not on reboot, only certain events using the webui: adding, removing fs and adding or removing NFS shares.
In your case only one line gets reverted so i don't know what's going on, maybe you left a script there at boot for writing those changes -
Thanks for the tips, gentlemen. @subzero79 - I actually don't have any scripts at the moment, this is a pretty fresh install of 4.x. The other changes I made were the ones for the flash memory plugin which have persisted. I wasn't even paying attention to what lines were within the tags. Thanks for your responses.
-
Just chiming in to mark this as resolved. Making changes to the config.xml file and running omv-mkconf fstab was the answer (which, of course, you already knew).
-
I have to do this even in the root directory where OMV4 is installed?
-
If your rootfs was mounted noexec OMV couldn't run at all. You have other problems.
-
I have to do this even in the root directory where OMV4 is installed?
Nope, only non-system drives. I am using a second SSD which I use for some tasks, and this was the drive from which I needed to remove the "noexec" argument. -
Changing the environment variable helps with new filesystems but you will need to change the mntent section of config.xml and then do omv-mkconf fstab to change existing filesystems.
Cool so far this finally fixed my plex "Conversion failed. The transcoder exited due to an error"
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!