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.

Beta 2 issue - Parity speed has dropped like a rock :(

Featured Replies

Actually, we're going to post a beta4 soon which might help with the lock-up issue.  The troublesome entry in your syslog is:

 

Sep 27 06:09:09 BEAST kernel: hda: irq timeout: status=0x80 { Busy }

Sep 27 06:09:09 BEAST kernel:

Sep 27 06:09:15 BEAST kernel: ide0: reset: success

 

Any ETA for beta 4?  I just popped 4 new 400GB drives into one of my machines and my syslog is full of this busy stuff while trying to format them.

 

beta 4 is up now  ;D

beta 4 is up now  ;D

 

Well OK then!

Obviously very interested if this eliminates the irq timeouts.

Obviously very interested if this eliminates the irq timeouts.

 

It appears to.  I bailed on the format of those drives in the middle, though.  Can you tell me the command to manually reformat them?

 

What do you mean "bailed"?

 

I mean I powered the machine down while the format was running.  Unraid appears to think it's successfully formatted after the restart, so maybe I'm OK.

 

  • Author

Moving to Beta4 in a few moments. I will halt the current Parity check and restart aftere upgrade. won't take me long!

Hm.  This doesn't look good:

 

Sep 27 14:39:40 media-two kernel: hdf: dma_timer_expiry: dma status == 0x60

Sep 27 14:39:40 media-two kernel: hdf: timeout waiting for DMA

Sep 27 14:39:40 media-two kernel: PDC202XX: Primary channel reset.

Sep 27 14:39:40 media-two kernel: hdf: timeout waiting for DMA

Sep 27 14:39:40 media-two kernel: hdf: (__ide_dma_test_irq) called while not waiting

Sep 27 14:40:00 media-two kernel: hde: dma_timer_expiry: dma status == 0x21

Sep 27 14:40:10 media-two kernel: hde: error waiting for DMA

Sep 27 14:40:10 media-two kernel: hde: dma timeout retry: status=0x51 { DriveReady SeekComplete Error }

Sep 27 14:40:10 media-two kernel: hde: dma timeout retry: error=0x84 { DriveStatusError BadCRC }

Sep 27 14:40:10 media-two kernel: hdf: status error: status=0x58 { DriveReady SeekComplete DataRequest }

Sep 27 14:40:10 media-two kernel:

Sep 27 14:40:10 media-two kernel: hdf: drive not ready for command

Sep 27 14:40:10 media-two kernel: hde: status timeout: status=0xd0 { Busy }

Sep 27 14:40:10 media-two kernel:

Sep 27 14:40:10 media-two kernel: PDC202XX: Primary channel reset.

Sep 27 14:40:10 media-two kernel: hde: drive not ready for command

Sep 27 14:40:10 media-two kernel: ide2: reset: success

Sep 27 14:40:31 media-two kernel: hdf: dma_timer_expiry: dma status == 0x60

Sep 27 14:40:31 media-two kernel: hdf: timeout waiting for DMA

Sep 27 14:40:31 media-two kernel: PDC202XX: Primary channel reset.

Sep 27 14:40:31 media-two kernel: hdf: timeout waiting for DMA

Sep 27 14:40:31 media-two kernel: hdf: (__ide_dma_test_irq) called while not waiting

Sep 27 14:40:51 media-two kernel: hde: dma_timer_expiry: dma status == 0x21

Sep 27 14:41:01 media-two kernel: hde: error waiting for DMA

Sep 27 14:41:01 media-two kernel: hde: dma timeout retry: status=0x51 { DriveReady SeekComplete Error }

Sep 27 14:41:01 media-two kernel: hde: dma timeout retry: error=0x84 { DriveStatusError BadCRC }

Sep 27 14:41:01 media-two kernel: hdf: status error: status=0x58 { DriveReady SeekComplete DataRequest }

Sep 27 14:41:01 media-two kernel:

Sep 27 14:41:01 media-two kernel: hdf: drive not ready for command

Sep 27 14:41:01 media-two kernel: hde: status timeout: status=0xd0 { Busy }

Sep 27 14:41:01 media-two kernel:

Sep 27 14:41:01 media-two kernel: PDC202XX: Primary channel reset.

Sep 27 14:41:01 media-two kernel: hde: drive not ready for command

Sep 27 14:41:01 media-two kernel: ide2: reset: success

 

  • Author

Up and running on Beta4 - Parity check is proceeding at 12-14K per second. W00t!

Up and running on Beta4 - Parity check is proceeding at 12-14K per second. W00t!

 

Do you mean 12,000 - 14,000 KB/sec

or

12-14 KB/sec

 

being displayed for "Estimated speed"??

DOH! I have butter fingers-  had it in Legacy mode, in Enhanced it's a lot faster- averaging 55,000  KB/sec.

 

Thanks Tom.

 

-a

  • Author

Up and running on Beta4 - Parity check is proceeding at 12-14K per second. W00t!

 

Do you mean 12,000 - 14,000 KB/sec

or

12-14 KB/sec

 

being displayed for "Estimated speed"??

 

Oh sorry, 12,000-14,000KB per sec, sorry if I gave you a heart attack :o I'd like to see 55KB though lol, what's making his so much faster? ??? Is that a SATA setup? If so I might be convinced to consider some SATA in my next array!

Is the upgrade to beta 4 still just copy the 3 files over and reboot the array like the first beta release?

 

-PGPfan

Is the upgrade to beta 4 still just copy the 3 files over and reboot the array like the first beta release?

 

-PGPfan

 

just the two files....

 

bzimage

bzroot

 

 

just upgraded now.... seems to be a working fine for me

 

 

55,000 KB!!! HOLY CRAP!!!

Hm.  This doesn't look good:

 

Sep 27 14:39:40 media-two kernel: hdf: dma_timer_expiry: dma status == 0x60

Sep 27 14:39:40 media-two kernel: hdf: timeout waiting for DMA

Sep 27 14:39:40 media-two kernel: PDC202XX: Primary channel reset.

 

Well, my problem appears to have been... (wait for it) ... a bad IDE cable.  I swapped out the lovely fancy round cable with the crappy one that came with the drive, and the problems went away.  So far.  Running parity check now to make sure, but all appears well.

 

 

Hm.  This doesn't look good:

 

Sep 27 14:39:40 media-two kernel: hdf: dma_timer_expiry: dma status == 0x60

Sep 27 14:39:40 media-two kernel: hdf: timeout waiting for DMA

Sep 27 14:39:40 media-two kernel: PDC202XX: Primary channel reset.

 

Well, my problem appears to have been... (wait for it) ... a bad IDE cable.  I swapped out the lovely fancy round cable with the crappy one that came with the drive, and the problems went away.  So far.  Running parity check now to make sure, but all appears well.

 

 

 

I tried to find a 'good' quality round cable and I came to the conclusion that they DO NOT exist. I had my whole array decked out with the round cables.. I ditched them and went back to the round cables. Always fun eh??  I think I was using Link Depot from NewEgg

  • Author

Round cables violate the IDE specs for RF interference. I have them on I think 2 maybe 4 drives but that's it. Flat is ugly but this isn't a parade float so I don't care ;D

I spoke too soon.  The problems are back.  Sigh.

 

I split off the topic here.....  Please keep this thread on BLKMGK's original issue - currently working offline with him on this.

  • Author

Actually, this was an issue with Beta2 - resolved in Beta4 it seems. However I encountered a different issue in Beta4. Doh! that thread is indeed elsewhere and we're working it!

Final update on my slow parity speed - it was a bad (NEW) hard drive right out of the box...well, actually after 39 hours in my server :'(. Now that I replaced it with another 'new' drive, all is well again. Thanks to Tom for all the offline support getting this working again! Man, how I am loving unRaid!

 

-PGPfan

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.