NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RAIDator 5.3.4 for Duo v2 Photos II
I just updated from RAIDiator 5.3.4 from 5.3.3 on my Duo v2, even though when I asked it to check for updates it said it was running the latest.
It appears that RAIDiator 5.3.4 tries to downgrade Photos II during the update process:
Sat Mar 31 22:23:38 PDT 2012 System is up.
Sat Mar 31 22:23:09 PDT 2012 Your ReadyNAS device has been updated with a new firmware image. (5.3.4)
Sat Mar 31 22:22:46 PDT 2012 196: ERROR: ReadyNAS Photos II cannot be revert back to older version.
It appears that RAIDiator 5.3.4 tries to downgrade Photos II during the update process:
Sat Mar 31 22:23:38 PDT 2012 System is up.
Sat Mar 31 22:23:09 PDT 2012 Your ReadyNAS device has been updated with a new firmware image. (5.3.4)
Sat Mar 31 22:22:46 PDT 2012 196: ERROR: ReadyNAS Photos II cannot be revert back to older version.
5 Replies
Replies have been turned off for this discussion
- You should have been prompted to do the firmware update.
As for the Photos II error that is to be expected. You cannot downgrade Photos II. The Photos II add-on is installed on each firmware update. You got that error because you have a newer version of Photos II installed than the version in the 5.3.4 firmware. As a result the add-on installation was aborted. Nothing to worry about. No damage was done. - I think there is an issue with 5.3.4 being detected as newer.
I have 5.3.3 installed and clicking check for updates, it too says I am running the latest. - The update server still points to 5.3.3.
5.3.4 is an update that addresses an issue where if the power timer feature was used and the NAS was auto powered off and the power on event happened while the power was disconnected the NAS would fail to boot when the power was reconnected leading to a RMA being required. Unless you use the power timer feature you don't need to update to 5.3.4. - Ok, yeah I was affected by that power thing. Just seems odd that you wouldn't push it out to everyone to stop that issue occuring.
- Don't know why NetGear didn't do that. They may have simply forgotten to push it to the update server.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
