September 21, 20232 yr I go this message in my log, but cant figure out what SAS controller the drive is attached to and what drive it is, can someone point me in the right direction? Sep 21 18:59:04 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 18:59:04 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 18:59:27 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 18:59:27 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 18:59:27 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 18:59:32 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 18:59:33 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 18:59:38 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 18:59:38 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 18:59:38 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 18:59:38 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 18:59:43 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 18:59:44 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred tower-diagnostics-20230921-1855.zip EDIT: I forgot to say this started when i replaced the disabled Second parity drive now i have paused the rebuild as i think is nt healthy for the dirve to restart every few seconds Edited September 21, 20232 yr by threiner forgot to explain
September 21, 20232 yr Below disk which connect to LSI controller. [8:0:2:0] disk ATA ST8000DM004-2U91 SED1 /dev/sdo /dev/sg15 state=running queue_depth=32 scsi_level=6 type=0 device_blocked=0 timeout=30 dir: /sys/bus/scsi/devices/8:0:2:0 [/sys/devices/pci0000:00/0000:00:1c.4/0000:07:00.0/host8/port-8:2/end_device-8:2/target8:0:2/8:0:2:0] Keep track does SMART data also count up. 0x06 ===== = = === == Transport Statistics (rev 1) == 0x06 0x008 4 61 --- Number of Hardware Resets 0x06 0x010 4 40 --- Number of ASR Events 0x06 0x018 4 0 --- Number of Interface CRC Errors |||_ C monitored condition met ||__ D supports DSN |___ N normalized value Edited September 21, 20232 yr by Vr2Io
September 21, 20232 yr Author 24 minutes ago, Vr2Io said: Below disk which connect to LSI controller. [8:0:2:0] disk ATA ST8000DM004-2U91 SED1 /dev/sdo /dev/sg15 state=running queue_depth=32 scsi_level=6 type=0 device_blocked=0 timeout=30 dir: /sys/bus/scsi/devices/8:0:2:0 [/sys/devices/pci0000:00/0000:00:1c.4/0000:07:00.0/host8/port-8:2/end_device-8:2/target8:0:2/8:0:2:0] Keep track does SMART data also count up. 0x06 ===== = = === == Transport Statistics (rev 1) == 0x06 0x008 4 61 --- Number of Hardware Resets 0x06 0x010 4 40 --- Number of ASR Events 0x06 0x018 4 0 --- Number of Interface CRC Errors |||_ C monitored condition met ||__ D supports DSN |___ N normalized value The smart test looks good to me, so i guess i should then try to use a other cable first tower-smart-20230921-2007.zip
September 21, 20232 yr Author after changing the cable i get this... Sep 21 20:18:09 Tower root: Error response from daemon: Pool overlaps with other one on this address space Sep 21 20:18:09 Tower kernel: mdcmd (36): check Sep 21 20:18:09 Tower kernel: md: recovery thread: recon Q ... Sep 21 20:18:13 Tower kernel: mpt2sas_cm0: log_info(0x31110d01): originator(PL), code(0x11), sub_code(0x0d01) Sep 21 20:18:19 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 20:18:23 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:23 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:23 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:23 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:23 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:23 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:23 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:23 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:23 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:23 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:23 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:23 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:23 Tower kernel: sd 8:0:2:0: [sdo] tag#313 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=4s Sep 21 20:18:23 Tower kernel: sd 8:0:2:0: [sdo] tag#313 CDB: opcode=0x88 88 00 00 00 00 03 a3 81 2a 00 00 00 00 08 00 00 Sep 21 20:18:23 Tower kernel: I/O error, dev sdo, sector 15628052992 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 Sep 21 20:18:28 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 20:18:29 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 20:18:37 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:37 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:37 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:42 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 20:18:43 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 20:18:47 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:47 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:47 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:47 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:47 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:47 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:47 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:47 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:52 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 20:18:53 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 20:18:57 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:19:02 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 20:19:03 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 20:19:07 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:19:12 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 20:19:16 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:19:16 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:19:16 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:19:16 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:19:16 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:19:16 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:19:21 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 20:19:22 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 20:19:26 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:19:26 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:19:26 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:19:31 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 20:19:32 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 20:19:36 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:19:36 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:19:41 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 20:19:42 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 20:19:46 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:19:46 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) so do i assume it right the drive seems to have problems??
September 22, 20232 yr You may try connect this disk to onboard SATA controller / H240 to test any different. Or it may be the case due to SMR disk busy on writing ( due to rewriting shingled track ) out of 4s timeout, you will found reset on every 10s. You also can test does same problem on read operation. ( rest enough time first ) i.e dd if=/dev/sdo of=/dev/null bs=1M count=10k Sep 21 20:18:23 Tower kernel: sd 8:0:2:0: [sdo] tag#313 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=4s Sep 21 20:18:37 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:42 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 20:18:47 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:52 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 20:18:57 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:19:02 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 20:19:07 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:19:12 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Edited September 22, 20232 yr by Vr2Io
September 24, 20232 yr Author On 9/22/2023 at 4:31 AM, Vr2Io said: You may try connect this disk to onboard SATA controller / H240 to test any different. Or it may be the case due to SMR disk busy on writing ( due to rewriting shingled track ) out of 4s timeout, you will found reset on every 10s. You also can test does same problem on read operation. ( rest enough time first ) i.e dd if=/dev/sdo of=/dev/null bs=1M count=10k Sep 21 20:18:23 Tower kernel: sd 8:0:2:0: [sdo] tag#313 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=4s Sep 21 20:18:37 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:42 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 20:18:47 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:52 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 20:18:57 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:19:02 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 20:19:07 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:19:12 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred After nearly two hear attacks, all sas sata cabels exchanged two controllers testetd i found it it was most likley the Powercable adapter from one to five... looks like it works now stable
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.