I'm a little disappointed that no one from the team or the developers has commented on the problem yet.
Severe system freeze with NFS on Proxmox 9 running kernel 6.14.8-2-pve when mounting NFS shares
- Thread starter Krailler
- Start date
-
- Tags
- kernel 6.14 n100 pve 9.0.0~11
Usually, that means there's nothing concrete to say yet.
This is a real issue, but it's also been noticeably difficult to pin down the causes on it. Something's going on in 6.14 with NFS, but not for everyone, and it doesn't seem easily repeatable in a way that would make testing easier.
Not to mention NFS setups themselves tend to get heavily tweaked, so incoming reports all have different underlying configurations.
Hey all, just seen this thread as a reply to a post I made a few days ago and seems related (although im using CIFS / Synology) some of it does sound the same
under normal usage it presents itself as random disconnections. (sonarr processing stalls or playback of media just stops)
Id replicated my setup from a pi4 (docker with jellyfin/sonarr/nextcloud but using a nice silent minipc with better cpu/ram and I prefer proxmox's ability for backup/restore and have tested restoring the container to a different device & get exactly the same symtoms.
(I first noticed just watching shows/films, some days its fine, some days random freezes) at first i just restarted the nas/proxmox but as it carried on ive been looking more into it, & it just appears that any large network transfers (e.g proxmox network backup, sonarr handling files, tdarr health checks etc) cause the mounts to vanish,
seen some posts mentioning intel nic issues and turning tso/gso/gro off which i tried last night, made zero difference (i can reliably reproduce this issue within 20-30 secs just by manually running a jellyfin media segment scan/keyframe extract task) so is easy to test things to see if anything fixes it, thus far nothing has changed and is broken.
NAS settings smb2/smb3/oplocks on/off etc
Network - tried jumbo frames / different ports / different cables (but i dont suspect network as the pi4 setup works flawless)
Firewall - unsered IDS/DOS protection bypassed
Proxmox network - tried tso/gso/gro off, tried a different USB3 nic - no change
would be nice to get this running reliably, the pi4 setup works flawlessly (but obviously less ram/cpu/slower processing) so proxmox on an i7/16gb/nvme should theoretically wipe the floor with it (and it does, for a short while!) its just so unreliable and unstable with this mounts issue.
for now for my sanity & reliability / usability i'll stick with the Pi4b setup, but if anyone has any solid fix for this, would love to hear what fixed it!
thanks
under normal usage it presents itself as random disconnections. (sonarr processing stalls or playback of media just stops)
Id replicated my setup from a pi4 (docker with jellyfin/sonarr/nextcloud but using a nice silent minipc with better cpu/ram and I prefer proxmox's ability for backup/restore and have tested restoring the container to a different device & get exactly the same symtoms.
(I first noticed just watching shows/films, some days its fine, some days random freezes) at first i just restarted the nas/proxmox but as it carried on ive been looking more into it, & it just appears that any large network transfers (e.g proxmox network backup, sonarr handling files, tdarr health checks etc) cause the mounts to vanish,
seen some posts mentioning intel nic issues and turning tso/gso/gro off which i tried last night, made zero difference (i can reliably reproduce this issue within 20-30 secs just by manually running a jellyfin media segment scan/keyframe extract task) so is easy to test things to see if anything fixes it, thus far nothing has changed and is broken.
NAS settings smb2/smb3/oplocks on/off etc
Network - tried jumbo frames / different ports / different cables (but i dont suspect network as the pi4 setup works flawless)
Firewall - unsered IDS/DOS protection bypassed
Proxmox network - tried tso/gso/gro off, tried a different USB3 nic - no change
would be nice to get this running reliably, the pi4 setup works flawlessly (but obviously less ram/cpu/slower processing) so proxmox on an i7/16gb/nvme should theoretically wipe the floor with it (and it does, for a short while!) its just so unreliable and unstable with this mounts issue.
for now for my sanity & reliability / usability i'll stick with the Pi4b setup, but if anyone has any solid fix for this, would love to hear what fixed it!
thanks