Server Randomly Shutting Down

[lance_mayfield]

I do…my etc/fsab is:

lance@PLEX-Server:~$ more /etc/fstab

/etc/fstab: static file system information.

Use ‘blkid’ to print the universally unique identifier for a

device; this may be used with UUID= as a more robust way to name devices

that works even if disks are added and removed. See fstab(5).

/boot/efi was on /dev/sda1 during installation

UUID=873B-15FD /boot/efi vfat umask=0022,fmask=0022,dmask=0022 0 1
/boot/efi/grub /boot/grub none defaults,bind 0 0
UUID=f493dad4-151a-43e6-81d2-78fd25b80ec8 none swap sw 0 0
192.168.1.247:/volume1/data /mnt nfs

[lance_mayfield]

Is there a better way? My son was my Unix guru before he passed, not I just try to use what I remember

[lance_mayfield]

I changed my /etc.fstab , adding

defaults,sec=sys,rw,auto,async,rsize=4194304,wsize=4194304,x-systemd.after=network-online.target,nofail,bg 0 0

to my mount

so now it’s like yours

192.168.1.247:/volume1/data /mnt nfs defaults,sec=sys,rw,auto,async,rsize=4194304,wsize=4194304,x-systemd.after=network-online.target,nofail,bg 0 0

[lance_mayfield]

Back to Christmas movies…if this works, I owe you a bottle of Bourbon sir!

[ChuckPa]

Things to watch for .

1. sec=sys changed authentication to UID/GID mode.
   Normally it’s username=username mode.
   If Plex can’t access media, this is likely candidate,

2. If you want Read-Only for your media, switch rw → ro

[lance_mayfield]

Thank you, I made the change, restarted, and it’s running. So, now I watch what the wife picked out and wait to see. Thank you for your help, Merry Christmas!! I’ll let you know what comes of the changes

[ChuckPa]

Merry Christmas to you and all as well!

[lance_mayfield]

Well…THOUGHT I had it fixed, but it’s still occurring, so far I have:

Synology Side (NFS Server) Checks

-Enabled NFS: (obviously it is because it’s been working for years)
-Checked NFS Permissions:
-Ubuntu client IP is in there.
-Privileged Access to Read/Write
-Under Squash, I changed to “map all users to admin”
-Restarted NFS
-Checked firewall:
-Synology firewall disabled

Client Side:

-Ensured NFS-common is up to date
-Checked /etc/fstab line for typos: looks to be good:
192.168.1.247:/volume1/data /mnt nfs defaults,sec=sys,rw,auto,async,rsize=4194304,wsize=4194304,x-systemd.after=network-online.target,nofail,bg 0 0

So, then I looked at all the logs, client kept giving me the following:

nfs: server 192.168.1.247 not responding, still trying

I then looked at the server and saw many of the following errors, all beginning in July:

sudo cat /var/log/messages | grep 192.168.1.97
MAYFIELD kernel: [2697535.436064] NFSD: client 192.168.1.97 testing state ID with incorrect client ID

A quick google search revealed an outdated kernel…and I discovered my Synology NES was pretty far out of date.

I updated it to the most recent version of DSM and thought it fixed it but after watching movies for about 3 hours it happened again