· After the latest installing of Roon updates, first Roon couldn’t recognize my iPhone and iPad as devices connected thru my Roon Nucleus Rev B, and now after seeing the connect to your nucleus page, which the nucleus does, the screen goes blank except for the spinning load symbol.
I’ve thoroughly researched the Roon community and tried every fix offered to remedy this problem, but to avail. I pay $15 a month for my Roon subscription and I’ve never encountered this issue before after a software update. I’ve taken screenshots of my Roon app trying to load, and I can also provide a list of my music gear listening chain.
Your attention to this issue would be greatly appreciated. Sincerely, Bruce Posey
Tell us about your home network
· I use a Calix CAT6 router > L-Com CAT6 Ethernet cable > D-Link network switch > Audioquest Cinnamon network cable > Cisco SG250-08 network switch > ENO streaming system AG > Roon Nucleus Rev B > AQ DIAMOND USB cable > Audiowise SRC•DX > single WAVE Storm BNC > Chord Hugo M Scaler > dual Wave Storm BNC’s > Chord Hugo TT2 Dac > 2 AQ Earth XLR’s > Woo Audio WA22 hp amplifier > Danacable Lazuli hp cable > Focal Utopia headphones.
This is my listening chain and it hasn’t had an issue in 5 years.
Diagnostics from the Nucleus show that the database is logging corruption:
03/03 18:41:32 [Local 03/03 12:41:32] Critical: scx: LevelDb.Exception: Corruption: missing start of fragmented record(2)
at LevelDb.Database._CheckError(IntPtr err)
at LevelDb.Database..ctor(String path)
at Sooloos.Broker.Database..ctor(String dbdir)
at Sooloos.Broker.State.<>c__DisplayClass154_1.g__Finish|1(Boolean vacuum)
at Sooloos.Broker.State.<>c__DisplayClass154_0.b__0()
at Sooloos.SynchronizationContextThread.<>c__DisplayClass45_0.b__0(Object _)
at Sooloos.SynchronizationContextThread._Dispatch(SendOrPostWrapper& ret)
Roon is encountering unexpected changes to crucial parts of the database on startup. This is likely the cause of the spinning during connection. Database corruption is uncommon but usually results from a physical cause: a failing drive, a power outage, or any repeated disconnection event while data was being written.
Corruption can only be resolved by restoring a Backup of your Roon database that precedes the corrupting event. Do you happen to have scheduled Backups for Roon, or a manual Backup handy? Try selecting “restore a Backup” instead of attempting to connect to the Nucleus.
Can you please also share a screenshot of the Nucleus Web Admin page, if accessible?
Connor, I tried all of yours and the Roon website suggestions. This is what I’m seeing now. I turned my system off and restarted it. Then I checked the IP address and configuration on my Apple devices. I’m not sure where I need to go now.
Thank you for your post. We totally empathize and understand how frustrating it can be to troubleshoot networking problems.
We need to ask a few due diligence questions to ensure we’re equipped to troubleshoot efficiently:
Our diagnostic servers show that at least some Roon Remotes have registered multiple subnetworks when using Roon. If you haven’t already, please double-check that this network environment is restricted to a single subnetwork/VLAN. Place any second routers in Bridge mode.
The Nucleus hasn’t responded to our log requests so far, so we’ll need to request a set of manual logs from the device. At your convenience, please use the directions found here to locate the RoonServer “logs” folder, compress (zip) it, and upload it our secure File Uploader
From there, our team should be able to pinpoint any connectivity issues clearly.
We’ve merged these threads together to ensure all our responses stay in the same place. We apologize that your initial report was inadvertently marked as resolved.
Your network setup contains a large number of managed switches. To reduce the number of variables in play, can you please try hardwiring the Nucleus directly to your main router? We’d like to test connectivity using that simplified topology and then build elements of this network back one by one.
We’ve not seen a response yet but we’re very eager to ensure you’ve found the support you need. Please reach out if we can assist further. We’ll ensure this thread doesn’t auto-close over the weekend. Thank you and we’ll await your reply.
Connor, thank you again for reaching out to assist with my non-functioning Roon Nucleus Rev B. I have not been able to solve the problem of its corrupted files or have been able to determine if its motherboard is fried. I will try again to go thru the suggested protocols and see if this unit can be resurrected. If you could please leave this thread open until I get back to you I would greatly appreciate it.
At this point I’m almost willing to have a Nucleus One sent to me because the closest possible repair person for my Rev B is 200 miles away in another state.
We have the auto-close mechanism, which will close the thread.
The best next step here is to get in touch with our RMA department directly, as they’re in charge of all hardware-related Nucleus issues. To do so, open the Typeform link below and select ‘Other’ followed by 'This issue is related to a physical component".
