I have CCR 1026-12G-EM which running NAT + Firewall +DHCP server.
When I trying to reboot this device I get “routerboard configuration” message on LCD screen and compleet freeze of device. It’s not accessible even by winbox! I have to power off severak time to start it working!!!
First time I did 2 time of power disconnections. Last time I did power disconnectons 4 times in order to push it to work!
Currently I am runing ROS 6.18. Is there anybody familiar with the same problem? This is absolutelly nighmare for production network!
Already done. But I am really afraid to make upgrade due to this issue. I need to prepare at least backup router for the same configuration. So I wondering is anyone have the same issue? Maybe it was some fix in changelog?
I bought spare CCR-1009-8G-1S in order to create backup router in case of problem with main. It was in default configuration with ROS 6.25. I put 6.27, selected System->Reboot and … again the same story!
Brand new device without configuraton don’t want to reboot. I have to remove power 3 times in order it start to work.
Then I’ve tried to issue reboot one more time. Finally I got brick! Removed power 10 times, did reset to default - no result!
Can anybody explain me what’s going on? How I can get money back? Anybody has the same problem? Just try to reboot you CCR!
I had a similar issue with early 1009’s. They would appear to freeze at power on or reboot. If you let them set like that after roughly 5 min they would finish booting. After a few upgrades of routerboot they stopped doing that and run fine.
I have quite a few later models out and dont have that issue anymore. Just a few dead after a week but that’s a separate issue.
Here is reply from Mikrotik support team. I did step 2 with netinstall. Sowething was wrong during regular software upgrade. You need console cable of course.
Hello,
Power your device off;
Press and hold reset button;
Power device on;
Hold reset button pressed for 1-2 seconds and then release;
If device boots up, then run command “/system routerboard upgrade”
If you have managed to do both of the things above (fresh firmware and version of
RouterOS), then unfortunately you will need to send this device to RMA. Seems more
like an hardware issue, but I advise to perform fresh installation in case it helps.