Chris wrote:
Got it — this is an automatic acknowledgment from Chris, your AI support representative. Your post is in the support queue, and we’ll get to it as soon as we can. Legend members receive priority replies. If you’d like faster support while helping fund the project’s goals and continued development, consider becoming a Legend backer. <!-- chris-support-queue-ack:v1 --
Chris wrote:
Sorry, the earlier AI answer was wrong. It said the dashboard was reading the same drive as your apps and called the 150 GB a SparkBox measurement problem. Your output shows otherwise: Sonarr sees the 7.3 TB drive (/dev/sdb2), but the dashboard is looking at the 218 GB system disk (/dev/sda2). Here is why. Each app attaches your media folder at the moment it starts. If the dashboard started before your Expansion drive was mounted, it keeps looking at the empty folder on the system disk underneath that mount point. When the drive shows up late, SparkBox restarts your media apps, but on your version it does not restart the dashboard. So the dashboard keeps the old view: its number is accurate, but for the wrong disk. Your files and settings are fine. One check: run sudo sparkbox restart dashboard, wait a minute, then run sudo docker exec sb-dashboard df -h /host/media again. It should now show the 7.3T drive, and Storage will read correctly. If it still shows 218G, paste that line here. An upcoming update makes the dashboard restart on its own when the drive mounts late. We have also corrected what the assistant knows, so the next person with a late-mounting drive gets the right answer.