CRS CRS354-48G-4S+2Q+RM does not boot

RouterOS General
1

Hi there,

I have a new CRS354-48G-4S+2Q+RM and it was preinstalled with routeros.
To have an easier setup I wanted to use SwitchOS on this device.

So I started winbox → went to System → Routerboard → and then went to Boot OS and selected “Switch OS” and rebooted.
Since that reboot I cannot access the Winbox anymore.
The network interfaces don’t come up, as it seems, because when I connect eth1 to PCs network interface the lights on ethernet-port dont come up, no data are transferred and I dont get access to the switch.

To make a netinstall I then tried to press reset-button when the device is without power, then I plugged in the power plug and keep pressing reset button until light goes out as described in the manual to start network boot. But this doesnt work either. The device doesnt come up.

Interesting: For this device “switch os” is not mentioned in operating systems in technicals specifications
https://mikrotik.com/product/crs354_48g_4splus2qplusrm#fndtn-specifications
So maybe this device doesnt support switch os at all. But why could I select “switch os” as a Boot OS in winbox menu?

Does anybody know how to get the device working again?

Regards
horstkevin

2

If you have a console cable, you should be able to see the Routerboot menu and use the backup bootloader or choose other boot options.

https://wiki.mikrotik.com/wiki/Manual:RouterBOOT

3

Thank you for this hint - I dont have such a cable yet, but I can get such a cable if this is a solution that definitely works.

What about the management port that is located under the console port? Does it also have the ability to access the switch if it doesnt boot anymore?

4

Those ports are only useful if the device boots. If it is stuck at the RouterBoot menu, you would really need a console cable.

5

Hi biomesh,

just wanted to show that I have instantly build a serial cable mac gyver style :wink:
20200915_004701-small.jpg
And you will not believe it: it worked!
I could connect to console and set boot os back to routeros.
Now everything works fine! :slight_smile:

Thank you very much!