Can't turn on ReadyCloud OS 6

[readynas-ru]

ReadyNAS Pro Pioneer running OS 6.9.2

Registered with mynetgear.com (see note below, though)

Merged with readycloud

When trying to turn ReadyCLOUD on, after entering the correct login info, i get a dialog box:

ReadyCLOUD

24002000011

and the Ok button

In case this is important ( s/n mismatch or something) - 

My other same model RNDP600E on OS 6.9.2 IS registered and connected to ReadyCLOUD (can see files in the iOS app, etc)

Whereas this one I couldn't for the life of me get to register.  the OS6 gave me the Serial number but mynetgear.com kept telling me the Serial number had already been registered.  By comparing the two I noticed that the "faulty" ReadyNAS GUI gave me the serial number with small letters, not caps.  Upon learning that the serial number should be 13 characters I noticed the one shown is only 12 (wish mynetgear would have told me THAT instead of "registered before")

By looking at the physical box I saw the rather prominent 12-char code sticker with all caps and a smaller paper sticker with barely legible symbols underneath the bar code with rather unhelpful little asterisks on each side.  Thirteen!  That got the device registered finally.

Yet as stated above, I still can't get it to connect to readycloud and the GUI is still showing the 12-char WRONG serial number (MAC address? Whatever) under Serial number:

A reboot did not help.

Thanks a lot,

PS I know the product is EOL and the upgrade to OS 6 on legacy devices is explicitly NOT supported, but the other same model box sitting right next to is happily connected to ReadyCLOUD, whereas this one can't, so I thought I'd ask anyway 🙂

[mdgm-ntgr · Accepted solution]

There were a batch of early Pro units that show the MAC address of eth0 as the serial number. This can be fixed. I've sent you a PM requesting further details.

ReadyCLOUD requires a NETGEAR 13-digit serial number

[readynas-ru]

EDIT: The OS is of course the latest 6.9.2, not 6.2.9

Antivirus not enabled

I CAN see both NASes from the readycloud site, clicking Manage opens the GUI.

[rickr1]

We are reporting this very issue on the following location https://community.netgear.com/t5/ReadyCLOUD/Readnas-cannot-connect-to-readycloud/m-p/1505647/highlig...

[mdgm-ntgr · Accepted solution]

There were a batch of early Pro units that show the MAC address of eth0 as the serial number. This can be fixed. I've sent you a PM requesting further details.

ReadyCLOUD requires a NETGEAR 13-digit serial number

[mdgm-ntgr]

The serial number for your systems are now fixed.

[readynas-ru]

Alright, I gotta say this:

1. The "official" upgrade to OS 6 for legacy systems is OFFICIALLY UNSUPPORTED.

(as I later found out) - one is officially warned that ReadyCLOUD will not work on some very old systems where the s/n is displayed as the eth0 MAC address (as clearly stated at the bottom of the upgrade instructions, which I happily missed on first reading, of course)

2. Let's be honest, the ReadyCLOUD access  is not exactly the most critical must-have reason for the upgrade

3. The device is EIGHT years old, after all, waaay out of warranty/support RAIDiator, OS 6 or whatnot..

and yet mdgm went the extra mile to fix this bug.

That's what I call standing by your products, netgear!

So, a great SPASIBO! from Russia to mdgm!

PS (sorry about the US:"OAR" Olympic hockey score today... sort of.. )

[StephenB]

---

@readynas-ru wrote:

and yet mdgm went the extra mile to fix this bug.

That's what I call standing by your products, netgear!

---

Netgear made a very smart decision when they hired him to help out here.

[mdgm-ntgr]

---

@readynas-ru wrote:

That's what I call standing by your products, netgear!

So, a great SPASIBO! from Russia to mdgm!

---

You're welcome.

---

@readynas-ru wrote:

PS (sorry about the US:"OAR" Olympic hockey score today... sort of.. )

---

I'm not American, so I don't care how they went.

@StephenB wrote:
Netgear made a very smart decision when they hired him to help out here.

Kind of you to say so. I do my best to help where I can.

This particular problem is pretty much as straightforward to fix as it can get.