NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Migrating Disks from NV+ to NVX
Hello Folks, I'm new here ... I have / had an old NV+ NAS with four 1TB drives. I hadn't used it for years and when I got it going again the other day, all was well for a few hours, backing up my MBP with TimeMachine, until - I'm guessing here - the PSU failed mid-backup, tripping the ring main breaker; the plug fuse (13A!) is Ok and it won't restart. Rather than try and repair or replace the PSU (my regular MO), I decided to buy a used NVX complete with disk trays - looking forward to the performance upgrade! So I've moved the four 1TB drives - in order - from the NV+ to the NVX and powered it up 'Normally'. Error message says that it can't mount the RAID disks ... Ok, so I boot into 'OS reinstall' mode, which seemed to be Ok until the same error message appeared. Any clues or ideas how to proceed? I'd really like to retain / recover the data on the RAID set. I haven't yet tried connecting over the network ... will try this next and see if RAIDar can see it. Many thanks in advance.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.Using ReadyNAS as backend for lightweight web tools — is it reliable?
Hi everyone, I currently maintain a small web tool (for example a gratuity / end-of-service benefit calculator for users in the UAE), and I’m evaluating options to host user data, logs, JSON storage files, and backups. My ideal setup is a lightweight, always-on system without needing a full server. That’s where ReadyNAS caught my interest. Some of the things I’m considering: Using ReadyNAS to host REST APIs, static JSON or YAML config files, and backing up user session data. Ensuring data integrity and performance — especially under concurrent access. Handling firmware updates without breaking API endpoints. Syncing backups to cloud or another NAS for redundancy. A few questions for those experienced with ReadyNAS: 1. Has anyone used ReadyNAS to back a small web service or tool (not just file server)? 2. What is the maximum recommended concurrent requests for lightweight API files (JSON) on ReadyNAS? 3. Which methods have you used for version-safe firmware updates so that custom services are not lost? 4. How do you handle secure access (SSL, tokens) when serving APIs from a NAS that’s also storing private user data? If anyone’s already built similar backend or microservice setups using ReadyNAS, I’d love pointers or pitfalls to avoid. Thank you!
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 } } }
