The paths for the shares listed below could not be found.

[cmcnamee]

I've got a ReadNAS NV in a RAID 5 configuration. I deleted a share and didn't wait until the delete was completed and recreated the a share with the same name. After the original delete was completed, I now get the following error: "The paths for the shares listed below could not be found. Typically, this occurs when the NAS is unable to access the data volume. Offsite_Backups"

The share is not listed in the shares list, and I constantly get the error. Anyone have any thoughts on how I can fix this?

Thanks!

[ewok]

Try connecting to the share as admin, going to the C folder and creating a folder by the same name.

[cmcnamee]

When I connect to "\\nasipaddress\c" as the admin account and try to create a new folder, I get the error "Unable to create the folder. Access Denied."

[ewok]

Which security mode are you using? Try creating a file in one of the shares as admin and seeing who the file is owned by.

[cmcnamee]

I am using the "User" security mode and the owner of the file I just created in one of the shares is "admin (NAS\admin)."

[ewok]

Are you able to create anything in C or is it just this particular folder that gives you the error message?

[cmcnamee]

I can't create anythin in the "\\nasipaddress\c" folder. I just get the "Access Denied" error and I am connected to the UNC with the admin account.

[ewok]

Hmm, I'm not sure how your NAS got into this state, but the admin should be able to write to the C volume. If you'd like to make your NAS available, I can debug it remotely, otherwise I can have one of our guys try to reproduce it here. Let me know how you'd like to proceed.

[cmcnamee]

Thanks for the offiver, but we have some very strickt network policies and I cannot make it availalbe to internet. All I did to get this NAS box in this situation was I deleted a share and didn't wait until the delete was completed and recreated the a share with the same name.

Do you think restoring the NAS to factory defaults would fix the issue?

[DivideByZero]

I have the EXACT same problem. I created a share...decided to delete it...and impatiently recreated it. Now the share is visible through CIFS, but I can't access it and it isn't listed in RAIDar.

Now I get the exact same error as the other gentlemen (Listed Below)

The paths for the shares listed below could not be found. Typically, this occurs when the NAS is unable to access the data volume.
[Sat Sep 6 16:28:13 PDT 2008]

How do I get rid of it?

[ewok]

cmcnamee wrote:
Thanks for the offiver, but we have some very strickt network policies and I cannot make it availalbe to internet. All I did to get this NAS box in this situation was I deleted a share and didn't wait until the delete was completed and recreated the a share with the same name. Do you think restoring the NAS to factory defaults would fix the issue?

A factory default would fix it, but would wipe out all of your data. An OS reinstall might do the trick though:

faq.php#How_do_I_re-install_the_firmware%3F

[cmcnamee]

I got my issue fixed, I installed the ToggleSSH and EnableRootSSH add-ons and then ssh'd into my NAS and manually created the missing share. I then rebooted my NAS and then removed the share through the web interface and my NAS is happy again!

[ghotz]

cmcnamee wrote:
I got my issue fixed, I installed the ToggleSSH and EnableRootSSH add-ons and then ssh'd into my NAS and manually created the missing share. I then rebooted my NAS and then removed the share through the web interface and my NAS is happy again!

Hello, I have the same problem and I have the SSH add-ons installed but I'm not familiar with the procedure to manually create the shares. Can you post the commands please?

[cmcnamee]

All you need to do is SSH into your NAS box and then do the following:

• Login as 'root' using the password of your NAS's 'admin' account


• Type 'cd /' to change into the root directory


• Type 'mkdir YOURSHARENAME' replaching 'YOURSHARENAME' with the name of the share that is missing


• Type 'logout' to logout of our NAS box

Now your missing share is restored and you should no longer receive the error messages. You can now go and try to delete the share through the web interface.

Hope this helps!

[ghotz]

cmcnamee wrote:

All you need to do is SSH into your NAS box and then do the following: Login as 'root' using the password of your NAS's 'admin' account Type 'cd /' to change into the root directory Type 'mkdir YOURSHARENAME' replaching 'YOURSHARENAME' with the name of the share that is missing Type 'logout' to logout of our NAS box Now your missing share is restored and you should no longer receive the error messages. You can now go and try to delete the share through the web interface.

Sorry I realized I never answered back to this 🙂

I tried, but it doesn't work. The directories are correctly created in root (where I can see also the other shared directories) but they don't show up in the "Share List" on the NAS web interface so it's not possible to delete them from there.

[rt1]

I tried, but it doesn't work. The directories are correctly created in root (where I can see also the other shared directories) but they don't show up in the "Share List" on the NAS web interface so it's not possible to delete them from there.

I had a similar problem where just recreating (or deleting) the directory through SSH did not fix the error message. Trying to create a share with the same name resulted in an error that the share already existed. The answer for me was in the configuration file, which had references to the missing share regardless of the true state of the directory tree. After confirming through SSH that a directory relating to the missing share did not exist on the drive, I reverted back to a configuration file that pre-dated my cock-up with the missing share.

It isn't an ideal solution if you haven't backed up your configuration recently (or at all), but it might save a full reset/wipe. Reverting to an earlier configuration file also affects your add-ons (for example, if you didn't have ToggleSSH installed when you backed up the configuration, you'll have to reinstall it after you revert).

Hope this helps.

[tsubasa99tsubas]

I am having a very similar issue with my ReadyNas Pro. you mentioned :

"The answer for me was in the configuration file, which had references to the missing share regardless of the true state of the directory tree. After confirming through SSH that a directory relating to the missing share did not exist on the drive, I reverted back to a configuration file that pre-dated my cock-up with the missing share."

Where is this configuration file located? Presumably FrontView is a bit confused...would like to just edit the file and remove the reference considering I have already deleted the user and the associated folders.....

[tsubasa99tsubas]

I think I may have figured out the problem with the missing shares, it stems from a mismatch between the file systems actual contents and what the Samba server shares config file states. It can be resolved by editing the "Shares.conf" file.

Here is my take on a "How-to" to fix the problem :

DISCLAIMER :

Exercise caution, I don't take any responsibility for your messed up ReadyNas. If you are concerned that you don't understand the "how-to", seek out help from a qualified professional.

ISSUE :

An error is shown the the ReadyNas log file stating :

"The paths for the shares listed below could not be found. Typically, this occurs when the ReadyNAS is unable to access the data volume. my_missing_user"

There is no user for "my_missing_user" listed under Frontview.
There is no home directory for "my_missing_user" showing under HOME or /.
There is no information showing in FrontView (Shares --> Share Listing) for Shares.
Frontview will not allow you to create a new share as user my_missing_user already exists.

RESOLUTION :

1. Install the SSH addon (if you dont have it already) for your ReadyNAS.

2. SSH into the ReadyNas as root "ssh root@192.168.X.X" where 192.168.X.X is your ReadyNAS IP address.

3. Change to the etc/frontview/samba directory "cd /etc/frontview/samba"

4. Backup the file "Shares.conf" by issuing the command "cp Shares.conf Shares.backup".

5. Look at the contents of "Shares.conf" by issuing the command "cat Shares.conf"

6. Look for entries that have your missing user share name as identified in the FrontView log file (i.e. my_missing_user). My Shares.conf file looked like the following :

[some_other_user]
...

[my_missing_user]
path = /c/my_missing_user
comment = "my_missing_user's Files"
oplocks = 1
admin users = "admin","Administrator"
hosts allow = "my_missing_user"
writeable = 1[/color]

[some_other_user]
...

7. Edit Shares.conf with vi "vi Shares.conf" and cursor down to the offending entry (in my case "my_missing_user").

8. Delete each line from the first bracket until the first empty line. (using the "dd" command in VI) (i.e. delete everything in purple)


[some_other_user]
...

[my_missing_user]
path = /c/my_missing_user
comment = "my_missing_user's Files"
oplocks = 1
admin users = "admin","Administrator"
hosts allow = "my_missing_user"
writeable = 1


[some_other_user]
...

9. Save the file ":wq"

10. Login to your ReadyNas view the Frontview web interface and reboot your ReadyNas.

11. Check your ReadyNas Frontview Log, problem should be gone!

12. Ensure that you have disabled SSH access via the ReadyNas Addon.

I hope this helps others that have suffered from the same problem. If you have any strange issues with Samba you can copy your backup file "cp Shares.backup Shares.conf" back to the original Shares.conf and you should be back to normal after a reboot.

Good luck!

[sanchrts]

Thanks very much for posting this solution.

I have to say however that as a user who craves reliability (and pays for it through my use of Netgear as opposed to cheaper products) and doesn't have the expertise (or time) to hack a NAS that's marketed at the SoHo market, this is a very disappointing problem to have.

I have had this issue on my Duo and also have an issue with shares that I believed I had deleted 'coming back from the grave' and also shares only being accessible via SMB/CIFS and not via AFP (see this thread).

Raf

[tsubasa99tsubas]

Raf,

I agree with you comment. They may need to tighten up their code a bit to catch these phantom shares. It would be simple enough to handle via an addon to compare the user list on the NAS with the Samba.conf config file for missing entries. Perhaps tech support will see this and address the issue.

Best luck with your ReadyNas.

[luckmca1]

Hi peepz!

Model of ReadyNAS: RNDX4000

I've the same trouble here... but a little more complicated... i can't access all shares, include Media and Backup folders.

I've already tried to do the steps listed above, but couldn't resolve...

The NAS have many important and confidential data of company, and if the data lose, i'll lose my job too...

HELP!

[StephenB]

you should start a new thread, rather than resume one that is 3 years old. Include the NAS firmware version, and also the security mode you are using.