[SOLVED] Bad CMOS battery in NAS - (was "Is Proxmox overloading my Synology NFS ???")

LooneyTunes

Active Member
Jun 1, 2019
203
26
38
Hi,

I use a Synology NAS setup to back up my VMs. It has worked fine for years and is accessible from both Proxmox and other devices. Issue I have had lately is that the NFS service on the Synology crashes, so started googling and finally came up with someone talking about limiting the speed by editing the file /etc/vzdump and set the parameter 'bwlimit' to something sensible. This actually seems to work, but is it really the best way to approach this? Naturally I want all performance I can get from the gear, not having to throttle it manually... If I remove this setting I am soon back to a crashed NFS service.

I understand there probably are tons of things in play here, so any guidance would be much appreciated. I am on the latest PVE: "pve-manager/7.2-7/d0dd0e85 (running kernel: 5.15.39-1-pve)"

Thanks
 
use a Synology NAS setup to back up my VMs. It has worked fine for years and is accessible from both Proxmox and other devices. Issue I have had lately is that the NFS service on the Synology crashes
If any NFS server crashes due to _any_ client activity (regular or malicious), its the fault of NFS server not the client.
What did Synology support say regarding this?


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
  • Like
Reactions: LnxBil and MrPete
Update and possibly the solution:
After more testing and eventually a failing CMOS battery in the NAS in question, this issue seems to be resolved by changing the same battery. It now performs way better and does not fail while backing up. Maybe can help someone in the future, who knows :)