Bough a new CRS317. Upgraded the RouterOS and the device went into a continuous booting loop.. I eventually did a netinstall with installation finished successfully but on reboot the CRS317 will not go pas jumping to kernel code. See below.Any help will be appreciated
I experienced the same symptoms.
I got the cooperation of Mikrotik support, but eventually I was instructed RMA.
I think that it is better to tell the support details to the symptoms. After that, as I think, you will be directed to RMA.
I have the same problem with a whole batch of CRS317-1G-16S+ switches.
I managed to upgrade two of them successfully by installing 6.41.1 and upgrading the RouterBOOT firmware to 6.41.1. The routers shipped with 6.40.5. My mistake was to upgrade the others directly to 6.41.2 and skipping 6.41.1 and not upgrading the RouterBOOT firmware. They are now all bricked. I can still boot into SwOS though, but that’s not what I want.
Below is output of switch that succesfully upgraded, as you can see the RouterBOOT firmware is at level 6.41.1
In summary: Upgrading directly from 6.40.5 to 6.41.2 results in bricked switches with exactly the same symptoms as others here described. It seems like the shipped RouterBOOT 3.43.2 is incapable of booting 6.41.2 or later (have tried even the RC candidates).
Downgrading to 6.40.5 via Netinstall also results in the same problem, kernel never loads and “Starting…” never appears. I can successfully run netinstall and install any of the later releases, but the kernel also never loads And now I can’t even downgrade to the orignally shipped RouterOS.
So it seems like there is a RouterBOOT problem, perhaps a flash variable that gets changed or something that stops the kernel from booting post upgrade.
Mikrotik, if you could make available the dx3230L_x.xx.fw firmware file for RouterBOOT 6.41.1 I will try to upgrade the RouterBOOT to see if it resolves the problem.
Hey, guys. I have the same problem, too. wrote in support of Mikrotik waiting. Here’s what I wrote in support:
After updating the firmware on CRS317-1G-16S+RM. Lost the ability to connect to the switch on all possible ports. RJ45, Serial. Did the firmware upgrade via Netinstall version 6.40.5. This did not help and the switch cannot be connected. When the switch is turned on, 1 beep occurs, SFP ports do not work when connected to them. Indication only on RJ 45 boot is lit, but there is no connection to the switch anyway. What could be the matter? To hand over a guarantee to the seller?
Xmodem Method
If there is no IP connectivity with your RouterBOARD, you can also use the Serial Console XMODEM transfer to send the FWF file to the router, while connected via Serial Console. From the Bootloader menu it’s possible to upgrade the firmware with this method. This method is the last resort, and should be used only if the first two methods are not available.
have installed firmware 6.41.3. Mistake has remained.
RouterBOOT booter 3.43.2
CRS317-1G-16S+
CPU frequency: 800 MHz
Memory size: 1024 MiB
Storage size: 16 MiB
Press any key within 5 seconds to enter setup.....
loading kernel... OK
setting up elf image... OK
jumping to kernel code
Same problem here… Got two of these switches, one completely bricked and the other one working at 6.41 but gets bricked if I install anything newer. Already made RMA…
But this will be a problem once people start upgrading these switches… Mikrotik should find a solution soon.
I came back from RMA for the time being.
(It is unknown what kind of correspondence was done)
However, after confirming startup, Fault-led became lit this time, so it became RMA compatible again …
Downgrade from RouterBOOT booter 3.43.2 to 3.41 solve this problem or not?
What was the result you got after updating RouterBOOT using this file: http://i.mt.lv/routerboard/files/dx3230L_3.41.fwf?
We managed to get RouterOS to boot again after finding in a Russian forum (unfortunately I do not have the link at the moment) a tip to downgrade from RouterOS to version 6.40.5.
We did the installation using NetInstall 6.42 with RouterOS 6.40.5 [https://download.mikrotik.com/routeros/6.40.5/routeros-arm-6.40.5.npk]
After that RouterOS started to initialize normally.
Now the question remains, should we keep this version forever? Can we never update RouterOS?