Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

30 Good

About unevent

  • Rank
    Advanced Member


  • Gender
  • Location

Recent Profile Visitors

1409 profile views
  1. http://www.frozencpu.com/ Look under Connectors - 4 Pin - Molex Never bought from them and not affiliated, but looks like they have what you are looking for.
  2. Is 'Direct Unpack' checked under switches?
  3. Got your message, will look at the other thread.
  4. If you think the changes you made to the sab switches caused it then undo them.
  5. Never really a bad idea to go for more CPU so that is up to you. My point was it won't fix that immediate problem you were seeing when running the mover. Not sure how many streams you can hardware transcode at a time so more CPU for Plex is not a bad idea. Plex says it takes roughly 2000 passmark (CPU) to soft transcode a 1080 @10Mbit stream.
  6. The mover is very aggressive and really should be run overnight on a schedule (settings-scheduler). The CPU going to 100% is not necessarily an issue unless it causes problems with something else then you deal with it by isolating or taming. I've run much more on much less processor so it really is just a matter of tuning your loads. The diagnostics (top.txt) show you were running mover which had top reporting 26.6% IO wait and 63.8% CPU idle with system load of 9.01, 9.33, 7.11. Not CPU bound, it is IO bound. More CPU won't fix that particular issue. Linux reports loading different than Windows, it includes IO in the load calc (waiting).
  7. I have /mnt/cache/.apps/calibre_library/ and /mnt/cache/.appdata/nginx/ as the only maps.
  8. This is on cache only and no maps to user shares. Can you elaborate on how spin up groups will solve the issue? Thanks
  9. ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-config: executing... [cont-init.d] 20-config: exited 0. [cont-init.d] 30-keygen: executing... using keys found in /config/keys [cont-init.d] 30-keygen: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. Signal handled: Terminated. [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] syncing disks. Signal handled: Terminated. [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] syncing disks.
  10. Is there a reason for a sync being issued on container stop? Can it be removed? It spins up the entire array when this container is stopped or updated. Thanks
  11. In sab you can change nice up to 19 (-n 10 up to -n 19) in sab-config-switches-Post_processing to lower the CPU priority. If you go to 19 on nice you can try leaving ionice at the defaults in the sab wiki (-c2 -n4) and see how the IO during unrar and par2 perform. The man page for ionice will explain why. There are also some switches for par2 in the sab wiki where can limit cores and other priorities depending on which version of par2 the Docker you have is using. For radarr/sonarr you can limit them to a single (same) core as an option (ex: sab is core 1, 2 and sonarr and radarr are core 1). Their bulk disk usage are copy/move and there are no exposed options to add nice/ionice parameters (that I know of). Usually only need or want to limit cores when you need something to not affect something else and vice versa. If running a CPU intensive Docker and want to maintain quality of Plex don't assign that Docker to the Plex cores, or configure core priorities. High disk IO affects everything regardless of what core it is running on. I don't think everyone has this issue due to server vs consumer hardware and other factors. Not sure what the latest firmware is for the 1015 or if upgrading will improve things regarding IO. You can configure radarr and sonarr to notify Plex on new stuff and then have Plex trigger an update only at that time. Not sure what method Plex uses when set to constantly watch for changes so up to you.
  12. https://sabnzbd.org/wiki/configuration/2.3/switches#ionice The defaults listed usually work fairly well. More Dockers should not be a problem as most are not as disk intensive like sab/sonarr/radarr and those you can tame by restricting resources and using nice/ionice and tweaking like pause download during processing. Which LSI HBA card do you have? Noticed from the logs the firmware is P11 on the one you have. Not familiar with the '--cpu-shares' setting, never used it. You would want to use '--cpuset-cpus=' to assign a Docker to specific cpu core(s). The '--cpu-sharing' not really needed I don't think in this case with sab/sonarr/radarr limited to the same two cores. The apps will battle it out for time on the two cores thereby limiting themselves while the ionice will lower the disk priority of rar/par2 and nice will lower the cpu priority of rar. Will take longer to process, but everything else will keep running.
  13. Assuming if you disable your downloads Plex works fine. Six cores to work with. If you're doing CPU transcoding (no-HEVC/h265) then assign Plex three to four cores depending on how you have your transcoding quality configured and number of simultaneous streams you often see. Don't assign anything else to those cores. Assign two cores to sab/nzbget, sonarr, and radarr (the same two cores). Within sab under 'config-switches-post-processing' utilize the 'nice' and 'ionice' (see sab wiki). If using nzbget add 'nice -n 10' to the unrar config in post processing (see nzbget help). Download to cache only and and post-process to the cache drive (enable cache on the necessary shares) so that the mover can do the bulk disk transfers during off-hours so not to bottleneck the I/O during prime time.
  14. Since you run pfsense you can issue your own cert from your CA and rid yourself of the unraid.net requirement or can install the acme package for pfsense and issue LE cert that way as well.
  15. Probably the way LT obtains the cert (DNS method a guess). Look into pfsense DNS rebinding protections for a solution, or disable https access to the GUI.