NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
ReadyNAS 6.7 on Legacy Hardware?
I've been running ReadyNAS 6 on my much upgraded Ultra 6 Plus for the longest time without issue. Previously when a new release came around, it would dutifully autoupgrade all the way to 6.6. However, now I see that an official 6.7.1 release is out, but not only was there no auto-update, when I check for update manually, the response is that 6.6.1 is the latest version and I don't need to upgrade.
I know how to (and have) upgrade the OS manually, but all of this suspiciously looks like a hint that 6.7 won't run properly on legacy hardware, no matter how upgraded. Or am I being paranoid and should just upgrade?
Ok, manual update performed and quick scan of all the dashboard screens reveals no obvious problems.
6 Replies
Replies have been turned off for this discussion
You could try a manual update.
I am running 6.7.1 on an Ultra 6 plus.
It works fine, the only issue I am having, and this may not be related to the OS, is that whenever I activate ReadyDR and use it, it seems to lead to filesystem corruption and a forced read only state that I can only fix with a factory reset. This did not happen on 6.6.
I've looked for other causes without finding one.
I wouldn't hesitate to upgrade, perhaps if you are using readyDR make sure any primary data is backed up.
Thanks for the advice. I'm fully backed up using CrashPlan and don't use readyDR yet, so that is one thing less to be worried about. Will try manual upgrade and report.
Ok, manual update performed and quick scan of all the dashboard screens reveals no obvious problems.
One final note: A day or so after the update, I noticed the SMB shares hosted by the NAS acting funny. SMB reads to my Win 10 workstation were fine, but trying to add or rename files resulted in volume full errors, even though there were still over 9 TByte free (and Windows reported that figure accurately).
It was not a permissions thing: I was still able to delete files over SMB.
Nor was it a problem with the underlying FS: If I logged myself in via SSH, I could perform all actions locally without a hitch and df reported accurate figures.
Well, no big deal, the problem went away when I rebooted the NAS and it may have been purely coincidental. But then I've never ever observed this issue before.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
