As the 18.06.03 release appears to be close (or did it already happen?), I remembered that I haven’t updated the packages running on my Archer C7 v2 in a few weeks. Did the usual opkg update && opkg upgrade $(opkg list-upgradable | awk '{print $1}’)
dance but after a while the router dropped the connection and the upgrade may or may not have continued in its tmux
session on the router.
As the router did not come back after a while, I decided to reboot but ran into the recently reported libjson issue and thus could not connect via http or ssh any more. Ouch! After regaining access to the router's failsafe mode and executing a soft (and then a hard) reset I attempted the opkg upgrade again - but the same thing happened!
I tried only upgrading some packages and sometimes this worked, but after when I attempted to e.g. only upgrade dropbear and busybox, I ran into:
/etc/rc.common: line 32: uci_load_validate: not found
The same was printed in the system log during boot, and thus dropbear was unable to start:
Fri Jun 21 12:26:29 2019 daemon.notice procd: /etc/rc.d/S19dropbear: /etc/rc.common: eval: line 117: uci_load_validate: not found
I tried to use sysupgrade to install a fresh image to the router, but ran into other issues and sysupgrade wasn’t doing anything. Almost bricked the thing by trying to revert back to the TP-Link firmware and needed to use the TFTP recovery to finally make it back to 18.06.2, r7676-cddd7b4c77 again - right where I started
With all that happening I wonder what’s going on and why opkg upgrades are currently broken. Is this a known issue and possibly related to the upcoming release? If so, I can wait of course but I’m kinda worried that sysupgrade to 18.06.3 (or whatever comes next) will fail and this all starts over again.
Does anyone have some ideas on what’s going on here?
Thanks,
C