@Ian_Mason is your ROCK allocated a static IP and is every device on the same subnet?
I believe there have been issues with discovery with both DHCP IPs and devices on different subnets.
Static IP no streaming services local access only.
1 Like
Same subnet. Static IP wired.
1 Like
Nope. Local only.
1 Like
The rationale is that if ever you use the Web Administration Interface of Roon OS to reinstall the OS, any music files on the m.2 SSD will be wiped, because only the default folders and files for Roon OS and Roon are recreated.
By design, there’s no straightforward way to put music files onto the m.2 SSD in the first place - those who insist on doing it have to add the watched folders as network shares…
Take the ROCK machine completely out of the equation. Put Roon on the 2017 iMac which should run a 500Gb collection just fine. Move your music storage to the iMac. That should eliminate the ROCK machine. If there are still issues then it may be a network issue but first eliminate ROCK hardware.
3 Likes
That was my next port of call. I ran it that way absolutely fine for several years with the NUC running Windows 10 connected to my Mac with the Roon Node software. With all the sarcastic comments in response to my post nobody has yet solved the problem.
You might want to raise an official support request in the Support category of the forum. That way, the support team will get involved and likely pull diagnostic logs from your system for review…
1 Like
I second Henry’s comment – put Roon back on the Mac where it worked for you.
The only real benefit of ROCK is hands-off no-tinkering management. That’s not working for you. Go back to what does.
2 Likes
Hi @Geoff_Coupe,
You are correct re the rationale, however, this is not what @Ian_Mason is doing.
He has two separate storage areas:
-
The internal nvme which is only being used for RoonOS/ROCK and holds the Roon DB.
-
The external, via USB, nvme (SSD) which is being used for music file storage.
There is no conflict here.
Hope this helps.
1 Like
Agreed, @Ian_Mason this is the best way to get to the root cause of the issues you are experiencing.
Roon’s support team can enable detailed diagnostics and drill down into them.
1 Like
I try to get to the bottom of a person’s issues because that is pretty much what I do for a living (on very different systems of course). Admin are quite correctly steering you in the direction of seeking support but there is stuff you can do to narrow things down a bit while you wait.
1 Like
What’s that in real money?
10K in the States? Well now you’ve got a decent pair of loudspeakers.
Edit: @Ian_Mason , apologies for the ball busting but @Henry_McLeod in my opinion is right on point. Get back to K.I.S.S. my friend, I run primarily a MacBook M1 via WiFi ( crazy I know ) Darned thing hardly ever burps or farts. Unbelievably robust. You’ve got to many moving parts to what end?
2 Likes
Those are harsh words, though I’m sure your frustration has played a part in your tone.
I’m not a network engineer, though I have a very “sorted” network:
Pretty heavy duty, though all of my hardware was obtained (switches were used purchases from eBay) for less than the cost of an entry-level “audiophile” network switch. As a network engineer, I’m sure you share my sentiments on “audiophile” networking.
I’ve been using Roon for ~3 years, and paid out for a lifetime subscription a year ago. My core is an Intel Xeon-based Synology Rackstation. Other than the occasional niggle with ARC on my Android phone, Roon has worked flawlessly for me, despite being enrolled in the beta/early release candidate programme.
I concur with the advice given. Go back to what worked before and re-evaluate your current setup.
A few people complain about support. On balance, I think Roon has it about right. The community irons out the more trivial issues, leaving the support team to deal with the heavier lifting.
“Better” support costs more. Given that the majority of users have little in the way of issues, I think the current model is appropriate.
6 Likes
NUCs have a way of failing slowly that causes all sorts of baffling behaviors. Often as a result of a dust-clogged fan causing overheating. My first NUC, a Roon server, started having hardware errors (I run Ubuntu Server so I can look at logs), causing Roon issues, and eventually failed totally. One of my Zotac ZBOX fanless servers is starting to glitch after several years of great service, the logs are increasingly full of USB and DMA errors. I expect it to give up the ghost soon, so I ordered a much burlier fanless server from a trusted custom vendor.
TL; DR: cheap hardware is cheaply made.
4 Likes
What?! You have CCTV on the same network as the rest of you stuff?
How did you graph your network?
1 Like
Indeed I do.
It was done in MS Excel.
I’m graphing my network now with old nmap readings from the latter 4 years until today, not sure where I will make the actual display, perhaps D3js
1 Like
As do I it’s simple to do with UniFi kit.
Does sound like failing hardware here and not Roon as the actual problem.
Rock user for 4-5 years it works fine and is a stable platform.,Roon has its fair share of bugs it is far from perfect and I have several tickets in as we speak. The only major instability one right now is the current ARC issue which is being worked on and this doesn’t affect everyone oddly. Complete instability really isn’t common and where it does raise its head it tends to be other determining factors that are causing it to happen.