[BUG] Automount fail on reboot with Ubuntu 20.04
It's working fine for me.
Here is what I have in fstab:
//uxxxxx.your-storagebox.de/backup /mnt/storage cifs iocharset=utf8,rw,credentials=/xxx/xxxxx-credentials.txt,uid=yellowtent,gid=yellowtent,file_mode=0660,dir_mode=0770 0 0
It did unmount once during a backup, but that's the only hiccup I've had to date.
If I am reading those version messages correctly, it does look like the automount on Ubuntu 20 has some kind of regression, while servers on 18 are working reliably?
In plain english yes the issue seams to be only with Ubuntu 20.04
Possible related to this?
SMB1 disabled by default: can still be enabled via a /etc/samba/smb.conf config change;
More info here:
@jdaviescoates I just look at it
and on Cloudron Samba server is not installed
so nothing to configure in /etc/samba/* which actually don't even exist.
I have the same behavior with webdav
on reboot I have to login and do
here the option for my davfs in /etc/fstab:
rw,_netdev,uid=yellowtent,gid=yellowtent,file_mode=0660,dir_mode=0770 0 0
I also tried with
few people suggest to use rc.local
it is possible than cloudron mount the volumes before my automount so then the target directory of my automount is not empty ?
nope, even without any volumes configured in Cloudron
CIFS and WEBDAV won't mount automatically
Cloudron itself does not handle any mount points as such. So this looks like this is some issue with 20.04 server then. Note that the desktop flavor has a lot more things installed usually, which may or may not trigger automounting correctly.
I have no doubt of the quality of coding from the Cloudron Team
but I just boot an ubuntu 20.04 LTS at Hetzner
apt update apt install -y davfs2 mkdir /mnt/storagebox
than cut and past my 2 lines
1 from /etc/fstab
1 for /etc/davfs2/secret
reboot and it work
so yes Ubuntu Desktop have probably more fuse than server but now the only difference is Cloudron.
thanks for testing, so then probably one of the dependencies we install, somehow changes either the init order or even disables some bits there. Looks like we have to debug this further then on fresh installations to get some more information what systemd does differently in both scenarios.
I'll run an fresh install of Cloudron than install davfs2 just to be sure
so boot up a new instance Ubuntu 20.04 LTS @Hetzner
wget https://cloudron.io/cloudron-setup chmod +x ./cloudron-setup ./cloudron-setup
reboot than install davfs2
apt install -y davfs2
it don't mount automatically
but mount without issue with