Arm based LHG5AC ros 6.40.3 (fw3.43), cannot upgrade nor downgrade, cant touch wlan
whenever I disable or try to change wlan protocol it results in
sudden reboot and prints in LOG:
"kernel failure in previous boot"
tried to upload new fw and reboot it cutting power off ( by omnitik managed POE )
results no upgrade and file from file list disappears.
ordinary /sys reboot with new ros files also doesn't upgrade and prints
kernel failure....

any IDEA how to get this crappy piece of hardware to work ?

I had similar results with other products too (disc5, SXTsq AC).

I contacted Mikrotik support (with sipout.rif), and their advice was to reinstall RouterOS.

I managed to recover all devices by doing a hardware reset. I did not try to reload my backup, in case the problem comes back.


Sent from my iPhone using Tapatalk

reinstall with netinstall?

Particular routerboard is xx km away on a mast. So netinstall is no acceptable solution for me :/

Support recommended a full reinstall using netinstall, but I was lucky to get away with software reset (either with /system reset-factory-defaults or by holding reset button).

I had the same concern, as one of the devices I had to reset was also on a highsite. But unfortunately there does not appear to be any other solution (and yes, I tried everything from manually upgrading, uploading upgrade with ftp etc).

I suspect the problem comes in when restoring a backup from a version which is not fully compatible.

That said, in the one instance it was a new config which acted up (SXTsq).

If you have alternative access to your router (via LTE etc) perhaps you could try manual reset and reconfigure remotely.


Sent from my iPhone using Tapatalk

ok, I did manage to reset to default remotely ( lucky me i'm on eth side )
and after testing similar ARM AC mtik on workbench i figured out that
on 6.40.3 You can not change back from nstreme to other wireless protocol.
as long as nv2/80211 is choosen there is no problem, but setting nstreme renders device
into dead end -> kernel failure.
so I reset to default, than upgraded to last RC and voilla now have decent uptime with reasonably good throughput.

Thank You for advice.

Only my pleasure [emoji4]

Thanks for sharing your findings (about nstreme causing the issue) - I really appreciate it.

G


Sent from my iPhone using Tapatalk