You are here

Problem with upgrading Miktrotik LHG XL 2

10 posts / 0 new
Last post
KN6RVU
Problem with upgrading Miktrotik LHG XL 2

Trying to upgrade my Mikrotik LHG XL 2 from 3.22.12.0 to 3.23.4.0.
Using the "Downloading AREDN Firmware" website, I downloaded:
 
aredn-3.23.4.0-ath79-mikrotik-mikrotik_routerboard-lhg-2nd-xl-squashfs-sysupgrade.bin
 
Using Setup --> Administration, I uploaded the file and the page stated "Uploading Firmware".
After about three minutes the unit reboot and came back unchanged.  Tried several time with same results.
 
I then tried using "Download Firmware" on the unit.   Refreshed and selected from the list:
 
aredn-3.23.4.0-ath79-mikrotik-mikrotik_routerboard-lhg-5hpnd-xl-squashfs-sysupgrade.bin
 
The unit started to upgrade and never came back.  It became a brick.  I had to reload the entire system by pushing the reset button on the dish, and reloading rb.elf, sysupgrade.bin and 3.22.12.0.
 

File Attachment: 
AB4YY
I've also bricked (or

I've also bricked (or whatever the correct term is) LHG's before, two times, but they were 5 GHz units.  I think (not 100% sure) that I may have attempted to do a sysupgrade with the wrong firmware, by accident.  I didn't think that could happen but the units sure were locked up and had be be removed from their outside locations and do the initial load.

The LHGs I have been using are LHG 5 GHz units (RBLHG-5HPnD-XL).  From the photo you attached looks like it might be the 5 GHz firmware and your unit is a 2 GHz unit?

- Mike

KN6RVU
No choices
Thanks Mike for the response.
 
The file from "Downloading AREDN Firmware" website wasn't accepted.
aredn-3.23.4.0-ath79-mikrotik-mikrotik_routerboard-lhg-2nd-xl-squashfs-sysupgrade.bin
 
The selection (see attached) from the "Download Firmware" for 3.23.4.0 was only:
aredn-3.23.4.0-ath79-mikrotik-mikrotik_routerboard-lhg-5hpnd-xl-squashfs-sysupgrade.bin
which killed the unit.
 
No other choices.
 
Image Attachments: 
nc8q
nc8q's picture
Downloading firmware
Go to https://www.arednmesh.org/
Hover your pointer over 'Software'.
Click 'Download'.
Click the big red 'Download' button
Type 'lhg' into the 'text box'.
Select 'MikroTik RouterBOARD LHG 2nD-XL (LHG 2)'.
Click the blue 'Sysupgrade' button.
Use
'aredn-3.23.4.0-ath79-mikrotik-mikrotik_routerboard-lhg-2nd-xl-squashfs-sysupgrade.bin'
to upgrade your 'Mikrotik LHG XL 2 from 3.22.12.0 to 3.23.4.0'.
Although, next, you may need to do a 'tftp' install.

73, Chuck
 
KN6RVU
Didn't Work
I started with that file 4 days ago.  After the 3 min "Updating Firmware" there was no change, it remained 3.22.12.0.

In investigating the problem, I found that the LHG dish wasn't processing the update.  When selecting the upload button and the "Updating Firmware" appeared, I refreshed the status and the status immediately appeared.  It actually didn't start updating.
 
I then tried uploading the present version 3.22.12.0 and it took 3 min to reload the firmware.  The dish doesn't like something about the update.  Unfortunately it doesn't indicate any error message.

What did you mean, do a TFTP install.  When I used the file in the dish "Download Firmware" which was:
 
aredn-3.23.4.0-ath79-mikrotik-mikrotik_routerboard-lhg-5hpnd-xl-squashfs-sysupgrade.bin
 
it bricked the dish and I had to reload the all of the firmware.  Starting with pushing the reset button on the dish, tftp rb.elf, downloading sysupgrade.bin and version 3.22.12.0.
 
AJ6GZ
other way...
I don't think I had any issues with my LHG-5 XL (Don't have a -2), but an alternate way to force an upgrade is to use 'scp' to transfer the file to the node running 3.22.12.0. Use WinSCP or your favorite linux command line. Drop the file in the /tmp folder. Then ssh in to the node and run sysupgrade -F ./tmp/aredn-3.23.4.0-ath79-mikrotik-mikrotik_routerboard-lhg-2nd-xl-squashfs-sysupgrade.bin
KN6RVU
Need Help
Did port scan on node IP address.  Only port open was 80.
 
WinSCP was refused connection on port 22.
 
WU2S
WU2S's picture
try port 2222
try port 2222
nc8q
nc8q's picture
Alternate loading of firmware from AREDN device

Go to

Scroll up to
"As an alternative to using the node’s web interface, you can manually copy the sysupgrade"

73, Chuck
 
KN6RVU
Problem Solved !
Thanks everyone for your help.
 
Chuck (NC8Q) got me headed in the right direction with his last post.  By using the "alternative" method, I was able to see the node response.  

Investigating further, I was able to determine the problem.  In my old "Mikrotik First Install Checklist" they used "factory.elf" to be rename "rb.elf".  In the new checklist, they use "initramfs-kernel" to be rename "rb.elf", which is specific to the device.
 
Using the correct rb.elf allowed uploading the 3.24.4.0 version.

 

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer