NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Can't access shares: NV, v3.01c1-p6 #24713456
Gang,
I'm learning the hard way that backing up files to NAS isn't enough. The good: I already have new equipment on deck to backup my NAS files. The bad: first I have to gain access to them.
Here's my scenario. I've been using the ReadyNAS NV (firmware v3.01c1-p6) for nearly a decade, happily. Several years back, I encountered the dead-power-supply incident many will recall. NetGear made good and sent me a new power supply, free of charge. Everything was beautiful from then until a month ago, when the power supply died again after an electrical storm.
At this late date, the NV is no longer supported. Fair enough. Fortunately, a buddy of mine lent me his power supply, so I have my NV up and running again. It booted nicely, resynced, and the LEDs say everything looks good. Only trouble now is that my shares are no longer accessible ... neither in FrontView nor in Windows (XP) Explorer.
Logging into FrontView alerts the following message:
---
The paths for the shares listed below could not be found. Typically, this occurs when the NAS is unable to access the data volume.
[names of shares]
---
When I view Shares > Share Listing, FrontView says "No shares exist. If you wish to enable file sharing, [...]," yet when I create a new share using the name of a previous share, an alert says "Error: Share already exists. [name of share]" Hrmm. Also, if I add a new backup job in FrontView, the selectbox for "Select backup source" includes my four "missing" shares. Also, viewing my NAS from Windows Explorer successfully shows the names of my shares, but clicking any of them alerts:
---
[name of share] is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. The network name cannot be found.
---
My hope was that creating a backup job would be my sneaky way around the apparent inaccessibility of my shares, because share names do show up as a possible backup source, but no matter what //host/share/path I enter, the "Test connection" button tells me the path is invalid.
After reading previous posts and replies, I'm considering the use of SSH or Telnet, but will apparently have to upgrade my firmware in order to install the plugin that allows root access with the FrontView password. I'm hesitant to go this route without community input.
Is this my best option?
I'm learning the hard way that backing up files to NAS isn't enough. The good: I already have new equipment on deck to backup my NAS files. The bad: first I have to gain access to them.
Here's my scenario. I've been using the ReadyNAS NV (firmware v3.01c1-p6) for nearly a decade, happily. Several years back, I encountered the dead-power-supply incident many will recall. NetGear made good and sent me a new power supply, free of charge. Everything was beautiful from then until a month ago, when the power supply died again after an electrical storm.
At this late date, the NV is no longer supported. Fair enough. Fortunately, a buddy of mine lent me his power supply, so I have my NV up and running again. It booted nicely, resynced, and the LEDs say everything looks good. Only trouble now is that my shares are no longer accessible ... neither in FrontView nor in Windows (XP) Explorer.
Logging into FrontView alerts the following message:
---
The paths for the shares listed below could not be found. Typically, this occurs when the NAS is unable to access the data volume.
[names of shares]
---
When I view Shares > Share Listing, FrontView says "No shares exist. If you wish to enable file sharing, [...]," yet when I create a new share using the name of a previous share, an alert says "Error: Share already exists. [name of share]" Hrmm. Also, if I add a new backup job in FrontView, the selectbox for "Select backup source" includes my four "missing" shares. Also, viewing my NAS from Windows Explorer successfully shows the names of my shares, but clicking any of them alerts:
---
[name of share] is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. The network name cannot be found.
---
My hope was that creating a backup job would be my sneaky way around the apparent inaccessibility of my shares, because share names do show up as a possible backup source, but no matter what //host/share/path I enter, the "Test connection" button tells me the path is invalid.
After reading previous posts and replies, I'm considering the use of SSH or Telnet, but will apparently have to upgrade my firmware in order to install the plugin that allows root access with the FrontView password. I'm hesitant to go this route without community input.
Is this my best option?
8 Replies
Replies have been turned off for this discussion
- Remaining on such old firmware certainly does make troubleshooting difficult when issues like this arise as it does limit the troubleshooting options available. Once an issue like this arises it is too late to update the firmware.
The firmware you are running is over 7 years old. There have been a lot of changes since then.
We introduced tech support mode in RAIDiator 4.
Under Status > Health in Frontview if you click on the SMART+ button what does the health of your disks look like?
I will send you a PM. Check your PM inbox. - Support was able to get your data volume mounted. You should backup your data and update the firmware.
- mdgm, thanks!
In fact, SUPER-big thanks. You did a lot to put my mind at ease--as much as could be hoped--while I was waiting to hear back from support, and even before I opened the ticket.
For anyone else tuned in, I'm pleased (and relieved) to say this story has a happy ending. I opened a ticket at mdgm's recommendation, paid for the standard data recovery assessment, and found that my issue was resolved as a result of that very assessment. For reasons unknown, my data volume was not mounted, which explains why the shares were inaccessible. But that's 100% fixed. I'm currently backing up all my data and will mirror my backup offsite when that's done (approximately another day of data-transfer pending).
In addition, NetGear is sending me a new power supply, no charge. This, in spite of what two other reps told me a month ago, shortly after the electrical storm occurred. The current rep apologized for the previous misinformation.
So I'm on cloud 9 today. - One final twist, as it turns out.
When I last replied on Feb 18, everything was indeed working just fine. I backed up my data, then shut down to install the new power supply. When I rebooted, the data volume was once again unmounted. I opened a new ticket and, fortunately, engineering was once again able to mount the volume. Whew! This time, the remount sticks ... even after I reboot. So all's well that ends well.
The only kink now is that I'm apparently unable to update my firmware. When I initiate a remote update, FrontView thinks about it for nearly a minute, then says "Unable to connect to the update server or retrieve update information." When I initiate a local update, to the latest firmware supported by my machine, FrontView fully loads the file, but then says, "Internal Server Error - The server encountered an internal error or misconfiguration and was unable to complete your request."
Specifically, I'm on v3.01c1-p6, trying to load 4.1.14 (Sparc). So maybe I'm aiming for the wrong file, or maybe I need to step in smaller increments, but I don't see anything other than this link here ...
http://kb.netgear.com/app/answers/detail/a_id/25786
... though the add-ins page references a 4.0 version.
Any takers? - You can reach back to 4.1.9 (http://www.downloads.netgear.com/files/ ... V4.1.9.zip), but I think the older releases have been deleted.
- Remote updates from RAIDiator 3 are broken.
Likely your web browser has some compatibility issues with 3.01c1-p6. - You could install an old version of firefox, and see if that works. https://ftp.mozilla.org/pub/mozilla.org ... /releases/ 2.0.0.1 was current when 3.01c1-pc was released (Dec 2006).
Make sure you remove the browser when done, as there are years of security fixes it is missing. - StephenB, thanks for the insights. As it turns out, mdgm hooked me up, so I'm good to go.
I'll be putting in a good word (again!) when I fill out the survey to my latest ticket.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
