CRS320-8P-8B-4S+ "controller issue" and "PSU1 removed from the slot"

Hardware MikroTik hardware general
1

I have a CRS320-8P-8B-4S+ that is reporting all sort of problems with the new firmware.


2025-06-10 15:40:16 health,warning PSU1 removed from the slot
2025-06-10 15:40:16 health,warning PSU2 removed from the slot
2025-06-10 15:40:18 poe-out,info ether15 detected poe-out status: wait_for_load
2025-06-10 15:40:18 poe-out,info ether8 detected poe-out status: wait_for_load
2025-06-10 15:40:18 poe-out,info ether11 detected poe-out status: wait_for_load
2025-06-10 15:40:18 poe-out,info ether13 detected poe-out status: wait_for_load
2025-06-10 15:40:18 poe-out,info ether14 detected poe-out status: wait_for_load
2025-06-10 15:40:18 poe-out,info ether16-Scraper detected poe-out status: wait_for_load
2025-06-10 15:40:18 poe-out,info ether7 detected poe-out status: wait_for_load
2025-06-10 15:40:18 poe-out,info ether3-Din_AP detected poe-out status: wait_for_load
2025-06-10 15:40:18 poe-out,info ether5-Pato_AP detected poe-out status: wait_for_load
2025-06-10 15:40:18 poe-out,info ether10 detected poe-out status: wait_for_load
2025-06-10 15:40:18 poe-out,info ether2-BAR_AP detected poe-out status: wait_for_load
2025-06-10 15:40:18 poe-out,info ether1-Office_AP detected poe-out status: wait_for_load
2025-06-10 15:40:18 poe-out,info ether12 detected poe-out status: wait_for_load
2025-06-10 15:40:18 poe-out,info ether6 detected poe-out status: wait_for_load
2025-06-10 15:40:18 poe-out,info ether4-PVT_AP detected poe-out status: wait_for_load
2025-06-10 15:40:18 poe-out,info ether9 detected poe-out status: wait_for_load
2025-06-10 15:40:23 poe-out,warning ether10 detected poe-out status: controller_error
2025-06-10 15:40:23 poe-out,warning ether2-BAR_AP detected poe-out status: controller_error
2025-06-10 15:40:23 poe-out,warning ether1-Office_AP detected poe-out status: controller_error
2025-06-10 15:40:23 poe-out,warning ether12 detected poe-out status: controller_error
2025-06-10 15:40:23 poe-out,warning ether6 detected poe-out status: controller_error
2025-06-10 15:40:23 poe-out,warning ether4-PVT_AP detected poe-out status: controller_error
2025-06-10 15:40:23 poe-out,warning ether9 detected poe-out status: controller_error
2025-06-10 15:40:23 poe-out,warning ether15 detected poe-out status: controller_error
2025-06-10 15:40:23 poe-out,warning ether8 detected poe-out status: controller_error
2025-06-10 15:40:23 poe-out,warning ether7 detected poe-out status: controller_error
2025-06-10 15:40:23 poe-out,warning ether11 detected poe-out status: controller_error
2025-06-10 15:40:23 poe-out,warning ether16-Scraper detected poe-out status: controller_error
2025-06-10 15:40:23 poe-out,warning ether3-Din_AP detected poe-out status: controller_error
2025-06-10 15:40:23 poe-out,warning ether14 detected poe-out status: controller_error
2025-06-10 15:40:23 poe-out,warning ether13 detected poe-out status: controller_error
2025-06-10 15:40:23 poe-out,warning ether5-Pato_AP detected poe-out status: controller_error
2025-06-10 15:40:26 health,info PSU1 returned to state OK
2025-06-10 15:40:26 health,info PSU2 returned to state OK
2025-06-10 15:40:26 poe-out,warning ether8 detected poe-out status: controller_init
2025-06-10 15:40:26 poe-out,warning ether7 detected poe-out status: controller_init
2025-06-10 15:40:26 poe-out,warning ether11 detected poe-out status: controller_init
2025-06-10 15:40:26 poe-out,warning ether16-Scraper detected poe-out status: controller_init
2025-06-10 15:40:26 poe-out,warning ether3-Din_AP detected poe-out status: controller_init
2025-06-10 15:40:26 poe-out,warning ether14 detected poe-out status: controller_init
2025-06-10 15:40:26 poe-out,warning ether13 detected poe-out status: controller_init
2025-06-10 15:40:27 poe-out,warning ether5-Pato_AP detected poe-out status: controller_init
2025-06-10 15:40:27 poe-out,warning ether10 detected poe-out status: controller_init
2025-06-10 15:40:27 poe-out,warning ether2-BAR_AP detected poe-out status: controller_init
2025-06-10 15:40:27 poe-out,warning ether1-Office_AP detected poe-out status: controller_init
2025-06-10 15:40:27 poe-out,warning ether12 detected poe-out status: controller_init
2025-06-10 15:40:27 poe-out,warning ether6 detected poe-out status: controller_init
2025-06-10 15:40:27 poe-out,warning ether4-PVT_AP detected poe-out status: controller_init
2025-06-10 15:40:27 poe-out,warning ether9 detected poe-out status: controller_init
2025-06-10 15:40:27 poe-out,warning ether15 detected poe-out status: controller_init
2025-06-10 15:40:31 health,warning PSU1 removed from the slot
2025-06-10 15:40:31 health,warning PSU2 removed from the slot

NO ONE is touching the power supplies.

I was able to downgrade to the routerOS I have at another site. Problem persists.

2

Went up to Beta. Problem persists.

Support is not reply to the sup files I am sending.

3

There were similar reports … and it often turned out that the I2C bus got locked by some attached device (mostly it was a not-very-well-supported SFP module with DDM) … and communication between router’s management function and hardware modules was interrupted making management function to panic.

If you’re using any SFP/SFP+ modules in your switch, try to unplug all of them and see if problem persists. If it doesn’t, then plug one module at a time and check if problem re-appears … that would indicate the problematic SFP module.

4

This is scary to think if your gear was in remote DC and access pass was hard to obtain

5

The network closet is locked at that site and my cohort has shown up 2 times to swap out the switch to be thwarted by no keys.

6

Did you managed to solve it? I have the same issue in logs, moreover ports 1-8 do not give me any poe out, ports 9-16 work fine.

7

Unit was RMA’d.

8

For anyone encountering “PSU removed” and “controller error” issues on the CRS320-8P-8B-4S:
Please update to the latest RouterOS beta/testing release, as recent versions include software fixes that address this behavior.

If the issue still persists after upgrading to the newest beta build, please generate a supout.rif file and open a support ticket for further analysis.