NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
rodcrit
Oct 28, 2017Luminary
backups from pc failing after upgrade
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...
- Oct 30, 2017
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.
Skywalker
Oct 30, 2017NETGEAR Expert
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.
Kimera
Oct 30, 2017Guide
Thanks Skywalker and mdgm-ntgr.
I'm going to try in few hours.
Just a question: is there a way (Through CLI included) to directly check/verify if the background update (hot fix) has been deployed once I reboot?
Like seeing (cat /var/log/dpkg.log as admin) 6.9.0+3 popping up after my previous 00:55 CEST reboot:
2017-10-31 00:59:34 startup packages configure 2017-10-31 01:01:41 startup archives unpack 2017-10-31 01:01:41 upgrade readynasos:amd64 6.9.0+2 6.9.0+3 2017-10-31 01:01:41 status half-configured readynasos:amd64 6.9.0+2 2017-10-31 01:01:42 status unpacked readynasos:amd64 6.9.0+2 2017-10-31 01:01:42 status half-installed readynasos:amd64 6.9.0+2 2017-10-31 01:01:42 status half-installed readynasos:amd64 6.9.0+2 2017-10-31 01:01:42 status unpacked readynasos:amd64 6.9.0+3 2017-10-31 01:01:42 status unpacked readynasos:amd64 6.9.0+3 2017-10-31 01:01:43 startup packages configure 2017-10-31 01:01:43 configure readynasos:amd64 6.9.0+3 <none> 2017-10-31 01:01:43 status unpacked readynasos:amd64 6.9.0+3 2017-10-31 01:01:43 status half-configured readynasos:amd64 6.9.0+3 2017-10-31 01:01:43 status installed readynasos:amd64 6.9.0+3 2017-10-31 01:01:43 startup packages configure
and (cat /var/log/apt/term.log as root):
Log started: 2017-10-31 01:01:41 (Reading database ... 13599 files and directories currently installed.) Preparing to unpack .../readynasos_6.9.0+3_amd64.deb ... Unpacking readynasos (6.9.0+3) over (6.9.0+2) ... Setting up readynasos (6.9.0+3) ... Log ended: 2017-10-31 01:01:43
or (cat /var/log/apt/history.log as admin):
Start-Date: 2017-10-31 01:01:41 Commandline: apt-get -qq install -fy rn-dictionary freeapp-collection readynasos ca-certificates Upgrade: readynasos:amd64 (6.9.0+2, 6.9.0+3) End-Date: 2017-10-31 01:01:43
Definitely something after last reboot was automatically installed...
- mdgm-ntgrOct 30, 2017NETGEAR Employee Retired
Yes, that's what you're looking for, though the current version is 6.9.0+4
The quickest way to check if it's installed would be to do e.g.
# dpkg -l readynasos
This will tell you the installed status of the package and the package version
You can also find this information in the logs zip file e.g. by looking at packages.log
- KimeraOct 30, 2017Guide
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?mdgm-ntgrthanks for the command!
- KimeraOct 30, 2017Guide
Great. Affected ReadyNAS managed Backup Jobs work again (Completed!). Really good job and prompt actions mates. Thanks, really. Davide.
- mdgm-ntgrOct 30, 2017NETGEAR Employee Retired
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. - KimeraOct 30, 2017Guide
Received. Done, it works flawlessly also with 6.9.0+4.
- SandsharkOct 30, 2017Sensei
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.
- KimeraOct 30, 2017Guide
Sandshark wrote: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).
Sandshark wrote: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?
- mdgm-ntgrOct 30, 2017NETGEAR Employee RetiredWe won’t build a new 6.9.0 image. Doing that would require going through the release process all over again.
The hot-fix allows us to push out urgent fixes that can’t wait for the next production release (6.9.1).
I haven’t tested applying the hot-fix on offline systems but that should be possible. - atb48Oct 31, 2017Guide
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?
- rodcritOct 31, 2017Luminary
Thank you ... my backups are now working.
- atb48Oct 31, 2017Guide
Thanks for the comments. I had assumed from the information in the thread that either the system log or system status would show the "b4" hot-fix suffix - can it be checked anywhere?
Anyway, I've now suceeded manually to complete 5 backups and so I feel somewhat relieved! There are many discussion threads on this issue so I have provided a link in one that had been marked as "SOLVED" yet had also suggested downgrading the firmware as a temporary fix.
Thanks
- KimeraOct 31, 2017Guide
atb48 wrote:Thanks for the comments. I had assumed from the information in the thread that either the system log or system status would show the "b4" hot-fix suffix - can it be checked anywhere?
Anyway, I've now suceeded manually to complete 5 backups and so I feel somewhat relieved! There are many discussion threads on this issue so I have provided a link in one that had been marked as "SOLVED" yet had also suggested downgrading the firmware as a temporary fix.
Thanks
Downgrading wasn't - really - a correct way of fixing thing (it's an extreme form of workaround...but it can have bad consequences too)...this night (CEST) Netgear released Hot-Fixes update 6.9.0-3 and 6.9.0-4 and all NASes picked them up after a (forced) reboot if done in the same time window (or after).
ReadyNAS logs those updates but it doesn't show them on the ReadyNAS Web GUI as it does in case of ReadyNAS OS releases (6.81, 6.9.0 and so on...) so you should read some posts above to learn where specific apt logs can be found and examined (and also a particular command to check the actual status of ReadyNAS OS WRT) to check what the NAS unit did under the hood.
- StephenBOct 31, 2017Guru - Experienced User
Kimera means this post: https://community.netgear.com/t5/Using-your-ReadyNAS/backups-from-pc-failing-after-upgrade/m-p/1410863/highlight/true#M138209
I posted a suggestion in the idea exchange to show the patch level on the system->overview page. It should also be shown in RAIDar.
That suggestion is here: https://community.netgear.com/t5/Idea-Exchange-for-ReadyNAS/Hot-Fix-patch-level-should-be-shown-on-system-gt-overview-page/idi-p/1411097
- KimeraOct 31, 2017Guide
Exactly, I meant that thread.
I gave a Kudo to your idea. Brilliant.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!