This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
after installing the upgrade 6.9.0 my backups from my PC no longer work
the backups ( 15 of them ) all start and remain in the " in progress" state. in previous version they remained in the " in queue" state until next one could be actioned - now they all go to in progress straight away but dont do anything.
on testing the source, I find that it is reporting invalid user name or password. my PC access is not protected by user name or password and in the previous version there was no problem with access of the PC with these fields left blank.
the only thing that has changed is the update to 6.9.0.
please advise... I have no backups running now since the upgrade to 6.9.0.
For anybody experiencing an issue with backup jobs remaining in "in progress" on SMB timestamp backup jobs, we have posted a hot-fix to resolve that issue, and your system should be automatically updated some time in the next week. If you'd like the receive the update immediately, you can reboot your NAS and it should be updated within 15 minutes.
Did you set SMB encrypton as Desired or Requrired?
If set SMB encrypton as Desired or Requrired, it won't allow Anonymous access.
Do you mean that explicitly setting "Disabled" (see here to understand why I ask this silly question WRT the issue reported) on each Share will be temporary workaround?
Yes.... you will probably find that if you go to settingts on the backup detail - and go to source - and test connection... you will get invalid user name and password ( Even if you do not have them set up anyway ).
if you do this and find some other report, would be useful for Netgear to know I think.
SMB encryption.... my SMB encryption is set - presumably - to what it has always been - "enabled". I have not made any changes. has the 6.9.0 update changed anything here?
Yes.... you will probably find that if you go to settingts on the backup detail - and go to source - and test connection... you will get invalid user name and password ( Even if you do not have them set up anyway ).
Not necessarily...in my case I did the Test Connection - was the very first test I did - and the result is OK for each share considered (as posted in other Threads my configuration is a RN314 joined to a Windows AD...and accesses to CIFS/SMB Share on a Server host are OK).
For anybody experiencing an issue with backup jobs remaining in "in progress" on SMB timestamp backup jobs, we have posted a hot-fix to resolve that issue, and your system should be automatically updated some time in the next week. If you'd like the receive the update immediately, you can reboot your NAS and it should be updated within 15 minutes.
Do I wake up a little bit too early or is the Hot Fix not yet released officially?
I did a reboot 5 minutes ago (00:55 CEST) and no new software is available: I checked for updates on "Long-Term Support" which is my default, the "Stable" and the "Beta" branches but the message is always the same laconic: "Your system is currently running the latest firmware. Your system does not need a firmware update".
Is there an alternative way (URL) to obtain such Hot Fix (thus being able to install it manually)?
I noticed that CDN propagation is taking longer than normal; so if it's not currently working for you, do one more reboot in an hour or so, and it should start working.
Yep, I noticed that. Wasn't totally sure so I rebooted 5 minutes ago and did a post-reboot check to see if there was anything more...
root@nas01:~# apt update
Hit:1 http://security.debian.org jessie/updates InRelease
Hit:2 http://apt.readynas.com/packages/readynasos 6.9.0 InRelease
Ign:3 http://mirrors.kernel.org/debian jessie InRelease
Hit:4 http://mirrors.kernel.org/debian jessie Release
Reading package lists... Done
Building dependency tree
Reading state information... Done
1 package can be upgraded. Run 'apt list --upgradable' to see it.
root@nas01:~# apt list --upgradeable
Listing... Done
readynasos/6.9.0 6.9.0+4 amd64 [upgradable from: 6.9.0+3]
N: There is 1 additional version. Please use the '-a' switch to see it
root@nas01:~# apt list --upgradeable -a
Listing... Done
readynasos/6.9.0 6.9.0+4 amd64 [upgradable from: 6.9.0+3]
readynasos/now 6.9.0+3 amd64 [installed,upgradable to: 6.9.0+4]
Is 6.9.0+4 related or I can safely ignore it (as explained on a post below, it was already automatically installed after my last reboot) and just go to test my affected Backup Jobs using the running 6.9.0+3?
The NAS would automatically install any available hot-fixes within 15 minutes of a reboot and weekly after that so by now you could well find the 6.9.0+4 update has been installed already.
I would check after it's installed the latest hot-fix.
I can understand the need for a hot fix method so critical updates are not ignored. But I really do think it should be in the log that one has occurred just in case the cure is worse than the disease. It would be good for a non-SSH user to know when it happened.
I also hope that the files that can be downloaded are already fixed so that anyone operating in an environment without internet availability can just re-install 6.9.0 manually to get the fix.
There are a lot of threads that seem to be related. I hope the word gets out to all affected.
I can understand the need for a hot fix method so critical updates are not ignored. But I really do think it should be in the log that one has occurred just in case the cure is worse than the disease. It would be good for a non-SSH user to know when it happened.
Correct. I agree. Was thinking about the same thing (I was a little bit surprised about the Hot-Fix autonomous install process as it was described...pardon me if I didn't know about it). I add: not only when it happened...but if it happened. Now I'm in cautious mode... ;-).
Logs history I saw on my unit shows that Hot-Fix(es) are seldom seen...so the fact 6.9.0+3 and 6.9.0+4 are jumped in as described is due to the necessity of hot-fixing without manual user intervention (reboot a part, that can also be scheduled...I personally don't do that).
I also hope that the files that can be downloaded are already fixed so that anyone operating in an environment without internet availability can just re-install 6.9.0 manually to get the fix.
There are a lot of threads that seem to be related. I hope the word gets out to all affected.
Good point. Really ReadyNAS OS was 6.9.0 or, as I saw it on logs, was already at 6.9.0+2 when I upgraded on October, 26th?
Is like asking: download from ReadyNAS and manual download from Netgear Support web site point to the same version of ReadyNAS OS or what?
Since upgrading to 6.9.0 I have not been able to backup anything! I have taken note of the issue of firmware releases and hot-fixes. So, I have now rebooted twice and checked the system logs and have seen no reference to any hot-fixes being applied - the system still is reporting 6.9.0 as the Firmware.
Please, what can I do to reinstate the essential backups?
