Hi @Chris_Russell1,
Thank you for your patience, over a month is a long time to be without Roon and I can hear how frustrated you are. Let me address each of your points as clearly as possible.
Step 1: Container is stopped 
Confirmed, no action needed here.
Step 2: Permissions Your screenshot shows the Music shared folder with both administrators and ChrisR having Read/Write access. That is correct and no changes are needed here.
Step 3:What folder to rename, and where to create the new one
This step is about creating a clean, dedicated folder for Roon’s application data (its database, settings, etc.) on your NAS. Here is exactly what to do:
- Open File Station on your QNAP (you'll find it in the main menu).
- Navigate to the homes shared folder, then into your own user folder (likely called ChrisR or admin).
- Look for a folder called RoonServer (this is where the old container was storing its data). Rename it to RoonServer_OLD, right-click it and choose Rename.
- Still in the same location, click Create Folder and name it exactly: RoonServer
Step 4: The YAML code and recreating the container
The “YAML code” is the text in the configuration box that looks something like this, it defines how your container is set up:
services:
roon-server:
image: steefdebruijn/docker-roonserver:latest
container_name: roon-server
network_mode: host
environment:
- TZ=Europe/London
volumes:
- /share/homes/ChrisR/RoonServer:/var/roon
- /share/Music:/music
restart: unless-stoppedTo recreate the container using this:
- Open Container Station on your QNAP.
- Click Create (or the + button).
- Choose Create Application (this is the option that accepts YAML).
- Paste the code above into the text box. Important: check that the paths match your setup, specifically:
/share/homes/ChrisR/RoonServershould be the path to your newly created RoonServer folder. If your username folder is named differently, adjust accordingly./share/Musicshould be the path to your Music folder on the NAS (this is where your audio files are stored).
- Click Create or Deploy.
Regarding Screen Sharing, Roon Support doesn’t offer screen sharing sessions unfortunatly. However, the good news is that you don’t actually need it, you are clearly following instructions carefully, and the remaining steps are very doable. The key is taking it one screenshot at a time.
What I’d suggest: attempt Step 3 first (renaming the folder in File Station), take a screenshot of the result, and post it. Then we can confirm you’re in the right place before moving on to Step 4. That way nothing goes wrong silently.
One more important thing with finding your backups. Before recreating the container, it’s worth checking whether your old Roon database backup exists.
In File Station, search across all shared folders for a folder called RoonBackups. It may be in the Download share, the homes share, or even on an external drive if one was connected. A screenshot of what you find would help confirm whether your library data is recoverable.
You are not far from the finish line here, the hard work is already done. Let’s take it one step at a time. 
