I have a rather unusual use case, for which I need some advice as I don’t want to risk my internal music collection.
Here is what I did in the past:
I installed Roon ROCK in my NUC7i7BNH
ROCK running on the internal 256Gb m.2 SSD
I put a 4Tb Samsung SSD in the SATA slot of the NUC
Let ROCK format the SSD and activated the internal storage
Moved my music collection from NAS to SSD
So far the steps are pretty standard at all worked flawlessly.
Then I bought a new Roon setup, a Grimm MU1. I didn’t buy it with an SSD as I already had one.
So the next step was:
Backup Roon from my NUC to my NAS
I removed the SSD from the NUC and installed it in the Grimm MU1
Restore Roon from my NAS to the Grimm MU1
This worked perfectly. The Grimm recognized not only the drive but also my music. I was playing in minutes. However, one flaw. I could not drag drop music to the Grimm to add music. Neither from Windows or Mac OS did I have writing privileges.
So here is what I did next:
Remove the SSD from the Grimm connecting onto my PC
Booted up my PC in Ubuntu
Renamed the SSD volume to ‘HEAP’ as that is what I saw in the screen shots of the Grimm user manual
Turned off my PC, and moved the SSD back into the Grimm MU1
Bingo. Now, I had writing privileges in the Grimm and my music collection was intact.
Now however, I want to move the SSD back into the NUC. However I don’t remember the volume name Roon ROCK is expecting.
I got two options:
Just move the SSD under volume name ‘HEAP’ back into the NUC and hope ROCK does not care for the volume name, and works straight away
Move the SSD first to my PC to rename it back to the right file name Roon ROCK gave it initially. And then move it into the NUC.
As I don’t know the original volume name ROCK gave the Internal Storage SSD, I cannot do scenario 2. I can of course take scenario 1 and hope for the best, but then I may risk ROCK reformatting the SSD making me lose all the music on it. I have a backup on my NAS but I want to save the hassle of copying all those terabytes if I don’t have to.
Does anyone know if ROCK cares about the volume name or not? Will scenario 1 work?
Otherwise, does anyone know the volume name Roon ROCK expects for the internal storage volume?
Thanks, I thought of that option. But unfortunately I don’t have a spare SSD lying around. And it is a bit exaggerated to buy one just for finding out the volume name. Hoping someone knows this here?
Thank you @Nickpi you answer multiple questions at once. But most importantly, I now see option 2 is the easiest one, just renaming the volume back from HEAP to ROONSTORAGE. But even option 1, nothing will happen until I press the button. I don’t know if putting the SSD named “HEAP” will also work, but why even bother. Renaming the volume is a matter of minutes. Thanks so much!
Surely I hope not! The advantage is it was formatted by ROCK in the same NUC and I’ve renamed it to HEAP after removing it. Renaming it back to ROONSTORAGE and ROCK will not know it ever had another name, I presume.
I’m traveling now, will do this small ‘operation’ in a few days when back home. Will update here the result!
Good news. I took out the 4Tb SSD of the Grimm, booted up Linux Mint off a USB thumbdrive on my PC with the SSD connected, renamed HEAP back to ROONSTORAGE and put the drive in the NUC it was originally in. Roon didn’t notice it was ever gone- it recognised all my music and didn’t even have to rescan or redo audio analysis. Worked straight away. Thanks for the advice here!
Glad that it worked!
I even added a new disk, that I partitioned, formatted (ext4) and renamed before from a live system with some files, it was also recognized as internal storage. So it seems that it is not necessary that internal storage be initialized by Rock, i.a.w. you can add a disk that contains data.
