NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Web admin doesn't register any changes after 4.2.28 firmware update
Hi all, I have a ReadyNAS Ultra 4 [X-RAID2], and I recently upgraded its firmware to 4.2.28. Now, whenever I access the web admin (e.g., https://192.168.192.12/admin/), none of the options seem t...
4GB root partition was full with Crashplan upgrade installers.
When writes to a full partition are made the written files are corrupted so some config was corrupted and naturally the firmware update couldn't be stored temporarily on the partition so it gave the error about the architecture check failing.
StephenB wrote:
The net is you need to get into tech support mode, either to fix this yourself or have Netgear support fix it remotely.
The other options are
(a) do a factory reset and lose the data
(b) try to mount the disks in another system
Is there another way of getting into tech support mode? I saw murmurs about a USB method?
Adrian
There is a USB recovery method for the flash, but that won't help you (your problem isn't in the flash).
It seems plausible that a USB drive could be set up to boot the NAS into tech support mode, but I've never seen any description on that.
Since my Reset button appears not to work, my only option (aside from taking the disks out and putting them in a new ReadyNAS) seems to be to use an undocumented USB method referenced in this thread: https://community.netgear.com/t5/Using-your-ReadyNAS/Cannot-access-boot-menu-on-ReadyNAS-Ultra-6/m-p/845932/highlight/true#M20471
There, @mdgm says "There is also an undocumented way to use a USB key to trigger boot menu options instead of using the reset button."
Can anybody help me with info on how to trigger the boot menu options via USB?
Adrian
4GB root partition was full with Crashplan upgrade installers.
When writes to a full partition are made the written files are corrupted so some config was corrupted and naturally the firmware update couldn't be stored temporarily on the partition so it gave the error about the architecture check failing.
mdgm wrote:
4GB root partition was full with Crashplan upgrade installers.
The odds of this happening can be greatly reduced if you move the CrashPlan cache to the data volume. All CrashPlan users should make that change.
I suspect you could also symlink the upgrade folder, though I haven't tried that myself.
StephenB wrote:
mdgm wrote:4GB root partition was full with Crashplan upgrade installers.
The odds of this happening can be greatly reduced if you move the CrashPlan cache to the data volume. All CrashPlan users should make that change.
I suspect you could also symlink the upgrade folder, though I haven't tried that myself.
Yes, symlinking the crashplan stuff to the data volume was the first thing I did as soon as I regained SSH access to the ReadyNAS. :-) Appears to be working fine. Thanks for all your help! Much appreciated!
Adrian
An extraction of the OS onto the disks was triggered overwriting some files. You may need to install the glibc add-on again (not sure on that, but it should be obvious if the Crashplan service is running or not).
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
