We are facing a problem here with at least (at the moment) 5 RB2011UiAS-RM routers. The problem is that for unknown reason after a reboot of the router it won’t come up. It reboots all the time after starting services. These are all placed in various remote locations and access to them by our IT staff is difficult. With the help of local users there i managed to netinstall them again and re-applied the configuration. I currently have one here so i can do any tests you might have in mind. I connected console on it and i see that after starting services the systems stays on the login screen for about 5 secs and then reboots. No error message no nothing. I also did a memory test that is built in on the Routerboot-configuration menu but everything completed successfully. Keep in mind that all of our routers are powered by big online ups and also keep in mind that one of them started acting like that after i did a reboot on it. I have already tried to change power supply but the problem remains the same. Is there anything else that i could try or anywhere that i could look for a solution?
Routeros V6.11 routerboard firmware 3.12 on all of my routers and no the problem is still not resolved. The thing is that i can’t identify what caused the problem. All of the routers worked fine for about 2-3 weeks and i even did a reboot remotely when needed with no problem since their installation nothing else changed. Why suddenly they stopped responding?
First time powering it up, it went into a reboot-loop after “starting services” displayed on the LCD.
I’ve rebooted the unit, and the router booted up this time, but i’m worried about the uptime capability of this unit should a power-loss or reboot occur.
Please let me know if there’s a known fix for this.
I have the same problem with several RB951G-2HnDs (ROS 6.7). The devices have been running for months and some day they suddenly started the reboot loop.
This seems to be a general problem of MikroTik (some of our customers reported this kind of problem a couple of months ago, too).
So far MikroTik has been advising to upgrade RouterOS, but this does not really solve the problem (we started with 5.25 and have reached 6.7 now).
If MikroTik agrees, I could ship the device to the factory in order to investigate the issue.
Our problem: 92 devices are about to be shipped to customers and there has been no solution so far…
thank’s for the reply “Try with netinstall procedure.”
I am aware of this (and it usually works), but it’s not about reviving a single (or some) routers.
The problem is, that the reason for the failure is not known. It may happen again any time - with new devices or with devices that have been running for quite a while. In that situation it’s hard to keep confidence in the product.
This is a general quality problem that is supposed to be investigated and solved. For that reason I suggested to ship the faulty device to MikroTik. Merely “netinstall” it does not help anything for a solution of the problem.