mpt2sas flooding dmesg

M

Mrt12

Well-Known Member
May 19, 2019
178
21
58
46
CH
Hello,
I have a Proxmox server with some SAS cards:

# lspci | grep SAS
51:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2308 PCI-Express Fusion-MPT SAS-2 (rev 05)
8a:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS3416 Fusion-MPT Tri-Mode I/O Controller Chip (IOC) (rev 01)


The SAS2 card is actually a 9207-8e where I connect my tape drive. I successfully do backups using PBS on my tapes and it works well since several months. However, recently (maybe 2, or 3 weeks ago, I cannot point it out more exactly) there was a Proxmox or Linux Kernel update, and since then, when I switch on the (external) tape drive, my dmesg looks like this:

Code: 
[Mon May 25 21:08:23 2026] mpt2sas_cm0: handle(0x0009), ioc_status(0x0022) failure at drivers/scsi/mpt3sas/mpt3sas_transport.c:228/_transport_set_identify()!
[Mon May 25 21:08:23 2026] mpt2sas_cm0: failure at drivers/scsi/mpt3sas/mpt3sas_scsih.c:8407/_scsih_add_device()!
[Mon May 25 21:08:24 2026] mpt2sas_cm0: handle(0x0009), ioc_status(0x0022) failure at drivers/scsi/mpt3sas/mpt3sas_transport.c:228/_transport_set_identify()!
[Mon May 25 21:08:24 2026] mpt2sas_cm0: failure at drivers/scsi/mpt3sas/mpt3sas_scsih.c:8407/_scsih_add_device()!
[Mon May 25 21:08:25 2026] mpt2sas_cm0: handle(0x0009), ioc_status(0x0022) failure at drivers/scsi/mpt3sas/mpt3sas_transport.c:228/_transport_set_identify()!
[Mon May 25 21:08:25 2026] mpt2sas_cm0: failure at drivers/scsi/mpt3sas/mpt3sas_scsih.c:8407/_scsih_add_device()!
[Mon May 25 21:08:26 2026] mpt2sas_cm0: handle(0x0009), ioc_status(0x0022) failure at drivers/scsi/mpt3sas/mpt3sas_transport.c:228/_transport_set_identify()!
[Mon May 25 21:08:26 2026] mpt2sas_cm0: failure at drivers/scsi/mpt3sas/mpt3sas_scsih.c:8407/_scsih_add_device()!
[Mon May 25 21:08:27 2026] mpt2sas_cm0: handle(0x0009), ioc_status(0x0022) failure at drivers/scsi/mpt3sas/mpt3sas_transport.c:228/_transport_set_identify()!
[Mon May 25 21:08:27 2026] mpt2sas_cm0: failure at drivers/scsi/mpt3sas/mpt3sas_scsih.c:8407/_scsih_add_device()!
[Mon May 25 21:08:28 2026] mpt2sas_cm0: handle(0x0009), ioc_status(0x0022) failure at drivers/scsi/mpt3sas/mpt3sas_transport.c:228/_transport_set_identify()!
[Mon May 25 21:08:28 2026] mpt2sas_cm0: failure at drivers/scsi/mpt3sas/mpt3sas_scsih.c:8407/_scsih_add_device()!
[Mon May 25 21:08:29 2026] mpt2sas_cm0: detecting: handle(0x0009),
                           sas_address(0x50014380353cba70), phy(3)
[Mon May 25 21:08:29 2026] mpt2sas_cm0: REPORT_LUNS: handle(0x0009),
                           retries(0)
[Mon May 25 21:08:29 2026] TEST_UNIT_READY: handle(0x0009) lun(0)
[Mon May 25 21:08:29 2026] mpt2sas_cm0: detecting: handle(0x0009),
                           sas_address(0x50014380353cba70), phy(3)
[Mon May 25 21:08:29 2026] mpt2sas_cm0: REPORT_LUNS: handle(0x0009),
                           retries(0)
[Mon May 25 21:08:29 2026] TEST_UNIT_READY: handle(0x0009) lun(0)
[Mon May 25 21:08:29 2026] START_UNIT: handle(0x0009), lun(0)
[Mon May 25 21:08:59 2026] mpt2sas_cm0: In func: _scsi_send_scsi_io
[Mon May 25 21:08:59 2026] mpt2sas_cm0: Command Timeout
[Mon May 25 21:08:59 2026] mf:
                              
[Mon May 25 21:08:59 2026] 00000009
[Mon May 25 21:08:59 2026] 00000000
[Mon May 25 21:08:59 2026] 00000000
[Mon May 25 21:08:59 2026] fe5ecd60
[Mon May 25 21:08:59 2026] 00600000
[Mon May 25 21:08:59 2026] 00000018
[Mon May 25 21:08:59 2026] 00000000
[Mon May 25 21:08:59 2026] 00000000
[Mon May 25 21:08:59 2026]
                              
[Mon May 25 21:08:59 2026] 00000000
[Mon May 25 21:08:59 2026] 00000006
[Mon May 25 21:08:59 2026] 00000000
[Mon May 25 21:08:59 2026] 00000000
[Mon May 25 21:08:59 2026] 00000000
[Mon May 25 21:08:59 2026] 00000000
[Mon May 25 21:08:59 2026] 00000000
[Mon May 25 21:08:59 2026] 00000000
[Mon May 25 21:08:59 2026]
                              
[Mon May 25 21:08:59 2026] 0000011b
[Mon May 25 21:08:59 2026] 00000001
[Mon May 25 21:08:59 2026] 00000000
[Mon May 25 21:08:59 2026] 00000000
[Mon May 25 21:08:59 2026] 00000000
[Mon May 25 21:08:59 2026] 00000000
[Mon May 25 21:08:59 2026] 00000000
[Mon May 25 21:08:59 2026] 00000000
[Mon May 25 21:08:59 2026]
                              
[Mon May 25 21:08:59 2026] d3000000
[Mon May 25 21:08:59 2026] ffffffff
[Mon May 25 21:08:59 2026] ffffffff
[Mon May 25 21:08:59 2026] 00000000

[Mon May 25 21:08:59 2026] issue target reset: handle (0x0009)
[Mon May 25 21:08:59 2026] mpt2sas_cm0: log_info(0x31140000): originator(PL), code(0x14), sub_code(0x0000)
[Mon May 25 21:08:59 2026] target reset completed: handle (0x0009)
[Mon May 25 21:08:59 2026] issue retry: handle (0x0009)
[Mon May 25 21:08:59 2026] TEST_UNIT_READY: handle(0x0009) lun(0)
[Mon May 25 21:08:59 2026] mpt2sas_cm0: detecting: handle(0x0009),
                           sas_address(0x50014380353cba70), phy(3)
[Mon May 25 21:08:59 2026] mpt2sas_cm0: REPORT_LUNS: handle(0x0009),
                           retries(0)
[Mon May 25 21:08:59 2026] TEST_UNIT_READY: handle(0x0009) lun(0)
[Mon May 25 21:08:59 2026] START_UNIT: handle(0x0009), lun(0)
[Mon May 25 21:09:29 2026] mpt2sas_cm0: In func: _scsi_send_scsi_io
[Mon May 25 21:09:29 2026] mpt2sas_cm0: Command Timeout
[Mon May 25 21:09:29 2026] mf:
                              
[Mon May 25 21:09:29 2026] 00000009
[Mon May 25 21:09:29 2026] 00000000
[Mon May 25 21:09:29 2026] 00000000
[Mon May 25 21:09:29 2026] fe5ecd60
[Mon May 25 21:09:29 2026] 00600000
[Mon May 25 21:09:29 2026] 00000018
[Mon May 25 21:09:29 2026] 00000000
[Mon May 25 21:09:29 2026] 00000000
[Mon May 25 21:09:29 2026]
                              
[Mon May 25 21:09:29 2026] 00000000
[Mon May 25 21:09:29 2026] 00000006
[Mon May 25 21:09:29 2026] 00000000
[Mon May 25 21:09:29 2026] 00000000
[Mon May 25 21:09:29 2026] 00000000
[Mon May 25 21:09:29 2026] 00000000
[Mon May 25 21:09:29 2026] 00000000
[Mon May 25 21:09:29 2026] 00000000
[Mon May 25 21:09:29 2026]
                              
[Mon May 25 21:09:29 2026] 0000011b
[Mon May 25 21:09:29 2026] 00000001
[Mon May 25 21:09:29 2026] 00000000
[Mon May 25 21:09:29 2026] 00000000
[Mon May 25 21:09:29 2026] 00000000
[Mon May 25 21:09:29 2026] 00000000
[Mon May 25 21:09:29 2026] 00000000
[Mon May 25 21:09:29 2026] 00000000
[Mon May 25 21:09:29 2026]
                              
[Mon May 25 21:09:29 2026] d3000000
[Mon May 25 21:09:29 2026] ffffffff
[Mon May 25 21:09:29 2026] ffffffff
[Mon May 25 21:09:29 2026] 00000000

[Mon May 25 21:09:29 2026] issue target reset: handle (0x0009)
[Mon May 25 21:09:29 2026] mpt2sas_cm0: log_info(0x31140000): originator(PL), code(0x14), sub_code(0x0000)
[Mon May 25 21:09:29 2026] target reset completed: handle (0x0009)
[Mon May 25 21:09:29 2026] issue retry: handle (0x0009)
[Mon May 25 21:09:29 2026] TEST_UNIT_READY: handle(0x0009) lun(0)
[Mon May 25 21:09:29 2026] mpt2sas_cm0: detecting: handle(0x0009),
                           sas_address(0x50014380353cba70), phy(3)
[Mon May 25 21:09:29 2026] mpt2sas_cm0: REPORT_LUNS: handle(0x0009),
                           retries(0)
[Mon May 25 21:09:29 2026] TEST_UNIT_READY: handle(0x0009) lun(0)
[Mon May 25 21:09:29 2026] START_UNIT: handle(0x0009), lun(0)
[Mon May 25 21:09:48 2026] TEST_UNIT_READY: handle(0x0009) lun(0)
[Mon May 25 21:09:48 2026] mpt2sas_cm0: detecting: handle(0x0009),
                           sas_address(0x50014380353cba70), phy(3)
[Mon May 25 21:09:48 2026] mpt2sas_cm0: REPORT_LUNS: handle(0x0009),
                           retries(0)
[Mon May 25 21:09:48 2026] TEST_UNIT_READY: handle(0x0009) lun(0)
[Mon May 25 21:09:48 2026] START_UNIT: handle(0x0009), lun(0)
[Mon May 25 21:10:05 2026] TEST_UNIT_READY: handle(0x0009) lun(0)
[Mon May 25 21:10:05 2026] mpt2sas_cm0: detecting: handle(0x0009),
                           sas_address(0x50014380353cba70), phy(3)
[Mon May 25 21:10:05 2026] mpt2sas_cm0: REPORT_LUNS: handle(0x0009),
                           retries(0)
[Mon May 25 21:10:05 2026] TEST_UNIT_READY: handle(0x0009) lun(0)
[Mon May 25 21:10:05 2026] START_UNIT: handle(0x0009), lun(0)
[Mon May 25 21:10:05 2026] TEST_UNIT_READY: handle(0x0009) lun(0)
[Mon May 25 21:10:06 2026] mpt2sas_cm0: detecting: handle(0x0009),
                           sas_address(0x50014380353cba70), phy(3)
[Mon May 25 21:10:06 2026] mpt2sas_cm0: REPORT_LUNS: handle(0x0009),
                           retries(0)
[Mon May 25 21:10:06 2026] TEST_UNIT_READY: handle(0x0009) lun(0)
[Mon May 25 21:10:06 2026] mpt2sas_cm0: handle(0x9) sas_address(0x50014380353cba70) port_type(0x1)
[Mon May 25 21:10:06 2026] scsi 0:0:7:0: Sequential-Access HP       Ultrium 6-SCSI   O5ID PQ: 0 ANSI: 6
[Mon May 25 21:10:06 2026] scsi 0:0:7:0: SSP: handle(0x0009), sas_addr(0x50014380353cba70), phy(3), device_name(0x50014380353cba72)
[Mon May 25 21:10:06 2026] scsi 0:0:7:0: enclosure logical id (0x500605b00b42f8b0), slot(3)
[Mon May 25 21:10:06 2026] scsi 0:0:7:0: qdepth(254), tagged(1), scsi_level(7), cmd_que(1)
[Mon May 25 21:10:06 2026] scsi 0:0:7:0: TLR Enabled
[Mon May 25 21:10:06 2026] st 0:0:7:0: Attached scsi tape st0
[Mon May 25 21:10:06 2026] st 0:0:7:0: st0: try direct i/o: yes (alignment 4 B)
[Mon May 25 21:10:06 2026] st 0:0:7:0: Attached scsi generic sg6 type 1
[Mon May 25 21:10:06 2026]  end_device-0:7: add: handle(0x0009), sas_addr(0x50014380353cba70)
[Mon May 25 21:10:06 2026] st 0:0:7:0: [st0] Block limits 1 - 16777215 bytes.
[Mon May 25 21:20:59 2026] st 0:0:7:0: device_block, handle(0x0009)
[Mon May 25 21:21:00 2026] mpt2sas_cm0: device is not present handle(0x049)!!!
[Mon May 25 21:21:01 2026] mpt2sas_cm0: device is not present handle(0x049)!!!
[Mon May 25 21:21:01 2026] st 0:0:7:0: device_unblock and setting to running, handle(0x0009)
[Mon May 25 21:21:01 2026] mpt2sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50014380353cba70)
[Mon May 25 21:21:01 2026] mpt2sas_cm0: removing handle(0x0009), sas_addr(0x50014380353cba70)
[Mon May 25 21:21:01 2026] mpt2sas_cm0: enclosure logical id(0x500605b00b42f8b0), slot(3)
[Mon May 25 21:21:02 2026] mpt2sas_cm0: handle(0x0009), ioc_status(0x0022) failure at drivers/scsi/mpt3sas/mpt3sas_transport.c:228/_transport_set_identify()!
[Mon May 25 21:21:02 2026] mpt2sas_cm0: failure at drivers/scsi/mpt3sas/mpt3sas_scsih.c:8407/_scsih_add_device()!
[Mon May 25 21:21:03 2026] mpt2sas_cm0: handle(0x0009), ioc_status(0x0022) failure at drivers/scsi/mpt3sas/mpt3sas_transport.c:228/_transport_set_identify()!
[Mon May 25 21:21:03 2026] mpt2sas_cm0: failure at drivers/scsi/mpt3sas/mpt3sas_scsih.c:8407/_scsih_add_device()!
[Mon May 25 21:21:04 2026] mpt2sas_cm0: handle(0x0009), ioc_status(0x0022) failure at drivers/scsi/mpt3sas/mpt3sas_transport.c:228/_transport_set_identify()!
[Mon May 25 21:21:04 2026] mpt2sas_cm0: failure at drivers/scsi/mpt3sas/mpt3sas_scsih.c:8407/_scsih_add_device()!
[Mon May 25 21:21:05 2026] mpt2sas_cm0: handle(0x0009), ioc_status(0x0022) failure at drivers/scsi/mpt3sas/mpt3sas_transport.c:228/_transport_set_identify()!
[Mon May 25 21:21:05 2026] mpt2sas_cm0: failure at drivers/scsi/mpt3sas/mpt3sas_scsih.c:8407/_scsih_add_device()!
[Mon May 25 21:21:06 2026] mpt2sas_cm0: handle(0x0009), ioc_status(0x0022) failure at drivers/scsi/mpt3sas/mpt3sas_transport.c:228/_transport_set_identify()!
[Mon May 25 21:21:06 2026] mpt2sas_cm0: failure at drivers/scsi/mpt3sas/mpt3sas_scsih.c:8407/_scsih_add_device()!
[Mon May 25 21:21:07 2026] mpt2sas_cm0: handle(0x0009), ioc_status(0x0022) failure at drivers/scsi/mpt3sas/mpt3sas_transport.c:228/_transport_set_identify()!
[Mon May 25 21:21:07 2026] mpt2sas_cm0: failure at drivers/scsi/mpt3sas/mpt3sas_scsih.c:8407/_scsih_add_device()!
[Mon May 25 21:21:08 2026] mpt2sas_cm0: handle(0x0009), ioc_status(0x0022) failure at drivers/scsi/mpt3sas/mpt3sas_transport.c:228/_transport_set_identify()!
[Mon May 25 21:21:08 2026] mpt2sas_cm0: failure at drivers/scsi/mpt3sas/mpt3sas_scsih.c:8407/_scsih_add_device()!
[Mon May 25 21:21:09 2026] mpt2sas_cm0: handle(0x0009), ioc_status(0x0022) failure at drivers/scsi/mpt3sas/mpt3sas_transport.c:228/_transport_set_identify()!
[Mon May 25 21:21:09 2026] mpt2sas_cm0: failure at drivers/scsi/mpt3sas/mpt3sas_scsih.c:8407/_scsih_add_device()!
[Mon May 25 21:21:10 2026] mpt2sas_cm0: handle(0x0009), ioc_status(0x0022) failure at drivers/scsi/mpt3sas/mpt3sas_transport.c:228/_transport_set_identify()!
[Mon May 25 21:21:10 2026] mpt2sas_cm0: failure at drivers/scsi/mpt3sas/mpt3sas_scsih.c:8407/_scsih_add_device()!
[Mon May 25 21:21:11 2026] mpt2sas_cm0: handle(0x0009), ioc_status(0x0022) failure at drivers/scsi/mpt3sas/mpt3sas_transport.c:228/_transport_set_identify()!
[Mon May 25 21:21:11 2026] mpt2sas_cm0: failure at drivers/scsi/mpt3sas/mpt3sas_scsih.c:8407/_scsih_add_device()!
[Mon May 25 21:21:12 2026] mpt2sas_cm0: handle(0x0009), ioc_status(0x0022) failure at drivers/scsi/mpt3sas/mpt3sas_transport.c:228/_transport_set_identify()!
[Mon May 25 21:21:12 2026] mpt2sas_cm0: failure at drivers/scsi/mpt3sas/mpt3sas_scsih.c:8407/_scsih_add_device()!
[Mon May 25 21:21:13 2026] mpt2sas_cm0: handle(0x0009), ioc_status(0x0022) failure at drivers/scsi/mpt3sas/mpt3sas_transport.c:228/_transport_set_identify()!
[Mon May 25 21:21:13 2026] mpt2sas_cm0: failure at drivers/scsi/mpt3sas/mpt3sas_scsih.c:8407/_scsih_add_device()!
[Mon May 25 21:21:14 2026] mpt2sas_cm0: handle(0x0009), ioc_status(0x0022) failure at drivers/scsi/mpt3sas/mpt3sas_transport.c:228/_transport_set_identify()!
[Mon May 25 21:21:14 2026] mpt2sas_cm0: failure at drivers/scsi/mpt3sas/mpt3sas_scsih.c:8407/_scsih_add_device()!
[Mon May 25 21:21:15 2026] mpt2sas_cm0: handle(0x0009), ioc_status(0x0022) failure at drivers/scsi/mpt3sas/mpt3sas_transport.c:228/_transport_set_identify()!
[Mon May 25 21:21:15 2026] mpt2sas_cm0: failure at drivers/scsi/mpt3sas/mpt3sas_scsih.c:8407/_scsih_add_device()!
[Mon May 25 21:21:16 2026] mpt2sas_cm0: handle(0x0009), ioc_status(0x0022) failure at drivers/scsi/mpt3sas/mpt3sas_transport.c:228/_transport_set_identify()!
[Mon May 25 21:21:16 2026] mpt2sas_cm0: failure at drivers/scsi/mpt3sas/mpt3sas_scsih.c:8407/_scsih_add_device()!
[Mon May 25 21:21:17 2026] mpt2sas_cm0: handle(0x0009), ioc_status(0x0022) failure at drivers/scsi/mpt3sas/mpt3sas_transport.c:228/_transport_set_identify()!
[Mon May 25 21:21:17 2026] mpt2sas_cm0: failure at drivers/scsi/mpt3sas/mpt3sas_scsih.c:8407/_scsih_add_device()!
[Mon May 25 21:21:18 2026] mpt2sas_cm0: handle(0x0009), ioc_status(0x0022) failure at drivers/scsi/mpt3sas/mpt3sas_transport.c:228/_transport_set_identify()!
[Mon May 25 21:21:18 2026] mpt2sas_cm0: failure at drivers/scsi/mpt3sas/mpt3sas_scsih.c:8407/_scsih_add_device()!
...

the "cm0" failure continues for several thousand lines. However, the tape drive works and PBS successfully writes my backups to tape.
I have not changed my hardware since a few months, and also not the tape drive; further, I have not touched any configuration files. I 100% definitely know that up until ~3 weeks ago it was working flawlessly without any dmesg error entries, but now these above errors appear.

I wonder:
a) does someone know what these mean? is it something to worry or should I just ignore it?
b) how to fix them?

Anyone else has similar entries?
 
Hey there.

I have this exact same card:
Code: 
51:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2308 PCI-Express Fusion-MPT SAS-2 (rev 05)

And I was experiencing the exact same issue. I did some digging around and the best I can figure, in my case at least, its a dead drive that is arguing with the SAS controller. The drive was just refusing to enumerate properly in /dev/sdX. I was able to disable it with echo 0 > /sys/class/sas_phy/phy-<H>:<E>:13/enable after I found the particular phy id.
 
Yes I have a similar workaround but I use

echo "0000:51:00.0" > /sys/bus/pci/drivers/mpt3sas/unbind
echo "0000:51:00.0" > /sys/bus/pci/drivers/mpt3sas/bind


the thing is: I have this card since ~1 yr and this workaround was never necessary, only since May. So clearly something changed. What is also interesting: the card is connected to a tape drive. Before May no problem. Since May, the tape drive makes super strange noises when I switch it on while it is connected to the card. However if the drive is disconnected when switched on, it sounds like always. So clearly the driver and card are doing "something" and I would like to know what, and why it was changed, and how I can restore the old behaviour that was having zero problems until May 2026.
 
You must log in or register to reply here.
Top Bottom
Back