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 7.3.0 --> 7.3.1 array start/performance related issues

Featured Replies

System: Supermicro CS836 chassis with a QNAP enclosure added via LSI SAS3216

Mobo: MSI Pro Z790-P WI-FI with 12700K

Drives: 22 mostly WDC SATA in BTRFS

Upgrade went smoothly. Rebooted and immediately noticed that UNRAID CLI was reporting the following repeatedly when tyring to scan the hard drives:

May 28 09:21:55 BigBoi kernel: I/O error, dev sdh, sector 128 op 0x0:(READ) flags 0x80700 phys_seg 48 prio class 2

May 28 09:21:55 BigBoi kernel: sd 0:0:10:0: attempting task abort!scmd(0x00000000fcba39fa), outstanding for 30463 ms & timeout 30000 ms

May 28 09:21:55 BigBoi kernel: sd 0:0:10:0: [sdk] tag#5615 CDB: opcode=0x28 28 00 00 00 00 80 00 01 80 00

May 28 09:21:55 BigBoi kernel: scsi target0:0:10: handle(0x0018), sas_address(0x300062b202aed2ce), phy(14)

May 28 09:21:55 BigBoi kernel: scsi target0:0:10: enclosure logical id(0x500062b202aed2c0), slot(4)

May 28 09:21:55 BigBoi kernel: scsi target0:0:10: enclosure level(0x0000), connector name( )

May 28 09:21:55 BigBoi kernel: sd 0:0:7:0: Power-on or device reset occurred

This happened over and over -- eventually the server booted (30-40 mins) and then allowed me to login where it struggled for another 30 mins to start the array (It eventually did)

I was able to grab snippets and diags prior to rolling back to 7.3.0.

Roll back successful and everything is running perfect on 7.3.0.

Happy to provide more information.

Skip

Screenshot 2026-05-28 093916.png

bigboi-diagnostics-20260528-0934.zip

Solved by JorgeB

  • Community Expert

If it works fine again after downgrading it, it could be a kernel regression, the other LSI controller is apparently working fine, problem is just the 9305-16e.

It may be worth looking for a firmware update; we can also see if any other users report similar issues.

  • Author

@JorgeB Fair enough. I didn't dive into the diagnostic- could you tell if the problem was actually coming from the 3216 or the 2308? I can check firmwares but i was pretty sure these old cards did not have updates.

Thanks,

Skip

  • Community Expert
31 minutes ago, Skipdog said:

could you tell if the problem was actually coming from the 3216

It only appears to affect this one

I have a 3224 and just had to roll back for the same issues. Including a system crash.

  • Community Expert
1 hour ago, jynxsee said:

I have a 3224

Same firmware?

  • Author

For me it looks like the bios/firmware is:

LSISAS3216: FWVersion(16.00.11.00)

  • Author

Just one more note-

OpenAI analysis spit out:

Diagnostics show repeated 30-second I/O timeouts resulting in task aborts and device resets on host0 (LSISAS3216 / SAS9305-16e running FW 16.00.11.00). No corresponding aborts are seen on host1 (LSISAS2308 running FW 20.00.07.00). Rolling back from Unraid 7.3.1 to 7.3.0 immediately resolves the issue. Controller remains operational and does not enter IOC fault state; failures appear to be command timeout related rather than HBA crashes.

I'm wondering would BIOS/Firmware update be worth it ? My feeling is no it would not help.

Skip

On 5/29/2026 at 9:39 AM, JorgeB said:

Same firmware?

Same firmware.

  • Community Expert
15 hours ago, Skipdog said:

I'm wondering would BIOS/Firmware update be worth it ?

It''s definitely worth a try.

  • Author

@JorgeB I could be wrong but for the 9305-16e it appears it is maxed out stable at:


IT_Nexus mode  - fw: 16.00.11.00, nvdata: 10.00.91.xx: Channel_9305-16e_IT_Nexus.bin
Abort Task Set - fw: 16.00.11.00, nvdata: 10.00.92.xx: Channel_9305-16e_ATS.bin

I don't believe there is anything newer but definitely could be wrong.

Skip

Edited by Skipdog

  • Author

@jynxsee I wasn't following the answer "Same firmware" -- same firmware as what? Are you running 16.00.11.00 or 16.00.12.00 ?

@JorgeB I'm very hesitant to even try the firmware upgrade as it is the only card I have to drive the external enclosure and these cards have doubled in price now.. Definitely don't want to render my system unusable. I would love to find out if anyone else having this issue is already on 16.00.12...

  • Community Expert

Firmware update should be pretty safe, and you can do it from Unraid:

  • Author

@JorgeB Before taking the plunge - the AI assistant is recommending trying to append "pcie_aspm=off" to the boot statement - do you think this is worth a try in lieu of flashing first?

  • Community Expert

I've not seen that help with a similar issue, but it won't hurt, so it's worth a try.

  • Author

OK some new data-
Upgraded to 16.00.12.00 and rebooted into the same 7.3.0 version to make sure everything worked good (it did)

Upgraded to 7.3.1 and rebooted and confirmed the timeout/resets are still happening (they are)

Tried to add pci_aspm=off to boot statement -- did not fix. The AI wants a couple more tests on the boot statement like:

/bzimage initrd=/bzroot pcie_aspm=off pci=noaer

and nomodeset pci=noaer pcie_aspm=off

and... pcie_port_pm=off pci=noaer

At this point I think i will revert it back to 7.3.0 and wait to see what can be done. Otherwise will need to change out the card to advance in UNRAID versions.

Skip

  • Community Expert
  • Solution

Doubt any kernel parameters will help, most likely you will need to wait for a kernel fix.

  • Author

@JorgeB What is the best way forward-- is there an avenue to log the bug report (regression) with Slackware, etc?

  • Community Expert

You can create a Linux kernel bug report, or just wait for a newer release, since those controllers are well used, I would think a fix would be available soon.

  • Community Expert

BTW, just found a user with a 9305-16i running Unraid without this issue, so it's not a general problem:

08:00.0 Serial Attached SCSI controller [0107]: Broadcom / LSI SAS3224 PCI-Express Fusion-MPT SAS-3 [1000:00c4] (rev 01)

Subsystem: Broadcom / LSI SAS9305-16i [1000:3190]

Kernel driver in use: mpt3sas

Kernel modules: mpt3sas

Jun 1 22:06:14 DL380G9 kernel: mpt3sas_cm0: FW Package Ver(16.00.12.00)

Jun 1 22:06:46 DL380G9 emhttpd: Unraid(tm) System Management Utility version 7.3.1

  • Author

@JorgeB Thanks for the input. That being the case it must be something different with the 9305-16e (my card) vs the internal variant -- SATA timings, expander negotiation, etc. I'll stay on the working version for now!

I am having the same issue with my 9305-16e: 7.3.1 can't finish booting and gets stuck in the loop described by Skipdog.

Configuration:

[1000:00c9] 01:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS3216 PCI-Express Fusion-MPT SAS-3 (rev 01)

FWVersion(16.00.11.00), ChipRevision(0x01)

QNAP TL-D1600S enclosure with 8 drives

  • Author

@paolobosco Good to know my scenario isn't a result of some strange configuration on my side. I can validate that going to 16.00.12.00 does not fix this problem so you can skip that!!

@JorgeB I can mark your response to wait for a potential fix via Kernel update as the solution.

  • 3 weeks later...
  • Author

@Kboogie Thanks for the detailed data point. Looks identical to my issue. I did look at another post where another user replaced his card with a 94xx series but they are expensive and i quickly ditched that idea. Hope they are able to fix the regression. 7.3.0 works great.

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

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.