Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MikroTik RouterBOARD LHG 2nD-XL refuses to take Nightly 2024 #582

Closed
k6ccc opened this issue Dec 24, 2022 · 10 comments
Closed

MikroTik RouterBOARD LHG 2nD-XL refuses to take Nightly 2024 #582

k6ccc opened this issue Dec 24, 2022 · 10 comments
Assignees
Labels
bug Something isn't working

Comments

@k6ccc
Copy link

k6ccc commented Dec 24, 2022

Updating my assorted collection of nodes to Nightly 2024. So far, all have gone well except a LHG 2nD-XL. Staring from Nightly 2002 and using the aredn-2024-fa898cc-mikrotik-lhg-2nd-sysupgrade.bun file. Node appears to update normally, but comes back to 2002 and uptime does not show that it rebooted. Repeated many times and have manually rebooted and power cycled with no change. My speculation is that because the update page shows that it is a hardware type of rb-lhg-5hpnd-xl (always has), that the update is showing the incorrect firmware type and rejects the update. Support file attached.
LHG 2nD status page
supportdata-K6CCC-RB-LHG-2nD-XL-202212241304.gz
LHG 2nD update page

@aanon4
Copy link
Contributor

aanon4 commented Dec 24, 2022

You wouldnt have a link to the specific nightly this is currently running would you?

For some upgrades which are going from a generic install to a specific install, the upgrade fails to start because it thinks the image is incompatible. We can fix this, but it would be easier if I had a copy of exactly what it's running.

@k6ccc
Copy link
Author

k6ccc commented Dec 24, 2022

It was Nightly 2002 to start with. I might still have a copy of that floating around...

@k6ccc
Copy link
Author

k6ccc commented Dec 24, 2022

Should have been: aredn-2002-29d1251-ar71xx-mikrotik-rb-nor-flash-16M-squashfs-sysupgrade.bin
That was downloaded on my work laptop which I can not access remotely.

The plot thickens. My LHG 5ndHP-XL also did not update. I missed the fact that that node also did not update. Guess I was going to fast. It also was Nightly 2002 - using the same file. Support data for that one attached.
supportdata-K6CCC-RB-LHG-5HPnD-XL-202212241517.gz

@aanon4
Copy link
Contributor

aanon4 commented Dec 24, 2022

Each build contains information which says what it's compatible with, so it wont install incompatible firmware (which is nice). I will need to add this compatibility information to the relevant new builds so they know they're compatible with these old generic builds .. I just needed the generic so I can extract that info (rather than guessing what it probably is).

@k6ccc
Copy link
Author

k6ccc commented Dec 24, 2022

Man, I really was not paying attention. The LHG 5nd also did not update. It also had been 2002.
supportdata-K6CCC-RB-LHG-5nD-202212241533.gz

@aanon4 aanon4 self-assigned this Dec 25, 2022
@aanon4 aanon4 added the bug Something isn't working label Dec 25, 2022
@AJ6GZ
Copy link

AJ6GZ commented Dec 29, 2022

Report: LHG-5HPnD-XL as of build 2045 updated OK.

@ab7pa
Copy link
Contributor

ab7pa commented Jan 4, 2023

My LHG-5HPnD will take the NB firmware, but only if I use the "Load Local Image" method for the firmware install. The typical "Upload Firmware" process displays the upgrade message, but reboots to the previous firmware image without ssh enabled. A manual reboot returns the node to working state on the previous firmware image with ssh. Then I can scp the image to the node and use the "Load Local Image" process to accomplish the upgrade without issue.

@aanon4
Copy link
Contributor

aanon4 commented Jan 4, 2023

@ab7pa Whatever's going on with your node is odd. I can upgrade my own LHG-5HPnD without a problem.
Can you describe your process when it fails? Particularly, how are you connected to the node you're upgrading? Over the mesh? Over wifi. On the LAN? The actual upgrading command is the same for both your failing case as well as the one which succeeds, so whatever is failing is before that. Ping me online so we can disable the part of the upgrade process which disables logging so we can get some more info.

@k6ccc
Copy link
Author

k6ccc commented Jan 4, 2023

This was resolved a week or so ago with the introduction of separate files for 2GHz vs 5GHz. All three of my LHG nodes have been updated several times since then successfully.

@ab7pa
Copy link
Contributor

ab7pa commented Jan 4, 2023

Thanks, @aanon4 Tim -- will work with you offline.
If this issue is resolved we can close it. THX

@aanon4 aanon4 closed this as completed Jan 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants