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.

Slow Parity Check After Moving Drives to Dell PERC H310

Featured Replies

Hello,

 

I moved the four drives in my existing array from built-in motherboard SATA to a Dell PERC H310 (taped and flashed to IT-Mode) in preparation of adding additional drives. Parity check progress was estimating weeks to months to complete. I let it run 8+ hours overnight and it was 29% complete (Average speed: 135 MB/s).

 

I have shutdown the system. Can you please check the attached diagnostic and let me know if there is an issue that is causing the parity check to take so long?

 

System Info:

The H310 is a 8-lane PCIe v2.0 card. The motherboard supports PCIe v2.0. Therefore, the theoretical throughput (of the controller card) should be x8 (eight lane) v2.0 PCIe slot: 8 * 500 MB/s = 4000 MB/s = 4 GB/s = 32Gb/s.

 

What is the expected throughput during a parity check with four 5,400 RPM SATA hard drives?

 

Thx

tower-diagnostics-20190123-0722.zip

unRAID Parity Check Status.PNG

Edited by busthead
Clarification and additional question

  • Community Expert

Didn't you notice these?

 

Jan 23 07:08:05 Tower kernel: md: disk1 read error, sector=4537757376
Jan 23 07:08:05 Tower kernel: md: disk1 read error, sector=4537757384
Jan 23 07:08:05 Tower kernel: md: disk1 read error, sector=4537757392
Jan 23 07:08:05 Tower kernel: md: disk1 read error, sector=4537757400
Jan 23 07:08:05 Tower kernel: md: disk1 read error, sector=4537757408
Jan 23 07:08:05 Tower kernel: md: disk1 read error, sector=4537757416
Jan 23 07:08:05 Tower kernel: md: disk1 read error, sector=4537757424
Jan 23 07:08:05 Tower kernel: md: disk1 read error, sector=4537757432
Jan 23 07:08:05 Tower kernel: md: disk1 read error, sector=4537757440

 

  • Author

I had not, thank you. Will run a few tests on that drive a report back.

 

If I replace that drive with another, of at least the same capacity, will the array rebuild itself?

 

Thx

  • Community Expert

Yes, it will rebuild the disk, disk has a high Raw_Read_Error_Rate, which is consistent with the issues you're seeing, like slow sectors and even bad ones, though since there are no read errors or pending sectors on SMART only an extended test would confirm, alternatively swap both cables with another disk and run another non correcting check, if errors persist it's the disk.

  • Community Expert

Oh, and make sure you enable system notifications so you'll get a warning when there's a disk with read errors.

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.