NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
ReadyNAS Pro 6 Firmware reinstalled but won't restore config
Hi,
My ReadyNAS Pro 6 stopped responding to network requests and when I rebooted it was in Safe mode, so I booted into the boot menu and reinstalled the firmware. It's running the latest 6.10.8 firmware.
When I try to restore the previous config backup it says its corrupted or the volume names don't match. I don't think the config file is corrupted as I have tried several other config backups and they give the same message.
How do I recover the existing volume and the data?
markbarlow wrote:I have mounted the USB drive and recovered the small number of files that weren't backed up.
Great news.
markbarlow wrote:
Is there a support article on the process?
https://kb.netgear.com/30267/RAIDiator-4-2-USB-Recovery-Tool
Note the prep requires use of a Windows PC. Also note the warning in the article. One thing the warning doesn't say - the NAS can be quite fussy about the USB drive. Generally it works best to use older/smaller flash drives. Using one that has an activity light is often useful, as it gives you some evidence that the drive is being accessed during the process.
Though doing the recovery could save some time, I'd personally just do the factory default.
markbarlow wrote:
How do I rename the OS6 bios file to use with the OS4.2 recovery system?
You can just rename it to match the 4.2.31 firmware before you select it via the recovery tool. (RAIDiator-x86-4.2.31)
Make sure you extract the image from the zip file.
40 Replies
markbarlow wrote:My ReadyNAS Pro 6 stopped responding to network requests and when I rebooted it was in Safe mode, so I booted into the boot menu and reinstalled the firmware.
Did you do an OS reinstall? Or did you do a factory default?
It sounds as if the data volume isn't mounted, so the "names don't match" is because there is no name for the unmounted volume. Do you see a data volume at all in the GUI or RAIDar? I hope you didn't miss a vital step prior to an OS re-install -- backing up your data. The NAS goes into safe mode to protect the data from further corruption when there is a file system error and give you the opportunity to insure your backup is up to date. An OS re-install was unlikely to fix your issue, but it (and especially the re-boot necessary) carry a lot of risk of making the volume unmountable. The usual fix for this is backup, re-initialize the NAS, and restore data.
You may still be able to manually mount the volume if it's not mounted, and StephenB can likely help you do so if you are comfortable with SSH and the Linux command line. He will likely need to see your logs, but don't try to post them here -- he'll tell you how if it comes to that. But it would likely still have errors that are best fixed by backing up the data, re-initializing the NAS, and restoring the data.
I think the first step is to confirm that markbarlow did an OS reinstall, and didn't do a factory reset.
OS Reinstall
Could it be that the config or VPD is corrupted?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
