NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Writing to the LCD (RN516)
Does anyone have any notes on how to enable hardware support or load kernel modules etc, in order to obtain a workable method to access the displays on ReadyNAS devices from within alternative linux OSs? Specifically I'm interested in RN516 and Pro6, but it would be great if we could start to share knowledge to help everyone with this particular issue. I've been running various different OSs on an RN516, and have stuff like fan control sorted. I've also sorted out a nasty ACPI issue which hogs a large chunk of CPU power due to interrupts from IRQ9. But, I've run out of talent so far on anything that lets me access the LCD hardware. Any pointers? And no, there's nothing in /dev like /dev/lcd or /dev/ttyS1 or similar that will do that job. Stuff that works inside ReadyNAS OS6 doesn't work in other linux OSs, presumably due to a lack of hardware support in the kernel, or the correct module. So far I've completely failed to work out how to resolve this. I managed for the fan/temperature/PWM hardware, but the LCD is kicking my butt.
ReadyNAS Ultra 6 OS 4.2.31 corrupted VPD
I upgraded 3 of my ReadyNAS Ultra 6 to OS 6, and although had issues, it is running smooth (touch wood). However, I left 1 of my Ultra 6 as stock on os 4.2.31. The VPD has now been corrupted after failed restart that corrupted root. FrontView and RAIDar are empty when rebuilding the NAS. I am looking for a stock v4.2.31 VPD from an Ultra 6. Willing to divert some funds to procure a valid file. Contact me if you have a file or can help. Not really looking at buying an old Ulyta 6 to scrape it's VPD, but willing to do this if this is the only option. Message me please if you have a solution. ThanksFirmware 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 } } }ReadyNAS 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.ReadyNAS 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)ReadyNAS 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?
