Hi Chris,True, makes me wonder why it had an effect. @LSX3 can you verify that this was indeed solved by adding the mount option by e.g. creating a new datastore after mounting without the cache mount parameters? It could be that maybe just the remount after adding the mount parameter had an effect?
I did a cross-check and removed the cache=strict option — the error reappeared immediately.
I was also able to reproduce the behavior on a second PBS instance.
In both cases, PBS was installed as a VM via ISO on a PVE host, and the same Synology NAS was used.