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

Syslog filling with errors during first parity sync right after setup

PaulZAP
in General Support

Featured Replies

Hi! 

 

New user here. I have a new machine setup with unraid using 5 brand new Toshiba 16tb HDD. It seems I'm already getting errors during first parity sync. Havent even setup a share yet. Apparently crc error count increased on 3 of 5 disks simultaneously. PSU is a modular seasonic with 350w. Cables came with the motherboard but I cant comment as to their quality.

 

  


Feb 25 02:01:50 HeimNAS nmbd[8320]:   Samba name server HEIMNAS is now a local master browser for workgroup WORKGROUP on subnet 172.17.0.1
Feb 25 02:01:50 HeimNAS nmbd[8320]:   
Feb 25 02:01:50 HeimNAS nmbd[8320]:   *****
Feb 25 02:02:57 HeimNAS kernel: ata3.00: exception Emask 0x50 SAct 0x3fc0 SErr 0x480900 action 0x6 frozen
Feb 25 02:02:57 HeimNAS kernel: ata3.00: irq_stat 0x08000000, interface fatal error
Feb 25 02:02:57 HeimNAS kernel: ata3: SError: { UnrecovData HostInt 10B8B Handshk }
Feb 25 02:02:57 HeimNAS kernel: ata3.00: failed command: WRITE FPDMA QUEUED
Feb 25 02:02:57 HeimNAS kernel: ata3.00: cmd 61/b0:30:28:8b:21/01:00:0c:00:00/40 tag 6 ncq dma 221184 out
Feb 25 02:02:57 HeimNAS kernel:         res 40/00:68:98:9c:21/00:00:0c:00:00/40 Emask 0x50 (ATA bus error)
Feb 25 02:02:57 HeimNAS kernel: ata3.00: status: { DRDY }
Feb 25 02:02:57 HeimNAS kernel: ata3.00: failed command: WRITE FPDMA QUEUED
Feb 25 02:02:57 HeimNAS kernel: ata3.00: cmd 61/40:38:d8:8c:21/05:00:0c:00:00/40 tag 7 ncq dma 688128 out
Feb 25 02:02:57 HeimNAS kernel:         res 40/00:68:98:9c:21/00:00:0c:00:00/40 Emask 0x50 (ATA bus error)
Feb 25 02:02:57 HeimNAS kernel: ata3.00: status: { DRDY }
Feb 25 02:02:57 HeimNAS kernel: ata3.00: failed command: WRITE FPDMA QUEUED
Feb 25 02:02:57 HeimNAS kernel: ata3.00: cmd 61/78:40:18:92:21/01:00:0c:00:00/40 tag 8 ncq dma 192512 out
Feb 25 02:02:57 HeimNAS kernel:         res 40/00:68:98:9c:21/00:00:0c:00:00/40 Emask 0x50 (ATA bus error)
Feb 25 02:02:57 HeimNAS kernel: ata3.00: status: { DRDY }
Feb 25 02:02:57 HeimNAS kernel: ata3.00: failed command: WRITE FPDMA QUEUED
Feb 25 02:02:57 HeimNAS kernel: ata3.00: cmd 61/48:48:90:93:21/01:00:0c:00:00/40 tag 9 ncq dma 167936 out
Feb 25 02:02:57 HeimNAS kernel:         res 40/00:68:98:9c:21/00:00:0c:00:00/40 Emask 0x50 (ATA bus error)
Feb 25 02:02:57 HeimNAS kernel: ata3.00: status: { DRDY }
Feb 25 02:02:57 HeimNAS kernel: ata3.00: failed command: WRITE FPDMA QUEUED
Feb 25 02:02:57 HeimNAS kernel: ata3.00: cmd 61/50:50:d8:94:21/01:00:0c:00:00/40 tag 10 ncq dma 172032 out
Feb 25 02:02:57 HeimNAS kernel:         res 40/00:68:98:9c:21/00:00:0c:00:00/40 Emask 0x50 (ATA bus error)
Feb 25 02:02:57 HeimNAS kernel: ata3.00: status: { DRDY }
Feb 25 02:02:57 HeimNAS kernel: ata3.00: failed command: WRITE FPDMA QUEUED
Feb 25 02:02:57 HeimNAS kernel: ata3.00: cmd 61/30:58:28:96:21/01:00:0c:00:00/40 tag 11 ncq dma 155648 out
Feb 25 02:02:57 HeimNAS kernel:         res 40/00:68:98:9c:21/00:00:0c:00:00/40 Emask 0x50 (ATA bus error)
Feb 25 02:02:57 HeimNAS kernel: ata3.00: status: { DRDY }
Feb 25 02:02:57 HeimNAS kernel: ata3.00: failed command: WRITE FPDMA QUEUED
Feb 25 02:02:57 HeimNAS kernel: ata3.00: cmd 61/40:60:58:97:21/05:00:0c:00:00/40 tag 12 ncq dma 688128 out
Feb 25 02:02:57 HeimNAS kernel:         res 40/00:68:98:9c:21/00:00:0c:00:00/40 Emask 0x50 (ATA bus error)
Feb 25 02:02:57 HeimNAS kernel: ata3.00: status: { DRDY }
Feb 25 02:02:57 HeimNAS kernel: ata3.00: failed command: WRITE FPDMA QUEUED
Feb 25 02:02:57 HeimNAS kernel: ata3.00: cmd 61/40:68:98:9c:21/05:00:0c:00:00/40 tag 13 ncq dma 688128 out
Feb 25 02:02:57 HeimNAS kernel:         res 40/00:68:98:9c:21/00:00:0c:00:00/40 Emask 0x50 (ATA bus error)
Feb 25 02:02:57 HeimNAS kernel: ata3.00: status: { DRDY }
Feb 25 02:02:57 HeimNAS kernel: ata3: hard resetting link
Feb 25 02:02:57 HeimNAS kernel: ata5.00: exception Emask 0x50 SAct 0x1 SErr 0x280900 action 0x6 frozen
Feb 25 02:02:57 HeimNAS kernel: ata5.00: irq_stat 0x08000000, interface fatal error
Feb 25 02:02:57 HeimNAS kernel: ata5: SError: { UnrecovData HostInt 10B8B BadCRC }
Feb 25 02:02:57 HeimNAS kernel: ata5.00: failed command: READ FPDMA QUEUED
Feb 25 02:02:57 HeimNAS kernel: ata5.00: cmd 60/10:00:d8:a1:21/04:00:0c:00:00/40 tag 0 ncq dma 532480 in
Feb 25 02:02:57 HeimNAS kernel:         res 40/00:00:d8:a1:21/00:00:0c:00:00/40 Emask 0x50 (ATA bus error)
Feb 25 02:02:57 HeimNAS kernel: ata5.00: status: { DRDY }
Feb 25 02:02:57 HeimNAS kernel: ata5: hard resetting link
Feb 25 02:02:57 HeimNAS kernel: ata4.00: exception Emask 0x50 SAct 0x80000000 SErr 0x480900 action 0x6 frozen
Feb 25 02:02:57 HeimNAS kernel: ata4.00: irq_stat 0x08000000, interface fatal error
Feb 25 02:02:57 HeimNAS kernel: ata4: SError: { UnrecovData HostInt 10B8B Handshk }
Feb 25 02:02:57 HeimNAS kernel: ata4.00: failed command: WRITE FPDMA QUEUED
Feb 25 02:02:57 HeimNAS kernel: ata4.00: cmd 61/40:f8:98:9c:21/05:00:0c:00:00/40 tag 31 ncq dma 688128 out
Feb 25 02:02:57 HeimNAS kernel:         res 40/00:f8:98:9c:21/00:00:0c:00:00/40 Emask 0x50 (ATA bus error)
Feb 25 02:02:57 HeimNAS kernel: ata4.00: status: { DRDY }
Feb 25 02:02:57 HeimNAS kernel: ata4: hard resetting link
Feb 25 02:02:57 HeimNAS kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 25 02:02:57 HeimNAS kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 25 02:02:57 HeimNAS kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 25 02:02:57 HeimNAS kernel: ata4.00: configured for UDMA/133
Feb 25 02:02:57 HeimNAS kernel: ata4: EH complete
Feb 25 02:02:57 HeimNAS kernel: ata3.00: configured for UDMA/133
Feb 25 02:02:57 HeimNAS kernel: ata3: EH complete
Feb 25 02:02:58 HeimNAS kernel: ata5.00: configured for UDMA/133
Feb 25 02:02:58 HeimNAS kernel: ata5: EH complete
Feb 25 02:07:35 HeimNAS kernel: ata7.00: exception Emask 0x50 SAct 0x200 SErr 0x280900 action 0x6 frozen
Feb 25 02:07:35 HeimNAS kernel: ata7.00: irq_stat 0x08000000, interface fatal error
Feb 25 02:07:35 HeimNAS kernel: ata7: SError: { UnrecovData HostInt 10B8B BadCRC }
Feb 25 02:07:35 HeimNAS kernel: ata7.00: failed command: READ FPDMA QUEUED
Feb 25 02:07:35 HeimNAS kernel: ata7.00: cmd 60/f8:48:88:96:5b/03:00:14:00:00/40 tag 9 ncq dma 520192 in
Feb 25 02:07:35 HeimNAS kernel:         res 40/00:48:88:96:5b/00:00:14:00:00/40 Emask 0x50 (ATA bus error)
Feb 25 02:07:35 HeimNAS kernel: ata7.00: status: { DRDY }
Feb 25 02:07:35 HeimNAS kernel: ata7: hard resetting link
Feb 25 02:07:35 HeimNAS kernel: ata4.00: exception Emask 0x50 SAct 0x400 SErr 0x480900 action 0x6 frozen
Feb 25 02:07:35 HeimNAS kernel: ata4.00: irq_stat 0x08000000, interface fatal error
Feb 25 02:07:35 HeimNAS kernel: ata4: SError: { UnrecovData HostInt 10B8B Handshk }
Feb 25 02:07:35 HeimNAS kernel: ata4.00: failed command: WRITE FPDMA QUEUED
Feb 25 02:07:35 HeimNAS kernel: ata4.00: cmd 61/d0:50:38:7d:5b/03:00:14:00:00/40 tag 10 ncq dma 499712 out
Feb 25 02:07:35 HeimNAS kernel:         res 40/00:50:38:7d:5b/00:00:14:00:00/40 Emask 0x50 (ATA bus error)
Feb 25 02:07:35 HeimNAS kernel: ata4.00: status: { DRDY }
Feb 25 02:07:35 HeimNAS kernel: ata4: hard resetting link
Feb 25 02:07:35 HeimNAS kernel: ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 25 02:07:35 HeimNAS kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 25 02:07:35 HeimNAS kernel: ata4.00: configured for UDMA/133
Feb 25 02:07:35 HeimNAS kernel: ata4: EH complete
Feb 25 02:07:35 HeimNAS kernel: ata7.00: configured for UDMA/133
Feb 25 02:07:35 HeimNAS kernel: ata7: EH complete

 

 

 

Am I in trouble?

 

 

Best Regards

Paul

  • Quote

    You should post your full diagnostics zip file to your next post.

     

    In any case, constant failures on several drives is not a good news. Unless it is a batch of bad drives, it is probably problem on a common part, controller, power supply, splitter, etc.

  • Quote
    • Community Expert

    Looks like a connection problem, and CRC errors usually point to the SATA cables, start by replacing those.

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