NUC10i7 with ROCK: Can I switch to UEFI booting easily?

I run ROCK on a NUC10i7FNH with 32gb RAM, 500gb NVME SSD for system, and a 4tb SSD for music (inside the unit).

At the time I set this up ROCK would only work with legacy booting, so that’s what I did.

I am wondering if I can set it to UEFI booting now and what changes I would have to make.

From memory, so maybe missing a step, but it’ll go something like this:

  • Backup Roon
  • Download the Rock install image
  • Create your bootable USB install stick
  • Enter the NUCs bios and disable legacy boot
  • If successful, you’ll should be able to boot and install Rock from the USB stick
  • Authorize, and restore your Roon database

What @mikeb said but probably worth keeping in mind:


Thanks for that quote. Yeah, I don’t think I’d bother either… “never touch a working system” :rofl:


Yeah, don’t fix it if it ain’t broke… :slight_smile:

1 Like

The biggest reason for me to try this was to then switch from Rock to DietPi, as I wanted protection for SMB through user access control, the ability to output Roon display to my TV and running Roon Extension manager and a few other packages that DietPi easily allowed.

If I had stayed on Rock I don’t think that the move to UEFI would have added anything.

1 Like

DietPi? Are you running the Roon core on a pi?!?! :smiley:

I guess it’s not unthinkable since you can run linux on it and I suppose you can install the core on that linux base?

DietPi can run on 64 bit X86 computers as well as RPi’s. It makes for a very easy to manage Roon Server whilst still offereing more management and monitoring tools than RoonOS (as installed by ROCK).

Highly recommended - unless you are running Early Access Roon Server - which presents a few more challanges on DietPi.

DietPi on a Raspberry Pi does not run Roon Server and does not allow a Roon Server install.

Edit: Fixed typo which made a nonsense of the last statement.


Exactly as Wade said.
There are quite a few of us running it and we are a pretty happy bunch (well for Room user’s at least :face_with_hand_over_mouth:)

1 Like

Yes makes sense. Is this on an RPI 4 or RPI 5? I have a few RPI4/8gb lying around that I could try just for fun.

I don’t understand… How does it run it without allowing it to be installed?

The one concern I would have is the flakiness of the microSD card as a system drive. Have you guys used the nvme method for system drive?

My emphasis!

Those of us running Roon Servers on DietPi are not running Roon Server on Rpi DietPi.

Sorry - this was a mistake - there was a missing ‘not’ from the first part of the statement - corrected in my original post.


Ok this is very interesting… So you run a NUC/PC with DietPi and install Roon Core linux version on it. This is particularly interesting if one wanted to run HQPlayer as a transport/resampler.

Do you run this computer headless?

Personnally, I do run the DietPi Roon Server headless.

DietPi, as you may be aware if you have run it on an RPi, has an interactive script for managing software installed on the machine. Roon Server and many other packages are directly supported by this script. To my knowledge HQPlayer (and I have only done a very quick search because I don’t use it) is not supported by this script (although "NAA daemon: signalyst network audio adaptor (naa) " is supported).

I would imagine that HQPlayer can still be installed but I wouldn’t know the details. Under the hood, DietPi is currently Debian Bookworm and apt and apt-get are supported using the debian package repositories.

However, there are some things that differ between many linux distros and DietPi that may require some manual intervention or “tweaking” in just the same way as the DietPi Roon Server install script differs from the normal Roon Server install script in respect of certain details (like where the user data should be stored).

Interesting, thank you.

HQPlayer can be set as the output endpoint in Roon, and if used over the network, would play to an NAA receiver (the NAA you see there is to make the device run the NAA client).

Ultimately, I could install any linux distro and use a command line interface to load any software that would run on linux.