· Roon is slow, freezing or won’t start
· Roon won’t start up at all
· Trying to bring up my Nucleus Titan after mini; crashes on restore
· Full Ubiquiti network, Titan connected directly to switch that router's connected to; router also Ubiquiti; all up to date.
Hi @David_Nanian,
Thank you for the report. The team has pulled diagnostics and will respond with more information once we have clearly identified what’s wrong.
Note that I restored a months old backup from the Titan which worked. But the day old backup did not; that is what caused the failure.
We pulled the diagnostics from the Titan and went through them. The short version is that the failure itself is not in there. The oldest entry in the archive is 09/24 17:59 UTC, and the system log starts at the boot at 17:02 that same day, so everything before the reboot has already rolled off. The logs from the Titan since then are clean: no crashes, one restart at 17:51 on 09/24 and then four days of uptime, and the nightly backups to the DiskStation have completed every night since.
What we can see raises a question about which backup failed. In both \ROON Backups\RoonBackups and \ROON Backups\Daily the sets run from mid May to 22 June, then nothing until 25 September, which is after the restore. So in those two locations there was no day old backup at the time you tried.
Could you please tell us:
If the backup is still on disk, please leave it in place. With the location and timestamp we can look at the right set rather than the one that worked.
Well, that’s unfortunate, Vadim. I had hoped that it wouldn’t wipe all of the info about the multiple failures there, but I can’t control your logging turnover. 
Anyway, the backups I was restoring were from the mini, since that’s what I’d been using. I restored the backup made that day, in Daily, which was listed in Roon for the mini. It’s the most recent one there. Are you unable to see them? The last date/tiime I attempted the restore would be about 30-60 minutes before sending you the screen shot of the failure, above.
The reason that there are no backups after mid June was that I had the Titan off and was using the mini, which remains more performant, even with a bunch of other stuff running on it. But the Titan, with the most recent stuff (eg the search improvements), seems to be running acceptably at present: as you said, no crashes over a few days, which is unusual, at least based on how it had been running since purchase (quite a while ago).
The Titan’s logs only enumerate its own machine folder, and the Mac mini writes to a different one, so the mini’s sets were never going to appear in what we were looking at.
On the timing, your numbers line up. The screenshot went up at 17:02 UTC, so the restore attempt was around 16:00 to 16:30. The Titan booted at 17:02:44, and the oldest surviving log entry is 17:59:42. That hour was consumed by the library rebuild after the restore that did work, and the volume of it pushed the failure out of the retained logs. Your point about turnover stands, and it is not something you should have to work around.
Where things are now. We pulled fresh diagnostics this morning: the Titan has been up for just under seven days with no restarts since 24 September, no crashes, and seven consecutive nightly backups. So there is nothing currently failing, which is a change from how you describe it behaving since purchase.
That leaves one open question.The library you are running on the Titan came from an older Titan backup, not from the mini. If you still want the mini’s recent library on the Titan, then the failed restore matters and we should work through it: we would ask you to attempt that same restore once more and tell us within the hour so we can collect the logs before they roll. If you are content with where things have landed, we would rather not have you disturb a system that is finally behaving.
