Skip to content
View in the app

A better way to browse. Learn more.
Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Unraid Summer Sale in live: 20% off Starter and Unleashed + buy one, get one 50% off

4-5 Hard drives showing error in logs. Causing Parity Sync to be extremely slow

dawson2938
in General Support

Featured Replies

My system is made up of 30 total drives, split up between main case and two JBODS. The JBODS have an ATX Power supply that connect to SAS hard drives using SATA power via an adapter. The 3.3V Wire has been removed from all sata power. They connect back to an Adaptec 82885T Expander which runs back to a LSI SAS9300-16I 9300-16I 16-PORT 12GBPS PCIE HBA. I have been dealing with this issue since the installation of the drives around a year ago. I got them stable by not mounting a few of the drives but the issue seams to have popped back up once I remounted them. I've noticed in the system logs I am constantly seeing the following 

Oct  2 22:53:03 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:53:03 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:53:03 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:53:03 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:53:03 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:53:03 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:53:03 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:53:03 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:53:03 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:53:03 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:53:03 Tower kernel: sd 7:0:4:0: device_block, handle(0x000e)
Oct  2 22:53:03 Tower kernel: sd 7:0:6:0: device_block, handle(0x0010)
Oct  2 22:53:04 Tower kernel: sd 7:0:4:0: device_unblock and setting to running, handle(0x000e)
Oct  2 22:53:04 Tower kernel: sd 7:0:6:0: device_unblock and setting to running, handle(0x0010)
Oct  2 22:53:04 Tower kernel: sd 7:0:4:0: Power-on or device reset occurred
Oct  2 22:53:04 Tower kernel: sd 7:0:6:0: Power-on or device reset occurred
Oct  2 22:53:27 Tower kernel: sd 7:0:2:0: device_block, handle(0x000c)
Oct  2 22:53:27 Tower kernel: sd 7:0:4:0: device_block, handle(0x000e)
Oct  2 22:53:27 Tower kernel: sd 7:0:5:0: device_block, handle(0x000f)
Oct  2 22:53:27 Tower kernel: sd 7:0:6:0: device_block, handle(0x0010)
Oct  2 22:53:28 Tower kernel: sd 7:0:2:0: device_unblock and setting to running, handle(0x000c)
Oct  2 22:53:28 Tower kernel: sd 7:0:4:0: device_unblock and setting to running, handle(0x000e)
Oct  2 22:53:28 Tower kernel: sd 7:0:5:0: device_unblock and setting to running, handle(0x000f)
Oct  2 22:53:28 Tower kernel: sd 7:0:6:0: device_unblock and setting to running, handle(0x0010)
Oct  2 22:53:28 Tower kernel: sd 7:0:4:0: Power-on or device reset occurred
Oct  2 22:53:28 Tower kernel: sd 7:0:5:0: Power-on or device reset occurred
Oct  2 22:53:28 Tower kernel: sd 7:0:2:0: Power-on or device reset occurred
Oct  2 22:53:28 Tower kernel: sd 7:0:6:0: Power-on or device reset occurred
Oct  2 22:53:53 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:53:53 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:53:53 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:53:53 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:53:53 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:53:53 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:53:53 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:53:53 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:53:53 Tower kernel: sd 7:0:4:0: device_block, handle(0x000e)
Oct  2 22:53:54 Tower kernel: sd 7:0:4:0: device_unblock and setting to running, handle(0x000e)
Oct  2 22:53:54 Tower kernel: sd 7:0:4:0: Power-on or device reset occurred
Oct  2 22:54:15 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:54:15 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:54:15 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:54:15 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:54:15 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:54:15 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:54:15 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:54:15 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:54:15 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:54:15 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:54:15 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:54:15 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:54:15 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:54:15 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:54:15 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:54:15 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:54:15 Tower kernel: sd 7:0:4:0: device_block, handle(0x000e)
Oct  2 22:54:15 Tower kernel: sd 7:0:6:0: device_block, handle(0x0010)
Oct  2 22:54:17 Tower kernel: sd 7:0:4:0: device_unblock and setting to running, handle(0x000e)
Oct  2 22:54:17 Tower kernel: sd 7:0:6:0: device_unblock and setting to running, handle(0x0010)
Oct  2 22:54:17 Tower kernel: sd 7:0:4:0: Power-on or device reset occurred
Oct  2 22:54:17 Tower kernel: sd 7:0:6:0: Power-on or device reset occurred
Oct  2 22:54:38 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:54:38 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:54:38 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:54:38 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:54:38 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:54:38 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:54:38 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:54:38 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:54:38 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:54:38 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:54:38 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:54:38 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:54:38 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:54:38 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:54:38 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:54:38 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:54:38 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:54:38 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:54:39 Tower kernel: sd 7:0:2:0: device_block, handle(0x000c)
Oct  2 22:54:39 Tower kernel: sd 7:0:4:0: device_block, handle(0x000e)
Oct  2 22:54:39 Tower kernel: sd 7:0:6:0: device_block, handle(0x0010)
Oct  2 22:54:40 Tower kernel: sd 7:0:2:0: device_unblock and setting to running, handle(0x000c)
Oct  2 22:54:40 Tower kernel: sd 7:0:4:0: device_unblock and setting to running, handle(0x000e)
Oct  2 22:54:40 Tower kernel: sd 7:0:6:0: device_unblock and setting to running, handle(0x0010)
Oct  2 22:54:40 Tower kernel: sd 7:0:2:0: Power-on or device reset occurred
Oct  2 22:54:40 Tower kernel: sd 7:0:4:0: Power-on or device reset occurred
Oct  2 22:54:40 Tower kernel: sd 7:0:6:0: Power-on or device reset occurred
Oct  2 22:55:03 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:55:03 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:55:03 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:55:03 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:55:03 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:55:03 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:55:03 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:55:03 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:55:03 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:55:03 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:55:03 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:55:03 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:55:03 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:55:03 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:55:03 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:55:03 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:55:03 Tower kernel: sd 7:0:4:0: device_block, handle(0x000e)
Oct  2 22:55:03 Tower kernel: sd 7:0:6:0: device_block, handle(0x0010)
Oct  2 22:55:04 Tower kernel: sd 7:0:4:0: device_unblock and setting to running, handle(0x000e)
Oct  2 22:55:04 Tower kernel: sd 7:0:6:0: device_unblock and setting to running, handle(0x0010)
Oct  2 22:55:04 Tower kernel: sd 7:0:4:0: Power-on or device reset occurred
Oct  2 22:55:04 Tower kernel: sd 7:0:6:0: Power-on or device reset occurred
Oct  2 22:55:36 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:55:36 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:55:36 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:55:36 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:55:36 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:55:36 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:55:36 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:55:36 Tower kernel: mpt3sas_cm1: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101)
Oct  2 22:55:36 Tower kernel: sd 7:0:7:0: device_block, handle(0x0011)
Oct  2 22:55:37 Tower kernel: sd 7:0:7:0: device_unblock and setting to running, handle(0x0011)
Oct  2 22:55:37 Tower kernel: sd 7:0:7:0: Power-on or device reset occurred

 

 

This is just a snippet but it keeps repeating and its always the same 4 sometimes 5 hard drives. 

 

Things I have tried already.

 

Upgrading firmware on 82885T to latest 

disabling EMC on Seagate drives. 

Replacing all 1x4 breakout cables. 

replacing Adaptec SAS Expander 82885T with a different one. 

 

I have tried pretty much everything I know to try and would love some assistance. 

tower-diagnostics-20241002-2302.zip

  • Quote
    • Community Expert
    3 hours ago, dawson2938 said:

    Oct  2 22:54:40 Tower kernel: sd 7:0:2:0: Power-on or device reset occurred
    Oct  2 22:54:40 Tower kernel: sd 7:0:4:0: Power-on or device reset occurred
    Oct  2 22:54:40 Tower kernel: sd 7:0:6:0: Power-on or device reset occurred

    These usually mean a power/connection issue.

  • Quote

    • 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.

    Guest
    Reply to this topic...
    Go to topic listing

    Account

    Navigation

    Search

    Search

    Configure browser push notifications
    Chrome (Android)
    1. Tap the lock icon next to the address bar.
    2. Tap Permissions → Notifications.
    3. Adjust your preference.
    Chrome (Desktop)
    1. Click the padlock icon in the address bar.
    2. Select Site settings.
    3. Find Notifications and adjust your preference.