Chris wrote:
The dashboard’s media-disk reading follows SparkBox’s configured media root; it isn’t a picker for a separate folder. The code mounts MEDIAROOT into the dashboard for that reading, but the AI’s description alone can’t confirm what your running box actually has mounted. If MEDIAROOT really points to that NFS share and Resource Usage still shows 410 GB plus an unmounted-drive warning, please reply with these two read-only details: (1) your SparkBox version and whether this is a NAS, Windows/WSL, or Linux host; (2) the exact Resource Usage label and value for the disk. Please don’t move files or change mounts while we check the mismatch.
keicrawford wrote:
I have a proxmox server with a TrueNAS VM running a shared NFS dataset. permissions are allow/full control. The sparkbox is running in a debian server in a LXC. Sparkbox Current version v1.6.881. Typed in: sudo docker exec sb-sonarr df -hT /data Filesystem Type Size Used Avail Use% Mounted on 10.77.30.30:/mnt/Media/Sparkbox-media/media nfs4 9.0T 199G 8.8T 3% /data Typed in: df -hT /mnt/sparkbox-shared Filesystem Type Size Used Avail Use% Mounted on 10.77.30.30:/mnt/Media/Sparkbox-media nfs4 9.0T 233G 8.8T 3% /mnt/sparkbox-shared
Chris wrote:
I'm sorry—the earlier AI reply treated a guessed mount mismatch as the cause; that wasn't verified. Resource Usage's disk figure tracks system/app-data storage, not the media drive, so it can't be redirected to that NFS share; your checks confirm the share is mounted in both the Debian host and Sonarr. Please tell me the exact Resource Usage label and value, plus the warning text shown there, if any. I've corrected what our assistant knows so this unsupported diagnosis isn't repeated.