MikroTik CRS328-24P-4+ Firmware & Boot loop & Kernel issues

RouterOS General
1

Dear Members

Please assist, I’ve having issues with my CRS328-24P-4S+, I suspect there was a power failure during the firmware upgrade script.
So firstly the CRS is in a boot loop.
I’ve connected to console port and connected with HyperTerminal / Putty.
Also kept Netinstall running with boot server enabled (192.168.1.2) and my pc being in same /24 subnet (192.168.1.1/24)
Downloaded the stable RouterOS 6.49.8 npk file for the ARM architecture.

Currently console view is:
“”
BootROM 1.41
Booting from SPI flash
BootROM: Image checksum verification PASSED


RouterBOOT booter 6.49.8

CRS328-24P-4S+

CPU frequency: 800 MHz
Memory size: 512 MiB
Storage size: 16 MiB

Press any key within 2 seconds to enter setup..
trying bootp protocol…
BootROM 1.41
Booting from SPI flash
BootROM: Image checksum verification PASSED


RouterBOOT booter 6.49.8

CRS328-24P-4S+

CPU frequency: 800 MHz
Memory size: 512 MiB
Storage size: 16 MiB


trying bootp protocol… OK
Got IP address: 192.168.1.2
resolved mac address C8:4B:D6:35:1D:73

********************************************************************************"

Tried also the backup bootloader, no success.
Also sometimes receive “Kernel not found message”

Can’t get it to appear also in Netinstall, but should be able to get it to appear in Netinstall if the system boots to the correct stage/mode.

Thank you!,

2

sometimes if you put a dumb switch between PC an MikroTik that helps to make Netinstall sucess

3

Thank you for the suggestion, but didn’t resolve it at first.
But I’ve started to check what will be the outcome if I work with different firmware versions that I extracted from the routeros-arm-6.49.10.npk file.
Loaded it on the CRS via serial connection, and download the same NetInstall version (used 6.49.10) this time I managed to get it to appear then NetInstall.
So installed the RouterOS (6.49.10) and managed then to set it to boot from NAND and booted fine and started the MikroTik service/packages.
Managed then to get it into Winbox, and re-configure the device in the network.
All good and working…YEAH, finally!

Btw…had a dump switch plugged in during this process, so maybe also assisted in getting it into NetInstall recover mode.

Thank you!