How to rename USB_HDD_2 - OS6.2.2

Do you have ssh enabled?
Are you comfortable using ssh?

Do you have ssh enabled?

No

Are you comfortable using ssh?

If it works with USB backup drives
I'v only got 1 NAS box.
Edit: it's change to USB_HDD_3 now and I haven't unplugged it or ejected it at all

I would first upgrade to 6.2.4.
If you enable ssh you can ssh in and edit the storage.conf file. This is in /etc/frontview/usb
You will need to use vi and the r command to replace the number of the USB label from 3 to 1
You can also delete any references to other USB drives.
You need to be careful that you don't make any mistakes, perhaps learn about the vi editor first.

http://www.tutorialspoint.com/unix/unix-vi-editor.htm

The USB drive reference number usually only changes if the USB drive has been removed without dismounting properly.

There may also be a problem with the USB drive compatibility that is making it do this.

Did you do anything between the change from 1 to 2 and from 2 to 3?

Editing the USB drive reference may only be a short term fix for your situation if the nas is allocating new drive references spontaneously without any incorrect dismount procedures.

I definitely did not unplug or eject the ext. hdd before it jumped from 2 to 3.
Yeah I've just updated to 6.2.4.
Thank you vandermerwe for the info. I'll give it a shot with the editing.

Just something a bit off-topic but do you recommend enabling "Allow snapshot access".
On one hand its good to have rollback of files/folders in a few clicks but on the other hand
the structure of the snapshot folders lends itself to becoming infected by a ransomware easily and all your snapshots are damaged.

Allow snapshot access allows you to browse snapshots using a browser, rather than from within the admin interface. The snapshots reside within the share if you select this, whereas if you don't they are not.

If you are using snapshots as a fail safe, then access should not be required, I would suggest not allowing snapshot access.

I don't think it's any easier to restore a file or folder from a snapshot if snapshot access is on. It is going to be a rare event and doing it via the admin interface is simple.

"restore previous versions" from windows explorer either (a) needs admin access to the NAS or (b) needs "allow snapshot access" to be on.

So with windows it can be a bit easier to restore a file or folder with it on.

On my NAS it is set to off, but I use admin credentials to access the NAS from all our family PCs.

teo2710, if you decide to rename the USB reference I would dismount the USB drive first then remount it once you have renamed the reference.

You could also ask support of course, particularly if if it recurs.

Thanks guys for the help. Sorry I'm a bit of a noob with the ReadyNAS boxes.
I managed to clear the data stored in the storage.conf file via SSH thanks to another thread I found on the forum.
All is good now - it's back to USB_HDD_1.

"restore previous versions" from windows explorer either (a) needs admin access to the NAS or (b) needs "allow snapshot access" to be on.

I'm a bit concerned with the "Allow Snapshot Access" method that a cryptolocker-type malware could run through the Snapshots folder and damage all the "snapshots"
since it's just a normal folder with different "versions" of that shared folder.

With the other method, the only way to access snapshots is via the ReadyNAS Admin Page?
What hidden folder is it under?
Will a rsync backup copy all the snapshots if the source is set to \data?

Thanks

I forget the exact path for the snapshots (and am away from my system right now).

-You can still access the snapshots with windows file explorer using admin credentials for the NAS.
-If you are using automatic snapshots, you don't want to try to using rsync to back them up, since they generally won't fit on a USB drive. If the main share is 100 GB, then each snapshot takes 100 GB on the USB drive.

You can still access the snapshots with windows file explorer using admin credentials for the NAS.

Can you show me how?
Just to clarify, I am NOT using the "Allow Snapshots Access" method where a snapshot subfolder is created.