[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
On 21/07/18 21:20, Julian Hall wrote:
Just to clarify.. there is a typo in the rm -rf line but I did execute it properly.On 21/07/18 20:38, mr meowski wrote:On 21/07/18 20:09, Julian Hall wrote:Still refusing point blank to mount at boot.. I did as above; commented out fstab, deleted the old .mount file, created the new one, then did steps 6-8. Then DEMETER loaded. Rebooted and it failed to load so I tried again and got: julian@Cerce ~ $ sudo systemctl daemon-reload [sudo] password for julian: julian@Cerce ~ $ sudo systemctl status media-julian-DEMETER.mount ● media-julian-DEMETER.mount - NFS lazy test Loaded: loaded (/etc/systemd/system/media-julian-DEMETER.mount; disabled; ven Active: inactive (dead) Where: /media/julian/DEMETER What: 192.168.1.3:/volume1/DEMETER Warning: "sudo systemctl start media-julian-DEMETER.mount" exists; Overwrite, Append or Don't log? Overwrite, Append, or Don't log? (Type "O", "A", "D" or "q" It will only mount after I start it manually with systemctl. BTW I only use media as the mount point as that seems to be the default in Mint (yes I am still using 18.3). Prior to mint I used mnt.Ok, nearly there... First, check to make sure that there isn't existing data in the folder you're trying to use to mount at /media/julia/DEMETER - systemd doesn't like the existing mount point. After checking it's empty, delete it: sudo rm -rf /media/julia/DEMETER systemctl will recreate it if necessary. Check to see if the unit file is enabled, I might have missed a step: systemctl is-enabled media-julian-DEMETER.mount If it's not enabled, enable it: sudo systemctl enable media-julian-DEMETER.mount Reboot. However this looks a bit suspect to me: "Warning: "sudo systemctl start media-julian-DEMETER.mount" exists;" That's a weird error message. I'd expect syntax more like "warning, mount point exists" as the return status from the command "sudo systemctl start media-julian-DEMETER.mount" whereas here they're mashed together.Clear the mount point and enable the unit first and then we can check again.Cheersjulian@Cerce ~ $ sudo rm -rf /media/julia/DEMETER [sudo] password for julian: julian@Cerce ~ $ systemctl is-enabled media-julian-DEMETER.mount disabled julian@Cerce ~ $ sudo systemctl enable media-julian-DEMETER.mountCreated symlink from /etc/systemd/system/multi-user.target.wants/media-julian-DEMETER.mount to /etc/systemd/system/media-julian-DEMETER.mount.julian@Cerce ~ $Then I did 'sudo systemctl start media-julian-DEMETER.mount' which loaded the share, and rebooted to see if it persists.Still not persisting. It stays /enabled/ through a reboot - I assume the symlink did that - but will only /load/ if I manually start the mount with systemctl.Julian
Julian -- The Mailing List for the Devon & Cornwall LUG https://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/listfaq