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.

Paritydisk 1 keeps restarting on Paritycheck/parity write

Featured Replies

Hey guys,

 

i do have a severe problem with my unraid server.

my parity disk1 kept restarting on parity checks (Seagate Ironwolf 8Tb CMR).

Smartchecks are clear and free of errors. 

Even though i've replaced the disk with a new disk same type.

I've changed the sata cable and powercable and my new drive keeps doing this while rebuilding parity information.

on every disk-restart parity checks slows down due to the spinup of the disk.

 

with the new disk rebuild runs longer until paritydisk1 restarts.

 

do you have any idea?

 

Diagnostics log is attached.

 

Thanks alot

 

sideinfo: i've enabled encryption on my array so i have to rebuild parity.

tower-diagnostics-20210814-0829.zip

Edited by desertfox_0815
texterror

  • Author

I've enabled the smart value "command time out" on both parity disks and parity disk2 gets errors.

is this something to worry about!?

should i change to single parity until the source error is found?!

 

 

error1.PNG

error2.PNG

  • Community Expert

Constant ATA errors on both parity disks, replace/swap cables, including power and try again.

  • Author

Ok thanks,

 

cables are already ordered. Will arrive monday.

could you tell me where you found these errors? 

  • Community Expert

You can see them in the syslog, see if they go way after the cables swap:

 

Aug 14 07:53:02 Tower kernel: ata2.00: status: { DRDY }
Aug 14 07:53:02 Tower kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Aug 14 07:53:02 Tower kernel: ata2.00: cmd 61/40:b0:e0:aa:bb/05:00:2c:00:00/40 tag 22 ncq dma 688128 out
Aug 14 07:53:02 Tower kernel:         res 40/00:a0:60:a0:bb/00:00:2c:00:00/40 Emask 0x50 (ATA bus error)
Aug 14 07:53:02 Tower kernel: ata2.00: status: { DRDY }
Aug 14 07:53:02 Tower kernel: ata2: hard resetting link
Aug 14 07:53:12 Tower kernel: ata2: softreset failed (1st FIS failed)
Aug 14 07:53:12 Tower kernel: ata2: hard resetting link
Aug 14 07:53:14 Tower kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Aug 14 07:53:14 Tower kernel: ata2.00: configured for UDMA/133
Aug 14 07:53:14 Tower kernel: ata2: EH complete
Aug 14 07:54:07 Tower kernel: ata16.00: exception Emask 0x10 SAct 0xf8000 SErr 0x190002 action 0xe frozen
Aug 14 07:54:07 Tower kernel: ata16.00: irq_stat 0x80400000, PHY RDY changed
Aug 14 07:54:07 Tower kernel: ata16: SError: { RecovComm PHYRdyChg 10B8B Dispar }
Aug 14 07:54:07 Tower kernel: ata16.00: failed command: WRITE FPDMA QUEUED
Aug 14 07:54:07 Tower kernel: ata16.00: cmd 61/40:78:50:88:91/05:00:2d:00:00/40 tag 15 ncq dma 688128 out
Aug 14 07:54:07 Tower kernel:         res 40/00:78:50:88:91/00:00:2d:00:00/40 Emask 0x10 (ATA bus error)
Aug 14 07:54:07 Tower kernel: ata16.00: status: { DRDY }
Aug 14 07:54:07 Tower kernel: ata16.00: failed command: WRITE FPDMA QUEUED
Aug 14 07:54:07 Tower kernel: ata16.00: cmd 61/48:80:90:8d:91/01:00:2d:00:00/40 tag 16 ncq dma 167936 out
Aug 14 07:54:07 Tower kernel:         res 40/00:78:50:88:91/00:00:2d:00:00/40 Emask 0x10 (ATA bus error)
Aug 14 07:54:07 Tower kernel: ata16.00: status: { DRDY }
Aug 14 07:54:07 Tower kernel: ata16.00: failed command: WRITE FPDMA QUEUED
Aug 14 07:54:07 Tower kernel: ata16.00: cmd 61/88:88:d8:8e:91/04:00:2d:00:00/40 tag 17 ncq dma 593920 out
Aug 14 07:54:07 Tower kernel:         res 40/00:78:50:88:91/00:00:2d:00:00/40 Emask 0x10 (ATA bus error)
Aug 14 07:54:07 Tower kernel: ata16.00: status: { DRDY }
Aug 14 07:54:07 Tower kernel: ata16.00: failed command: WRITE FPDMA QUEUED
Aug 14 07:54:07 Tower kernel: ata16.00: cmd 61/40:90:60:93:91/05:00:2d:00:00/40 tag 18 ncq dma 688128 out
Aug 14 07:54:07 Tower kernel:         res 40/00:78:50:88:91/00:00:2d:00:00/40 Emask 0x10 (ATA bus error)
Aug 14 07:54:07 Tower kernel: ata16.00: status: { DRDY }
Aug 14 07:54:07 Tower kernel: ata16.00: failed command: WRITE FPDMA QUEUED
Aug 14 07:54:07 Tower kernel: ata16.00: cmd 61/a0:98:a0:98:91/02:00:2d:00:00/40 tag 19 ncq dma 344064 out
Aug 14 07:54:07 Tower kernel:         res 40/00:78:50:88:91/00:00:2d:00:00/40 Emask 0x10 (ATA bus error)

 

Currently ATA2 is parity, ATA16 is parity2.

 

  • Author

Changed Powercables...Problem is gone. 

I was able to rebuild parity without errors. the "safety" parity check was also clean.

 

Thanks alot

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.