-
[Support] Linuxserver.io - Nginx
Agreed, the above steps solved the problem for a short time, but the issue returned.
-
Unraid OS version 6.11.5 available
I'm having the same "problem". Everything appears to be working as expected, however.
-
NNate started following [6.9.0 beta 30] Pre-Skylake Intel CPUs Stuck at Lowest pstate
-
[6.9.0 beta 30] Pre-Skylake Intel CPUs Stuck at Lowest pstate
Update: Slow parity check is a symptom of a 5.8 Kernel Bug where pre-Skylake CPUs get stuck at the minimum pstate MHz (often 800MHz). Scroll down in this thread for links to the associated Kernel bug and discussion. Otherwise, this link will jump you to my updated post in this thread. I've been noticing that 6.9.0 has been slower than 6.8.3 for disk access when using dockers (also the high amount of disk reads on my cache even after making them 1MB aligned, but that's another issue). I did my first parity check and it's markedly slower than historical. Normally parity check will complete in under 19hours at 118MB/s. The current parity check run happening now has been running for 9.5 hours and is only 30% done at 74 MB/s - with another 21 hours estimated to remain. If that estimate is true (and I know things slow down toward the end), that'll be over 30 hrs vs 19 hrs. 10 more hours than history shows. I haven't made any hardware changes vs 6.8.3. I've attached my diagnostics as well.
-
Unraid OS version 6.7 available
Smooth update here from 6.6.6 after over 100 days of uptime - thanks for all the hard work!
-
Do you use spin up groups?
My 2 9211-8i controllers suffer from the problem of a lag when another drive on the same controller spins up. This causes issues when we're watching one movie, but another process spins up a different drive on the same controller. Any suggestions for a controller that won't exhibit this problem so I can stop using spin-up groups?
-
[Support] Linuxserver.io - Deluge
Just roll back to the previous release 145. Not a big deal.
-
[Support] Linuxserver.io - Deluge
Yeah, happening here too. Never had an issue until today. For now I've rolled back to previous release 145 (Go to edit and for repository just put a :145 at the end so it says linuxserver/deluge:145) Working so far, but time will tell
-
cache_dirs - an attempt to keep directory entries in RAM to prevent disk spin-up
Yeah, 2.2.2 if I remember correctly. Yesterday I changed the cache pressure setting to 0 which seemed to help with the spinups when navigating the disks (if I manually spin them down). The file activity plugin is still showing files getting opened during the night - the only thought I have is that cache_dirs is hitting them again to refresh the cache? They are files no other docker or plugin would otherwise touch.
-
cache_dirs - an attempt to keep directory entries in RAM to prevent disk spin-up
Same here, my disks no longer spin down either. Disabling the plugin allows them to spin down. It started around the same time for me too (when the plugin would no longer start with the array).
-
cache_dirs - an attempt to keep directory entries in RAM to prevent disk spin-up
I'm aware you escape spaces with a backslash, but a backslash comma doesn't seem correct "TV\,Shows"
-
cache_dirs - an attempt to keep directory entries in RAM to prevent disk spin-up
One of my cached folders has a space in it. It's showing up weird in the line "Setting Included dirs:" as "TV\,Shows" Perhaps that's just a logging bug and doesn't impact behavior? Just checking. Seeing a lot more spin ups (and far fewer spin downs) recently. I'll wake up in the morning expecting to see the whole array spin down, but that's not the case any longer. It's changed in the past week or two. Maybe since 6.6.3 or since some updates to the plugin and the changes? Unsure. cache_dirs version 2.2.2 No Memory ulimit applied Setting cache_pressure=10 Arguments=-i Movies -i Nate -i Pictures -i TV\ Shows -i Videos -l on -U 0 Max Scan Secs=10, Min Scan Secs=1 Scan Type=adaptive Min Scan Depth=4 Max Scan Depth=none Use Command='find -noleaf' ---------- Caching Directories --------------- Movies Nate Pictures TV Shows Videos ---------------------------------------------- Setting Included dirs: Movies,Nate,Pictures,TV\,Shows,Videos Setting Excluded dirs: min_disk_idle_before_restarting_scan_sec=60 scan_timeout_sec_idle=150 scan_timeout_sec_busy=30 scan_timeout_sec_stable=30 frequency_of_full_depth_scan_sec=604800 cache_dirs started
-
Calling All Graphic Artists: Help Design the Logo for unRAID!
Ah yes, there it is. In any case, good reasons why the logo shouldn't contain taglines
-
Calling All Graphic Artists: Help Design the Logo for unRAID!
I'm in agreement with you, but that's acceptable spelling in British English (not so much in American English) so he's likely from somewhere in the UK.
-
[support] gfjardim's Docker Repository
Installing the Cloud print driver is probably the easiest way to print to it from Windows: https://tools.google.com/dlpage/cloudprintdriver I was having trouble printing until I gave my printer a static IP address. CUPS would lose the printer over time otherwise. Maybe that would help? Beyond that, I'm not sure. You could try restarting the docker as well.
-
NNate started following 6.3.3 - Buffering/Pauses Streaming Video
-
[support] gfjardim's Docker Repository
For those having issues getting Cloud Print to work in the CUPS docker... Here's how I got it all going: Add your printer in the WebUI ssh into your unRAID box run the following command to log into your CUPS docker. If you've renamed the docker, replace CUPS with your new image name docker exec -t -i CUPS /bin/bash run the following command to start up the cloudprint service and attach it to your Google account: ./etc/service/cloudprint/run This will give you a URL to use to link the Printer to your Google account. Copy/paste it into your local browser and follow the directions Once linked, go back to your ssh session... Press control-C and type exit Restart your docker. Print to celebrate
NNate
Members
-
Joined
-
Last visited