Server: Nucleus Titan (RoonOS 3.0 build 274)
Client: Windows 10 - Roon 1665
As the title states, I can access my Nucleus Titan’s internal storage at \\ROCK\Data and not \\NUCLEUSTITAN\Data. I’m not certain when this changed and it could either be from RoonOS 3.0 or one of the more recent Roon EA releases.
(I’m not looking for assistance, just wanted to report it.)
For reference, here’s the internal storage kb.
@Wade_Oram - the Roon Server Name in 
> Setup is independent of the hostname, so changing this won’t have any effect on the hostname.
Something else is going on.
@gsuzor91 - this needs to be investigated by the EA team, your Nucleus Titan should certainly not have ROCK as the hostname.
Of course the question about previously owning a ROCK is nevertheless interesting because the network name can be configured on the router in the local DNS.
Perhaps an old „rock“ DNS name carried over if the Titan has the same reserved IP, for instance.
Have you installed Roon OS 3.0 on the Titan. If so, you’ve probably changed it to a ROCK machine (AFAIK, there is only one bin file.)
If so, you will likely require another step as all Nucleus do to finalise the setup, which is the same for production releases. I guess the web interface will confirm this.
But this would only happen on a reinstall if one must switch to UEFI I would think. However, the Titan is already UEFI, so I don’t know why this in-place update to 3.0 would be any different than any other RoonOS updates.
There is only one bin file, but the title of the release notes for RoonOS 3.0 mentions both Nucleus and ROCK systems.
What are other Nucleus owners seeing if they have installed this EA?
IIRC, anyone reinstalling Roon OS, including pre-3.0, requires a support request to install Nucleus-specific features for cooling, home control, and to change the device from ROCK to Nucleus. I’m not aware that this has changed (but I note @Geoff_Coupe’s comment.)
Seeing the web interface would help. Is the device identified as a Nucleus or not? If it is, then maybe the host name was missed during the build, and each device type is configured during installation. If not, ???
Yes, if you reinstall from scratch, but this should not be necessary to switch a Titan to 3.0. Only Legacy BIOS installations require a reinstall from scratch with UEFI.
Just clicking the Reinstall button in the web UI has never required a separate reinstallation of the specific Nucleus software through a support request. At least support staff never said so after they gave the “click reinstall in the web UI” advice, AFAICT
But that was likely reinstalling a Nucleus image. If the EA release is generic, it will overwrite what was previously installed. Ideally, it should check the hardware, and configure accordingly.
Sure, but we have no idea yet whether it doesn’t 
based on the available info in the OP. Perhaps there really is something wrong, perhaps there are other causes for the DNS name assignment.
Yeah - but that’s not the route for installing this EA of RoonOS 3.0 - this uses the placing of a bin file in the reinstall folder rather than installing from scratch using a USB stick.
@ivan - some clarification is required here, please.
The bin file is small, so probably pulls an image according to the device. I agree it’s not clear, which is why a screenshot of the web interface may help.
This is a tiny file, so another image is downloaded as part of the process.
Exactly And as per @ivan
So, I would expect that the running system would first check to see what flavour of RoonOS is currently installed so as to be able to download the same flavour of RoonOS 3.0.
The EA team need to investigate whether this instance of ending up with the ROCK flavour is a one-off glitch or pointing to a deeper problem.
But, I agree with your suggestion: @gsuzor91 - could you please post a screenshot of your Titan’s Web Administration Interface screen?
Here it identifies correctly as a Nucleus Titan. Therefore, it seems that what I wrote here is still a possibility:
Or something got forgotten in the new Titan EA build?
It could be because the planets haven’t aligned. I’d wait for @ivan to appear on Monday before spending another 8 hours bashing out plausible causes. 
