my RN104 says its firmware 6.10.8 is up to date, even if I search for updates no update ion any kind s available; but I know there is a 6.10.9 release.
Is it safe to upload it on the NAS and manually install it anyway?
Yes, it is safe. Netgear always releases for local installation before putting it on the update server. But this time they are being even slower than usual, likely because most of the folks who supported ReadyNAS no longer do.
Hello, I have the RN214 and tried to do the manual update but I kept getting the "unrecognized server error" when I tried to upload the image. Would you mind walking through the steps you took to manually install?
I tried uploading the arm, and the x86, both as .zips and then just the .img files and every time it immediately failed. Did you instead overwrite the files? Did you install it in a way other than through the admin page settings?
Please find the steps for upgrading or downgrading the Firmware : 1.Download the required firmware image from google browser compatible to your ReadyNAS model. 2.Open the NAS admin UI 3.Navigate to system >> settings >> update 4.Click on Install firmware >> browse the downloaded firmware 5.Click on upload.
Hi, surely I downloaded the file , unzipped it and uploaded it from the admin page; as far as I can remember, I used the .img file. Now I am not home and I can’t tell you more about it. Did you read the .readme file about direct update from older os version?
Hi @NiveditaP3, I suppose your last answer was for @Etarsha and not for me. I got my install successfully about two weeks ago, and anyway I could do nothing now, as I am far from home until the end of this month😀
Hello Nivedita, I'll give that a try, I did follow the steps you previously posted and when I selected the file from the browse, I encountered the "unspecified server error". Hopefully it was just a corrupted download, I will reply after I re-download and try again later today.
And 77Pale77, Thank you for confirming you didn't do anything different. I did read the files attached and since I was installing from 6.10.8 it didn't look like any other upgrades were needed.
@Etarsha wrote: I did follow the steps you previously posted and when I selected the file from the browse, I encountered the "unspecified server error". Hopefully it was just a corrupted download, I will reply after I re-download and try again later today.
If you get that again, try rebooting the NAS. Then see if 6.10.9 ends up installed anyway.
FWIW, it is installed on my RN102, so it should work fine with your RN104.
I tried downloading the ReadyNASOS-6.10.9-arm from the link you provided and I am still having the "unrecognized server error". After a NAS reboot, I tried again the .zip, then the .img and even tried putting them in different locations (c://, d://, on the NAS storage itself) to make sure it wasn't a permissions issue. Still no luck.
I am using the RadyNAS 214, antivirus 02Aug2023 02:34:4 so at least that is getting updated. I have file search enabled, running firmware 6.10.8. Checking for updates results in "Your system does not need a firmware update". The firmware version 6.10.8 appears to be causing issues with my installed apps and now I cannot even upgrade to 6.10.9; any other suggestions?
Plex, it hasn't let me update the app since I updated the firmware. I get an error code 22007100001; which there was another thread about and I tried all of their actions but nothing worked. Everything currently "works" but I am worried how many updates before things start breaking.
Additionally I have tried to manually install an older firmware version (6.10.7-arm) and I tried to reinstall 6.10.8-arm to see if that would do anything, both resulted in the unknown server error. Short of combing through he storage and overwriting files, which I do not want to do, I am at a loss.
Additionally I have tried to manually install an older firmware version (6.10.7-arm) and I tried to reinstall 6.10.8-arm to see if that would do anything, both resulted in the unknown server error.
I am puzzled by this, as I did not see this behavior with my RN102 or my RN202.
You can follow these steps manually and try installing the firmware:
1. copy the image to :/root/ReadyNASOS-6.10.9.img
2. and echo /root/ReadyNASOS-6.10.9.img >/etc/.flash_update 3. then reboot, it should install the 6.10.9
Note this requires ssh to be enabled. If you use these exact steps, then delete /root/ReadyNASOS-6.10.9.img after the reboot. Though you can simplify by just copying the image to /etc/.flash_update
Can you confirm that I have to do this through some form of SSH? Using windows explorer, I see no root folder on my NAS even with unhidden files/folders. Must I copy these files over using the cmd or other console like program (like PuTTy)?
Can you confirm that I have to do this through some form of SSH? Using windows explorer, I see no root folder on my NAS even with unhidden files/folders. Must I copy these files over using the cmd or other console like program (like PuTTy)?
The issue is the automatic and manual updates from the admin page are failing. So I am trying to find another way to force it to complete and hope that fixes whatever is causing the errors. I really do not want to factory reset the NAS since that also wipes the drives.
Can you confirm that I have to do this through some form of SSH? Using windows explorer, I see no root folder on my NAS even with unhidden files/folders. Must I copy these files over using the cmd or other console like program (like PuTTy)?
@Etarsha following the ssh based update process does not magically cure (most or any) update issues.
Start with a cold reboot to clear out the RAM disk based root file system - I understand, you already tried this. Poor deployments of Apps can easily cause many issues, the "wrong" file systems are easily flooded.
When having a root shell access open, check (and post) the output of mount and df (disk free) for further reference. And no, this does not imply there is a risk or a problem in deploying firmware updates.
When having a root shell access open, check (and post) the output of mount and df (disk free) for further reference. And no, this does not imply there is a risk or a problem in deploying firmware updates.
@Etarsha - it is possible that the OS partition is too full to apply the update.
If you don't want to use ssh, you can also check for this by downloading the log zip file from the web ui log page. Open volume.log, and scroll down to the section that starts with === df -h ===
hello from France Version 6.10.9 has been available since May 5, but it is not automatically offered for download/installation. In France we discovered that this new version allowed to unlock two problems: - a ReadyNas 102 blocked in version 6.4.2 and which refused the installation of a 6.10.8 version - a ReadyNas 104 which refused to install applications This version 6.10.9 seems more important than Netgear announces it. So much the better No, the ReadyNas is not dead ... 😉
ReadyNAS 102, 104, and 2120 systems must not be updated directly to 6.10.x from 6.3.x or older firmware. They must first be updated to either 6.2.5 or 6.3.5 then to 6.5.2 and then to 6.10.x.
Some folks have bricked their NAS by not following those instructions.
- a ReadyNas 104 which refused to install applications
The Netgear 6.10.8 repo is broken, and so far Netgear hasn't bothered to fix it. Another aspect is that the Debian 8 ("Jessie") version of Linux used by the ReadyNAS is outdated, and the Debian folks archived its repos. There is an extended discussion here:
The most recent ReadyNAS product was released in 2017, so about 6 years ago.
ReadyNAS products were removed from the main Netgear webpages a while ago, and are only on the support pages. All say "This product/software is end-of-life."
ReadyCloud has been turned off
Firmware updates have been less frequent, and largely limited to security updates
Several folks have complained here about their inability to get support from Netgear (including data recovery contracts).
So I think "dead" is a good description. That said, I have no plans to discontinue using them, as mine are still working well for me.
