![]() See man systemd.mount for systemd-specific mount options you can use in /etc/fstab. Samba's nmbd isn't running yet) when the mount attempt happens, as suggested in the appropriate Debian Wiki page. The most likely reason is that NetBIOS name resolution isn't available (i.e. You'll need to check the status of the appropriate mount unit to see why it failed: please run systemctl status Share.mount. Systemd will use the contents of the traditional /etc/fstab file to dynamically create "mount units". ![]() I had to add sudo mount -a to crontab to get them to show up, but is there a more "proper" way for Debian 10 to recognize fstab the way other Debians do? ![]() That dialect message doesn't come up at every restart, though. To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. I looked at dmesg, and these are the only mentions of mounts or cifs: FS-Cache: Netfs 'cifs' registered for caching The fstab entry looks like this: //hostname/Share /Share cifs _netdev,dir_mode=0777,file_mode=0777,username=,password=,rw,uid=1000,gid=1000 0 0Īfter restart, the mount folder is empty and is not listed in the mounts. On all the Linuxes that I've tried before, whenever one puts something in /etc/fstab it gets automatically mounted when the machine is restarted, however after installing Debian 10, the same mechanism doesn't seem to work on it.
0 Comments
Leave a Reply. |