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.

Hardware problems log attached.

Featured Replies

  • Community Expert

Timeout errors on multiple drives, likely a controller or cable problem, your cache device (ata7) ended up disable:

 

Dec 12 02:01:21 Tower kernel: ata7.00: exception Emask 0x0 SAct 0x180000 SErr 0x0 action 0x6 frozen
Dec 12 02:01:21 Tower kernel: ata7.00: failed command: WRITE FPDMA QUEUED
Dec 12 02:01:21 Tower kernel: ata7.00: cmd 61/08:98:40:00:02/00:00:00:00:00/40 tag 19 ncq dma 4096 out
Dec 12 02:01:21 Tower kernel:         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 12 02:01:21 Tower kernel: ata7.00: status: { DRDY }
Dec 12 02:01:21 Tower kernel: ata7.00: failed command: WRITE FPDMA QUEUED
Dec 12 02:01:21 Tower kernel: ata7.00: cmd 61/08:a0:40:00:00/00:00:20:00:00/40 tag 20 ncq dma 4096 out
Dec 12 02:01:21 Tower kernel:         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 12 02:01:21 Tower kernel: ata7.00: status: { DRDY }
Dec 12 02:01:21 Tower kernel: ata7: hard resetting link
Dec 12 02:01:27 Tower kernel: ata7: link is slow to respond, please be patient (ready=0)
Dec 12 02:01:31 Tower kernel: ata7: COMRESET failed (errno=-16)
Dec 12 02:01:31 Tower kernel: ata7: hard resetting link
Dec 12 02:01:37 Tower kernel: ata7: link is slow to respond, please be patient (ready=0)
Dec 12 02:01:41 Tower kernel: ata7: COMRESET failed (errno=-16)
Dec 12 02:01:41 Tower kernel: ata7: hard resetting link
Dec 12 02:01:47 Tower kernel: ata7: link is slow to respond, please be patient (ready=0)
Dec 12 02:01:52 Tower kernel: ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Dec 12 02:01:52 Tower kernel: ata9.00: failed command: WRITE DMA EXT
Dec 12 02:01:52 Tower kernel: ata9.00: cmd 35/00:40:d8:c8:15/00:05:6b:00:00/e0 tag 28 dma 688128 out
Dec 12 02:01:52 Tower kernel:         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 12 02:01:52 Tower kernel: ata9.00: status: { DRDY }
Dec 12 02:01:52 Tower kernel: ata9: hard resetting link
Dec 12 02:01:52 Tower kernel: ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Dec 12 02:01:52 Tower kernel: ata10.00: failed command: WRITE DMA EXT
Dec 12 02:01:52 Tower kernel: ata10.00: cmd 35/00:40:d8:db:15/00:05:6b:00:00/e0 tag 15 dma 688128 out
Dec 12 02:01:52 Tower kernel:         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 12 02:01:52 Tower kernel: ata10.00: status: { DRDY }
Dec 12 02:01:52 Tower kernel: ata10: hard resetting link
Dec 12 02:01:53 Tower kernel: ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Dec 12 02:01:53 Tower kernel: ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Dec 12 02:01:58 Tower kernel: ata10.00: qc timeout (cmd 0xec)
Dec 12 02:01:58 Tower kernel: ata9.00: qc timeout (cmd 0xec)
Dec 12 02:01:59 Tower kernel: ata9.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Dec 12 02:01:59 Tower kernel: ata9.00: revalidation failed (errno=-5)
Dec 12 02:01:59 Tower kernel: ata9: hard resetting link
Dec 12 02:01:59 Tower kernel: ata10.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Dec 12 02:01:59 Tower kernel: ata10.00: revalidation failed (errno=-5)
Dec 12 02:01:59 Tower kernel: ata10: hard resetting link
Dec 12 02:02:00 Tower kernel: ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Dec 12 02:02:00 Tower kernel: ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Dec 12 02:02:10 Tower kernel: ata10.00: qc timeout (cmd 0xec)
Dec 12 02:02:10 Tower kernel: ata9.00: qc timeout (cmd 0xec)
Dec 12 02:02:11 Tower kernel: ata10.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Dec 12 02:02:11 Tower kernel: ata10.00: revalidation failed (errno=-5)
Dec 12 02:02:11 Tower kernel: ata10: limiting SATA link speed to 3.0 Gbps
Dec 12 02:02:11 Tower kernel: ata10: hard resetting link
Dec 12 02:02:11 Tower kernel: ata9.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Dec 12 02:02:11 Tower kernel: ata9.00: revalidation failed (errno=-5)
Dec 12 02:02:11 Tower kernel: ata9: limiting SATA link speed to 3.0 Gbps
Dec 12 02:02:11 Tower kernel: ata9: hard resetting link
Dec 12 02:02:11 Tower kernel: ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 320)
Dec 12 02:02:11 Tower kernel: ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 320)
Dec 12 02:02:16 Tower kernel: ata7: COMRESET failed (errno=-16)
Dec 12 02:02:16 Tower kernel: ata7: limiting SATA link speed to 3.0 Gbps
Dec 12 02:02:16 Tower kernel: ata7: hard resetting link
Dec 12 02:02:21 Tower shfs/user: err: shfs_read: read: (5) Input/output error
Dec 12 02:02:21 Tower kernel: ata7: COMRESET failed (errno=-16)
Dec 12 02:02:21 Tower kernel: ata7: reset failed, giving up
Dec 12 02:02:21 Tower kernel: ata7.00: disabled
Dec 12 02:02:21 Tower kernel: ata7: EH complete

 

  • Author

Thank you.

  • Community Expert

Everything looks normal now, you'll need to resync both parity disks or since they are mostly valid you can do a new config with trust parity and then run a correcting check.

  • Author

I'm just letting parity run it s new course

  • Community Expert

P.S. you want to avoid the 4 Marvell ports (the first four 4 white ports) at all costs, guess where all the problem disks were connected on the previous diagnostics?

  • Author

You are correct, I moved the two parity drives to SATAIII_0 & SATAIII_1 but left the cache drive on SATAIII_M0. 

  • Community Expert
32 minutes ago, deaerator said:

but left the cache drive on SATAIII_M0. 

You should move it also.

Archived

This topic is now archived and is closed to further replies.

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.