Took delivery of my first RB1200. The first two times I applied power, it failed to boot: no initial beep, not even output to the serial port. The third time it booted into RouterOS normally. After / system reboot, it stopped after displaying “Restarting system.” and I had to remove & reapply power–which occasionally works, but usually does not.
Overall I’m seeing ~90% failure to run the boot loader upon power-up or reboot command. I see a slightly better rate if I hold down the reset button to force the default boot loader, but even that fails to load much of the time. Sometimes the green LED will come on and stay on; sometimes it doesn’t come on at all. Rarely, the boot loader will start but print garbage rather than the “MikroTik” logo, sometimes it says “not an elf header” and tries bootp, then locks up before it finds the netinstall machine.
None of the following measures have made any difference:
upgrade to ROS 5.24 (boot loader 3.02)
downgrade to ROS 5.22 (boot loader 2.38)
downgrade to ROS 5.11 (boot loader 2.37)
using the reset button to force the backup boot loader
reducing CPU speed to 666MHz
format NAND
force backup-booter loading (from the boot menu)
So… does any of this look wrong (particularly the PCI settings)?
After (re)installing 5.24 and the 3.02 boot loader, I ran a series of tests last night. 11 of 34 cold-boots failed, and 15 of 36 soft-boots ( / sys reboot ) failed. In every case, the failure occurred before the boot loader was able to send anything to the serial port. Conversely (or contrapositively ), if the boot loader launched successfully, it would reach the ROS login prompt every time.
It didn’t seem to matter how long the box was left powered on or off, or whether it was a cold-boot or a warm-boot, so I don’t think it’s a heat issue. It is as though the main board or memory board has an intermittent, low-level problem (race condition?) that makes it a coin-toss whether the boot loader will launch or hang.
At this point it’s a curiosity, as I will be returning this box–but now I’m concerned that this might be a systemic problem that affects a certain production run, rather than an isolated defect. FTR, the serial number of this particular unit is 2D720112642D/121, and the MAC range is 00:0C:42:CF:30:9A - A3.
I have 2 pieces od RB1200 on the desk. Both are freezing + failed booting … no answer from Mikrotik.
//if you change original 512mb ram to kingston 2 GB …random rebooting will disappear. But I havent got enough courage to deploy it on network.
//with original 512mb ram…router upgrade from 5.11 to → 5.24 will fail on boot…kernel error..now with 2 gb ram upgrade from 5.11 to 5.24 without any problem…
I’m having the same problem. Just bought an RB1200, upgraded to 5.24 - rebooted - it won’t boot. Had to disconnect and reconnect power to boot it. Upgraded firmware to 3.02 and rebooted (again, had to disconnect and reconnect power to boot it).
But now reboots are working (tried 5 times in a row, it reboots ok now). I’ll leave it running overnight to see if it reboots like the ohters have mentioned. Damn, I planned to deploy this one on site today.
I have a similar problem, Brand new RB1200 that I upgraded all packages to 6rc14.
The unit will reboot on command, but if I shutdown or power off the unit it will not boot unless I hold in the reset button and then plug in the power. The unit beeps after a few seconds and then boots ok.
Is there any fix for this if there is a power cut and the UPS runs dry then some has to go to site and pull it out of the rack and push the button!
Same problem here with brand new RB1200 - as in same as Hotz1 is getting: randomly on reboot the system never starts up, with no output on the serial terminal at all after “Restarting system.”
If the boot starts, everything works perfectly. If boot doesn’t work, pull power and reinsert has worked each time. Failure to boot seems to be about 1/3 of the time
Experienced the problem on all of these so far (in order):
Original firmware as shipped 5.11, boot 2.37
Upgraded ROs to 5.24, boot 2.37
Upgraded bootloader to 3.02, still ROs 5.24
Upgraded to ROs 6.2, upgraded bootloader to 3.07
After going to 6.2/3.07, problem seems to be less…maybe 20% of reboot attempts lead to no boot…but that’s anecdotal on only about a dozen reboots.
I haven’t tried any downgrades, reducing CPU freq etc., as these don’t seem to have any affect for anyone else.