Hi, I have a GL.iNet GL-MT3000 (firmware OpenWrt 21.02-SNAPSHOT r15812+912-46b6ee7ffc)and as of today, when I reboot the router, I have to press and hold the reset button for 4 seconds then release to repair your network, otherwise I can't connect to the router, either via Wi-Fi or Ethernet. the light on the front is set to blink on network traffic, but after a reboot, it just stays on. so after the repair of the network, everything works normally. the question is, I can't troubleshoot till after the repair, and at that point, everything is working normally, what can I do to troubleshoot this issue.
Thanks
Well, you can't access it during startup, but you can do a logread afterwards, searching in the first few seconds of startup, when the LED changes from blue to white. But if the reset works, I would look through the startup settings and exclude the network settings, then crontab and rc.local. Even if there is nothing directly interfering with the network, there may be something creating conflicts and blocking it until you get past them. Unfortunately, the best thing is always to remember what you did in luci and ssh before it happened. Or sweat over logread.
Thank me.fab for responding, I was able to get an export of the logfile the first time. But since then, I've not been able to get back into the router. and the worst part of all this, is have haven't made any changes to the config in the last 6 months, and it's been working fine, so there's nothing I would be able to change, even if I got back into the device.
Now, whenever I boot up the device, the LED blinks blue, and never goes to white, and I'm not able to access it at all. I've tried doing the repair, and that isn't working anymore, and I've tried doing a factory reset, and that isn't working either. I'm thinking something actually broke in the device, but I'm not even guessing how that could happen, as it was mounted after from everything.
I'm going to try doing some more factory resets and see if I can get back into the device at all, and go from here, but I have a feeling I'm going to need to replace the device
Thanks again for your help
In the worst case scenario (if you have corrupted the firmware partition), you can reset it from the u-boot bootloader and the firmware for your model downloaded from gl.inet as described here Debrick via Uboot - GL.iNet Router Docs 3
Otherwise, it's a hardware problem and you can throw it away.
Apart from that, you're really unlucky if you just have the log to find the bug and it crashes completely.
I have to thank you me.fab!
I couldn't get into the device at all, so I followed the instructions you sent for unbricking my device with Uboot, which worked. I was able to get back into it and redo the configuration, and it seems to be working mostly. But I can't use the ethernet ports(1 LAN, 1 WAN) without the device locking up and having to do the network repair after unplugging anything from the ports. So it seems I still have something wrong with it, but at least now I can get into it and work on it.
Thank you again for that link and that information!
What if the problem is the cables you connect to the ports? If they have a short circuit, they block everything. Try others, even ordinary ones, and try connecting different devices, just to see, including the ONT, check locally.
Yea, I thought of that, and had already replaced them, with no change. but thanks for bringing up just to double check. Thanks
If I think back to how you could restart it with a reset, it's still possible that it's a software problem. If for some reason it kept your settings, you can delete them manually from ssh with rm -R /overlay/* followed by reboot. I would do it, but I take no responsibility if you try it, you may have to go back to u-boot.
I'll keep that in mind, except when it locks up, I can't connect to it to even ssh into it.
I've already have a replacement device coming, just in case. Since I have whole network connecting to this router as my gateway to my internet device.
you can connect wifi to ssh, locally, no need wan
no, when this happens, I can't connect to it via wifi or ethernet, it's pretty much bricked, until I do the network reset.
I've been using for the last day without issues, and I'm just going to replace it when the new one comes it, then I can really play with it,since I won't have to rely on it for most of my network access.
If you weren't among the first to buy it, it should still be under warranty, even if you ordered another one, if you didn't fail it they will replace it and resell it or gift it. See you elsewhere, bye
That's my plan, and thanks again for your help!
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.