NUC Rock cannot see second USB drive to transfer but is using it for Roon playback?

Roon is using the folder(s) under the 4T USB drive to play but the Win 11 system only finds the 64M USB drive that I used to transfer/reinstall/upgrade when setting up a network location?

Please advise, and thanks,

Martin Booker

Where are you looking to find the drive?
Here are few KB articles to read:

Also, when looking at the network share (\\rock\data) You should see a “storage” directory. All drives connected to the NUC (not the OS drive) will be under this directory.
It “should” look something like this:

The “InternalStorage” would be the the drive that you might have installed for your music files (not the OS drive).
Any USB drive would show up like what my back-up thumb drive is showing (some long arbitrary name and “USB” somewhere in the name). Don’t change the name as this will screw things up for ROCK.

1 Like

Thanks for the links. My first post contained incorrect information. Although the 4T USB drive is powered up and was previously working it is now not seen by the NUC running Rock (meaning could be hardware). It is interesting though that the 64G drive USB, which was used to transfer the Roon account information, is the drive it sees and defaulted to in Roon Storage. \rock\data only shows this drive. There are no music files on the NUC internal drive.

Speculation:
There was an update recently that occurred that may be traced back to the day the 4T drive stopped working (highly unlikely)? Any tools that can be used on the Rock to check drive status (terminal screen, etc.)? I will try to reboot the Rock with the 64G out and see if the Roon database(?) made it to the internal drive of the NUC. Then attach just the 4T and see if it finds it. Asking to add a folder in Roon only finds the 64G heading.

Other options appreciated,
Martin Booker

There have been issues with USB drives not being read correctly by Nucleus/ROCK devices due to not being “ejected” after having been connected to a windows machine. have you had the 4T drive connected a windows machines lately?

You might try connecting to a Windows machine and then “ejecting” it before disconnecting it.
You might need to run a scan of the disk to fix errors, also?

That should fix it , this is normally down to incorrect removal. Just run and thenunmount properly.

If all else fails it may need re-formatting as ex-FAT . Mine is NTFS but has been put in once and never removed since.

Don’t forget that re-formatting will wipe the disc !!

Turns out the original 4T drive must have gone bad. Tried two other USB T drives and Rock immediately saw them both. I have rebooted, and pointed to the new T drive. After several hours the 6k worth of albums etc., have been found on both a Mac and iPad client. But a reinstallation of the mpg codec (\Rock\Data\Codecs )and a reboot now gives me the loading library error.

Options are another reboot or restore backup. Read the posts on how to fix this but I probably don’t yet have a backup because it is all new? Or will just renaming the RoonServer to ‘old’ and a reboot fix it. Also a little confused about a ‘power’ reboot (the red button) versus a Roon Server ‘restart’ versus a Roon Database ‘reset’.

Thanks,
Martin Booker

Answering the last part first :slight_smile:

Reboot does:

  • Shutdown the Roon Server Application
  • Shutdown the Operating System (RoonOS in this case)
  • Reboot the Operating System
  • Restart the Roon Server Application

Roon Server Restart does the first and last of these only. i.e.

  • Shutdown the Roon Server Application
  • Restart the Roon Server Application

On the first point, if necessary, can you use a web browser to navigate to http://rock, then you should be able to reset the database from there (image copied from Roon Help Centre because I don’t run ROCK any more):

You can then restore a database. If restoring the database results in the same issue, then you likely have a corrupted backup or more likely, a backup of a corrupted database. If you have historic backups, you could try restoring an older backup and see if that works.