For additional information: this mount succeeds with no problem if I do it manually via fstab / cifs with the same credentials. I also get a different error message “share not found” if I instead type an incorrect share. There is no information in the server logs for any failure
Thanks BlackJack, it does look related though I see different errors in the CIFS logs when attempting to mount through roon. Honestly if I could just schedule forced rescans every x timeframe for “local” folders I’d be happy as I could just do an os level mount through fstab.
I reverted my roonserver back to ubuntu lts 2024. Couldn’t get it stable on a clean debian install with associated kernel and since there was no reaction from roon for a couple of weeks I decided to go back to something that has proven to work.
On Ubuntu I did a fstab mount, scanning works, watching in realtime for added music also. Mounting another directory on my nas works for the database backups etc etc.
Yes, I’ve mounted the same synology share on ubuntu lts204 without issues. Also mounted a smb share from a openmediavault server via the roon interface without issues.
Before I switched to the latest debian I also ran roonserver on a ubuntu 2024 lts box.
In the end I decided to mount the synology via fstab, because you don’t have to wait or start a manual scan when you add new music files. The backup-share is still mounted via the roon-interface and the database backups are 100% succesfull.
As a extra info, also tried a minimal arch linux install, same issues with mounting smb shares via the roon interface.