9.13 MR2: R710 fails to upgrade

  • 1
  • Question
  • Updated 8 months ago
It looks like there's a serious problem with the 9.13.2 update just posted. I upgraded my ZD1200 to this firmware and unfortunately after the upgrade, both of my R710's failed to upgrade to the new firmware:

2 23:26:46 R710 local2.err syslog: Firmware update error(-29)
Jan 2 23:26:48 R710 kern.warn kernel: [ 147.710684] : vid[1:0]=1,0
Jan 2 23:26:48 R710 kern.warn kernel: [ 147.710684] : vid[1:0]=1,0
Jan 2 23:26:51 R710 daemon.notice Firmware Daemon[2890]: working|looking up control server IP
Jan 2 23:26:51 R710 daemon.notice Firmware Daemon[2890]: working|reading control file
Jan 2 23:26:51 R710 daemon.notice Firmware Daemon[2890]: working|reading firmware file header
Jan 2 23:26:51 R710 kern.warn kernel: [ 150.222774] : vid[1:0]=1,0
Jan 2 23:26:51 R710 kern.warn kernel: [ 150.222774] : vid[1:0]=1,0
Jan 2 23:27:01 R710 daemon.notice Firmware Daemon[2890]: failed|AP Image Signing : Firmware public key verification failed.
Jan 2 23:27:01 R710 local2.err syslog: Firmware update error(-29)
Jan 2 23:27:06 R710 daemon.notice Firmware Daemon[3029]: working|looking up control server IP
Jan 2 23:27:06 R710 daemon.notice Firmware Daemon[3029]: working|reading control file
Jan 2 23:27:06 R710 daemon.notice Firmware Daemon[3029]: working|reading firmware file header
Jan 2 23:27:16 R710 daemon.notice Firmware Daemon[3029]: failed|AP Image Signing : Firmware public key verification failed.
Jan 2 23:27:16 R710 local2.err syslog: Firmware update error(-29)
Jan 2 23:27:21 R710 daemon.notice Firmware Daemon[3192]: working|looking up control server IP
Jan 2 23:27:21 R710 daemon.notice Firmware Daemon[3192]: working|reading control file
Jan 2 23:27:21 R710 daemon.notice Firmware Daemon[3192]: working|reading firmware file header
Jan 2 23:27:30 R710 authpriv.info dropbear[2116]: Exit before auth: Exited normally
Jan 2 23:27:31 R710 daemon.notice Firmware Daemon[3192]: failed|AP Image Signing : Firmware public key verification failed.
Jan 2 23:27:31 R710 local2.err syslog: Firmware update error(-29)
Jan 2 23:27:33 R710 kern.warn kernel: [ 192.711871] : vid[1:0]=1,0
Jan 2 23:27:33 R710 kern.warn kernel: [ 192.711871] : vid[1:0]=1,0
Jan 2 23:27:33 R710 authpriv.info dropbear[3306]: Child connection from 10.0.200.240:50893
Jan 2 23:27:34 R710 authpriv.notice dropbear[3306]: Deferring to RKS shell to authenticate password.
Jan 2 23:27:34 R710 authpriv.err dropbear[3306]: chown(/dev/ttyp0, 0, 5) failed: Read-only file system
Jan 2 23:27:34 R710 authpriv.err dropbear[3306]: chmod(/dev/ttyp0, 0620) failed: Read-only file system
Jan 2 23:27:36 R710 daemon.notice Firmware Daemon[3324]: working|looking up control server IP
Jan 2 23:27:36 R710 daemon.notice Firmware Daemon[3324]: working|reading control file
Jan 2 23:27:36 R710 daemon.notice Firmware Daemon[3324]: working|reading firmware file header
Jan 2 23:27:36 R710 kern.warn kernel: [ 195.648359] : vid[1:0]=1,0
Jan 2 23:27:36 R710 kern.warn kernel: [ 195.648391] : vid[1:0]=1,0
Jan 2 23:27:46 R710 daemon.notice Firmware Daemon[3324]: failed|AP Image Signing : Firmware public key verification failed.
Jan 2 23:27:46 R710 local2.err syslog: Firmware update error(-29)
Jan 2 23:27:51 R710 daemon.notice Firmware Daemon[3465]: working|looking up control server IP
Jan 2 23:27:51 R710 daemon
Photo of John D

John D, AlphaDog

  • 497 Posts
  • 136 Reply Likes

Posted 8 months ago

  • 1
Photo of John D

John D, AlphaDog

  • 497 Posts
  • 136 Reply Likes
I was able to downgrade back to 9.13.1 MR1 Refresh and bring my network back online.
Photo of Michael Brado

Michael Brado, Official Rep

  • 1933 Posts
  • 271 Reply Likes
Please open a ticket with Support asap!  Thanks John.
Photo of John D

John D, AlphaDog

  • 497 Posts
  • 136 Reply Likes
Yep I'll attach both soon. I am on 9.13.1 MR1 Refresh again, so hopefully the logs still contain something useful. At the moment unfortunately I can't risk further downtime until early next week.
Photo of Dave Watkins

Dave Watkins

  • 59 Posts
  • 12 Reply Likes
Hi John

Did this go anywhere or get resolved? There are a couple of things in this release that would be quite useful, but I've got some R710's and really don't want to risk it failing and having to downgrade.

Thanks
Photo of John D

John D, AlphaDog

  • 497 Posts
  • 136 Reply Likes
My case is still open. We exchanged some more logs on Friday when I was able to reproduce the issue again.

I suspect it's something related to either my AP's or my configuration but I'm waiting to hear back.
Photo of Dave Watkins

Dave Watkins

  • 59 Posts
  • 12 Reply Likes
Thanks, I'll hold off then, I've got a couple of 710s forming a mesh link, with R600's on the other side of that link 
Photo of Jill Eldridge

Jill Eldridge

  • 1 Post
  • 0 Reply Likes
I have 5 R700s that are failing to allocate DHCP addresses post 9.13.2 upgrade to ZD1200 although it shows that the APs are upgraded with the new cert.