Hello.

Using winbox, i saw an update pending ( 7.4rc2)

Chose to update and install

crs305 went rebooting - verrrry long time

after reboot, the sfp+ leds 1-2-3-4 are blinking once every 40 seconds

no sfp+ link are establish with my 3 devices connected to the crs305

no winbox access via crs305 IP
winbox doesnt see any crs305 in neighbors list

conclusion, crs305 is bricked due to firmware fucked

SO

tried netinstall

tried using sfp+ but no link

tried using eth/boot with IP sets to 192.168.88.1

crs305 not seen by netinstall ( tried all netinstall version ) !

----------

I don't know what to do anymore.

This is not the first time i had issue with firmware update on this crs305.
To be honets, almost every update were funcky. Never been straight forward once !!
But i always was successful with the netinstall process.
But this time, i am stuck and bricked.

Should i consider the unit dead and switch to a more friendly pieces of hardware...

I am no beginner, but i am so fed up by this model.

IF ANYONE HAS A STEP BY STEP WAY TO UNBRICK THIS UNIT, I WOULD BE GRATEFUL...

did follow this https://wiki.mikrotik.com/wiki/Manual:Netinstall but no success !

try netinstall using a simple switch between your PC and the CRS

if you are not sure you are triggering netinstall put another mikrotik between your pc and the CRS when you trigger netinstall you will see broadcast RX counters increasing on eth interface connected to CRS

sometimes netinstall works at first try, someothers netinstall is a matter of pacience, but is worth it to recover a device


take a look on this topic
viewtopic.php?t=182373
item H

a splendid guide about netinstall and other matters

Hi,

Netinstall is trigger fine, RX count increasing ok...


To be clear:
- I have a win PC set to 192.168.88.8/255.255.255.0/ with dns and gateway set to 192.168.88.1
- My CRS305 seem's to be in netinstall mode ( led for Eth/Boot is kind of blinking )
- From time to time, it seem's to start a new netinstall loop ( all green leds E-1-2-3-4 are blinking once )
- netinstall is start... nothing happened. No device discovered.

--> bricked

of course, switch the eth cable in case of defect...

Did you follow all of the documented steps?

For instance, I don’t see where you say you disabled all the auxiliary network interfaces to ensure there’s only one externally-facing route. Common causes of failure here are leaving the WiFi link up.

Did you follow all of the documented steps?

For instance, I don’t see where you say you disabled all the auxiliary network interfaces to ensure there’s only one externally-facing route. Common causes of failure here are leaving the WiFi link up.

including virtual interfaces like Virtual box created etc