What’s happening?
· Something else
How can we help?
· None of the above
Other options
· Other
Describe the issue
Installing new SATA SSD Roon core won't recognise disc
Describe your network setup
Roon Rock running on a pc. Network cable to router.
Roon library was corrupt. Suspected failed SATA SSD. Removed suspect disc, installed new one. This drive had the library on it. On relaunch, Roon still asks me to restore a backup. Can’t get past that screen. I can’t see the new drive through a network link. I can’t therefore reinstall the music files. I don’t want to run a restore without the music files on the new disc. Do I need to format the new disc? If so, how do I do that?
If I understand you correctly I would purchase a SATA SSD adapter for USB-C.
One for USB may have come with your replacement SSD. Per Roon documentation:
“ ROCK will also work with NTFS ,FAT32, and EXT2/3/4 drives, but if you are starting fresh with USB storage, our recommendation would be to use exFAT.”
This would allow you to format the drive using a separate computer. It sounds like your new SSD may have been formatted for Mac possibly you can check the packaging.
Considering that you have said that your music files are on the corrupt SSD you can then later use that SSD connected via the adapter to a new machine in an attempt to restore your music collection.
If you can’t seem to recover your music collection via Windows or Mac I wouldn’t give up until I’ve tried Linux. I hope I’ve interpreted your post correctly.
For ROCK internal storage:
For “There was an issue loading your database” you likely replaced the wrong drive (because it is not related to the drive that holds your music files):
1 Like
Hi Singleton
Thanks for the suggestions. To be clear, it is a replacement internal SATA SSD drive that I have fitted, and I couldn’t get past the error screen on Roon Remote that simply said 'There was an error loading your library. The only option available was to restore a backup, which obviously never worked. However, it turns out you can access the Web UI once you’ve tried to do a backup (there’s a link at the bottom of the screen before you select your server). I have now been able to format the drive using Roon’s Web UI, now I can see it on the network, and I am reloading my music to the new drive (I had a backup copy of my music files on my desktop computer, thankfully). It will take many hours to transfer the files. Whether the old backups will eventually work or not is anyone’s guess. Time will tell…
1 Like
@Vaughan_Barnacle ‘
Great to hear. Hoping for the best
Thank you for your post.
Traces in diagnostics from your earlier attempt indicate that RoonOS skipped this storage drive because it was formatted incorrectly as a removable USB drive. The reformat via WeBUI should resolve this issue, but keep us posted and we’re here to assist.
So, I’m still getting the same issue. I have deleted and then rebuilt my database from scratch - rescanned every music file. Then restored from a backup. Roon core still throws up the same error every time it tries to do a new backup. It looks like the SSD wasn’t the issue here. I think maybe the RAM is struggling when Rock tries to snapshot the database. I don’t think the database is corrupt as all albums, playlists etc appear as normal, and play normally. Do I now replace the RAM? I’m getting a little tired of throwing good money away on new parts just because Roon Rock can’t diagnose faulty hardware.
I’m sorry, but what exactly are you trying to do here? Make a backup and store it onto an internal SSD?
If so, then whether you are trying to use the m.2 SSD or the second internal 2.5" SSD, then this won’t work. You have to put a Roon Backup on a USB-attached drive, a NAS location or Dropbox.
Hi Geoff. No, I have a usb attached thumb drive which has been used as my backup media for years with no trouble. Now, every time Roon tries to do a backup, it fails at the snapshotting of the database phase and says that there is a problem with my database and that I should restore a backup. Except if I reboot, all is well (until the next backup is attempted). The history on this thread explains…
I should add, I have tried both a new SSD and a new thumb drive. To no avail.
And when you tried the new (USB-attached?) SSD or the thumb drive, you did first set up a new backup location on these drives, because your originally defined location would no longer be valid?
Please first define an entirely new Backup location per @Geoff_Coupe’s suggestion above.
It’s my understanding from your earlier posts here that you have other, older Backups available on your USB-drive Backup location that was previously functioning as your main automatic Backup location.
It’s worth restoring a Backup from before the drive failed - if there is latent corruption in this database, it will further corode the database over time.
Yes, when using a new usb drive, I did define it as my new backup location. And to be clear, I don’t think the drive failed. I have installed a new SSD drive, completely installed my entire music library again from scratch, then restored. All works fine until I try to backup again, when it fails at the snapshotting phase. And I thought that Roon could no longer make a backup of a corrupted database? Wasn’t that one of the improvements a few years back?
Hi again Vaughan, What version of macOS are you running? Sorry but there is a lot of detail left out that may provide some clues. Can you please explain this statement:
By what method did you attempt to accomplish this? Can you walk me through just a bit.
What is the path to your directories or your attempted paths? i.e. \computer\user\vaughan\music\roonbox
Screenshots can be forwarded of these and or anything which you believe may be helpful.
Hi Singleton. The issue with not being able to see the drive was just because I couldn’t find a way past the error message screen on Roon. Once I discovered how to do that, I was able to instal the new SSD and I have also put in a new usb thumb drive as a backup location. All correctly mapped and operational - no issues there. The only remaining issue is the original one: Roon is still throwing up the same error message when it attempts a backup. It fails early doors (within about 8-10 seconds of starting that process - at the database snapshotting stage). In answer to your query about my system: no MacOS. I’m running Roon Rock on an NUC, directly linked to my router, which means I access the machine via my desktop PC or phone via wi-fi. I’m tempted to try changing the RAM in the NUC in case that has failed, now that I know it isn’t the SSD. It’s just painful to waste money on trial and error troubleshooting.
Thanks again for answering my questions Vaughan. I know that this is beyond irritating. Sorry I was working on a few matters concerning Macs and was confused yes of course your running Rock. I could be wrong but I would hold off on any consideration of RAM for a bit. I think we’ve all been overlooking something. It’s rather easy to do when a computer isn’t right in front of you.
How are the external drives being formatted? On what kind of machine and under what format? Your Rock installation. One consideration I would have would be to reinstall Rock using a fresh download on a different installer. Re-installing software and your music library certainly aren’t fun but given the choice starting over is sometimes the worthier option. I always recommend giving consideration to the best way to spend my time. Either spending hours, days or weeks attempting to find a solution or just 2 to 3 hours just starting over. Just food for thought for you. I don’t think that’s the case here not yet at least. Speaking for myself, I and I’m sure other support volunteers just love solving puzzles and assisting the Roon support team.
If you can go the extra mile and upload screenshots from your phone regarding the step by step process that you’re taking before it ends during the backup process. You certainly appear to be capable. Which is another reason why I believe that we are all overlooking something anyway I could be wrong.
Another thing how large is that library of your’s. I don’t think that’s the issue “but” I’m wondering if you could examine all of your media files. Please search for any files which you may have transferred that are not compatible to Roon. Just throwing a few things out there while I’m scratching my head. Anyway, if your inclined to please share photos of your mapping etc not because anyone doubts you but because were all looking for the slightest bit of something out of order.
This is a known issue , when you start a “forced backup” you get an error saying can’t see server ?
Leave it alone for 10-20 mins (DO NOT restart the server) and it will come back.
The remote sends a command to the server which kicks off the BU , after that you don’t need the remote , the sever does all that work . Support are currently investigating .
@Mike_O_Neill is correct in their statement above - let us know if you’re able to eventually get a successful backup by leaving things alone for a little while! 
I must admit, I am suspecting a Roon issue here. The issue is at the snapshotting phase, though (only takes about 10 secs for the error message to pop up). It’s happening on regular and forced backups equally. It’s not a case of leaving it to sort itself out: it goes wrong almost straightaway. But looking at similar support posts from other users, it’s not likely to be a hardware issue. One user found that the snapshot couldn’t cope with a user-added jpeg for an album cover. I guess I’ll keep using Roon without being able to do any backups, and just hope Roon sorts it eventually. Worrying, though.