I thought it was worth a shot preparing a new Roon OS and trying to boot it from that.
It looked promising initially, recognised the SSD and checked I wanted to proceed. I got the message ‘Preparing Disk’ but then
‘ERROR : Failed to partition disk’
‘There was a critical failure during installation’
Looking back in the BIOS it had added the USB stick to the boot list, nothing else.
Trying to find a way out here .. ;( .. This was a useful Roon Server once !
Because MBR partioned drives aren’t valid boot drives for UEFI. You may have to find a way to remove all previous partitioning, then you’re probably able to install RoonOS fresh from an USB stick. Again: There should be threads here on the forum detailing the process of converting older BIOS RoonOS installations to newer UEFI ones.
Thanks, BlackJack, I’ll start searching ..
Bit disappointed Roon support let me walk into this one 
I’m struggling to find a relevant route out of this hole .. I see a suggestion for a migration guide but nothing pertinent to my situation.
I did try a recovery of the RoonOS from USB with the same result.
And going back to Legacy boot recognises the SSD but not as a boot device.
Would a new M.2 SSD come with valid (GPT ?) or no partitioning ?
A brand new SSD should not be partitioned.
Going by some other thread, You should be able to install RoonOS in UEFI mode onto a connected SSD. If this gives you an error, then maybe your SDD is corrupt/dying and needs to be replaced.
PS: You can also use an USB stick to boot into a more functional OS (Ubuntu desktop install media allows you to boot into Ubuntu Linux without installing) to inspect/format/partition your SSD.
Hello,
Would you kindly provide the photo of the Boot configuration in the BIOS settings, and what do you see on the step when you choose the drive to install the Roon OS?
Thanks again, BlackJack !
There it was ‘Failed to partition disk’ leading to buying an USB enclosure to reformat it on a PC. The enclosures are no cheaper than a Lexar 250GB drive so I’ll do that next.
I only know enough Linux to be dangerous .. 
I got a choice to install new or recover previous ROCK
Re the drive choices, it identified the SSD correctly, then I just got 1/1 so no choices.
Confirm the choices, then message ‘Preparing disk’, ERROR etc
Exactly as in BlackJack’s link above
The screen photo is not very clear, but it looks to me as though you have Legacy Boot checked as well as UEFI boot - you should not have Legacy Boot enabled…
Geoff, that’s a definite no ..
Progress at last ! Installed the new SSD (cost less than trying to re-partition the old one) and went into BIOS to check all was well.
Still nothing showing in boot order, but the new disk was identified correctly. This gave me enough confidence to boot from the Rock USB and it all went well, except for installing v 1 build 258.
However, doing a re-install got me v 2.1 build 271. Installed the codecs and hit the Tailscale button. After a couple of sign in messages I got this unexpected message.
If you’re here, it’s because someone in your domain is already using Tailscale. If you don’t know who created your account or need additional assistance, contact us.
Can anyone enlighten me on this one ? I used my btconnect email to sign up.
I don’t know who marked the topic as solved, but the user limit issue seems that it is not really. It might be good if you remove that (as the original creator of the topic I think you can do that) so that it gets attention from @support
Hi @Suedkiez,
I’ve just removed the solved flag and adjusted the auto-close timer.
While I await any further info on the Tailscale issue, I was pursuing the re-configuration of my Rock server.
Using a windows Roon client I switched to the new install rather than the non-existant one and got to adding the network share to access my music on NAS. I put in \ds418j\music, hit enter and it thought about ‘Adding’ it for a while then spat out an ‘unexpected error’ message.
I also cannot access the WebUI. Any ideas ?
Many thanks to Vadim and especially BlackJack for assistance provided to date.
cheers, Maurice
Finally got access to the Deco devices and created a new network, then set it in Access Point mode. Strangely this left me with a 192.168.8.0 mesh network, so I imagine the multi-NAT issue will still be there, necessitating Tailscale. So some help with that user limit failure is needed
At least the webUI is accessible now, but I can’t get the NAS share in for love nor money.
I’ve been trawling FAQs etc on the NAS share issue all afternoon, I don’t seem to be doing it wrong, it is as I remember it. 2 backslashes then ds418j\music
Anyone ?
Please post screenshots of the relevant Roon screens, maybe of configurations screens from the NAS too.
Note: To be able to address a device by its name (ds418j), a working local name resolution system is needed. Most home networks don’t have that. If Zeroconf/Bonjour is used, try ds418j.local instead.
Could you please describe your current setup in a bit more detail so we can better understand the current situation? In particular:
This will help narrow down whether the issue is related to the network, the NAS path, or the ROCK configuration.
OK, thanks for coming out to play.
The NUC install went fine with the new SSD, connected via ethernet
We are definitely on UEFI only, no legacy.
Now we have Access Point mode, ISP router, Deco and all devices are on 192.168.8.xxx
Bonjour is on here, I tried ds418j.local result was Unexpected Error Invalid Network Path
Vadim, is anyone looking at the Tailscale issue ?
