I’m trying to mount my Synology NAS on a Raspberry Pi 4 with Raspian. I works when I do it the following command:
sudo mount -t nfs 192.168.178.**:/volume1/my_data / /home/pi/mount/NAS
but it doesn’t work with this entry in /etc/fstab:
192.186.178.**:/volume1/my_data /home/pi/mount/NAS nfs defaults 0 0
What am I doing wrong?
Edit: pro tip: make sure you get the IP addresses right so you won’t spend days chasing after a trivial error like some idiot. Don’t ask me how I know. Thanks to @Arlos for pointing that out.
I assume you’ve just twisted two numbers in the second octet.
186but in the example above it’s168Fix it and it should work.
Holy crap. You’re right. For the record: I’m an idiot.
What do you mean “doesn’t work”? Is there some error message in the log (dmesg, /var/log/messages, on the console, whatever raspbian uses)?
after modifying /etc/fstab you’d have to manually run
sudo mount -afor the settings to take effect.What error message do you have (if any) when you try to mount your folder (
sudo mount /home/pi/mount/NAS)I just get this:
mount.nfs: Connection timed outWeird. Have you tried removing
0 0at the end of your fstab entry? This option is not supported on recent NFS versions
Filesharing drove me insane.
I ended up ripping the HDDs and putting them on my server, then proceeded to share the drives as normal. My docker containers now use them perfectly fine. IDK wtf Synology is doing but it’s cumbersome AF.
As a wild guess, try completely specifying the IP address in your fstab instead of relying on a wildcard. Wouldn’t be the first time there was a slight difference in how a marginal feature like that worked in different contexts.
The IP address in the actual file is complete. I just didn’t want to put it here. I guess I should have put another number.
This is what my fstab entry looks like.
synas.com:/volume1/Music /mnt/music nfs nofail,noauto,x-systemd.automount
If that works, but you want to figure out the root cause, let me know and we can get it figured out.
