Compare config files and use sudo to mount directly.
Compare config files and use sudo to mount directly.
Hello, I just set up a virtual Ubuntu server (17.04) on top of Freenas 11 to run my personal website. All my HTML files are stored on my Freenas, and I planned to access them in the same manner as on my laptop—also running Ubuntu 17.04 but as a desktop version. My /etc/fstab file contains a line identical to what I used on my laptop: it points to //192.168.0.5/Path/To/Files /home/username/WebDocs with cifs credentials. The UFW is installed with the default deny policy, but I allowed access from the Samba app to 192.168.0.5 and vice versa. The main point is that my WebDocs folder won’t mount at boot, yet it appears to mount instantly once I log in using 'sudo mount -a'. This seems odd—why would mounting work immediately but not at startup? A note: my Retropie has the same problem with mounted ROMs, but it doesn’t have UFW enabled.
the network is linking once the disks are attached. A method exists to postpone this or trigger it automatically when the network becomes active.
This setup aligns well with expectations. Your configuration in /etc/fstab appears correct, using the proper path and mount options. The '_netdev' component resolved an issue, while the 'uid' setting ensured proper access control. Adding 'x-systemd.automount' improved boot performance significantly.