NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
rgm60527
Jan 03, 2014Aspirant
Share wierdness with share named data
I am moving from a ultra plus (or at least I was) and I had three shares backup, data and media. In the ReadyNAS 312 running 6.1.5 when I create the shares that I want all seems well. Well that is u...
beisser1
Jan 03, 2014Tutor
this was just a test.
another workaround would be to delete the volume on the new nas and create a new volume with a different name (data is just the default name used for the first volume).
if you create a new volume you can use whatever name you like and keep using a share named data.
this wouldnt have happened if there was a mechanism telling you that you cannot use a share with the same name as the volume.
unfortunately this is not the case and you should inform support, so that they can open a feature request for this.
you would get the exact same type of issues if you had a share named "c" on the older readynas models since the default volumename there is "c".
so for you as a short term solution use any of the provided workarounds and as a long-term solution please contact support and have them add a feature request to put in a mechanism that prevents that kind of thing in a future firmware.
another workaround would be to delete the volume on the new nas and create a new volume with a different name (data is just the default name used for the first volume).
if you create a new volume you can use whatever name you like and keep using a share named data.
this wouldnt have happened if there was a mechanism telling you that you cannot use a share with the same name as the volume.
unfortunately this is not the case and you should inform support, so that they can open a feature request for this.
you would get the exact same type of issues if you had a share named "c" on the older readynas models since the default volumename there is "c".
so for you as a short term solution use any of the provided workarounds and as a long-term solution please contact support and have them add a feature request to put in a mechanism that prevents that kind of thing in a future firmware.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!