NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Cannot enable SSH on RN102 w/ 6.9.2
So I bought a used RN102. It came with OS6.0.0, and it went through the update process to 6.2.x, then 6.5.x, then 6.9.2. Only the default options were enabled through that process. I was pleased i...
Perhaps the previous owner was unaware of ReadyNAS OS 6: RN100/RN2120 cannot update due to invalid checksum
It's important to use the above workaround as a one-off for the update from pre-6.4.0 firmware to 6.4.0 or newer.
I manually started the SSH service from the backend and stopped it again successfully so it's not a problem with the service.
My guess would be that a database upgrade (or something similar) somewhere was missed. 6.0.0 to 6.2.4 is a pretty big firmware jump.
In any case for optimal performance you really should do a factory reset (wipes all data, settings, everything) to get a clean setup. There were some changes (e.g. in 6.1.5) that would require creating a new volume to take advantage of.
Perhaps the previous owner was unaware of ReadyNAS OS 6: RN100/RN2120 cannot update due to invalid checksum
It's important to use the above workaround as a one-off for the update from pre-6.4.0 firmware to 6.4.0 or newer.
I manually started the SSH service from the backend and stopped it again successfully so it's not a problem with the service.
My guess would be that a database upgrade (or something similar) somewhere was missed. 6.0.0 to 6.2.4 is a pretty big firmware jump.
In any case for optimal performance you really should do a factory reset (wipes all data, settings, everything) to get a clean setup. There were some changes (e.g. in 6.1.5) that would require creating a new volume to take advantage of.
Actually, that would have been me that was unaware, since it had OS6.0.0 when I purchased it and this is my first ARM based OS6 NAS. But it did successfully say it updated to 6.2.x (I didn't pay great attention to the last digit) and then offered to update to 6.5.2, which I did, and then 6.9.2. Oddly, though, the update to 6.2.x is not in the log, which is another reason I cannot precisely identify the version. So, maybe it's related. I have initiated the factory default (which I already thought was my best solution) and will post an update when it completes.
Factory default cleared everything up. But not everyone would be happy having to do that.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
