NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RR2304 "Shares" Missing In ReadyNAS Ver 6.10.3 Frontview Admin Page After Unexpected Power Failure
RR2304 (RR230400) "Shares" missing in ReadyNAS (Ver 6.10.3) Frontview Admin Shares Page after an Unexpected Power Failure. (Prior power failure, all "Shares" were there and normal) After the inci...
Thanks for the workaround.
However, Netgear should resolve the inherent OS Frontview Shares bugs problem of Disconnected Shares, which I'm not the only one but many other cases happened already due to various problems.
Mine was coincidentally running normal without any upgrading or migration, except the only power interruption that assumed had caused the "Frontview OS's Shares corrupted/disconnected".
Please note that all my Data in the NAS are still there and after Full Data comparison check against other backup was NOT corrupted, EXCEPT Frontview's Shares Configuration integrity which not always changing seems corrupted, which I have no idea.
So Netgear should fix the Frontview OS problem to include its Shares self-check/rebuilt/system checks.
If the script could repair the configs, then should let the updated Netgear system firmware to have this option instead asking enduser to access SSH, which some enduser not even know how to do that.
In the meanwhile, I could only try study your solution if feasible. Please email me the script and method.
Thank you.
cheajack77 wrote:
... However, Netgear should ...
That's not my call, as I don't work for them.
cheajack77 wrote:
In the meanwhile, I could only try study your solution if feasible. Please email me the script and method.
To be clear, it's not my script - and it's not something I've needed to run. The Netgear mods have sometimes suggested it (and provided the link), and it's resolved the problem in most (if not all) cases. I haven't seen any cases posted here where it has done more damage. But you of course are on your own if you choose to run it.
You can find it here
I have looked at the script, and my conclusion is that running it for the wrong problem could cause more damage than good. It is also set up to provide feedback if it's seeing something unexpected, and getting that feedback out would be another challenge. Thus, I understand why it's not automatic or available for running without first interacting with support or the forum to insure it's the right fix. Building in the smarts to insure it's really the right fix and do so automatically would be quite an undertaking, especially for a failure that is very uncommon (it may seem more common if you look here in the forum only because people with no problems don't post that fact). I initially wondered why it was not available as an add-on instead of a shell script, so SSH is not necessary. But seeing the feedback messages that can be given, I now also understand that.
Your problem does sound like the script is the correct fix, however.
Since you do have access to your data, just not in the typical share organization, you should insure your backups are up to date before using the script in case your situation is one of those that can be made worse by it. If it does get made worse, you can then factory default and restore the data.
Latest workaround restoring SHARES in Frontview without entering SSH.
Following steps:
1. Login the network path of the NAS using admin account (\\RR2304\data)
(Note: the access path to NAS could be your own NAS assigned IP address \\xxx.xxx.xxx.xxx\ or other NAS name instead of \\RR2304\)
2. All related SHARES of folders will be listed there (e.g. \\RR2304\data\media)
(At this point should be able to access all data, recommend backup your data before proceed with following although tested will not affect the existing NAS data with files comparison software).
3. Login the NAS Frontview at SHARE tab page, expecting missing shares like "media".
4. Create new share (e.g. "media2") and setup necessary approriate user access.
5. After confirmed the "media2" share is created by checking at Frontview. (or check the folder path should appear (e.g. \\RR2304\media2))
6. Then at Frontview edit the share setting "media2" and RENAME the "media2" to "media". This will map the new share to old "media" folder with the name "media".
7. Wait for the NAS mapping disk activity finish rebuild share and the new share should be available at "\\RR2304\media".
8. Repeat above steps for the rest of shares. You may create multiple temporary shares all at once in frontview but one after another RENAME mapping disk activity finished rebuilding share to prevent unexpected scenarios (which had not been tested concurrent rename without waiting completed mapping yet).
Hope this workaround solution could help others restoring their shares.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
