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

Extremlely slow data rebuilt

Keint
in General Support

Featured Replies

Hello )
I just switch my 8TO HDD by a 10TB HDD.

When I m rebuilding, it s extremely slow ...
10 MB/S average ...

But everything seems ok from my NOOB side, I don t understand why it s so slow ...
I tried to stop all the docker service, and same ....
Any idea?

Thanks in advance !!!!

Attached my diag ...

tower-diagnostics-20260323-1340.zip

  • Quote
    • Community Expert

    Disk6 keeps having connection errors and being reset/downgraded to SATA 1 speeds, check/replace SATA cable.

    Mar 23 13:41:50 Tower kernel: ata13: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Mar 23 13:41:50 Tower kernel: ata13.00: configured for UDMA/33
Mar 23 13:41:50 Tower kernel: ata13: EH complete
Mar 23 13:41:53 Tower kernel: ata13.00: exception Emask 0x10 SAct 0x1f000 SErr 0x4890000 action 0xe frozen
Mar 23 13:41:53 Tower kernel: ata13.00: irq_stat 0x0c400040, interface fatal error, connection status changed
Mar 23 13:41:53 Tower kernel: ata13: SError: { PHYRdyChg 10B8B LinkSeq DevExch }
Mar 23 13:41:53 Tower kernel: ata13.00: failed command: READ FPDMA QUEUED
Mar 23 13:41:53 Tower kernel: ata13.00: cmd 60/98:60:30:60:12/03:00:03:00:00/40 tag 12 ncq dma 471040 in
Mar 23 13:41:53 Tower kernel:         res 40/00:01:04:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
Mar 23 13:41:53 Tower kernel: ata13.00: status: { DRDY }
Mar 23 13:41:53 Tower kernel: ata13.00: failed command: READ FPDMA QUEUED
Mar 23 13:41:53 Tower kernel: ata13.00: cmd 60/10:68:c8:63:12/02:00:03:00:00/40 tag 13 ncq dma 270336 in
Mar 23 13:41:53 Tower kernel:         res 40/00:0d:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
Mar 23 13:41:53 Tower kernel: ata13.00: status: { DRDY }
Mar 23 13:41:53 Tower kernel: ata13.00: failed command: READ FPDMA QUEUED
Mar 23 13:41:53 Tower kernel: ata13.00: cmd 60/c0:70:d8:65:12/04:00:03:00:00/40 tag 14 ncq dma 622592 in
Mar 23 13:41:53 Tower kernel:         res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
Mar 23 13:41:53 Tower kernel: ata13.00: status: { DRDY }
Mar 23 13:41:53 Tower kernel: ata13.00: failed command: READ FPDMA QUEUED
Mar 23 13:41:53 Tower kernel: ata13.00: cmd 60/30:78:98:6a:12/04:00:03:00:00/40 tag 15 ncq dma 548864 in
Mar 23 13:41:53 Tower kernel:         res 40/00:01:e0:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
Mar 23 13:41:53 Tower kernel: ata13.00: status: { DRDY }
Mar 23 13:41:53 Tower kernel: ata13.00: failed command: READ FPDMA QUEUED
Mar 23 13:41:53 Tower kernel: ata13.00: cmd 60/50:80:c8:6e:12/04:00:03:00:00/40 tag 16 ncq dma 565248 in
Mar 23 13:41:53 Tower kernel:         res 40/00:01:e0:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
Mar 23 13:41:53 Tower kernel: ata13.00: status: { DRDY }
Mar 23 13:41:53 Tower kernel: ata13: hard resetting link
Mar 23 13:41:59 Tower kernel: ata13: link is slow to respond, please be patient (ready=0)
Mar 23 13:42:04 Tower kernel: ata13: hard resetting link
Mar 23 13:42:09 Tower kernel: ata13: link is slow to respond, please be patient (ready=0)
Mar 23 13:42:14 Tower kernel: ata13: hard resetting link

    Edited by Kilrah

  • Quote
    • Author
    3 hours ago, Kilrah said:

    Disk6 keeps having connection errors and being reset/downgraded to SATA 1 speeds, check/replace SATA cable.

    Mar 23 13:41:50 Tower kernel: ata13: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Mar 23 13:41:50 Tower kernel: ata13.00: configured for UDMA/33
Mar 23 13:41:50 Tower kernel: ata13: EH complete
Mar 23 13:41:53 Tower kernel: ata13.00: exception Emask 0x10 SAct 0x1f000 SErr 0x4890000 action 0xe frozen
Mar 23 13:41:53 Tower kernel: ata13.00: irq_stat 0x0c400040, interface fatal error, connection status changed
Mar 23 13:41:53 Tower kernel: ata13: SError: { PHYRdyChg 10B8B LinkSeq DevExch }
Mar 23 13:41:53 Tower kernel: ata13.00: failed command: READ FPDMA QUEUED
Mar 23 13:41:53 Tower kernel: ata13.00: cmd 60/98:60:30:60:12/03:00:03:00:00/40 tag 12 ncq dma 471040 in
Mar 23 13:41:53 Tower kernel:         res 40/00:01:04:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
Mar 23 13:41:53 Tower kernel: ata13.00: status: { DRDY }
Mar 23 13:41:53 Tower kernel: ata13.00: failed command: READ FPDMA QUEUED
Mar 23 13:41:53 Tower kernel: ata13.00: cmd 60/10:68:c8:63:12/02:00:03:00:00/40 tag 13 ncq dma 270336 in
Mar 23 13:41:53 Tower kernel:         res 40/00:0d:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
Mar 23 13:41:53 Tower kernel: ata13.00: status: { DRDY }
Mar 23 13:41:53 Tower kernel: ata13.00: failed command: READ FPDMA QUEUED
Mar 23 13:41:53 Tower kernel: ata13.00: cmd 60/c0:70:d8:65:12/04:00:03:00:00/40 tag 14 ncq dma 622592 in
Mar 23 13:41:53 Tower kernel:         res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
Mar 23 13:41:53 Tower kernel: ata13.00: status: { DRDY }
Mar 23 13:41:53 Tower kernel: ata13.00: failed command: READ FPDMA QUEUED
Mar 23 13:41:53 Tower kernel: ata13.00: cmd 60/30:78:98:6a:12/04:00:03:00:00/40 tag 15 ncq dma 548864 in
Mar 23 13:41:53 Tower kernel:         res 40/00:01:e0:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
Mar 23 13:41:53 Tower kernel: ata13.00: status: { DRDY }
Mar 23 13:41:53 Tower kernel: ata13.00: failed command: READ FPDMA QUEUED
Mar 23 13:41:53 Tower kernel: ata13.00: cmd 60/50:80:c8:6e:12/04:00:03:00:00/40 tag 16 ncq dma 565248 in
Mar 23 13:41:53 Tower kernel:         res 40/00:01:e0:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
Mar 23 13:41:53 Tower kernel: ata13.00: status: { DRDY }
Mar 23 13:41:53 Tower kernel: ata13: hard resetting link
Mar 23 13:41:59 Tower kernel: ata13: link is slow to respond, please be patient (ready=0)
Mar 23 13:42:04 Tower kernel: ata13: hard resetting link
Mar 23 13:42:09 Tower kernel: ata13: link is slow to respond, please be patient (ready=0)
Mar 23 13:42:14 Tower kernel: ata13: hard resetting link

    Thanks a lot !
    For my info, how do ou know it s a disk 6 who has a problem? To avoid to bother you next time :)

    Thanks!!!

  • Quote
    • Community Expert

    Search for the "ata13.00" in syslog, you'll find a line with the drive model, then refer to your main page

    Mar 23 12:53:55 Tower kernel: ata13.00: ATA-11: ST10000NE0008-2PL103, SN04, max UDMA/133

    Edited by Kilrah

  • Quote
    • Author

    Thanks a lot !

    but I change all the SATA SAS cables and same same ... I m rebuilding at 6/ 10MB/S I can t understand where is the probleme ...

    tower-diagnostics-20260323-2151.zip

  • Quote
    • Community Expert

    There's somthing elese reading from disk9.

  • Quote
    • Author
    1 hour ago, JorgeB said:

    There's somthing elese reading from disk9.

    thanks but what is mean?

    After 1h the transfert start to be faster like 150/200 MB/S super weird ...

    Edited by Keint

  • Quote
    • Community Expert

    Anything reading/writing to the array while the rebuild is running will slow it down. Avoid any activity if you want it to run as fast as possible.

    Edited by Kilrah

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