Thanks for giving that a try. To be clear, you first disabled the backup path before removing the drives, correct?
With that, I would also test out disabling your watched folder on your two other external drives as well to test if the same issue occurs. You could take it a step further and clean up you library after disabling the watched folders, but then you’d have to re-add you library back onto your core, which can be tedious (as you know firsthand )
An additional log set would be good to review! Please use the directions found here and send over a set of logs to our File Uploader.
Hello @benjamin
I tried to disable my watched (internal storage) folder containing my music before restart, and this time actually it did NOT go in to endless restarts. But after that when I enable my watched folder, the remote lost connection to the server which started the endless restart again
How do I disable the backup path? I have not set up a scheduled backup at the moment as I can not make use of any backup as things are now.
I just tried disabling the watched folder, then doing a clean, enable the folder again (doing a rescan) and then restart. Same thing happens, looping restart, but now it restarts every 16 seconds, not every 21 seconds.
I have uploaded two set of log files: one before the clean up sequence (restart every 21 seconds) and one after (restart every 16 seconds).
Thank you very much for looking in to this. It is much appreciated! I look forward hearing what you find.
This points to the issue potentially being related to the internal storage drive on the NUC. As a next step, please reinstall the OS via the webUI of your NUC.
If that doesn’t help, we’ll want to consider reinstalling ROCK from an external drive.
Do you by chance have another internal drive you could test? You’d need to format it via webUI, but that’s an easy click.
Thanks @Benjamin - I did a reinstall from the webUI, but unfortunately it goes directly into the restart loop every 21 seconds.
Unfortunately I have no spare internal drives (but I could buy one). Can you please explain to me:
Do you suspect my internal system drive or my watched folder drive to be faulty?
Does Roon 2 have special hardware requirements (compared to Roon 1.8) when it comes to internal drives? With my existing internal drives I can run 1.8 with no problem, restore and reboot, which makes me reluctant to think that a new drive will solve the problem. Also I can run Roon 2, restore and reboot, if I only use Qobuz (and no watched folder) and I can run Roon 2 after scanning my watched folder - until I reboot (then I have to reset my database and do a new rescan).
The web-interface showed that Roon core was running fine. But the remote on my Mac crashed every time I tried to start it, even after a clean install of the remote.
Reinstall from the webinterface and things were running agin. This time I did not add Qobuz but did add/scan my watched folder, everything running fine until the test: hitting the restart button on the web-interface brings it into endless restarting (now every 16 seconds). Only solution from here is to reset the database, and scanning my musicfiles once again.
Based on the issues you’ve been experiencing, it does sound like you could be running into your internal music store SSD slowly starting to fail. If you haven’t yet, I would make sure to get a copy of your library saved to another location.
That said, if you perform the above, and again disable your internal storage, but set up your library on a different drive, do you still run into this issue? If not, then it may be time to replace the SSD.
Do you restart your core often? I’d be curious how things run if you didn’t try to restart so shortly after, and let things run for a few hours.
Our team reviewed your logs a few different times. We’re seeing a large amount of Critical traces but we cannot yet verify if they are related to your internal music storage SSD.
Hello @benjamin,
Finally - after almost 4 month of Roon troubles - I have found out what caused the problem. As I wrote 14 days ago I suspected that it was one (or more) of my files that caused the problem. Files that for some reason works in Roon 1.8 but not in Roon 2.0.
I started from scratch adding my 2.700 albums in portions until I ran into the problem (not being able to restart). Then I once again started from scratch adding portions of this portion until restart-problem. And so on. And so on. Until one last file. THE file.
It turned out that one of my more than 24.000 flac files caused the problem. Removing this file from my internal drive means that I’m now able to backup, restore and restart my Roon core when needed without being forced to reset my database!
Inspecting the file revealed a weird/faulty and very long title tag. After fixing this tag I could add the track to my database causing no problems.
I wonder why this file causes problems in Roon 2.0 but not in 1.8?
I’m surprised and somehow disappointed that this problem could not be identified through the log files. That would have saved me a lot of frustration and a huge amount of time. Had I not been a lifetimer I would have unsubscribed from Roon.
This is interesting indeed! I’ve yet to come across a situation like this. We’d love to take a closer look at the track involved with your issue. Feel free to upload it here:
Hello @benjamin,
I have uploaded the file. Hope you can make some good use of it. I have no idea how the title field ended up in such a screwed-up way!
)
