You are here

Home » Forums » Hardware » Nodes

Nanostation M2 (XM) stuck at 3.19.3.0 - Upgrading "bricks" it

20 posts / 0 new
Log in or register to post comments
Last post
Tue, 12/20/2022 - 01:51
#1
W5CWT
Nanostation M2 (XM) stuck at 3.19.3.0 - Upgrading "bricks" it

Unit works, but can't seem to upgrade one of my M2s past 3.19.3.0

I have two (seemingly) identical Nanostation M2 (XM) units (as well as other units). One M2 upgraded fine to 3.20.XX and then recently to 3.22.XX without problems. The other one will not. When I upgrade via the Aredn GUI, it reboots and eventually gets to state with the power LED on and a very slow red flash only (left strength LED). Noting works at that point. I must use TFTP to revert back to AirOS 5.6.16, then I can load the 3.19.3.0 factory bin.

I've tried several suggestions. Turning off the RF, working in network isolation, using TFTP to go straight from AirOS to 3.22 (using the factory.bin), using TFTP to upgrade from 3.19.3.0 to 3.20 or 3.22 (using the sysupgrade bin). I even tried the XW bin just in case (although I've been treating them as XM boards).  Nothing works. All ends in the same state (slow blink of the red LED). 

Seems like the unit will be stuck at 3.19 forever. 


 

Top
Tue, 12/20/2022 - 06:33
nc8q
nc8q's picture
TFTP only a factory.bin

Hi, David:

As long as you can get the device into TFTP state, a factory.bin should be loaded.
As long as you can get the device into TFTP state, there is no need to go to a manufacturer's .bin before loading an AREDN factory.bin.

Because I have many remote nodes without internet access,
I upgrade my nodes by first downloading the sysupgrade.bin to my workstation, then
uploading to my device from its admin page.

Someone else had a similar failure as you mention.
https://www.arednmesh.org/content/firmware-failure

Use the
http://localnode.local.mesh/cgi-bin/sysinfo
to compare model: 0x???? among your Nanostation M2 XM devices.

Please attach your 'Download Support Data' on your next post.

73, Chuck

Top
Thu, 12/22/2022 - 00:23
(Reply to #2)
W5CWT
Chuck,

Chuck,

  Here's the rsults of comparing the sysinfo pages (interestingly, only one of them had a model in the format of "0xe...":

Able to Upgrade
node: W5CWT-203
model: 0xe012

system type : Atheros AR7241 rev 1
machine : Ubiquiti Nanostation M
processor : 0
cpu model : MIPS 24Kc V7.4



Failed to Upgrade (stuck at 3.19.3)
node: W5CWT-204-6-132-150
model: NanoStation M2 

system type : Atheros AR7240 rev 2
machine : Ubiquiti Nanostation M
processor : 0
cpu model : MIPS 24Kc V7.4

73
David
 
Support File Attachments: 
File Support data for Node that works
File Support data for Node that is stuck at 3.19.3
Top
Tue, 12/20/2022 - 11:39
K5DLQ
K5DLQ's picture
what is the exact firmware
what is the exact firmware filename that you are using?
Top
Wed, 12/21/2022 - 23:36
(Reply to #4)
W5CWT
I tried and failed to upgrade

I tried and failed to upgrade to (via AREDN GUI) : aredn-3.22.12.0-ath79-generic-ubnt_nanostation-m-squashfs-factory.bin
To restore AirOS, I TFTP'ed: XM.v5.6.15.30572.170328.1107.bin
Then, using TFTP, loaded: aredn-3.19.3.0-ubnt-nano-m-factory.bin
I tried (and failed) upgrading via the AREDN GUI from 3.19.3.0: aredn-3.20.3.0-ath79-ubnt_nanostation-m-sysupgrade.bin
I tried (and failed) using TFTP (after restoring AirOS above): aredn-3.22.1.0-ath79-generic-ubnt_nanostation-m-squashfs-factory.bin

David


Anything else fails.  

Top
Thu, 12/22/2022 - 10:41
(Reply to #5)
K5DLQ
K5DLQ's picture
Curious... try this one:  
Curious... try this one:   http://downloads.arednmesh.org/firmware/aredn-3.22.12.0-ar71xx-generic-ubnt-nano-m-squashfs-sysupgrade.bin
(this is this the older architecture build ar71xx instead of the new ath79).
 
Top
Mon, 12/26/2022 - 01:04
(Reply to #6)
W5CWT
Success! The aredn-3.22.12.0
Success! The aredn-3.22.12.0-ar71xx-generic-ubnt-nano-m-squashfs-sysupgrade.bin worked via the GUI upgrade from 3.19.3. 

73
David
Top
Mon, 12/26/2022 - 13:37
(Reply to #7)
K5DLQ
K5DLQ's picture
good deal!
good deal!
Top
Sun, 12/25/2022 - 09:42
(Reply to #8)
nc8q
nc8q's picture
Anything else fails.  
To be sure...does a TFTP load of 
aredn-3.22.12.0-ath79-generic-ubnt_nanostation-m-squashfs-factory.bin
fail?


73, Chuck

 
Top
Mon, 12/26/2022 - 00:51
(Reply to #9)
W5CWT
Yes, it fails. I tried it
Yes, it fails. I tried it (via TFTP) after restoring AirOS. However, I don't think I tried it using TFTP BEFORE resotring the AirOS.

David
Top
Sat, 12/24/2022 - 13:37
KK4ZUZ
Try the latest nightly to see
Try the latest nightly to see if that works
Top
Sun, 12/25/2022 - 16:07
k1ky
k1ky's picture
Turn MESH RF OFF
I found that disabling MESH RF usually frees up enough memory to upgrade
Top
Mon, 12/26/2022 - 00:52
(Reply to #12)
W5CWT
I tried upgrading with the
I tried upgrading with the Mesh RF off, but had the same results.

David
Top
Thu, 01/05/2023 - 08:24
N7JYS
Nanostation M2 (XM) stuck at 3.19.3.0 - Upgrading "bricks" it

Good morning. I am having the same issue with the Nanostation M5 XW. I have uploaded my support file from the M5 node.

Eric 

Support File Attachments: 
File Nanostatino 5M XW
Top
Thu, 01/05/2023 - 10:41
(Reply to #14)
nc8q
nc8q's picture
same issue with the Nanostation M5 XW.
Hi, Eric:
Please describe anew your issue.
Regarding 'same issue as David W5CWT;
David mentioned using the AREDN GUI to upload a factory.bin.
Usually the TFTP method is used with a factory.bin.
Usually the AREDN GUI method is used to load a sysupgrade.bin.
A sysupgrade is from an AREDN image to an AREDN image...not RouterOS to AREDN image. ;-)
Please state explicitly your issue.
? You tried to AREDN GUI load
aredn-3.22.12.0-ath79-generic-ubnt_nanostation-m-xw-squashfs-sysupgrade.bin

? You tried to TFTP load
aredn-3.22.12.0-ath79-generic-ubnt_nanostation-m-xw-squashfs-factory.bin

73, Chuck

 
Top
Fri, 01/06/2023 - 08:26
N7JYS
Nanostation M5 XW
 Sorry Chuck I was not a little more clear on my procedure. My M5 XW is running 3.20.3.1 so I was using the GUI upgrade method. I have not tried the factory file using TFTP load yet. It is mounted on my tower at 55 feet and not I can get it in TFTP mode with out climbing the tower. Will see :)

Thanks

Eric 
Top
Fri, 01/06/2023 - 12:56
w6bi
w6bi's picture
Remote TFTP
Eric, most of the Ubiquiti power injectors have a remote reset button on them accessible by a tiny hole (a large paper clip works pretty well).   By using that you can put a remote Ubiquiti device into tftp mode.   While you can't see the device LEDs, you can confirm it's in tftp mode by pinging 192.168.1.20 and seeing if the device responds.

Note - this only works for Ubiquiti devices.

Orv W6BI
 
Top
Sun, 01/29/2023 - 19:38
N6OIL
Same Issue as Eric

Hello all, new to the game here but I do know my way around IT. I have a NanoM5 that I have tried loading 4 different types of bin files and all get the connection refused error. I can ping the radio at 192.168.1.20 I'm afraid this might be bricked because just doing a simple reset I can't get into the ubqt gui.
I'll monitor this thread and maybe Eric will have a solution that will work for me.

Rory
N6OIL
 

Top
Sun, 01/29/2023 - 19:47
(Reply to #18)
N6OIL
Update

I was able to get into the factory GUI which is on 6.3.6 (XM). I'll try a GUI xfer from it.

Rory

Top
Sun, 01/29/2023 - 22:16
(Reply to #19)
N6OIL
Update #2

Bloody firewall, yup, turn off Windows Defender, and Bob's your uncle, I'm in. Now for the fun part, configuring my station.

de N6OIL

Top

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer