Shares Gone 2120v2

[John245]

@Marc_V 

In the 4th comment of this post it was mentioned that a script is available to solve the issues of shares that are gone.

https://community.netgear.com/t5/New-ReadyNAS-Users-General/Shares-gone/m-p/1825296#M38777

If I SSH into the system I see this and my shares/folders are in TEAPHOMENAS01_DATA. Will this script help. How can I get my shares vissible?

---

John

[StephenB · Accepted solution]

---

@John245 wrote:

root@TEAPHOMENAS01:~# root@readynasos:#/ curl -s https://gitlab.codycook.us/readynas-scripts/share_lun_ui_fix.sh/raw/master/share_lun_ui_fix.sh | bash
-bash: root@readynasos:#/: No such file or directory

---

You're supposed to just enter this bit:

curl -s https://gitlab.codycook.us/readynas-scripts/share_lun_ui_fix.sh/raw/master/share_lun_ui_fix.sh | bash

The root@readynasos:#/ preamble was just representative of the normal Linux CLI prompt.

Did you use df to check the fullness of the root partition?  You really should do that before running the script.

Also, as the web page notes, you need to be running 6.10.0 or later firmware.

[StephenB]

What firmware are you running?

---

@John245 wrote:

. How can I get my shares visible?

---

One option is to used paid technical support via my.netgear.com.  The mods ( @JohnCM_S and @Marc_V ) can facilitate that.  Ask if you can get per-incident support.

If you want to pursue this yourself:

1. It'd be good to first check if the root partition is full with df, as that can damage configuration files.  The root partition is only 4 GB. Normally it's about 25% full. 
2. If you can download the full log zip file from the web ui Logs tab, then you could also look in there to get more information on what went wrong.
3. There is a script you could try here: https://gitlab.codycook.us/readynas-scripts/share_lun_ui_fix.sh

[John245]

Thanks for the suggestions. But acces to root is denied. And running the script will tell that the filename directory is missing.

---

John

[StephenB]

---

@John245 wrote:

Thanks for the suggestions. But acces to root is denied.

---

is SSH enabled?  If so, connect with ssh using root as the username and the NAS admin password.  The script also needs to be run as root.

[John245]

Ok, So I logged in wit username root and the NAS admin password. I have access to the root folder, which is empty.

Script including result will look teh following:
root@TEAPHOMENAS01:~# root@readynasos:#/ curl -s https://gitlab.codycook.us/readynas-scripts/share_lun_ui_fix.sh/raw/master/share_lun_ui_fix.sh | bash
-bash: root@readynasos:#/: No such file or directory

---

John

[StephenB · Accepted solution]

---

@John245 wrote:

root@TEAPHOMENAS01:~# root@readynasos:#/ curl -s https://gitlab.codycook.us/readynas-scripts/share_lun_ui_fix.sh/raw/master/share_lun_ui_fix.sh | bash
-bash: root@readynasos:#/: No such file or directory

---

You're supposed to just enter this bit:

curl -s https://gitlab.codycook.us/readynas-scripts/share_lun_ui_fix.sh/raw/master/share_lun_ui_fix.sh | bash

The root@readynasos:#/ preamble was just representative of the normal Linux CLI prompt.

Did you use df to check the fullness of the root partition?  You really should do that before running the script.

Also, as the web page notes, you need to be running 6.10.0 or later firmware.

[John245]

@StephenB Thanks a lot for your help, much appreciated.

The issue is solved. But the question is ofcourse how to prevent this in the future.

---

John

[StephenB]

---

@John245 wrote:

The issue is solved. But the question is ofcourse how to prevent this in the future.

---

I'm glad it's fixed.

Not sure how to prevent it (and of course we don't know what damaged the NAS configuration files).  It's not something I've experienced on my own ReadyNAS.

[John245]

I also not experienced it before. However when searching on the internet it seems that more people encountered this issue.

---

John

[StephenB]

---

@John245 wrote:

I also not experienced it before. However when searching on the internet it seems that more people encountered this issue.

---

The usual cause is a full root partition, combined with change in the configuration from the web ui. The change fails because there's no place to write the updated config.  So you end up with with missing config files.

But we don't have evidence that points to a full root partition in your case.