My UNRAID journey started 2 weeks ago. I got everything setup and all my data slowly transferred over. My new parts finally came yesterday and I was excited to install them.

I have a ROG Strix 370-E

an 8700K CPU and Corsair Vengeance RGB PRO 32GB (16x2).

Ever since I got the HW switched over things have seemed weird.

At first i thought it was because my docker utilization was a 91%, but I got that fixed and added a TON (1500GB) of space. I think SABnzbd was taking up space with my 1TB+ dl queue.

That fixed that.

Still having issues. For one thing I can't seem to reliably log into plex. From the docker I click open webui and it asks me to login EVERY time. Then it tries to load plex but sometimes says it failed and asks me to login again. When it does load it seems like its slow.

 

The other thing that happened was I set a static IP address on my router for the server. Then I restarted and had to change the IP address of Sabnzbd in sonarr and radarr. It saved and was working just fine. The next time I restarted the settings were back to the original and I had to edit them again. Is that because mover had to move them to the appdata on the array? It shouldn't be right?

 

I have noticed on both my old and my new CPU that my CPU utilization always seems high. My temp is fine, like 34C. But its at like 50-70% utilization with no active streamers or any transcoding. The only thing running currently is mover, moving files from the cache drive to the array.

 

The dockers I have currently are binhex-plex, binhex-sonarr, binhex-radarr, binhex-sabnzbd, tautulli.

 

1 minute ago, m0larmechanic said:

At first i thought it was because my docker utilization was a 91%, but I got that fixed and added a TON (1500GB) of space. I think SABnzbd was taking up space with my 1TB+ dl queue.

The usual (and recommended solution) is to NOT have any downloads from SAB be stored within the docker.img file.  1.5TB is WAY overkill, and for the vast majority of people, 20GB is more than sufficient.  A few entries in the Docker FAQ about the image becoming full

 

Might not be a bad idea to post your diagnostics

Here are the diagnostics.

Thanks for the help!

 

I saw multiple posts that you actually made but I am new and failed to completely understand. Can you explain how to change the Sabnzbd download location to outside the docker? I figured adding the 1500 GB would give me room if I needed a large queue size again.

molar-diagnostics-20200321-1000.zip

It appears that you've got a poor connection to one or more of the drives attached to your HBA.  Reseat power / sata to the drives (they keep resetting).

 

Also, disable Mover Logging within Settings - Scheduler - Mover.  It serves no real function unless you've got issues.

 

And, not sure (or at least not what I would do) why you have your downloads share set to user cache:yes.  Slows everything down as it'll keep moving from the cache drive to the array, and IMO is pointless.  Set it to Use cache: prefer so that it'll tend to stay on the cache drive, and only use the array for an overflow.

Ok I’ve done everything you said except reseating all the drives. I can’t shut it down right now and I’d have to move the entire unit which I’d rather do when it’s off.

will do that when I can here soon.

 

That alone seemed to have dropped my CPU usage to around 6% instead of 50-60%

I am also getting write cache errors in fix common problems on all my drives. Do you see anything in my diag file to indicate what is up?

That's not logged.  Follow the link that FCP is giving you for directions.

I just checked all the drives. Reseated the SATA and power cables.  As well as fixing the cache set to yes, and the mover logging.

 

Here is my diag file now.

 

molar-diagnostics-20200321-1607.zip

One thing I am noticing is every time I try to open Tautulli it makes me sign into my plex account.

It seems to me that something isn't saving... this wasn't happening before I upgraded my hardware.

There's a problem with the HBA:

 

Mar 21 13:07:18 Molar kernel: mpt2sas_cm0: fault_state(0x7c35)!

 

Make sure it's well seated or try a different slot if available, you should also update the firmware since it's on a very old one.