NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Installation & Upgrade
5098 TopicsFirmware Downloads
FYI here's a little script that downloads all available firmware versions starting with v6.0.0. It'll be good to keep them on hand for the day that they go away online. Unfortunately, however, some of the early incremental versions are no longer published, making updating for some impossible, depending on their device and what OS version they're running. For example, from the ReadMe for v6.5.2-arm: ReadyNAS 102, 104, and 2120 must not be updated directly from 6.3.0 - 6.3.4 to 6.5.2. They must first be updated to 6.3.5. There is no download available for v6.3.5, so a 102 user on OS v6.3.4 is stuck. That is, unless someone knows of a different (official/reliable) repository. If you do, let me know and I'll update the script. This starts at v6.0.0 and proceeds through v6.10.10, downloading both arm and x86_64 architectures to separate folders. It counts 0-19 for the minor.build numbers, just to be safe. That ought to cover just about everything. The only thing you should need to adjust is the base target folder for your downloads. Let me know if you run into problems. So, without further ado: # ______________________________________________________________ # # A script to download ReadyNAS firmware updates # ______________________________________________________________ # # Define path/folder pairs as tuples $Pairs = @( @{ Path = "100"; Arch = "arm" }, @{ Path = "300"; Arch = "x86_64" } ) foreach ($Pair in $Pairs) { $Path = $Pair.Path $Arch = $Pair.Arch $BaseUrl = "https://www.downloads.netgear.com/files/GDC/READYNAS-$Path" $OutDir = "S:\Setup\SysAdmin\ReadyNAS\Firmware\$Arch" # Ensure the output directory exists New-Item -ItemType Directory -Force -Path $OutDir | Out-Null # Initialize a stop flag for the max version number $lStop = $false # Enumerate minor and build versions for ($Minor = 0; $Minor -lt 20; $Minor++) { for ($Build = 0; $Build -lt 20; $Build++) { $Version = "6.$Minor.$Build" if ($Version -eq "6.10.11") { $lStop = $true break } $FileName = "ReadyNASOS-$Version-$Arch.zip" $OutFile = Join-Path $OutDir $FileName $Url = "$BaseUrl/$FileName" if (Test-Path $OutFile) { Write-Host "Skipping $FileName (already exists)" } else { Write-Host "Checking $Url" $Response = Invoke-WebRequest -Uri $Url -Method Head -ErrorAction Stop if ($Response.StatusCode -eq 200) { Write-Host " Found → downloading..." Invoke-WebRequest -Uri $Url -OutFile $OutFile -UseBasicParsing Write-Host " Saved to $OutFile" } } } if ($lStop) { break } } }4Views0likes0CommentsReadyNAS RN4220 wont boot up after shutdown from WebUI
Hello to anybody who can help, I got a ReadyNAS RN4220 out of eWaste from some company, and it worked perfectly! I have 100tb of NAS HDD storage in it and it has run fine for over a year now. Last week i decided to shut down my home rack gracefully just to give it a breather in the Australia summer heat. For the RN4220 i shut it down by using the Web Interface, telling it to turn off. It did so fine. A few days later, i tried turning it back on. It spins the fans to the highest settings and does not turn on. I have tried leaving it for a few hours overnight (approx. 8) to no avail. Does not even show up on RAIDar. What happens is it just sits there with the power LED blinking green and the network lights blinking green with fans on highest. If i force turn it off by holding down the power button the Red Health LED blinks once then goes away and the power LED goes back to amber as per normal. Again nothing has changed with the setup aside from me just shutting it down from the Web UI and turning it back on. I have done so in the past no issues. No clue whats changed. Here are some of the debugging steps i have tried: I cannot do an OS reinstall or Factory Reset as holding down the reset button for a minute on boot does not change the LEDs at all (as shown in the Hardware user manual, -> https://www.downloads.netgear.com/files/GDC/RN2120/ReadyNAS_OS6_Rackmount_HWM_EN.pdf the power LED, UI LED and Health LED should all be blinking, only the power LED blinks, assume it just isnt taking the reset command for some reason) Taking out all the disks and network cables and trying to boot up, no change Taking out all but 1 disk and booting up, no change I have tried removing both power cables (Its powered by wall power, not a UPS) and leaving it off overnight fully power cycling. no change. I have tried using the serial port on the back with a USB RS232 cable, a null modem cable (as its female port and i needed male-male) and Putty on a windows machine. Nothings happening on the console. Tried a few different baud rates to no avail. I have tried taking the top off, reseating the RAM and a few cables (Not all as im unsure what most of them do and they are quite tight in there) no change. I have tried taking out the CMOS battery from the Mobo and powering off the machine (unplugging) for a few hours. No change. I have tried running with just 1 of the PDUs on the back, it runs a red LED on the health indicator but otherwise no change. Please let me know if any additional info or photos can be useful for fixing this. I know its an older unit (if there are any newer replacements i could just take my drives and plug into with atleast 12 bays let me know, pref rack mount, and i can also look into that). I heard you can just swap drives between READYNAS products and they should work fine yeah? In terms of firmware on the device i think i installed the latest some time last year when i got it. But i cant access it to get the info anymore. I just am so confused why a simple reboot (done through the web UI!!!) would cause it to never boot up again.... Thanks for your time.80Views0likes9CommentsReadyNAS Duo v1 unable to access
I own an older ReadyNAS duo (v1 based upon it NOT saying v2 on the front access door). It was running fine until recently and here's what the current power up/boot sequence looks like Power on Start RAIDar and click on rescan while the NAS is booting up NAS power on light and drive 1 flashing, drive 2 solid grren RAIDAR report System Staus IP address 192.168.xxx.xxx (actual numbers omitted but it does show a valid IP address issued via DHCP from my router) no firmware version is displayed Unable to connect to admin page. Browser returns (Unable to connect/establish a connection to the server at 192.168.xxx.xxx. RAIDar reports Checking file system and then Quota Check (power activity and drive 1 LED's blinking drive 2 soli green. RAIDar shows both drives with green checkmarks. after a few moments the RAIDar display clears and issues a "RAIDar could not find any NETGEAR storage on your network. Check that your storage device is powered on and connected correctly. For more help, visit http://my.netgear.com" Rescan yields the same result in step 7. The NAS was setup as a RAID volume using approved (at the time WD RED NASware 1.0TB drives)31Views0likes1CommentReadyNAS Duo v2 switch to JBOD
Hi , I have an old ReadyNAS Duo v2 and it has been running in flexi raid 0 but have been trying to change it to JBOD but have tried 3 times and it just keeps going back to raid 0. I am just doing a factory reset then selecting JBOD from the drop-down when the option comes up, should I be doing something else?22Views0likes2CommentsPro6 reduction of power consumption
I have several Netgear Pro6 systems. They were upgraded to RaidOS 6.10, Intel E7600 CPUs and 4GB ram and are working great (had to recap the Seasonic power supplies since the caps were bulging). I also have an Ultra 6. I noticed the Ultra 6 uses (without drives plugged in) 19.5 watts while the Pro6 with E7600 CPUs and no drives plugged in uses 55-60watt. With the original Intel E2160 CPU the power consumption is not much different. I would like to downgrade the CPUs on the Pro6s I have to a single core model which uses as little as possible electricity. I only use them for storage, nothing fancy and since Ultra6 is fast enough with that Atom a single core Celeron in Pro6s should also be fast enough. Anyone knows what CPU should I look for ?54Views0likes3CommentsPower outage - RN528X does not auto-power on, causing UPS Slave errors
Early southern California winter storm, lost power for a few hours. Have the following setup: Cyberpower CP1500PFCLCDA 1500VA UPS RN528X is USB-connected to UPS and configured in RN OS 6.10.9 "Power" Settings RN528X Wake on LAN is ENABLED Power outage triggered UPS battery-low condition after 13 minutes, prompting RN528X to shut down: However, after power was restored, RN528X did not power back on. It remained powered down. According to Netgear, an OS 6 device with WoL enabled should auto-power on after a shutdown event: "When wake-on-LAN is enabled, if the unit is disconnected from AC power it will power on when AC power is reconnected." Wondering why this did not happen...? Normally, I would say "who cares"... however in my setup I have 3 other ReadyNAS OS6 boxes configured as "Remote UPS" to the RN528X. They are RN424, RN314, and RN212, all running 6.10.9 and all with WoL enabled. When the RN528X doesn't power back on, the other NAS boxes each begin complaining with this frequent message: Am I doing something wrong by using one NAS as the "Host" for UPS and the others as "Slaves"? I thought this is how it's supposed to be managed using a single UPS.Migrate X-RAID Disk to new NAS
Hello all... I'm using RNDP400 with 4 x 3TB HDD (X-RAID setup). Firmware already upgrade to OS 6.10.9 and all system running normal for couple of years. Now I just get new RNDP600-100 still in diskless condition in factory setting. So I believe the firmware still OS 4. I need advise the reliable step if I want migrate existing full array of HDD to diskless RNDP600 : 1. Is it possible to switch off RNDP400 then move full array of HDD to diskless RNDP600 (also in power off condition) then just Power ON without upgrading the OS 4 to OS 6? 2. worst case, if I must upgrade RNDP600 OS 4 to OS 6 before do the migration I must prepare new HDD. how big size that OS 4 support? 6TB or 8TB make sense? Please advise.. and thanks beforeSolved40Views0likes3CommentsReadyNAS Pro 6 max RAM
Hi all, Yes, I'm aware the Pro 6 is ancient and I'm aware that many threads here seem to suggest that 8GB is the maximum this box can take. But I'd like to have zfs/TrueNAS on it and I'd love 16GB on it. So I thought I'd ask: is 8GB the actual limit or could it be that it might take 16GB, it's just that nobody ever tried that? It's DDR2 so I'd imagine it might simply be because 8GB DDR2 sticks don't exist? Thanks!Drive replacement for failed drive
Hello everyone I've been running a ReadyNAS RNDU4000 (Ultra 4) populated with 4 x ST4000VN000 4TB drives in a RAID 5 configuration giving me 10.9TB available volume space for many years now. I've also upgraded the device to run on OS6 (currently 6.9.3). I've had a single drive failure and was looking at what I could replace it with. The ST4000VN000 are no longer available and was looking at the current Seagate IronWolf 4TB drives. The one that looked promising was the ST4000VN006 but it runs at 5400rpm which differs from the 5900rpm my current drives are. Would this be a problem? I use my NAS for music streaming and media playback. Has anyone used these drives or better still replaced a ST4000VN000 with one? Anyone got any further suggestions on drive replacement as I cannot find a drive compatibility chart anywhere any more especially for upgraded NAS devices on OS6. Many thanks40Views0likes2CommentsNew NAS & Giving Up X-RAID
In researching my possible replacement for my RN424 (which is fully operational, just no longer supported), I have come to appreciate the benefits of X-RAID. While I am technically competent in many ways, I am not an IT expert, and up to this time (for the past 10-12 years in which I have been using a Netgear RND2110 and then the current RN424), I was unaware of the benefits that X-RAID and what it had been performing for me in the background: basically, managing the sizes of my four volumes (shares). In contrast, Asustor NAS' apparently do not provide this feature. (I am considering their AS6804T.) It seems that I have to manage the sizes of the volumes myself, and I can find no clear direction on how to do this in their support resources. Furthermore, the documentation says that volumes can be expanded (how I cannot tell so far) but they can not be reduced, providing fertile ground for my making largely irreversible mistakes. If I have found any disadvantage of X-RAID, it is the inconvenience that Windows does not report the actual utilization of individual volumes; instead, Windows Explorer reports each volume as total utilization of the total NAS capacity. As a result, I don't know how large each volume actually is, or how to "size" each volume in my hypothetical new NAS (TBD) if I want to migrate and replicate each volume in the new system. The point of this post is not to depend on you all for me to learn about Asustor devices; perhaps it is best that I post this in an Asustor forum somewhere. But, I would be grateful for any verification of my understanding, and any insights any of you might have. I assume that many of you here are or have been in the same position as myself and have had to deal with the same issue.Solved74Views0likes4Comments