I currently have Roon server on a NUC with a DietPi install. I know I could get ROCK instead but that’s not exactly what I need/want.
Server works great however, there’s a persistent issue when update happens as it seems it’s wiping out the server and basically need a restore after the update to get back library, settings etc.
That issue has already been reported on Dietpi forum here and the DietPi folks are saying they’re actually following every steps as described in Roon installation and that this issue should be raised here.
Lovely - I’ll give it a go there. Thank you v much. As you said that’s one of the caveat of using this distro but I prefer this to a full fledged Linux distro as I find the maintenance of DietPi so easy.
I actually had an arch Linux core but the effort to put it up again after I had a hard disk failure really put me off doing it a 2nd time. Also I was looking at a solution that’s easier to update as well as automated scripts to backup which Dietpi is fantastic at.
With respect to your first question, Dietpi has images for nuc and it’s something they support.
Just need to find a way to get the update clean for roon but it looks like all I have to do is install as if it was a regular Linux box instead of using the Dietpi installer.
Hey guys, I’m sorry that this issue has been open for such a long time. If you face an issue with DietPi, please @MichaIng mention me here now, I’ve enabled email notifications.
Thanks for figuring out that the data directory within the core directory is the reason for this issue. We’ll fix this with next DietPi release by splitting both, a PR has been opened (which triggered my activity here):
Hey guys, a PR is now up to fix it, and I also want to fix it for existing installations. Current solution is to simply reinstall it on next DietPi update, which will install it to a new directory /opt/roonserver and then remove the related files from the previous combined install + data/config/logs dir /mnt/dietpi_userdata/roonserver, while leaving actual data/configs/logs in place. But this means that there are no migrations done to the database, in case required, like the internal updater may do. So the question is whether a new Roon Server version will do this in case automatically, or if this may fail with an old database or old settings?
Another solution would be to move files from /mnt/dietpi_userdata/roonserver to /opt/roonserver to keep the Roon Server version untouched. I’d be happy for suggestions: XXXX
EDIT: Trying to add link to GitHub triggers a spam flag for all my posts? Can someone revert this, please?
Since the database is not touched at all, not even moved, a backup is probably not required. Although when there is a disk that a new Roon Server can corrupt an old database, if not migration steps are done, then yes. But in this case I would go the way to skip updating the Roon Server and only move its core files to the new location, adjust the systemd server and go.
Thanks for unflagging my posts to whoever did . Probably I need to wait for a higher trust level before posting any link.