As a follow-up step I have gone ahead and activated diagnostics mode for your account and what this action does is automatically upload a set of logs to our servers for analysis.
I can confirm that this report has been received and I’m seeing some issues surrounding this folder: /mnt/sda1/flac/Agujetas/Cantaor/.
Can I please ask that you move this folder out of your GRIMM, reboot the Core and let me know if that helps with the issue? Page 13 of the MU1 Manual provides instructions on how to access the storage via a PC.
Note: Please do not delete this folder, but just move it out of the GRIMM Storage, because if we identify this folder to be problematic I would kindly request it for QA purposes.
Sorry to hear that the issue is still the same. I can confirm that new diagnostics have reached out servers and I have requested QA to take another look at them, I will be sure to let you know once I hear back, appreciate your patience!
I spoke to QA recently and they believe that this issue could be database-related. In situations like these, we typically have users set aside their current Roon database and request the old database for analysis.
Since you are using a non-standard Core, I can’t guarantee that these instructions will work exactly the same, but if this doesn’t work please reach out to Grimm for clarification on how to set the database aside.
Navigate to your Grimm’s Roon’s Database Location using a PC
Glad to hear that you have been able to make the database switch with the help of Justin!
I can confirm I received your dropbox link, I will forward this to QA for closer inspection.
I suggest to keep using the new database until QA’s investigation is complete, but if you wish to try one of your older database backups that might help (but it is possible that you may also want to keep running with the fresh one to avoid this potential issue re-occuring until the investigation is complete).
Please leave the file in your dropbox until this reaches QA’s queue. Thanks!