Roon Crashing on Windows 10 x64 1903

Support
22

What other options do you recommend?
What does you tech team says based on Log files I have sent?
Is there a way to run Roon.exe in diagnostic mode?
Would copying the Roon Folder to another Win10 PC and Running that PC as core work? Or is the DB specific to a PC?

Is there a way to programatically access the Database via an API? I can do programming.

I see there are multiple people having the same issue with Windows 10. Don’t you think its somehow related?

Can you please respond as I only get time during evenings?

23

Can anyone please help as support is not responding to my questions?

24

@support
I unauthorized Roon from PC that was having crash and installed Roon x64 on a different Windows 10 PC Version|10.0.17763 Build 17763.

I copied the Roon Folder from other PC but the crash still happens.
Surprisingly I was able to play a clip for few seconds before the crash so it seems there is something Corrupt in the Database.

All I’m trying to do is get back my Playlist and Playdata that I have created over many years.

I would appreciate if anyone from Support can help restore that data.

25

@support
@dylan
I was able to locate Roon Backup files from last week. Somehow I forgot the location and I discover it tonight.
I reinstalled Roon by renaming current Roon folder to Roon_Old.
On Installation I choose Restore From Backup.
Roon comes up but after playing music for about 10 mins it crashes again and keeps on crashing after that.
I tried two Roon backup from past 2 weeks and crash happens again.
Here is the dropbox link to crash that happened Aug 15th at 12:55am CST

I’m not sure why crash keeps happening even after restoring from old backups.
I’ve spent past 2 days chasing this issue and there has been no resolution.

26

@dylan
I uninstalled Roon completely and reinstalled fresh.
On Startup I choose restore from backup.
After Restore I relaunch Roon UI and let it still for few mins without playing any music.
Roon crashes within 10 mins.
I checked logs file of crash happened last night and right now. The last call to meta data server is same
before the crash

08/15 00:54:36 Trace: [metadatasvc] REQ [2949] https://metadataserver.roonlabs.net/md/4/getmetadata?uid=91c858d9-2622-46c0-8ee4-a8d399ba1b64&lid=&token=111ab3a8-4e96-4e62-bddf-8d276748c75b&metadataid[]=7b004d5430303034343533333036&metadataid[]=7a004d4e30303030313138353039&metadataid[]=7a004d4e30303030333035313432&metadataid[]=7a004d4e30303030353130383035&metadataid[]=640101c48797afadf56ae7d549d8a10f2292&metadataid[]=79004d5230303030343731373732&metadataid[]=7a004d4e30303030383133383936&metadataid[]=7b004d5430303033373533343138&metadataid[]=640119d460c67ff7afcc144f75a4d0148c47&metadataid[]=7b004d5430303035333436393236&metadataid[]=64018a589901420363a6ec11467a3d5e60a8&metadataid[]=7b004d5430303034373736373132&metadataid[]=6401483a08b53236c6bba230c55cc87d677c&metadataid[]=7b004d5430303035343739363631&metadataid[]=64014694c2c955017175652e50f0458864b1&metadataid[]=7b004d5430303031383536333135&metadataid[]=6401c3906ecc37ffb944cd16f2b2c65ba0cb&metadataid[]=7b004d5430303034313638333432&metadataid[]=64010833c109566f994824371d34b601e922&metadataid[]=7b004d5430303034323336353233&metadataid[]=6401fee95befb9ec6f0d7d74fc48ab895b9f&metadataid[]=7b004d5430303034363632303038&metadataid[]=6401fd5a1afb9ff7a0b9bad1a7f50a476dc5&metadataid[]=7b004d5430303031323433353031&metadataid[]=64017876adabd42c80d3f5ec7553b4b42631&metadataid[]=7b004d5430303033383438373330&metadataid[]=640151f7bcb9e3b8d0e2bae3b2f1f7ad2f8d&metadataid[]=7b004d5430303034313937313835&metadataid[]=6401f7693966849d6bf1e61e320096a38b07&metadataid[]=79004d5730303030303233343233&metadataid[]=79004d5730303030323038353938
08/15 00:54:36 Trace: [dbperf] flush 0 bytes, 0 ops in 16 ms (cumulative 839337038 bytes, 446386 ops in 123948 ms)

08/15 06:16:57 Trace: [metadatasvc] REQ [2943] https://metadataserver.roonlabs.net/md/4/getmetadata?uid=91c858d9-2622-46c0-8ee4-a8d399ba1b64&lid=&token=111ab3a8-4e96-4e62-bddf-8d276748c75b&metadataid[]=7b004d5430303034343533333036&metadataid[]=7a004d4e30303030313138353039&metadataid[]=7a004d4e30303030333035313432&metadataid[]=7a004d4e30303030353130383035&metadataid[]=640101c48797afadf56ae7d549d8a10f2292&metadataid[]=79004d5230303030343731373732&metadataid[]=7a004d4e30303030383133383936&metadataid[]=7b004d5430303033373533343138&metadataid[]=640119d460c67ff7afcc144f75a4d0148c47&metadataid[]=7b004d5430303035333436393236&metadataid[]=64018a589901420363a6ec11467a3d5e60a8&metadataid[]=7b004d5430303034373736373132&metadataid[]=6401483a08b53236c6bba230c55cc87d677c&metadataid[]=7b004d5430303035343739363631&metadataid[]=64014694c2c955017175652e50f0458864b1&metadataid[]=7b004d5430303031383536333135&metadataid[]=6401c3906ecc37ffb944cd16f2b2c65ba0cb&metadataid[]=7b004d5430303034313638333432&metadataid[]=64010833c109566f994824371d34b601e922&metadataid[]=7b004d5430303034323336353233&metadataid[]=6401fee95befb9ec6f0d7d74fc48ab895b9f&metadataid[]=7b004d5430303034363632303038&metadataid[]=6401fd5a1afb9ff7a0b9bad1a7f50a476dc5&metadataid[]=7b004d5430303031323433353031&metadataid[]=64017876adabd42c80d3f5ec7553b4b42631&metadataid[]=7b004d5430303033383438373330&metadataid[]=640151f7bcb9e3b8d0e2bae3b2f1f7ad2f8d&metadataid[]=7b004d5430303034313937313835&metadataid[]=6401f7693966849d6bf1e61e320096a38b07&metadataid[]=79004d5730303030303233343233&metadataid[]=79004d5730303030323038353938

Here is the link to logs file for fresh installed Roon that crashes

27

Hi @Arshad_Malik,

Moving forward here, I’d next like to try to this:

Power off both the Synology and the FreeNas where your media is stored. Then try to launch the database that is having the issue.

When you do this, are you able to navigate Roon without the crash occurring?

28

Ok powered off both Synology and FreeNas.
Changed to Roon folder with Database that was having crash.
Restarted Roon and after 10 mins I get this message below. I’ve copied the link to log file
“There was an issue loading your Database. Don’t worry. Roon staff ready to help”

Instead of renaming should I restore Roon from backup with the Server’s DOWN?
Please advice next steps

29

I tried restoring database with fresh Roon install with Server Down.
I get the same error message “There was an issue loading your Database”.
I think the restore needs the Media drive to be running.

Can you please suggest what other options I have to fix this?
Can you have your tech team look at it as this seems to be a technical issue with your MetaData Server?

30

Hi @Arshad_Malik,

Can you zip up the entire logs folder and send it over via a shared Dropbox link so the team can take a look?

Also, do you have any other, older backups you could try?

Thanks!

32

Yes I have 10 backups from Jul 4 2019 till Aug 10th.
I’ve tried these 4 backups unsuccessfully
8/10, 8/6, 7/28, 7/4
I’m trying 7/24 right now and will report back shortly.
Will also share Log files

33

Hi @dylan
Tried a clean Roon install and restore from backup from Jul 24th files and it still crashes after about 10 mins after relaunch of UI
Here are the dropbox link to log files

I would appreciate it if you can have this looked at with your tech team right away as you already know I’ve spent past 3 days and night to work out a fix for this.

Thanks,
Arshad

34

Hi @Arshad_Malik,

I appreciate the thorough testing here. I’ve passed your testing results and logs along to the team — I’ll reach out ASAP once they’ve analyzed them.

35

One thing i noticed is whenever I restart Roon it always rescans all files from FreeNas but it does not do that for Synology Diskstation. This has always been that way since I started using Roon.
Do you know why Roon does that?

36

Hi @Arshad_Malik,

I spoke with the team about our next steps here and wanted to reach out. Please see the following steps:

  • Power down the NAS devices
  • Navigate to Settings > Storage
  • Disable all watched folders except for one
  • Power the NAS devices back on

With a limited subset of you library active is there any change here?

37

Hi @dylan
Followed the steps

  • Disabled Free Nas watched folder
  • Kept Synology DS1813+ enabled
  • Restarted Roon and it does not crash
    I don’t understand why as I have not added any new music to FreeNas and it’s been running 11.2 stable build for many months.
    I’m running diagnostics & checks on FreeNas and will report back when its finished.

Have you come across this issue with any other users?

image

image
image.jpg637×684 72.7 KB

38

Thanks for confirming that this works, @Arshad_Malik.

Can you confirm how many tracks are on the FreeNas that import into Roon?

It sounds like there is some media that is likely causing the crash that is located on the FreeNas. We’re hoping to narrow this down a bit by trying the following — Split up the media on the NAS into two folders that can be watched by Roon. Activate them one at a time. Does one of these folders work while the other one causes Roon to crash?

39

I enabled FreeNas and it crashed while scanning the folder as shown below. It has about 297,351 tracks

Also I ran the diagnostics on FreeNas and found one of the drive had unreadable sectors. I replaced the drive and currently its re-slivering the ZFS Pool and will be done probably tomorrow.
I want to wait until the re-slivering is done to Split the folders to prevent any data corruption.

image
image.jpg807×705 77.8 KB

40

Thanks for the update, @Arshad_Malik. Let us know how things go after things have re-scanned.

41

@dylan
I added each folder individually from FreeNas to Roon library last night and it started downloading metadata
Roon crashed this morning around 7:17am CST while importing meta-data from Roon server.
I restarted again around 12 pm CST but crashes again. So seems like there is some issue with metadata extraction.

Here is the link to log files