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.

Parity check much slower than with new motherboard

Featured Replies

I was running a supermicro X8SIL-F and the parity check was very quick (just under a hundred MB per sec)

Parity check took 13 1/2 hours on the X8SIL-F

 

I upgraded my motherboard to a supermicro X8DTH-6F and now the parity check is about 28MB/sec

This one says it was going to take over 2 days

 

I have 15 hard drives and 2 SSD cache drives

 

Is there something I could tweak to speed up the parity check?

I am attaching a diagnostic

 

tower2-diagnostics-20180901-1012.zip

  • Community Expert

Didn't you notice the errors on the failing disk3?

 

197 Current_Pending_Sector  -O--CK   195   195   000    -    1356

Notifications disabled?

  • Community Expert

BTW, you should immediately cancel the parity check, since disk errors on a correcting check can corrupt parity, scheduled checks should always be non correct.

  • Author

I have cancelled parity check 

it looks like I need to replace disk3 then?

  • Author

Would disk3 having read errors cause the parity check to take almost 3 days to run?

 

Every read error means that the system has to recalculate the information that is supposed to be in that sector from all of the other drives, and re-write the offending sector.  So, yes

  • Author

Thanks Squid

I will replace the drive immediately then - I have a spare here

 

  • Community Expert

And make sure you enable system notifications, you would get warnings of the pending sectors and the read errors.

13 hours ago, Squid said:

Every read error means that the system has to recalculate the information that is supposed to be in that sector from all of the other drives, and re-write the offending sector.  So, yes

I also think it should be , but recent disk read error event show negative.

So, if it is true, then tick correction or not during parity check also need consider.

 

 

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.