Printable Version of Topic

Click here to view this topic in its original format

Linuxhelp _ Technical Support _ Can't mount NAS at boot

Posted by: JaimeTheLimey Jan 2 2016, 03:19 PM

Hi all,
Linux newbie and first time poster. I have a couple other Pi projects going that have gone without a hitch but this one has me stumped.
I decided to set up my new Pi2 with a Plex server which is working great. However all my media is on a NAS drive (MyCloudEX2).
I can mount the drive manually but for some reason it won't mount at boot. Hoping you all can point me in the right direction.

My fstab is set up as:
<code>//192.168.1.51/User_Files /home/pi/myNAS/User_Files cifs username=user,password=pass,uid=1000,gid=1000,iocharset=utf8 0 0</code>

Manually mounting is no issue but on boot I'm returned this:
<code>[FAILED] Failed to mount /home/pi/myNAS/User_Files.
See' systemctl status home-pi-myNAS-User_Files.mount' for details.
[DEPEND] Dependency failed for Rmote File System,</code>

Systemctl produces this:
<code>pi@raspberrypi:~ $ sudo systemctl status home/pi/myNAS/User_Files.mount -l
● home-pi-myNAS-User_Files.mount - /home/pi/myNAS/User_Files
Loaded: loaded (/etc/fstab)
Active: failed (Result: exit-code) since Sat 2016-01-02 11:51:33 PST; 12min ago
Where: /home/pi/myNAS/User_Files
What: //192.168.1.51/User_Files
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
Process: 386 ExecMount=/bin/mount -n //192.168.1.51/User_Files /home/pi/myNAS/User_Files -t cifs -o username=user,password=pass,uid=1000,gid=1000,iocharset=utf8 (code=exited, status=32)

Jan 02 11:51:33 raspberrypi mount[386]: mount error(101): Network is unreachable
Jan 02 11:51:33 raspberrypi mount[386]: Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
Jan 02 11:51:33 raspberrypi systemd[1]: home-pi-myNAS-User_Files.mount mount process exited, code=exited status=32
Jan 02 11:51:33 raspberrypi systemd[1]: Failed to mount /home/pi/myNAS/User_Files.
Jan 02 11:51:33 raspberrypi systemd[1]: Unit home-pi-myNAS-User_Files.mount entered failed state.</code>

The only thing I can guess is that it's trying to reach the network before services are up??? Anyone experienced this or can point me in the right direction?

Cheers.

Posted by: michaelk Jan 3 2016, 10:01 AM

Try adding x-systemd.automount as an option. When you access the mountpoint the share should automount.

Powered by Invision Power Board (http://www.invisionboard.com)
© Invision Power Services (http://www.invisionpower.com)