NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Netgear Readynas NVX (Buisness)
I just bought the device for 30 euros and have managed to install the latest official firmware (4.2.31) with Root SSH and fixed the TLS issue. Now I am wondering moving onto flashing something more modern, like Alpine Linux x86. I was wondering if this is possible, advisable and what issues might arise. I have ordered a UART TTL to USB adapter and ask if I would need anything else for this. I appreciate all kinds of feedback. Thanks in advancedBest way to swap drives ReadyNAS nv+ v2
I know that my ReadyNAS nv+ v2 is no longer supported, however I would like to use it as a place to store data that can easily be reproduced. I've had it fitted from day 1 with two 3 TB Western Digital WD30EFRX drives using X-raid2 (effectively using RAID-1 giving me 3 TB of net capacity). I got hold of four 3 TB Hitachi DK7SAD300 drives; my plan is to install all 4 drives in my ReadyNAS (giving me 9 TB of net capacity in RAID-5). Here's what I plan to do: Create a backup of the existing data on one of the Hitachi DK7SAD300 drives (done). Remove existing two Western Digital WD30EFRX drives from my ReadyNAS. Install three of the four Hitachi DK7SAD300 drives in my ReadyNAS; perform a factory reset and install using RaidAR version 4.3.8; my plan is to use X-raid2 again, so will end up with a single volume. Copy the data back from the backup created under (1). Finally, insert the final Hitachi DK7SAD300drive in the ReadyNAS (destroying the backup on there). Any suggestions or recommendations? Alternatively, I could create a backup on one of the two Western Digital WD30EFRXdrives (removing one from the ReadyNAS). And configure the ReadyNAS with all four Hitachi DK7SAD300 drives from the start. Only drawback is that I would have to backup my data once more (which will take a couple of days over 1 Gbps ethernet). And should I use or 4.3.8 of RaidAR software? I also came across 6.5.0. Finally, should the above plan hit any issues. Can I still put my two Western Digital WD30EFRX drives back in my ReadyNAS? Thanks!
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. ThanksWriting 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.Firmware 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 } } }
