NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Shares Gone 2120v2
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/Share...
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 directoryYou'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.
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
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 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
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.
I also not experienced it before. However when searching on the internet it seems that more people encountered this issue.
---
John
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
