[Solved] Disks set to noauto in fstab still mounted at boot.

[mts]

Using AV Linux with debian stretch.

I have spent days trying to troubleshoot this problem.
I used Gnome Disk Utility to set most of my drives to noauto at boot.
I can clearly see in fstab that they are set to noauto but still they are mounted.
For the life of me I can't work out why.
Reading the man for fstab it says drives marked noauto will not be mounted at boot.
This however is just not the case. I have to use Disks to unmount them all after booting up.

Any clues as to why this is happening would be greatly appreciated.
Thanks in advance.

[GarryRicketson]

The problem is, even though it is based on Debian, like many of the other distros , it is not Debian.
So what works for Debian, might not work for that distro. Did you try asking them at their support forum ? http://bandshed.net/forum/

Also did you try this ?
Disks set to no auto in fstab still mounted at boot on Debian 9
Several hits that probably answer this,
One ,

https://unix.stackexchange.com/question ... nt-on-boot

The 'noauto' option is interpreted by mount to not mount the entry implicitly. This has the consequence that it will not be mounted on boot on SysVInit systems.

Systemd does not interpret "automatic" to mean it can not mount it on-demand. Systemd only interprets 'noauto' to mean that it should not be a dependency of local-fs.target but if its a dependency of something else it will mount it. This is includes fsck, automount and mountpoints below the mountpoint.

You probably either have a mountpoint that is not noauto beneath the noauto mountpoint or the x-systemd.automount option is in the fstab entry.

And that leads to this, seems like it would be obvious, but guess it isn't. Some better details would make it easier for anyone to helpyou, for example showing us what your fstab file actually has in it, (please use code boxes), and also What kind of devices or partitions it is that you do not want to mount automatically ?

[4D696B65]

post your fstab, lets have a look

[sunrat]

Yes you should be asking in AVLinux forums. AVL has a custom drive automount function set in /etc/rc.local, you may be able to change it there.

[mts]

@sunrat

You hit the nail on the head. I knew it must be some system function overriding fstab.
The entries in fstab are ok because I used gnome disk utility to set noauto.
This is the culprit. /usr/bin/mountomatic &
Removed execute bit and all is as it should be.
#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.

# Remove comment to enable automatic mounting of all partitions
/usr/bin/mountomatic &

exit 0
Thanks for the heads up!

[sunrat]

Thanks for the heads up!

You're welcome.
Luckily you caught one of the very few people here who use AVLinux, and I'm one of the small percentage of AVL users who know about the automount script.
AVLinux is the best-of-breed distro for multimedia production IMO. I use it regularly.

[mts]

@sunrat

When I signed up for the AV Linux forum I saw you had posts there so I was indeed lucky.
A search for /usr/bin/mountomatic gives no hits at all.
Again I really appreciate your help.
I am loving AV Linux. My Ardour install on Solus 4 is very slim pickings and the directories seem to be a mess.
I find I am booting AV Linux for every day Linux use. Sorry Solus
One thing I wonder about is how safe is it to keep AV Linux updated via Synaptic.
I have already updated everything since the ISO install and hope it doesn't cause problems.

[sunrat]

One thing I wonder about is how safe is it to keep AV Linux updated via Synaptic.

I update regularly and haven't broken it yet.

[mts]

Cheers

Thanks again.