Firmware Downloads

InteXX wrote:

There is no download available for v6.3.5, so a 102 user on OS v6.3.4 is stuck.

Despite the release notes, v6.3.x releases were limited to the RN200 series.  

There are KB articles here:

• https://kb.netgear.com/27321/ReadyNAS-OS-6-Software-Version-6-3-2
• https://kb.netgear.com/27326/ReadyNAS-OS-Version-6-3-3-ReadyNAS-200-Only
• https://kb.netgear.com/27498/ReadyNAS-OS-Version-6-3-4-ReadyNAS-200-Only
• https://kb.netgear.com/29397/ReadyNAS-OS-Version-6-3-5-ReadyNAS-200-Only

A direct download to 6.3.5 is here:

• https://www.downloads.netgear.com/files/GDC/READYNAS-200/ReadyNASOS-6.3.5-arm.zip

What script is that?  Powershell or something?

Shame it's not linux so you could run on the readynas!

Someone should probably download the documentation and KBs too, before they go walkies.

After learning from StephenB​ that there're download URLs for the 200 product line as well, I've updated the script to include those. Two levels of folders are created now: one for each of the product lines (100, 200 or 300), and then two subfolders under each of those for the architextures (arm and x86_64). Six folders total.

This update also includes error handling for non-200 server responses, just in case. It's probably not needed, but it can't hurt.

Here's the updated version:

# Define product lines and architectures
$Lines = @("100", "200", "300") 
$Archs = @("arm", "x86_64")

foreach ($Line in $Lines) {
  foreach ($Arch in $Archs) {
    $BaseUrl = "https://www.downloads.netgear.com/files/GDC/READYNAS-$Line"
    $OutDir = "S:\Setup\SysAdmin\ReadyNAS\Firmware\$Line\$Arch"

    # Ensure output directory exists: line → arch
    New-Item -ItemType Directory -Force -Path $OutDir | Out-Null

    # Stop flag for ending at 6.10.11
    $Stop = $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") {
          $Stop = $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"

          try {
            $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"
            }
          }
          catch {
            # Ignore 404 and other errors
          }
        }
      }

      if ($Stop) {
        break
      }
    }
  }
}

Since it is not necessary to upgrade through the entire sequence of updates, downgrading to anything prior to the one running that's a major downgrade (e.g. 6.10.x to 6.9.x) can cause real problems (especially on ARM systems), and it's also not recommended to  run really ancient OS versions at all, I don't see the point here of keeping them all.  But go ahead if you want. 

I don't know where you got that statement of the necessary incremental upgrades, but it's incomplete.  The complete statement, assuming one is moving to 6.10.x, is "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. ReadyNAS 202, 204, 212 and 212 systems must not be updated directly to 6.10.x from 6.3.x. They must first be updated to 6.3.5 then 6.5.2 and then to 6.10.x." 

But with 6.3.5 being only for the 200 series, I believe a more accurate statement would be  ReadyNAS 102, 104, and 2120 systems must not be updated directly to 6.10.x from 6.2.4 or older firmware. They must first be updated to 6.2.5 then to 6.5.2 and then to 6.10.x. ReadyNAS 202, 204, 212 and 212 systems must not be updated directly to 6.10.x from 6.3.4 or older firmware. They must first be updated to 6.3.5 then 6.5.2 and then to 6.10.x.   Hopefully, it's obvious from that that a unit between 6.2.5/6.3.4 (as appropriate) and 6.5.2 still needs to go through 6.5.2.

FYI, the reason for the mandated sequence has to do with changes made to U-Boot.  I don't know the details, but I know you can brick a unit by not following the sequence.

While I don't know why anyone would need to, on Intel-based units, it is actually safe to downgrade to a much earlier version via USB recovery and starting fresh with blank(ed) drives.  USB recovery fully overwrites the flash, and there is no U-Boot involved.

InteXX wrote:

Frankly, I think they could have done a better job with this. Satisfaction of the incremental requirements could have been easily automated, relieving the user of this tedious and error-prone burden.

 

It was.  If you used the online upgrade process, the required sequence was followed.  I purchased a used never-updated unit (a 204, I think) and verified it was following the proper sequence before committing to each download.  The notes were only for those who are doing an offline local update.  Of course, now, that's the only way one can update, so it's become more important.