Hi, I updated a firmware today on 20 pieces of RB493G, after the update I went to reboot, which needs to be done by procedure. After that none of the Routerboards did't work, all LED are constantly lighted, can't access the router over serial... Does anyone know what the problem is? Is it possible that Mikrotik has tsuch a large bug?? 20 RouterBoard 493g, this is not small money!! What should I do??

try Connect via Serial cable, and check what the boot say.

Hi!

I've seen this kind of problem before when skipping
firmware versions.

My experience is that upgrading to firware version2.39
allways works. I belive 2.39 was last in 5.19

RGDS

I can't establish connection via serial. RB is acting like is dead.

According to RB493G manual

S3 - Software Reset 1 button. Loads the Primary boot loader

Will load the backup firmware and continue from there.....

Hi did anyone resolve this?

I have just bricked my 6th RB493G

All Brand new. I had been trying to upgrade to v. 6.27 from 5.26

Routerboard Firmware was 3.18. no update available before I tried to upgrade Router OS.

The very last unit, all I did was remove the Default Config, rebooted and now I don't even giet the first beep when I power up the device.

These were bricked two at a time!

First two arrived from supplier and died after attempted firmware upgrade. I just assumed it was a fault batch as the MAC addresses were in series, sent them back and requested two more not from same batch.

Got them. Same again.

Then got 2 more from a different supplier and same again.

What am I doing!!?

I work with Routerboards all the time and have never had this issue before?

I tried to update two 2-months old 493G's from 6.25 to 6.27, both are dead now. After reboot I don't get any beep, all ethernet ports are dead, no data in console. Both front LEDs and 4 LEDs on board are on, nothing happens when trying to reset.

Grrrr.

There are three threads asking about this same problem. No solutions other than a suggestion from Mikrotik support to contact your distributor.

I guess I'll have to contact support@ to get the top secret answer tomorrow.