- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Readynas nv+ v2 - The paths for the shares listed below could not be found.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Readynas nv+ v2 - The paths for the shares listed below could not be found.
getting error Readynas nv+ v2 - The paths for the shares listed below could not be found., when doing a scan, comes back scan is fine, however it will not show any volume
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Readynas nv+ v2 - The paths for the shares listed below could not be found.
What firmware is the NAS running? Did you try downloading the logs?
Unfortunately, the data probably has been lost (though we don't know why at this point). Do you have a backup of the data?
Netgear does offer a data recovery service, and there is a chance that paid support (my.netgear.com) could remount the array w/o needing full recovery.
Some folks have had success with a software package called ReclaiMe. Either way, data recovery is expensive, and of course it might not be possible to recovery anything.
If you want to try Netgear support or a data recovery tool, then it is important not to let any additional data be stored on the NAS. Also, if you try things on your own, you risk doing more damage.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Readynas nv+ v2 - The paths for the shares listed below could not be found.
Firmware: RAIDiator 4.1.16 [1.00a043]
downloaded the logs,
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Readynas nv+ v2 - The paths for the shares listed below could not be found.
For the record, you have a v1. A v2 system runs OS 5.3.x, not OS 4.1.16. The labels on the back can be confusing; the definitive labels we need here are on the front.
System.log can be overwhelming, but you could look in there and see if there are any errors reported with the volume or disks.