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 mover and parity check speeds after upgrade to 6.9 beta

Featured Replies

So I noticed this morning that my mover was still running at 9:30am when I have it scheduled to start at 4am. Normally it takes a couple hours tops. It was running at 50mb/s when it usually runs around 180-250mb/s. I also tried running a parity check ant it was running at 50mb/s also. I'm new to the forum so I'm not sure what other info I need to provide. I've attached the diagnostics to start.

System specs:

AMD Threadripper 2970wx 24 core

LSI Logic SAS 9207-8i

RTX Quadro 4000

13 12TB Seagate drives (12 Exos and 1 Iron Wolf)

2TB nvme cache

500gb nvme Plex drive

 

homeserver-diagnostics-20201125-1032.zip syslog-192.168.1.99.log

  • Community Expert

If you run mover and parity check at the same time they are both going to impact each others performance since they must use the same disks. Probably a lot of seeking going on as mover and parity will need to access very different parts of the disk with head movement and other latency.

  • Community Expert

Looks like you rebooted before starting the parity check so I assume mover wasn't running at the same time.

 

Reported parity speed can vary somewhat in the beginning. How fast is it going now?

  • Author
4 minutes ago, trurl said:

If you run mover and parity check at the same time they are both going to impact each others performance since they must use the same disks. Probably a lot of seeking going on as mover and parity will need to access very different parts of the disk with head movement and other latency.

I didn't run them at the same time. I waited for the mover to finish then started the check.

  • Author
2 minutes ago, trurl said:

Looks like you rebooted before starting the parity check so I assume mover wasn't running at the same time.

 

Reported parity speed can vary somewhat in the beginning. How fast is it going now?

After a few minutes it was still around 50mb/s. So I stopped it. It's always gone full tilt when ever it runs. All my drives are the same speed and none are above 75% capacity.

  • Community Expert
13 minutes ago, Eldaren said:

Normally it takes a couple hours tops. It was running at 50mb/s when it usually runs around 180-250mb/s.

How do you know what speed mover was running or what speed it usually runs?

  • Community Expert

If you revert to stable version does it behave differently?

  • Author
Just now, trurl said:

How do you know what speed mover was running or what speed it usually runs?

By looking at the read and write speeds while it's running on the Main tab.

  • Author
1 minute ago, trurl said:

If you revert to stable version does it behave differently?

Haven't given that a go just yet. I'm running the 6.9 beta 35 for Plex to work with HW transcoding. The new docker updates require updated Nvidia drivers that are only on this version. If I revert back to 6.8, check, then revert back to the current version will I break anything?

  • Community Expert
1 minute ago, Eldaren said:

will I break anything?

no

  • Author

Okay reverting back to 6.8 didn't change anything.... I guess there's a problem somewhere else?

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.