rb450 reboot problem

i have lot of rb450 and rb450g, when i am rebooting them it cannot start and i after i need to reboot it from power,

its very big problem for me because i have them on towers so on evry reboot i need to go there and reboot it manualy,
what can be the problem?

It would be great you can get one of the boards from tower, and check the console output to have more information about the problem.

and what about supout.rif, will it help?

I have same problem with RB450G ROS 4.16
It’s not reboot - it shutdown when you try to reboot it.
Good solution - downgrade to ROS 4.13
In downgrade process it will shutdown too, and need to unplug power.

shrek777
I’m not sure support output file will help, console output + support output file will be great.

Rusteko
Do you have the latest firmware (/system routerboard print shows it)?

Same problem whit RB450G ROS 4.16 , when I reboot from Winbox it shutdown, and need power restart to start.

More information is required about your problem. The best option is to report the problem to support (support@mikrotik.com) with the following information,

  • attached support output file;
  • console output after reboot command.

This is output from my RouterBOARD 450G, where RouterOS 4.16 is installed (the latest firmware is installed as well),

Reboot is from Winbox,

MikroTik 4.16
Sergejs_Switch Login: 

Rebooting...
Stopping services...
Restarting system.
?

RouterBOOT booter 2.29

RouterBoard 450G

CPU frequency: 680 MHz
  Memory size: 256 MB

Press any key within 2 seconds to enter setup..
loading kernel from nand... OK
setting up elf image... OK
jumping to kernel code
Starting...
Starting services...

MikroTik 4.16
Sergejs_Switch Login:

Small point I noticed…


I have a 450G running 4.16. I experience the “crash on reboot issue” occasionally. I can reboot with no problem MOST of the time, but the common factor I notice is this:

Occasionally, when adjusting rules (mostly in ip>firewall>filter or >queue tree) in winbox, the window will freeze up. All buttons lock and only after a couple minutes (or minimizing and then maximizing winbox) does the window free up and will respond again. I usually close the window and re-open at that point.

The reboot into shutdown issue almost always happens if one of these window freezes has occurred during the router’s uptime. If no freezes have occurred, it tends to reboot perfectly.

Perhaps that means something to Mikrotik?

Any new developments on this? I had a router do this tonight. 493G Running 4.16. Anyone have this happen with any other routers besides 450 series?

This is a big fear for me as a lot of my routers are half a days trip away.

I had a 450g do this a few weeks ago, I just thought I choose shutdown instead of reboot but now I think it was this issue. I have a extra 450G and i’m gonna try to reproduce it tomorrow. My routers that have had it happen are running OSPF and PPPoE server and some PCQ queues if that helps

Only this I have is log entries that show: “: terminating… - system is going to shutdown” when I chose reboot in winbox

45 min later I was at the tower in the cold power cycling it

I have same problem again, so i willnot reboot mikrotik until this problem will be solved :slight_smile:

Same here but sometimes reboot is necessary. Gonna mess with my spare 450g later today.

Please describe powering of those Routerboards. Can you reproduce this problem using default configuration?

my configuration is very simple, i have bridge interface, pppoe server and thats all

We too are seeing this. We don’t use Winbox. I was terminated in the one time and the box just sat at a blank screen instead of rebooting.

Are you by any chance using microSD flash with these units that are failing to reboot?

Tom

No.

The boards simply shutdown rather than reboot.

Can anyone post console output after reboot command as requested by sergejs?

Em

No, because there is none. The system just shuts down.

i have one rb1100 with the same problem

if i trigger a system reboot command, the routerboard never came back again. only if i took the power off and on.

no console messages.