Same problem here. Router locks up hard on boot after upgrade to 3.12. Have power cycled several times and tried changing bios settings (Glad it’s not just me). I hear the 2 beeps after boot and it takes my username, then just locks up every time. It’s not pingable or anything. Intel P4 2.6Ghz single core (1M Cache) / 512MB RAM / Intel board.
What can we do? I’m going to really freak out if I lose my config! This is the replacement router for a 250+ user apartment complex and I just got everything working properly. Please Help!
Lol, here is a hint from my many years of experience in the Telco and Enterprise sector. Never apply new firmware builds to a production environment without doing your own testing! and thats not just for Mikrotik it applies to all critical IT infrastructure.
Yes, yes, agreed - those are great rules to live by but it still does not change the fact that MT may have just introduced one of the biggest bugs in their history. The fault here lies (mainly) with MT - IMO.
Not following proper upgrade protocol doesn’t change the fact that MT widely distributed a horrendously faulty and completely broken update. We updated like we always do and this box is completely hosed now. This absolutely should have been tested by MT - PERIOD. I believe this does give us some right to vent.
BTW, this was a replacement box (not live - but supposed to go live tomorrow morning - thank god it wasn’t). So, I wasn’t applying in a production environment (this time). This will just delay our deployment deadline by a few days, cost us valuable time and further agitate the customer(s). I guess it could always be worse though.
This has me very hesitant to apply an upgrade to a pre-configured MT box ever again, which makes me very sad. I feel like we are now approaching the M$ update model. I have been known, once in a while, to upgrade a live production box in a pinch - never again! BTW2, not everyone has the time or money for a lab environment (e.g. people that buy extremely inexpensive routing software like MT). Luckily, we usually do. I guess we’re just so spoiled because all of the previous upgrades have gone so flawlessly.
I sincerely wish the best of luck to all affected by this. Good Luck!
I know you might say where is your backup? I was so desperate and frustrated with Mikrotik halts that I totally forgot about that. that is my mistake as well. however I have a bit of a old backup, before one full day of work which I have redo again.
I was just wondering if they actually test a new version or if there is any beta stage for a introduced version? there is no guarantee if these things happen or not when you upgrade, but mikrotik support will not answer if you’re not on latest version (which may be a total disaster like this case)
Guys - what configuration did you have on those routers??? Maybe it is related to specific configuration (user-manager, dude ,etc) - I for instance have no problems so far with upgrading
today I install clean and keep old config.
MT seem workin good.(I used 5-10 min. under 70mbit traffic) When I install ssh-key and connect with ssh then MT crushed.
yeah! Xen package is evil! you can install it, but you cannot uninstall! if you remove Xen, the router still shows “Loading system with XEN”, not “… with initrd”. so I had to downgrade to 3.10 and then upgrade back to 3.11 w/o Xen =(
Router just dies after 3.12 install.
In my case mutli cpu is not the cause.
I have got 3.11 working for some time.
I upgraded it to 3.12 BANG router goes Bye Bye
I reinstalled 3.12 formatting everytHing. I setup everything EXCEPT some simple Queues.
Working without problem for about 8 hours.
Later I just adD 1 simple queue!
BANG Router gone again. No response!
This time setup was painful, really really painful because it’s day time all my customer shouting at me. And my BGP session refuses to go online!
THANK YOU MIKROTIK! THANK YOU VERY MUCH!
YOU RUINED MY BEAUTIFUL DAY WITH YOUR UNTESTED BUGGY UPDATE!
THANK YOU!