Possible to rename USB attached drive?

[Untried3868]

Using a SATA drive in a Ugreen enclosure. I was wondering if it's possible to rename that drive without reformatting and setting all the scripts up again?

I tried searching (advanced search) SNBF but no results. Searched AMTM options as well with no luck.

TIA

 

[sfx2000]

The share name is important, not the drive name...

usually defined in smb.conf

 

[ColinTaylor]

Using a SATA drive in a Ugreen enclosure. I was wondering if it's possible to rename that drive without reformatting and setting all the scripts up again?

I tried searching (advanced search) SNBF but no results. Searched AMTM options as well with no luck.

TIA

Which specific "name" are you referring to? There are various names related to a USB drive depending on what you're looking at. Can you give an example of the name you want to change?

 

[Untried3868]

Which specific "name" are you referring to? There are various names related to a USB drive depending on what you're looking at. Can you give an example of the name you want to change?

When I initially setup the drive, using FD command in AMTM, it asks (highly recommends) to provide a name for said drive. This is the name I'd like to change. For example, if I named it Ugreen (originally) and would like to change it to something like Ugreen-01.

 

[ColinTaylor]

When I initially setup the drive, using FD command in AMTM, it asks (highly recommends) to provide a name for said drive. This is the name I'd like to change. For example, if I named it Ugreen (originally) and would like to change it to something like Ugreen-01.

OK, So that's a volume (or filesystem) label, rather than a disk name.

It is possible to change the volume label. The exact command varies depending on which filesystem type was used to create it. e.g. NTFS, ext4, etc.

Whether your third party scripts could cope with the name change I couldn't say. That's down to how each individual script has been written. For example, if a script uses an explicit path like /mnt/Ugreen/Data/ and you change the volume name as you propose the new path would be /mnt/Ugreen-01/Data/. So that script might not be able to find its data.

 

[Untried3868]

OK, So that's a volume (or filesystem) label, rather than a disk name.

It is possible to change the volume label. The exact command varies depending on which filesystem type was used to create it. e.g. NTFS, ext4, etc.

Whether your third party scripts could cope with the name change I couldn't say. That's down to how each individual script has been written. For example, if a script uses an explicit path like /mnt/Ugreen/Data/ and you change the volume name as you propose the new path would be /mnt/Ugreen-01/Data/. So that script might not be able to find its data.

I called it "disk name" instead of "volume label" due to my old MS indoctrinated brain still trying to learn Linux/Unix terminology.

I guess I'm off to use FD and build from scratch rather than risk breaking scripts.

Thank you.