NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Could not properly extract after update to 6.10.5
I tried to install the latest firmware update for my ReadyNAS, 6.10.5, and on the system reboot I get the error that it could not properly extract. I've tried creating a recovery USB with the latest ...
It sounds like the OS image in flash is corrupt. A USB recovery should fix that, but I'm not sure you successfully went through that complete process.
Did you follow these steps?
- If your ReadyNAS system is an RN420, RN520, or RN620 series:
- After powering on the ReadyNAS system, wait for the backlight on the navigational buttons to turn off.
- Instead of the Backup button, press and hold the OK button (the center of the navigational buttons) for up to 30 seconds, until the LCD confirms that the ReadyNAS is attempting to boot from the USB drive.
- If your ReadyNAS system has an LCD, the LCD confirms that the ReadyNAS is in USB Recovery mode.
If you tried this and didn't see it updating, make sure you follow all the steps for creating the recovery USB. Many users find that running the creation tool with admin rights also helps. I know other models of ReadyNAS can be finicky about the actual USB drive, so try more than one. It's also best if you use one with an access LED so you can see it's actually doing something from it when you boot, though that's more important on units without a LCD panel.
It's not necessarily corrupt firmware on the internal flash. Other possible causes include a fairly full 4GB root volume (insufficient space to extract) or user changes via SSH interfering with the extraction of the firmware onto the disks.
I would have thought it should have attempted to automatically boot off the USB key, but if that doesn't happen pressing the O.K. button at the right time is worth a try.
USB Boot Recovery will only help if the problem is corrupt firmware on the internal flash.
Booting from a USB recovery doesn't help. Interestingly enough, the unit will boot into the new firmware if none of the disks are connected, so the actual flash should be in good stead.
As additional troubleshooting steps, I tried running the memory and disk tests from the device, and no issues were found in either instance.
There may be something with the SSH suggestion: I did add a TLS certificate from my company's internal CA and made one of the frontview config files immutable as part of the process to prevent a firmware update from changing it, and it hasn't been an issue in the past.
I'm going to try booting into tech support mode to see if I can at least see some portion of the file system to see if there are any space issues.
rthonpm wrote:There may be something with the SSH suggestion: I did add a TLS certificate from my company's internal CA and made one of the frontview config files immutable as part of the process to prevent a firmware update from changing it
It should be easy for you to verify if that is the problem.
Extracting the OS files onto the root volume manually can also identify if it can't replace a file/folder.
There can also be things like a file put where the system expects a folder or vice versa.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
