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.

Hardware upgrade causing issues

Featured Replies

I had a really cheap 4 sata addon card in my unraid. I decided to upgrade to a Lsi Logic 179356 Controller Card 05-25703-00 9305-16i 16-port Sas 12gb/s Pci-express 3.0. Got everything back up and running fine, but now it feels like it is lagging and does not run the docker containers well. CPU is often hitting 100% on multiple cores. I did change some other settings after the upgrade like setting drives not in use to go to standby and Cache to back up to array.

tower-diagnostics-20250204-1044.zip

Solved by trurl

  • Community Expert
7 minutes ago, Golagres said:

Cache to back up to array

What do you mean by this?

  • Community Expert

Your Docker/VM related shares (appdata, domains, system) have files on the array, in fact, they are configured to be moved to the array.

 

Ideally these shares would have all files on pool such as cache with nothing on the array, so Dockers/VMs will perform better, and so array disks can spin down since these files are always open.

  • Author

Primary for all those locations are on the cache. Secondary is set to the array.  I thought they only updated on Secondary when the mover is invoked. So setting them only on the cache would prevent the array from slowing them down?
 

  • Community Expert
  • Solution

The correct settings for those shares would be

Primary:cache; Secondary:array; Move action:array->cache. That would get them moved to cache.

 

But, nothing can move open files, so you have to disable Docker and VM Manager in Settings before running mover

 

Try that, wait for Mover to complete, then

 

Post new diagnostics.

  • Author

It took a lot longer than I thought it would to finish running. The Mover moved over 50g of data. That seems to fix the excessive cpu demand. I have just left it on the Primary cache after it finished for now as I keep a monitor on it. I will re-setup the back up onto the array later. Thanks for the help. 

tower-diagnostics-20250206-0934.zip

  • Community Expert

Your appdata share still has files/folders on the array. In fact, it doesn't look like you followed my instructions for that share. So, try again.

On 2/4/2025 at 9:26 PM, trurl said:

The correct settings for those shares would be

Primary:cache; Secondary:array; Move action:array->cache. That would get them moved to cache.

 

But, nothing can move open files, so you have to disable Docker and VM Manager in Settings before running mover

 

Try that, wait for Mover to complete, then

 

Post new diagnostics.

 

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

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.