March 27, 20251 yr I noticed some messages in my syslog that seem concerning: Mar 25 14:29:29 SF-unRAID kernel: mpt2sas_cm0 fault info from func: mpt3sas_base_make_ioc_ready Mar 25 14:29:29 SF-unRAID kernel: mpt2sas_cm0: fault_state(0x7e23)! Mar 25 14:29:29 SF-unRAID kernel: mpt2sas_cm0: sending diag reset !! Mar 25 14:29:30 SF-unRAID kernel: mpt2sas_cm0: diag reset: SUCCESS Mar 25 14:29:30 SF-unRAID kernel: mpt2sas_cm0: CurrentHostPageSize is 0: Setting default host page size to 4k Mar 25 14:29:30 SF-unRAID kernel: mpt2sas_cm0: overriding NVDATA EEDPTagMode setting Mar 25 14:29:30 SF-unRAID kernel: mpt2sas_cm0: LSISAS2308: FWVersion(20.00.07.00), ChipRevision(0x05) Mar 25 14:29:30 SF-unRAID kernel: mpt2sas_cm0: Protocol=(Initiator,Target), Capabilities=(TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ) Mar 25 14:29:30 SF-unRAID kernel: mpt2sas_cm0: sending port enable !! Mar 25 14:29:37 SF-unRAID kernel: mpt2sas_cm0: port enable: SUCCESS Mar 25 14:29:37 SF-unRAID kernel: mpt2sas_cm0: search for end-devices: start Mar 25 14:29:37 SF-unRAID kernel: scsi target2:0:1: handle(0x000a), sas_addr(0x50060480d018e78b) Mar 25 14:29:37 SF-unRAID kernel: scsi target2:0:1: enclosure logical id(0x50060480d018e7be), slot(114) Mar 25 14:29:37 SF-unRAID kernel: scsi target2:0:0: handle(0x000b), sas_addr(0x50060480d018e78d) Mar 25 14:29:37 SF-unRAID kernel: scsi target2:0:0: enclosure logical id(0x50060480d018e7be), slot(112) Mar 25 14:29:37 SF-unRAID kernel: scsi target2:0:2: handle(0x000c), sas_addr(0x50060480d018e790) Mar 25 14:29:37 SF-unRAID kernel: scsi target2:0:2: enclosure logical id(0x50060480d018e7be), slot(109) Mar 25 14:29:37 SF-unRAID kernel: scsi target2:0:3: handle(0x000d), sas_addr(0x50060480d018e792) Mar 25 14:29:37 SF-unRAID kernel: scsi target2:0:3: enclosure logical id(0x50060480d018e7be), slot(107) Mar 25 14:29:37 SF-unRAID kernel: scsi target2:0:4: handle(0x000e), sas_addr(0x50060480d018e793) Mar 25 14:29:37 SF-unRAID kernel: scsi target2:0:4: enclosure logical id(0x50060480d018e7be), slot(106) Mar 25 14:29:37 SF-unRAID kernel: scsi target2:0:5: handle(0x000f), sas_addr(0x50060480d018e794) Mar 25 14:29:37 SF-unRAID kernel: scsi target2:0:5: enclosure logical id(0x50060480d018e7be), slot(102) Mar 25 14:29:37 SF-unRAID kernel: scsi target2:0:6: handle(0x0010), sas_addr(0x50060480d018e797) Mar 25 14:29:37 SF-unRAID kernel: scsi target2:0:6: enclosure logical id(0x50060480d018e7be), slot(104) Mar 25 14:29:37 SF-unRAID kernel: scsi target2:0:7: handle(0x0011), sas_addr(0x50060480d018e7be) Mar 25 14:29:37 SF-unRAID kernel: scsi target2:0:7: enclosure logical id(0x50060480d018e7be), slot(117) Mar 25 14:29:37 SF-unRAID kernel: mpt2sas_cm0: search for end-devices: complete Mar 25 14:29:37 SF-unRAID kernel: mpt2sas_cm0: search for end-devices: start Mar 25 14:29:37 SF-unRAID kernel: mpt2sas_cm0: search for PCIe end-devices: complete Mar 25 14:29:37 SF-unRAID kernel: mpt2sas_cm0: search for expanders: start Mar 25 14:29:37 SF-unRAID kernel: expander present: handle(0x0009), sas_addr(0x50060480d018e7bf), port:255 Mar 25 14:29:37 SF-unRAID kernel: mpt2sas_cm0: search for expanders: complete Mar 25 14:29:37 SF-unRAID kernel: mpt2sas_cm0: mpt3sas_base_hard_reset_handler: SUCCESS Mar 25 14:29:37 SF-unRAID kernel: mpt2sas_cm0: _base_fault_reset_work: hard reset: success Mar 25 14:29:37 SF-unRAID kernel: mpt2sas_cm0: removing unresponding devices: start Mar 25 14:29:37 SF-unRAID kernel: mpt2sas_cm0: removing unresponding devices: end-devices Mar 25 14:29:37 SF-unRAID kernel: mpt2sas_cm0: Removing unresponding devices: pcie end-devices Mar 25 14:29:37 SF-unRAID kernel: mpt2sas_cm0: removing unresponding devices: expanders Mar 25 14:29:37 SF-unRAID kernel: mpt2sas_cm0: removing unresponding devices: complete Mar 25 14:29:37 SF-unRAID kernel: mpt2sas_cm0: scan devices: start Mar 25 14:29:37 SF-unRAID kernel: mpt2sas_cm0: scan devices: expanders start Mar 25 14:29:37 SF-unRAID kernel: mpt2sas_cm0: break from expander scan: ioc_status(0x0022), loginfo(0x310f0400) Mar 25 14:29:37 SF-unRAID kernel: mpt2sas_cm0: scan devices: expanders complete Mar 25 14:29:37 SF-unRAID kernel: mpt2sas_cm0: scan devices: end devices start Mar 25 14:29:37 SF-unRAID kernel: mpt2sas_cm0: break from end device scan: ioc_status(0x0022), loginfo(0x310f0400) Mar 25 14:29:37 SF-unRAID kernel: mpt2sas_cm0: scan devices: end devices complete Mar 25 14:29:37 SF-unRAID kernel: mpt2sas_cm0: scan devices: pcie end devices start Mar 25 14:29:37 SF-unRAID kernel: mpt2sas_cm0: log_info(0x3003011d): originator(IOP), code(0x03), sub_code(0x011d) Mar 25 14:29:37 SF-unRAID kernel: mpt2sas_cm0: log_info(0x3003011d): originator(IOP), code(0x03), sub_code(0x011d) Mar 25 14:29:37 SF-unRAID kernel: mpt2sas_cm0: break from pcie end device scan: ioc_status(0x0022), loginfo(0x3003011d) Mar 25 14:29:37 SF-unRAID kernel: mpt2sas_cm0: pcie devices: pcie end devices complete Mar 25 14:29:37 SF-unRAID kernel: mpt2sas_cm0: scan devices: complete Mar 25 14:29:37 SF-unRAID kernel: sd 2:0:1:0: Power-on or device reset occurred Mar 25 14:29:37 SF-unRAID kernel: sd 2:0:0:0: Power-on or device reset occurred Mar 25 14:29:37 SF-unRAID kernel: sd 2:0:2:0: Power-on or device reset occurred Mar 25 14:29:37 SF-unRAID kernel: sd 2:0:5:0: Power-on or device reset occurred Mar 25 14:29:37 SF-unRAID kernel: sd 2:0:6:0: Power-on or device reset occurred Mar 25 14:34:13 SF-unRAID flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Mar 25 15:34:09 SF-unRAID kernel: sd 2:0:3:0: Power-on or device reset occurred Mar 25 15:34:10 SF-unRAID kernel: sd 2:0:4:0: Power-on or device reset occurred I started a rebuild of Parity 2 with a new drive about 20 minutes before these messages appeared. I believe they relate to the drives in my EMC KTN-STL3 enclosure, connected via an LSI 9207-4i4e controller. That setup has been working for quite a while now (none of the drives in it are newly added). I haven't noticed similar messages before. I did have an external cable connection issue once. I'm careful to check the cable seating now any time I touch the server, but I guess I can't be 100% sure it's perfect. I recently opened up the main server box to connect a couple drives to one of the motherboard controllers. I suppose it's possible that there's extra stress on some subsystem with that controller active along with the LSI controller. I also just upgraded from 6.12.6 to 7.0.1 a few days ago. I want to upgrade one of the data disks with the old parity drive, but I'm hesitant to proceed without knowing why these messages appeared. Does anybody have thoughts on likely causes and steps I should take to diagnose? sf-unraid-diagnostics-20250326-1949.zip Edited March 27, 20251 yr by fritzdis
March 27, 20251 yr Community Expert Solution Make sure the HBA is well seated and sufficiently cooled, you can also try a different PCIe slot.
March 29, 20251 yr Author Double-checked the HBA card & cable seating - definitely OK. An overheat of the HBA is a possibility, I guess. I had already replaced the stock heatsink with a much larger copper finned one with a case fan directing air at it from about 6-8 inches away. That combo was fine for a couple years, as far as I knew. But the fan may not have been moving all that much air, and it was pretty warm in the room on the day the messages appeared. I've jury-rigged a significantly larger fan (double the max CFM per specs) in place of the old one and made sure it's at full speed. Currently running a parity check, and if that goes well, I'll do the data drive upgrade. One thing I wonder about is how I should monitor if those mpt2sas/device reset messages reoccur. I found this, but the last post makes it unclear if it would still work. Is there a better way to generate notifications for these kinds of syslog messages?
April 12, 20251 yr Author Well, unfortunately, this may not be solved yet. I was preclearing a drive (used, but new to me) in the external enclosure and got these messages related to that drive: Apr 10 13:09:25 SF-unRAID kernel: mpt2sas_cm0: log_info(0x31120310): originator(PL), code(0x12), sub_code(0x0310) Apr 10 13:09:25 SF-unRAID kernel: mpt2sas_cm0: log_info(0x31120310): originator(PL), code(0x12), sub_code(0x0310) Apr 10 13:09:25 SF-unRAID kernel: mpt2sas_cm0: log_info(0x31120310): originator(PL), code(0x12), sub_code(0x0310) Apr 10 13:09:25 SF-unRAID kernel: mpt2sas_cm0: log_info(0x31120310): originator(PL), code(0x12), sub_code(0x0310) Apr 10 13:09:25 SF-unRAID kernel: mpt2sas_cm0: log_info(0x31120310): originator(PL), code(0x12), sub_code(0x0310) Apr 10 13:09:25 SF-unRAID kernel: sd 2:0:3:0: [sdi] tag#9828 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s Apr 10 13:09:25 SF-unRAID kernel: sd 2:0:3:0: [sdi] tag#9828 CDB: opcode=0x88 88 00 00 00 00 02 24 7f f4 00 00 00 04 00 00 00 Apr 10 13:09:25 SF-unRAID kernel: I/O error, dev sdi, sector 9202299904 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 3 Apr 10 13:09:25 SF-unRAID kernel: sd 2:0:3:0: [sdi] tag#9832 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s Apr 10 13:09:25 SF-unRAID kernel: sd 2:0:3:0: [sdi] tag#9832 CDB: opcode=0x88 88 00 00 00 00 02 24 80 02 00 00 00 02 00 00 00 Apr 10 13:09:25 SF-unRAID kernel: I/O error, dev sdi, sector 9202303488 op 0x0:(READ) flags 0x80700 phys_seg 64 prio class 3 Apr 10 13:09:25 SF-unRAID kernel: sd 2:0:3:0: [sdi] tag#9831 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s Apr 10 13:09:25 SF-unRAID kernel: sd 2:0:3:0: [sdi] tag#9831 CDB: opcode=0x88 88 00 00 00 00 02 24 7f fe 00 00 00 04 00 00 00 Apr 10 13:09:25 SF-unRAID kernel: I/O error, dev sdi, sector 9202302464 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 3 Apr 10 13:09:25 SF-unRAID kernel: sd 2:0:3:0: [sdi] tag#9830 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s Apr 10 13:09:25 SF-unRAID kernel: sd 2:0:3:0: [sdi] tag#9830 CDB: opcode=0x88 88 00 00 00 00 02 24 7f fa 00 00 00 04 00 00 00 Apr 10 13:09:25 SF-unRAID kernel: I/O error, dev sdi, sector 9202301440 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 3 Apr 10 13:09:25 SF-unRAID kernel: sd 2:0:3:0: [sdi] tag#9829 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s Apr 10 13:09:25 SF-unRAID kernel: sd 2:0:3:0: [sdi] tag#9829 CDB: opcode=0x88 88 00 00 00 00 02 24 7f f8 00 00 00 02 00 00 00 Apr 10 13:09:25 SF-unRAID kernel: I/O error, dev sdi, sector 9202300928 op 0x0:(READ) flags 0x80700 phys_seg 64 prio class 3 Apr 10 13:09:25 SF-unRAID kernel: sd 2:0:3:0: Power-on or device reset occurred This happened twice during the pre-read and once during the post-read (different sectors each time). I also tried the HBA in a different PCIE slot, but starting a new pre-clear produced the same kind of messages. SMART doesn't show any problems with the drive, so I'm guessing it's an issue with the HBA->enclosure chain. I've ordered a 40mm fan to attach to the heatsink (and I'll reapply paste). While I wait, I'll connect the drive to one of the motherboard connectors to see if it pre-clears OK. Just to double-check, are there any known issues with 9200 series LSI cards and Toshiba MG08 drives?
April 13, 20251 yr 13 hours ago, fritzdis said: Just to double-check, are there any known issues with 9200 series LSI cards and Toshiba MG08 drives? They only tested until 2016, see the compatibility document here. They tested and found compatible MG04 drives.
May 18, 20251 yr Author I've had to deal with several other issues in the meantime, but the 40mm fan solution has held up so far at least.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.