I recently purchased my CRS210 and it worked fine when I received it. I made all my changes and it worked fine.
I decided to upgrade it to 6.35.2. After completion it rebooted but just sat there with the green light blinking.
After about an hour I unplugged it and plugged it back in and it just stayed in the same mode with the light blinking.
I then power cycled it and pushed the reset button and it defaulted the box and I verified it had upgraded the software.
Now anytime I reboot or lose power the box just sits there and won’t reboot unless you turn it off and power it up with the reset button pushed.
I downgraded it to 5.26 and have the same result so I upgraded it again using Netinstall. Same result.
I see where this problem was mentioned several years ago but no resolution except upgrade. I am new to Mikrotik and I am excited about the possibility of using these routers for our VOIP installations but I am having second thoughts now.
I followed all the procedures on the wiki for this and all indications are that it was successful. It is simply this booting issue.
Any suggestions.
Judging by your problem description it seems that main bios is failing and you are forced to run device with backup bios.
- Netinstall CRS back to latest v6.xx.xx version (if you haven’t already). As ROS v5 is not supported on these devices.
- Regarding that startup problem. Try starting it up once again with reset button and then run bios upgrade. That should rewrite the main bios and possibly fix the issues that you are having with the device.
* /system routerboard upgrade
* (y to accept action)
* /system reboot
Perfect. That fixed it. I will make sure to check that in the future. I didn’t realize you had to do that separately from the Software upgrade. Just for future reference, does the software upgrade load the new firmware? If so should I always check after a software upgrade to see if the firmware needs to be upgraded. If this is so then how would I upgrade a remote router as this one was unreachable after the upgrade without a physical reset?
Only in some rare cases we push forced firmware upgrade, in other words when it contains some critical fixes. Normally you have to do it manually via the same method I as posted before.
In this case I do not think that it was old FW problem. I guess it could simply have been corrupt main FW. While such problem is an rare occurrence it is still a fairly annoying one. And this is really where dual bios feature comes in handy.
Thank you for the clarification. I am very pleased with the router and your quick response.