I am having some trouble using the Remotemount plugin to mount my smb shares. I hope somebody can help ...
After successfully completing the add dialog, I get the standard "Please wait... Applying configuration changes" but it never finishes. Seems to be looping somewhere.
While waiting for the GUI to complete, I took a look at fstab from a terminal and it now contains
proc /proc proc defaults 0 0
/dev/mmcblk0p1 /boot vfat defaults 0 2
/dev/mmcblk0p2 / ext4 defaults,noatime,nodiratime 0 1
# >>> [openmediavault]
UUID=fa36508a-b3c4-4499-b30a-711dd5994225 /media/fa36508a-b3c4-4499-b30a-711dd5994225 ext4 defaults,nofail,acl,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
/dev/disk/by-uuid/F474B7AA74B76DCC /media/F474B7AA74B76DCC ntfs defaults,nofail,noexec,noatime,big_writes 0 2
//192.168.1.73/Valgraph /media/571d7507-e025-4457-9dd9-6864fcb45d14 cifs guest,_netdev,iocharset=utf8 0 0
# <<< [openmediavault]
# a swapfile is not a swap partition, no line here
# use dphys-swapfile swap[on|off] for that
which looks about right to me - Remotemount has indeed added a line for the share Valgraph on 192.168.1.73
I don't know how to get out of the GUI loop other than closing the browser tab so I opened another GUI session and tried to delete the problematic remotemount but another loop. I closed the GUI tab again. In yet another tab I tried to delete the plugin but that also failed.
So finally I tried to reboot OMV only to find that it would not boot and so no access via ssh. Using a keyboard and a local display I was able to remove the aforementioned line in fstab that was created by RemoteMount and then OMV booted OK and with some messing about I was able to delete the plugin.
So a few questions:
- In the event that the GUI hangs up somewhere, what is the recommended means of escape?
- It seems as if RemoteMount is trying to mount the remote share when it is "applying configuration changes" but gets stuck if there is something wrong with the share. Surely there should be a timeout?
- RemoteMount creates a valid entry in fstab but does not by default add qualifiers like nofail or ,x-systemd.device-timeout. Therefore if there is a problem with the share, the next boot fails to complete. Is it the intention that users should add failsafe qualifiers themselves - or should they be default
- 4) In case the GUI fails in this way, what is the best procedure for removing a plugin from the CLI? How can I recover if I make a mess??
thanks for your help
n