So sorry to hear this! I hope you find a way to restore a backup. Honestly: I‘d be in tears if I would loose all the work I put into the data… Have you opened a ticket at the Roon forum?
there’s a thread for 1.8 installation issues, and I posted to that. Many, many users have had this same database-corruption issue. I figure another ticket will just get lost in the noise. I can wait for there to be an official Roon response/announcement.
Or just walk the dog and move on.
The Roon Beta locked site had similar reports. Apparently they chose to rollout anyway. I keep all my playlists in Qobuz or Todal after being burned once on Roon playlists.
yeah, bummer is that I have (well, had) some playlists that are a combination of Tidal, Qobuz and local files. My giant “Cool dinner party” playlist was like 40 hours of great jazz from all sources. Poof.
I read that quite a few people with Win7 are having problems. I don’t think I saw anyone with issues running ROCK or a Nucleus.
I can’t tell either. I’ve recently installed a new cabinet and changed several power cords and cables. I kinda wish I hadn’t upgraded Roon for a few more weeks while these changes settle in. Oh well.
Roon uses a database that wasn’t really ever intended to be run in harsh environments* (like the way Roon is using it). It was meant to be run in data centers and compute clusters where data integrity is already taken care of so the DB itself doesn’t need to worry about these things. However, the DB has some very strong advantages with one being a data structure that allows you to use the DB on almost any platform as well as move between platforms. That’s probably why Roon went with it. It can also be very fast if you’re careful about how the data is stored.
But, it can corrupt itself in a way that you won’t realize it is corrupted until it hits that point in the tree. This means your DB can be corrupted for a long time before Roon crashes. It is often you only find this corruption at reboot or upgrade. For most it occurs well after they have gotten rid of a “good” backup.
*harsh environments… I mean consumer PCs where users have a tendency to not properly shutdown, don’t have redundant power, using file systems with minimal write checks, etc.
Anywhooo… I’m not a DB guy I only play one on the Intertubewebnets. I don’t have a good alternative other than someone forked that DB code a while back trying to fix this shortcoming and make the DB itself much more robust. However, that occurred after Roon was a thing and I have no idea the monumental effort it would be to move data into a different DB at this point.
MegaOuch.
I’m running roon core on a mac mini. (And roonserver is basically the only thing that mac mini runs.)
Seriously, it’s been flawless up to now. I mean, a few little niggles here and there, but pretty trouble free. I’ve often found the Roon forum exhausting, or at least tough to read at times, with so many users having issues I’ve never had.
I guess I get to join the club!
Preach it. I have spurts of engagement on that forum. Most of the time I just read some threads and don’t engage.
Oh there some closed mindedness regarding cables. Especially digital ones on Roon Forum.
I’m seeing some issues for the release and have filed a few bus with Roon.
Crusades level closed mindedness. Convert or perish.
They act as if we were spending their money. That amount of vitriol has to be exhausting.
With my NEW CABLES the new version of ROON sounds pretty swell.
I blame my NEW CABLES.
Those darn new cables, they have a bad habit of making everything sound better. How dare they!
Please post your cable journey on the Roon forum I will bring the popcorn.
I don’t want to talk about my old cables.
I just want to talk about my NEW CABLES.
OK, I will bite.
@aangen - rumor has it that you have new cables. How are they?
We know it’s because of that fuse you like those new cables so much. That stock fuse was holding everything back. BTW I’ll trade some better fuses for those cables.
They are NEW!
Make sure your roon remote matches your roon core (should be build 880). The beta test was 861 something (?), afaik. Like everybody else, I upgraded recently even though I had the beta installed. It was late last night that I did it, but noticed today that my main roon remotes were still 860-whatever. I actually had to go to the app store(s) to initiate the upgrade, after being at a loss for other ways and means. Seems to have really helped after search fails engendered this activity. I must not have clicked the “update all” as per usual. Good luck, chums.