I'm finding a lot of older nodes while showing plenty of resources available, won't accept the current nightly release until rebooted immediately prior to applying the upgrade (and in a couple of cases, not even then).
I have an NSM3 with this behavior (with both the ar71xx and ath79xx images):
Start the upload. By watching the upload network bandwidth, the upload immediately aborts.
The node is unresponsive for a couple of minutes, then returns NOT having rebooted.
At that point, ssh is not responding:
Further upgrade attempts will fail until the node has been rebooted.
I grabbed a support data file - it may be helpful. Renamed from .tgz to .txt to allow upload.
Orv W6BI
I have an NSM3 with this behavior (with both the ar71xx and ath79xx images):
Start the upload. By watching the upload network bandwidth, the upload immediately aborts.
The node is unresponsive for a couple of minutes, then returns NOT having rebooted.
At that point, ssh is not responding:
root@w6bi-house-pc:~# nmap -p 2222 w6bi-vc-siminorth-3g Starting Nmap 7.80 ( https://nmap.org ) at 2020-02-15 12:34 PST Nmap scan report for w6bi-vc-siminorth-3g (10.100.65.151) Host is up (0.0086s latency). rDNS record for 10.100.65.151: W6BI-VC-SimiNorth-3G.local.mesh PORT STATE SERVICE 2222/tcp closed EtherNetIP-1 Nmap done: 1 IP address (1 host up) scanned in 0.26 seconds
Further upgrade attempts will fail until the node has been rebooted.
I grabbed a support data file - it may be helpful. Renamed from .tgz to .txt to allow upload.
Orv W6BI
File Attachment:
aredn-1326-c0bac78-ath79-ubnt_nanostation-m-sysupgrade - for a nano M3
aredn-1326-c0bac78-ath79-ubnt_nanostation-m-xw-sysupgrade - for a nano M2-xw
neither system appears to have updated - unless I'm reading the admin page wrong
M3 currently running version AE6XE-19.07test2e35eec (uploaded successfully while working with Joe on constant dropout problem. device runns fairly stable up th the last week or so where in now drops and has to be hard booted every few hours. admin page still reads this version after selecting and uploading above nanostation-m build.
M2 currently running 3.19.3.0 and again retains that version number after firmware upload reboots
I have an after supportdata file for the M2 and a before and after file for the M# but am unable to upload with this thread as they are a) dowmloaded to my Mac from device as .tar files and b) they are all over 400 kb. Will try Orv's trick and sent to you as .txt & let you rename to .tar
Ref: https://www.arednmesh.org/content/nightly-build-now-available-openwrt-19...
One more tip since the prior post:
* the device can be very sluggish. I've waited 15 or 20 min and found the device finished the upgrade.
================
Here is what you need to know to start using this nightly and future builds:
1) 32M RAM devices continue to be at the limit of available memory. This means that doing a sysupgrade to load new firmware may take many tries to succeed. Don't use these devices at hard to reach tower sites! The sysupgrade process needs close to 10M of memory to succeed. Tips to get it to work:
ii) disable mesh RF and any use of wireless, reboot before sysupgrade
iii) disable or uninstall any packages that are running, e.g. meshchat
iv) as an almost last resort, scp the .bin image to /tmp on the node and from the command line type "sysupgrade -n <.bin filename>" (does not save settings)
v) as the last resort, tftp to load the factory image (does not save settings)
3) To know what image to use, pay close attention to the table located here (scroll down): https://github.com/aredn/aredn_ar71xx .
4) please report any bugs encountered. At this time, there are no known and new issues.
Orv W6BI