I have a pi 4 running Bullseye. I mount an NFS (NAS) server in fstab, and for the most part I am able to access files on that server. However, every so often I can't access the files on that device for a short while. ( short in human time, but extremely long in computer time ).
fstab entry looks like...
Since I was connecting by WiFi, and also had Bluetooth active, I assumed that there was some negative interference there, so I plugged the pi4 directly into my router with an Ethernet cable, and did an rfkill on the wan. The problem still exists. A Windows PC plugged into the same router is able to access the NAS. It is using SMB, not NFS, so that's one difference. However, I think it proves that the NAS server is still alive on the network.
For example, I timed a simple "ls" command. Here's the result...
Seriously? The connection disappeared for 3min 20 sec?
Is there something wrong with my fstab parameters?
Any suggestions to diagnose this problem?
fstab entry looks like...
Code:
192.168.0.202:/volume1/music /media/music nfs rw,namlen=255,hard,proto=tcp,timeo=600,retrans=2For example, I timed a simple "ls" command. Here's the result...
Code:
pi@rPi4-Player:~ $ time ls -l /media/musictotal 20drwxrwxrwx 4 1024 users 4096 Nov 10 2018 Flacdrwxrwxrwx 71 1024 users 4096 Feb 5 2024 iTunesdrwxrwxrwx 173 1024 users 4096 Dec 20 2019 MP3sdrwxrwxrwx 3 1024 users 4096 Feb 25 15:05 Playlistsdrwxrwxrwx 114 1024 users 4096 Aug 7 2018 Vinylreal 3m20.306suser 0m0.005ssys 0m0.011sIs there something wrong with my fstab parameters?
Any suggestions to diagnose this problem?
Statistics: Posted by ronter — Tue Apr 08, 2025 9:00 pm