I am reporting this issue for one of our 432 EVO customers, for which the dealer returned the boot SSD drive. The OS failed to correctly boot and we could not service the machine remotely.
The following directory was filling the / partition:
/root/.RoonServer/Cache
and more specific smc.db
[root@432OS Cache]# du -h -s --si smc.db
39G smc.db
The customer’s music collection is extremely small:
Thanks for reaching out. The SMC stands for streaming media cache, and it is used when buffering content from streaming services. It is very strange that it grew to 39GB in size. I looked for similar reports in our system, but I could not locate any such instances.
Does the user have the same database on a different machine? Is the smc.db directory size also very large on the other machine? How far ago did he notice the issue? If it was a recent issue, I wonder if the recent TIDAL outage due to AWS was causing some kind of retry loop filling that folder up.
This was first reported by the dealer on 08/10/2025. We received email screenshots of the machine booting, and showing a lot of services in red, meaning they would not start at boot. Usually this happens when the disk is full, and indeed, the disk was filled by smc.db
This was long before the Tidal issue caused by the AWS outage.
When we received the disk today, the user was also logged into a different system with the same account, so I had to deauthorize that machine first, to get back into the Roon on the SSD we received, and after moving away the Cache to a larger fs on the disk we received, everything seems to be working again, and Roon works correctly.
Something very similar happened years ago at a local Belgian dealer, where I remember that Roon was creating > 30GB worth of files. Also a customer who mainly has music added to Roon via Tidal/Qobuz.
We also had to move those away, and then everything worked again.
So far a this issue has happened 2 times in the whole history of 432 EVO + Roon, where a physical intervention was needed as we could no longer get into the system via VPN, because some files used by Roon were filling up the root filesystem.
Thanks for those details. Do you happen to still have the RoonServer/Logs folder from the affected user? If so, can you please upload it to the below link and let us know once uploaded?
Or if you could let me know the email address of the affected user (via private message, not in public - this can be done by clicking my name on the forum → message), after I can enable diagnostics to see if there are any clues in the logging. Thanks!