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.

Couple drive errors on new drive: "exception Emask 0x0 SAct 0x8ce8007e SErr 0x0 action 0x6 frozen"

Featured Replies

Hey all! Long time listener, first time caller.

Just built a new server, and added a second parity drive (TOSHIBA 10TB N300 PRO NAS). The other night, had a bunch of read errors and the drive was disabled. Naturally, I replaced the SATA cable and even ran to a different port on the mobo. Worked fine until last night (couple days later) and now I have 9 errors on the disk tab, and some errors in the log. The drive is still enabled however.

Drive log has these, and I've also attached full logs. I did the basics like running an extended SMART test, and unplugging/replugging SATA data and power cables to make sure they were seated. Just seems weird that it's my only new drive in a new build, and the one having issues...

Dec 25 18:35:33 UnraidServer kernel: ata2: SATA max UDMA/133 abar m2048@0x81902000 port 0x81902180 irq 128 lpm-pol 0

Dec 25 18:35:33 UnraidServer kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)

Dec 25 18:35:33 UnraidServer kernel: ata2.00: ATA-11: TOSHIBA HDWG71AUZSVB, 0501, max UDMA/133

Dec 25 18:35:33 UnraidServer kernel: ata2.00: 19532873728 sectors, multi 16: LBA48 NCQ (depth 32), AA

Dec 25 18:35:33 UnraidServer kernel: ata2.00: Features: NCQ-sndrcv NCQ-prio

Dec 25 18:35:33 UnraidServer kernel: ata2.00: configured for UDMA/133

Dec 25 18:35:33 UnraidServer kernel: sd 1:0:0:0: [sda] 19532873728 512-byte logical blocks: (10.0 TB/9.10 TiB)

Dec 25 18:35:33 UnraidServer kernel: sd 1:0:0:0: [sda] 4096-byte physical blocks

Dec 25 18:35:33 UnraidServer kernel: sd 1:0:0:0: [sda] Write Protect is off

Dec 25 18:35:33 UnraidServer kernel: sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00

Dec 25 18:35:33 UnraidServer kernel: sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Dec 25 18:35:33 UnraidServer kernel: sd 1:0:0:0: [sda] Preferred minimum I/O size 4096 bytes

Dec 25 18:35:33 UnraidServer kernel: sda: sda1

Dec 25 18:35:33 UnraidServer kernel: sd 1:0:0:0: [sda] Attached SCSI disk

Dec 25 18:36:30 UnraidServer emhttpd: online: TOSHIBA_HDWG71AUZSVB_64U0A08WFW5J (sda) 512 19532873728

Dec 25 18:36:30 UnraidServer kernel: mdcmd (2): import 29 sda 64 9766436812 0 TOSHIBA_HDWG71AUZSVB_64U0A08WFW5J

Dec 25 18:36:30 UnraidServer kernel: md: import disk29: (sda) TOSHIBA_HDWG71AUZSVB_64U0A08WFW5J size: 9766436812

Dec 25 18:36:31 UnraidServer emhttpd: read SMART /dev/sda

Dec 25 18:36:37 UnraidServer emhttpd: shcmd (50): echo 128 > /sys/block/sda/queue/nr_requests

Dec 25 18:38:07 UnraidServer emhttpd: read SMART /dev/sda

Dec 25 18:38:54 UnraidServer kernel: mdcmd (2): import 29 sda 64 9766436812 0 TOSHIBA_HDWG71AUZSVB_64U0A08WFW5J

Dec 25 18:38:54 UnraidServer kernel: md: import disk29: (sda) TOSHIBA_HDWG71AUZSVB_64U0A08WFW5J size: 9766436812

Dec 25 18:39:55 UnraidServer emhttpd: read SMART /dev/sda

Dec 25 18:40:02 UnraidServer kernel: mdcmd (2): import 29 sda 64 9766436812 0 TOSHIBA_HDWG71AUZSVB_64U0A08WFW5J

Dec 25 18:40:02 UnraidServer kernel: md: import disk29: (sda) TOSHIBA_HDWG71AUZSVB_64U0A08WFW5J size: 9766436812

Dec 25 18:40:14 UnraidServer emhttpd: shcmd (325): echo 128 > /sys/block/sda/queue/nr_requests

Dec 25 18:40:38 UnraidServer emhttpd: spinning down /dev/sda

Dec 25 18:40:40 UnraidServer emhttpd: read SMART /dev/sda

Dec 26 16:37:14 UnraidServer emhttpd: spinning down /dev/sda

Dec 27 00:00:23 UnraidServer emhttpd: read SMART /dev/sda

Dec 27 01:01:26 UnraidServer emhttpd: spinning down /dev/sda

Dec 27 23:30:20 UnraidServer emhttpd: read SMART /dev/sda

Dec 27 23:30:49 UnraidServer kernel: ata2.00: exception Emask 0x0 SAct 0x8ce8007e SErr 0x0 action 0x6 frozen

Dec 27 23:30:49 UnraidServer kernel: ata2.00: failed command: READ FPDMA QUEUED

Dec 27 23:30:49 UnraidServer kernel: ata2.00: cmd 60/00:08:18:95:8c/04:00:69:02:00/40 tag 1 ncq dma 524288 in

Dec 27 23:30:49 UnraidServer kernel: ata2.00: status: { DRDY }

Dec 27 23:30:49 UnraidServer kernel: ata2.00: failed command: READ FPDMA QUEUED

Dec 27 23:30:49 UnraidServer kernel: ata2.00: cmd 60/00:10:18:99:8c/04:00:69:02:00/40 tag 2 ncq dma 524288 in

Dec 27 23:30:49 UnraidServer kernel: ata2.00: status: { DRDY }

Dec 27 23:30:49 UnraidServer kernel: ata2.00: failed command: READ FPDMA QUEUED

Dec 27 23:30:49 UnraidServer kernel: ata2.00: cmd 60/00:18:18:9d:8c/04:00:69:02:00/40 tag 3 ncq dma 524288 in

Dec 27 23:30:49 UnraidServer kernel: ata2.00: status: { DRDY }

Dec 27 23:30:49 UnraidServer kernel: ata2.00: failed command: READ FPDMA QUEUED

Dec 27 23:30:49 UnraidServer kernel: ata2.00: cmd 60/00:20:18:a1:8c/04:00:69:02:00/40 tag 4 ncq dma 524288 in

Dec 27 23:30:49 UnraidServer kernel: ata2.00: status: { DRDY }

Dec 27 23:30:49 UnraidServer kernel: ata2.00: failed command: READ FPDMA QUEUED

Dec 27 23:30:49 UnraidServer kernel: ata2.00: cmd 60/00:28:18:a5:8c/04:00:69:02:00/40 tag 5 ncq dma 524288 in

Dec 27 23:30:49 UnraidServer kernel: ata2.00: status: { DRDY }

Dec 27 23:30:49 UnraidServer kernel: ata2.00: failed command: READ FPDMA QUEUED

Dec 27 23:30:49 UnraidServer kernel: ata2.00: cmd 60/30:30:18:a9:8c/03:00:69:02:00/40 tag 6 ncq dma 417792 in

Dec 27 23:30:49 UnraidServer kernel: ata2.00: status: { DRDY }

Dec 27 23:30:49 UnraidServer kernel: ata2.00: failed command: READ FPDMA QUEUED

Dec 27 23:30:49 UnraidServer kernel: ata2.00: cmd 60/00:98:18:79:8c/04:00:69:02:00/40 tag 19 ncq dma 524288 in

Dec 27 23:30:49 UnraidServer kernel: ata2.00: status: { DRDY }

Dec 27 23:30:49 UnraidServer kernel: ata2.00: failed command: READ FPDMA QUEUED

Dec 27 23:30:49 UnraidServer kernel: ata2.00: cmd 60/00:a8:18:7d:8c/04:00:69:02:00/40 tag 21 ncq dma 524288 in

Dec 27 23:30:49 UnraidServer kernel: ata2.00: status: { DRDY }

Dec 27 23:30:49 UnraidServer kernel: ata2.00: failed command: READ FPDMA QUEUED

Dec 27 23:30:49 UnraidServer kernel: ata2.00: cmd 60/00:b0:18:81:8c/04:00:69:02:00/40 tag 22 ncq dma 524288 in

Dec 27 23:30:49 UnraidServer kernel: ata2.00: status: { DRDY }

Dec 27 23:30:49 UnraidServer kernel: ata2.00: failed command: READ FPDMA QUEUED

Dec 27 23:30:49 UnraidServer kernel: ata2.00: cmd 60/00:b8:18:85:8c/04:00:69:02:00/40 tag 23 ncq dma 524288 in

Dec 27 23:30:49 UnraidServer kernel: ata2.00: status: { DRDY }

Dec 27 23:30:49 UnraidServer kernel: ata2.00: failed command: READ FPDMA QUEUED

Dec 27 23:30:49 UnraidServer kernel: ata2.00: cmd 60/00:d0:18:89:8c/04:00:69:02:00/40 tag 26 ncq dma 524288 in

Dec 27 23:30:49 UnraidServer kernel: ata2.00: status: { DRDY }

Dec 27 23:30:49 UnraidServer kernel: ata2.00: failed command: READ FPDMA QUEUED

Dec 27 23:30:49 UnraidServer kernel: ata2.00: cmd 60/00:d8:18:8d:8c/04:00:69:02:00/40 tag 27 ncq dma 524288 in

Dec 27 23:30:49 UnraidServer kernel: ata2.00: status: { DRDY }

Dec 27 23:30:49 UnraidServer kernel: ata2.00: failed command: READ FPDMA QUEUED

Dec 27 23:30:49 UnraidServer kernel: ata2.00: cmd 60/00:f8:18:91:8c/04:00:69:02:00/40 tag 31 ncq dma 524288 in

Dec 27 23:30:49 UnraidServer kernel: ata2.00: status: { DRDY }

Dec 27 23:30:49 UnraidServer kernel: ata2: hard resetting link

Dec 27 23:30:55 UnraidServer kernel: ata2: link is slow to respond, please be patient (ready=0)

Dec 27 23:30:59 UnraidServer kernel: ata2: hard resetting link

Dec 27 23:31:05 UnraidServer kernel: ata2: link is slow to respond, please be patient (ready=0)

Dec 27 23:31:09 UnraidServer kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)

Dec 27 23:31:09 UnraidServer kernel: ata2.00: configured for UDMA/133

Dec 27 23:31:09 UnraidServer kernel: ata2: EH complete

Dec 28 01:01:20 UnraidServer emhttpd: spinning down /dev/sda

Dec 29 02:18:21 UnraidServer emhttpd: read SMART /dev/sda

Dec 29 02:18:48 UnraidServer kernel: sd 1:0:0:0: [sda] tag#17 UNKNOWN(0x2003) Result: hostbyte=0x03 driverbyte=DRIVER_OK cmd_age=38s

Dec 29 02:18:48 UnraidServer kernel: sd 1:0:0:0: [sda] tag#17 CDB: opcode=0x88 88 00 00 00 00 01 80 01 b0 98 00 00 00 48 00 00

Dec 29 02:18:48 UnraidServer kernel: I/O error, dev sda, sector 6442561688 op 0x0:(READ) flags 0x0 phys_seg 9 prio class 0

Dec 29 03:20:36 UnraidServer emhttpd: spinning down /dev/sda

Dec 29 04:40:08 UnraidServer emhttpd: read SMART /dev/sda

Dec 29 04:40:38 UnraidServer kernel: ata2.00: exception Emask 0x0 SAct 0x10 SErr 0x0 action 0x6 frozen

Dec 29 04:40:38 UnraidServer kernel: ata2.00: failed command: READ FPDMA QUEUED

Dec 29 04:40:38 UnraidServer kernel: ata2.00: cmd 60/08:20:80:76:01/00:00:00:01:00/40 tag 4 ncq dma 4096 in

Dec 29 04:40:38 UnraidServer kernel: ata2.00: status: { DRDY }

Dec 29 04:40:38 UnraidServer kernel: ata2: hard resetting link

Dec 29 04:40:43 UnraidServer kernel: ata2: link is slow to respond, please be patient (ready=0)

Dec 29 04:40:48 UnraidServer kernel: ata2: hard resetting link

Dec 29 04:40:53 UnraidServer kernel: ata2: link is slow to respond, please be patient (ready=0)

Dec 29 04:40:58 UnraidServer kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)

Dec 29 04:40:58 UnraidServer kernel: ata2.00: configured for UDMA/133

Dec 29 04:40:58 UnraidServer kernel: ata2: EH complete

Any ideas where to go from here? I do see a ton of "disk shift" on this drive that I don't have on my other Toshiba drives... but it seems that's pretty common from my Google-fu.

Thanks in advance!

unraidserver-diagnostics-20251229-1920.zip

6 hours ago, deadwynter said:

Dec 27 23:30:20 UnraidServer emhttpd: read SMART /dev/sda

Dec 27 23:30:49 UnraidServer kernel: ata2.00: exception Emask 0x0 SAct 0x8ce8007e SErr 0x0 action 0x6 frozen

The errors happened just after spin up, you may want to try that drive in a different controller, and if it doesn't help, disable pin down.

  • Author
3 hours ago, JorgeB said:

The errors happened just after spin up, you may want to try that drive in a different controller, and if it doesn't help, disable pin down.

Oh good catch! I actually did switch it after the first time from my LSI SAS card to a direct SATA port on the mobo, but I also changed the SATA data cable at that time as well. That error might have been different though... so I'll try disabling spin down. Thanks!

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.