[Solved] sshfs can't mount via fstab on startup

Varemenos · 2014-06-26 18:11:33

Well, this is weird then...

It's always this:

read: Connection reset by peer

catalin · 2014-06-26 18:12:38

could you tell me your kernel , systemd versions

Varemenos · 2014-06-26 18:37:35

$ uname -a
=> Linux home 3.15.1-1-ARCH #1 SMP PREEMPT Tue Jun 17 09:32:20 CEST 2014 x86_64 GNU/Linux

$ pacman -Q systemd
=> systemd 214-2

catalin · 2014-06-26 18:42:01

let's try one more time using fstab , use this line in fstab

pi@192.168.2.86:/media/mydrive  /home/username/media/downloads/mydrive fuse.sshfs users,_netdev,noauto,x-systemd.automount,reconnect,allow_other,workaround=rename,umask=117,uid=1000,gid=1000 0 0

noauto # does not immidiately mount
x-systemd.automount # manually connects on demand if using systemd (not upstart)
_netdev # don’t try if no network
reconnect # reconnect to server
users # not documented anywhere, but needed to allow users other than root to activate

print me the errors if is not mounted at boot

don't forget to disable systemd service

Last edited by catalin (2014-06-26 18:43:29)

catalin · 2014-06-26 18:53:20

if still not working please try this

assuming that your key file is stored under /root/.ssh/id_rsa

pi@192.168.2.86:/media/mydrive  /home/username/media/downloads/mydrive fuse.sshfs    x-systemd.automount,_netdev,user,idmap=user,transform_symlinks,identityfile=/root/.ssh/id_rsa,allow_other,default_permissions,uid=1000,gid=1000,umask=0   0 0

Varemenos · 2014-06-26 19:15:06

Still happening...

Log parts from journal:

NetworkManager[250]: <info> NetworkManager (version 0.9.8.10) is starting...
NetworkManager[250]: <info> Read config file /etc/NetworkManager/NetworkManager.conf
NetworkManager[250]: <info> WEXT support is enabled
systemd[1]: Started Authorization Manager.
accounts-daemon[265]: started daemon version 0.6.37
NetworkManager[250]: Error parsing file '/etc/NetworkManager/NetworkManager.conf': No such file or directory
NetworkManager[250]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
NetworkManager[250]: Error parsing file '/etc/NetworkManager/NetworkManager.conf': No such file or directory
NetworkManager[250]: keyfile: Cannot read directory '/etc/NetworkManager/system-connections': (4) Error opening directory '/etc/NetworkManager/system-connections': No such file or directo
NetworkManager[250]: Error parsing file '/etc/NetworkManager/NetworkManager.conf': No such file or directory
systemd[1]: Started Accounts Service.
NetworkManager[250]: <info> monitoring kernel firmware directory '/lib/firmware'.
NetworkManager[250]: <info> WiFi enabled by radio killswitch; enabled by state file
NetworkManager[250]: <info> WWAN enabled by radio killswitch; enabled by state file
NetworkManager[250]: <info> WiMAX enabled by radio killswitch; enabled by state file
NetworkManager[250]: <info> Networking is enabled by state file
NetworkManager[250]: <warn> failed to allocate link cache: (-26) Protocol mismatch
NetworkManager[250]: <info> (enp0s25): carrier is OFF
systemd[1]: Started Network Manager.
systemd[1]: Starting Network is Online.
systemd[1]: Reached target Network is Online.
systemd[1]: Mounting mydrive...
mount[280]: read: Connection reset by peer
systemd[1]: Starting Multi-User System.
systemd[1]: Reached target Multi-User System.
systemd[1]: Starting Graphical Interface.
systemd[1]: home-username-media-downloads-mydrive.mount mount process exited, code=exited status=1
systemd[1]: Failed to mount mydrive.
systemd[1]: Startup finished in 1.251s (kernel) + 1.179s (userspace) = 5.571s.
systemd[1]: Unit home-username-media-downloads-mydrive.mount entered failed state.
NetworkManager[250]: <info> (enp0s25): preparing device.
NetworkManager[250]: <info> (enp0s25): deactivating device (reason 'managed') [2]
NetworkManager[250]: <info> Added default wired connection 'Wired connection 1' for /sys/devices/pci0000:00/0000:00:19.0/net/enp0s25
NetworkManager[250]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
NetworkManager[250]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
NetworkManager[250]: <info> (enp0s25): carrier now ON (device state 20)
NetworkManager[250]: <info> (enp0s25): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
NetworkManager[250]: <info> Auto-activating connection 'Wired connection 1'.
NetworkManager[250]: <info> Activation (enp0s25) starting connection 'Wired connection 1'
NetworkManager[250]: <info> (enp0s25): device state change: disconnected -> prepare (reason 'none') [30 40 0]
NetworkManager[250]: <info> NetworkManager state is now CONNECTING
NetworkManager[250]: <info> Activation (enp0s25) Stage 1 of 5 (Device Prepare) scheduled...
NetworkManager[250]: <info> Activation (enp0s25) Stage 1 of 5 (Device Prepare) started...
NetworkManager[250]: <info> Activation (enp0s25) Stage 2 of 5 (Device Configure) scheduled...
NetworkManager[250]: <info> Activation (enp0s25) Stage 1 of 5 (Device Prepare) complete.
NetworkManager[250]: <info> Activation (enp0s25) Stage 2 of 5 (Device Configure) starting...
NetworkManager[250]: <info> (enp0s25): device state change: prepare -> config (reason 'none') [40 50 0]
NetworkManager[250]: <info> Activation (enp0s25) Stage 2 of 5 (Device Configure) successful.
NetworkManager[250]: <info> Activation (enp0s25) Stage 3 of 5 (IP Configure Start) scheduled.
NetworkManager[250]: <info> Activation (enp0s25) Stage 2 of 5 (Device Configure) complete.
NetworkManager[250]: <info> Activation (enp0s25) Stage 3 of 5 (IP Configure Start) started...
NetworkManager[250]: <info> (enp0s25): device state change: config -> ip-config (reason 'none') [50 70 0]
NetworkManager[250]: <info> Activation (enp0s25) Beginning DHCPv4 transaction (timeout in 45 seconds)
NetworkManager[250]: <info> dhcpcd started with pid 387
NetworkManager[250]: <info> Activation (enp0s25) Beginning IP6 addrconf.
NetworkManager[250]: <info> Activation (enp0s25) Stage 3 of 5 (IP Configure Start) complete.
dhcpcd[387]: version 6.4.0 starting
NetworkManager[250]: <info> (enp0s25): DHCPv4 state changed nbi -> preinit
dhcpcd[387]: DUID 00:01:00:01:1b:34:ee:74:d0:50:99:26:a7:76
dhcpcd[387]: enp0s25: IAID 99:26:a7:76
dhcpcd[387]: enp0s25: rebinding lease of 192.168.1.64
dhcpcd[387]: enp0s25: soliciting an IPv6 router

The weird things, this used to work just fine (mounting via fstab on boot, I mean) before I tried to install Gnome's NetworkManager

Last edited by Varemenos (2014-06-26 19:22:59)

catalin · 2014-06-26 19:22:52

from your log file the home-username-media-downloads-mydrive.mount is executed before enp0s25 is up

please

systemctl enable NetworkManager-wait-online.service

edit home-username-media-downloads-mydrive.mount

replace After=netctl@eth0.service
After=network-online.target

Varemenos · 2014-06-27 23:43:28

Hi, sorry I didn't get the chance to reply sooner, I've had a lot of work to do.
It seems like fstab started working again after

systemctl enable NetworkManager-wait-online.service

So I just went back to using that again.

catalin · 2014-06-28 11:10:28

yep , all problems were generated by NM - https://wiki.archlinux.org/index.php/Ne … ait_Online , now both methods should work : service / fstab .

Arch Linux

#26 2014-06-26 18:11:33

Re: [Solved] sshfs can't mount via fstab on startup

#27 2014-06-26 18:12:38

Re: [Solved] sshfs can't mount via fstab on startup

#28 2014-06-26 18:37:35

Re: [Solved] sshfs can't mount via fstab on startup

#29 2014-06-26 18:42:01

Re: [Solved] sshfs can't mount via fstab on startup

#30 2014-06-26 18:53:20

Re: [Solved] sshfs can't mount via fstab on startup

#31 2014-06-26 19:15:06

Re: [Solved] sshfs can't mount via fstab on startup

#32 2014-06-26 19:22:52

Re: [Solved] sshfs can't mount via fstab on startup

#33 2014-06-27 23:43:28

Re: [Solved] sshfs can't mount via fstab on startup

#34 2014-06-28 11:10:28

Re: [Solved] sshfs can't mount via fstab on startup

Board footer