I just realized that apparently my whole remote network storage is not available anymore in roon. I used have to several network shares but roon always tells me "This drive is not available..." in "Storage". However, it actually is when manually accessed through smb directly (Ubuntu). If I try to add the same network location again in roon and click "apply" then it seems to work but I simply get the Info "Error loading folder NotAvailable". Seems to me that logging in actually works but there's another issue. Unfortunately, I cannot exactly say since when this happend but I remember updating roon some days ago (-> very recent). Other info: -IP adresses etc have not changed -Version roon: 2.73 (build 1694) (Android App and Server) -NAS: TrueNAS smb for network storage (restarted multiple times) -Roon server restarted multiple times -Roon app restarted multiple times -Briefly activated SMB1 -> still didnt work -> deactivated again -In "Storage", network locations / folders have been disabled and enabled again multiple times.
I hope that helps in identifying the issue!
Tell us about your home network
· Roon runs in an Intel NUC -> Switch -> Switch -> Router (Fritzbox 7690). No VLAN so far or anything.
Thanks for the details on the network shares and the recent update. Could you let us know the name of the share that is causing the issue?
We’ll activate diagnostics so we can look for more clues in the logs. If you want to check them yourself in the meantime, you can also review our Logs knowledge base article for instructions on how to access them.
There are currently eight shares in total and every share is affected (e.g. Audio/Music/Fantasy).
I just followed the Log instructions you pointed out and followed the instructions: created an archive out of it (.tar.zst) and uploaded it through this Roon Log Uploader. I hope this was the correct process..? Or do you meant that you will jump on my server from remote?
Thank you for uploading the logs. We went through them, and here is what we see.
Your Roon Server runs in a container on Proxmox. Since the restart on September 24 at 8:03 PM (your time), when Roon updated to 2.73, all eight folders on \192.168.178.109\Media are marked as unavailable. They never come online in the logs. We also see Roon trying to reach a second location, \192.168.178.65\Media, with the same result. The logs do not show the result of the connection attempt itself, so we cannot yet tell the reason.
We also see that on September 26 the Proxmox host kernel changed from 6.8.12 to 7.0.14 (around 12:30 PM your time), after the shares were already unavailable.
To narrow this down, please tell us:
Is the Roon container privileged or unprivileged, and is SMB/CIFS enabled under the container’s Features in Proxmox?
Were any updates applied on Proxmox or inside the container around September 24 to 26? And is 192.168.178.65 another NAS or an older address of the same one?
From inside the Roon container, please try mounting the share by hand, for example with mount -t cifs //192.168.178.109/Media /mnt -o username=YOURUSER, and send us the exact output or error.
When you re-add a share in Roon, please enter the path with the share name, for example \192.168.178.109\Media. One attempt on September 26 at 11:52 AM was rejected because the path ended after the IP address.
thanks for your reply and sorry for my late response!
I am happy to confirm that it is working again! The issue was indeed deactivated SMB on container level.. wherever that came from ..must have been one of the updates I applied before. And restarting after changing the settings (SMB feature) also helps a lot
..must have been one of the updates I applied before. And restarting after changing the settings (SMB feature) also helps a lot 
