I recently moved my Roon Server to a laptop (a super powerful gaming laptop). What I really like about it is: at the end of the day all I have to do is close the laptop lid, and the laptop goes to sleep. The next day, I open the lid and that’s it! I don’t have to do anything else and the Roon Server is back up in no time.
In the last two days, I noticed, there is a change in behavior. Now, when I open the laptop, Roon server goes to rescan all my drives, and that is quite a few. So now it takes time before I can get to my music, plus the drives are getting worn down with all the unnecessary re-scanning.
To me, the original was the correct behavior. All that happened was sleep and wake up without any re-scanning.
How can I get back to that behavior? Is there a setting I can set on either Windows 10 or Roon Server?
What is the model of router and switch in use here?
Looking at your screenshots, I notice a couple of watched folders don’t have any tracks. Is there a reason those are added?
Moving forward, I’d like to enable diagnostics so the team can take a closer look. Before I do so, may I ask that you please reproduce this behavior once more (wake the machine) and note the time that you see scanning start. Respond here with that time, along with your timezone, and I’ll be sure to enable diagnostics.
Now that I have the timestamps, diagnostics have been enabled on your account. I’ll have the team take a look at the diagnostics report and will be sure to let you know as soon as I receive their feedback.
I am not sure I understand: I gave you the time when the most re-scan started, but you enabled the diagnostics a few hours later - when the re-scan was already done.
So I don’t think your diagnostics will catch anything unless I make the Roon Server Windows 10 go to sleep and wake up again - which of course I am happy to do.
As it is, i left Roon Server up all night, because performance of search and play is terrible while he is re-scanning.
I wanted to reach out because I’ve been keeping an eye on our servers, waiting for the aforementioned diagnostics report.
For some reason it is not reaching our servers, even after I tried re-enabling diagnostics on your account. I also ran a quick test and I was able to submit a similar report from my setup here, so something else is going on.
So we can move forward, I was hoping for now you could use the directions found here and send us over a set of logs using a shared Dropbox link. We will need logs from your Core machine.