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.

[SOLVED] Help with very slow parity check

Featured Replies

I apologize in advance for my limited knowledge base with Linux, but I was hoping for some help with what I fear is a problem with one of my unRaid systems.  The unit in question was built for me by Tom, and has worked flawlessly for a couple of years.  It uses only IDE drives.  Today I noticed that it had spontaneously started a parity check, which was progressing very slowly.  I stopped the array, powered down, and restarted.  I then re initiated a parity check, which started out running usual speed, but quickly slowed to about 1500 KB/sec, much slower than usual.  So far no parity errors reported.  I viewed the syslog using instructions and the wiki, which I will attach below.  I was hoping one of the experts here could review this to see if there might be an explanation for my trouble?  Thank you in advance for any assistance.

syslog3-11-11.txt

Disk11 has had some errors communicating with the disk controller, almost as if it was using a poor quality IDE cable, or a 40 condustor one instead of an 80 conductor one.

 

Mar 11 14:12:24 TowerIDE kernel: md: import disk11: [56,64] (hdj) Maxtor 6Y250P0 Y64QKG1E size: 245117344

 

It has dropped down to PIO mode, and as a result is much slower.

 

Mar 11 14:15:54 TowerIDE kernel: hdj: dma_intr: status=0x51 { DriveReady SeekComplete Error }

Mar 11 14:15:54 TowerIDE kernel: hdj: dma_intr: error=0x84 { DriveStatusError BadCRC }

Mar 11 14:15:54 TowerIDE kernel: hdj: possibly failed opcode: 0x25

Mar 11 14:15:54 TowerIDE kernel: hdj: dma_intr: status=0x51 { DriveReady SeekComplete Error }

Mar 11 14:15:54 TowerIDE kernel: hdj: dma_intr: error=0x84 { DriveStatusError BadCRC }

Mar 11 14:15:54 TowerIDE kernel: hdj: possibly failed opcode: 0x25

Mar 11 14:15:54 TowerIDE kernel: hdi: DMA disabled

Mar 11 14:15:54 TowerIDE kernel: hdj: UDMA/100 mode selected

Mar 11 14:15:54 TowerIDE kernel: pdc202xx_new: Primary channel reset.

 

Could be as simple as a bad/loose cable.  Or a failing drive or drive controller.  Or a power supply at its limits.

 

 

  • Author

Joe L.,

 

Thanks so much for the help!  I replaced disk11 and data rebuild is in progress at the expected speed.  Looks like it was a failing drive.  Is there an easier way to detect this kind of problem?

 

By the way, I post infrequently but read the forums here regularly.  You are an incredible resource for all of us using unRaid systems!

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.