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.

Seagate Exos16 12TB hard drive read errors only in Unraid

Featured Replies

 I've bought a refurbished Seagate Exos16 12TB SATA Hard Drive. Plugged it into my PC and did smart and HDDScan read test on all sectors, no reported bad sectors.

Once i plugged it into my Unraid server, it started showing errors in the array so i did the normal procedure and turned it off, replaced SATA cables and had a power supply waiting to go in as mine was a bit sketchy so i took the opportunity to replace that as well.

Same issue continued. I replaced the disk with other ones and no errors, tried it on the SATA ports and on the LSI HBA as well.

Took the disk out and checked firmware on the PC again, it was on SS03 so i updated the disk firmware to the latest SS04 version.

Put it back in and still have errors. But nothing on SMART test.

Any idea what it could be?

Many thanks

Sep  7 20:50:28 UNRAIDSERVER kernel: mdcmd (4): import 3 sdc 64 11718885324 0 ST12000NM003G-2MT113_ZL293Q0S
Sep  7 20:50:28 UNRAIDSERVER kernel: md: import disk3: (sdc) ST12000NM003G-2MT113_ZL293Q0S size: 11718885324 
Sep  7 20:50:28 UNRAIDSERVER emhttpd: read SMART /dev/sdc
Sep  7 20:51:04 UNRAIDSERVER kernel: ata8.00: exception Emask 0x0 SAct 0x8000001f SErr 0x0 action 0x0
Sep  7 20:51:04 UNRAIDSERVER kernel: ata8.00: irq_stat 0x40000008
Sep  7 20:51:04 UNRAIDSERVER kernel: ata8.00: failed command: READ FPDMA QUEUED
Sep  7 20:51:04 UNRAIDSERVER kernel: ata8.00: cmd 60/00:f8:40:0c:00/04:00:00:00:00/40 tag 31 ncq dma 524288 in
Sep  7 20:51:04 UNRAIDSERVER kernel: ata8.00: status: { DRDY SENSE ERR }
Sep  7 20:51:04 UNRAIDSERVER kernel: ata8.00: error: { ABRT }
Sep  7 20:51:04 UNRAIDSERVER kernel: ata8.00: supports DRM functions and may not be fully accessible
Sep  7 20:51:04 UNRAIDSERVER kernel: ata8.00: supports DRM functions and may not be fully accessible
Sep  7 20:51:04 UNRAIDSERVER kernel: ata8.00: configured for UDMA/133
Sep  7 20:51:04 UNRAIDSERVER kernel: sd 9:0:0:0: [sdc] tag#31 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Sep  7 20:51:04 UNRAIDSERVER kernel: sd 9:0:0:0: [sdc] tag#31 Sense Key : 0x5 [current] 
Sep  7 20:51:04 UNRAIDSERVER kernel: sd 9:0:0:0: [sdc] tag#31 ASC=0x24 ASCQ=0x0 
Sep  7 20:51:04 UNRAIDSERVER kernel: sd 9:0:0:0: [sdc] tag#31 CDB: opcode=0x88 88 00 00 00 00 00 00 00 0c 40 00 00 04 00 00 00
Sep  7 20:51:04 UNRAIDSERVER kernel: critical target error, dev sdc, sector 3136 op 0x0:(READ) flags 0x0 phys_seg 128 prio class 0
Sep  7 20:51:04 UNRAIDSERVER kernel: ata8: EH complete
Sep  7 20:51:04 UNRAIDSERVER kernel: ata8.00: exception Emask 0x0 SAct 0x10f000 SErr 0x0 action 0x0
Sep  7 20:51:04 UNRAIDSERVER kernel: ata8.00: irq_stat 0x40000008
Sep  7 20:51:04 UNRAIDSERVER kernel: ata8.00: failed command: READ FPDMA QUEUED
Sep  7 20:51:04 UNRAIDSERVER kernel: ata8.00: cmd 60/60:78:e0:4f:00/00:00:00:00:00/40 tag 15 ncq dma 49152 in
Sep  7 20:51:04 UNRAIDSERVER kernel: ata8.00: status: { DRDY SENSE ERR }
Sep  7 20:51:04 UNRAIDSERVER kernel: ata8.00: error: { ABRT }
Sep  7 20:51:04 UNRAIDSERVER kernel: ata8.00: supports DRM functions and may not be fully accessible
Sep  7 20:51:05 UNRAIDSERVER kernel: ata8.00: supports DRM functions and may not be fully accessible
Sep  7 20:51:05 UNRAIDSERVER kernel: ata8.00: configured for UDMA/133
Sep  7 20:51:05 UNRAIDSERVER kernel: sd 9:0:0:0: [sdc] tag#15 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Sep  7 20:51:05 UNRAIDSERVER kernel: sd 9:0:0:0: [sdc] tag#15 Sense Key : 0x5 [current] 
Sep  7 20:51:05 UNRAIDSERVER kernel: sd 9:0:0:0: [sdc] tag#15 ASC=0x24 ASCQ=0x0 
Sep  7 20:51:05 UNRAIDSERVER kernel: sd 9:0:0:0: [sdc] tag#15 CDB: opcode=0x88 88 00 00 00 00 00 00 00 4f e0 00 00 00 60 00 00
Sep  7 20:51:05 UNRAIDSERVER kernel: critical target error, dev sdc, sector 20448 op 0x0:(READ) flags 0x0 phys_seg 12 prio class 0
Sep  7 20:51:05 UNRAIDSERVER kernel: ata8: EH complete

unraidserver-diagnostics-20250907-2140.zip

  • Community Expert

Swap both cables with another disk, one that is connected to the HBA, try again, and post new diags.

  • Author

Swapped the SATA cable with a drive that was connected to the HBA.

Will post another one with the power connector swap as well

Here's the new diags

unraidserver-diagnostics-20250908-0918.zip

Edited by raizan

  • Community Expert

Since the issue persists, it suggests an actual disk problem, despite the good looking SMART, try a different disk if possible.

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.