Zonediver

Whats up with the strange "spinup of all disks" and not working Cache-Dirs? Is this fixed in this release?

xxx

I already did this but it doesnt help...

Here we are unraid-diagnostics-20181027-0026.zip

I am using only standart-plugins and just four dockers... so what can this be?

It isn't - i already did this... no effect. Cache-Dirs shows running but its not working. There must be something additional be wrong in 6.6.3

So... reverted back to 6.6.2 and all is working again - i dont know whats up with this 6.6.3 release but its not working properly. Cache-Dirs not working, Sys terrible slow - it takes ages till my shares are reacting... bad - cant recommend it...

Same here - since 6.6.3 it seems that this plugin is not working anymore - there is no difference between enable or disable... nothing happens. Whenever i do something on my server, it takes about 30-50sec, all disk spin up and then i can copy to the server.

Okidoki 😉

Thanks for your help - Folder caching function was "Disabled"... strange...

It seems, that since 6.6.3 the plugin Cache Directories is no longer working. Every time i klick a directory, my Explorer needs 30-120sek to find it - and sometimes it doesnt. But the most strange thing is, every time "all" disk spin up... not cool...

...Limtech should rename itself to LimeBeer 🤣 Update went smooth and without problems - thanks a lot!

...updating the BIOS as solution for everything?... hmmmm... The latest BIOS for my machine is from 27. Dec 2013... not realy helpfull... and i "dont want" to change my hardware as well... But i dont use VMs and unraid itself is working fine - so there is no need for updates (yet) 😉

Ah - ok - thanks 🤣

Where can i find this setting??? I dont have it...

Yep - thats it 🤣

Upgraded from 6.5.3 - only issue: The CPU load for Docker is not working properly.... Plex shows sometimes more then 100% (???) - i saw 221 and 504% - is it cpu-core related maybe? 🙂 The gray CPU-Bar exeed all infos to the right when it goes over 100%. Highest value so far: 674% (!)

You have 4 fans for blowing into the case - how many fans will blow the hot air out of the case? About "stock cooler on chipset": Do you mean the CPU-Cooler? If your Mainboard has "really" 109° then there is something wrong...

...and which "status" have the unRAIDables?

This Company is a "one man private show"??? WTF... i thought its a real company with employees and much more... strange... So it "can" be that this project will die in the future?? Stranger than weird...

FIRST, put a Firewall infront of the Server - then fix the lag... Priority???

If you have a powerful CPU, yes

Like this? @echo off wake 00-00-00-00-00-00 192.168.2.255 ping -n 3 127.0.0.1>NUL cd /Program Files (x86) cd OpenPHT OpenPHT.exe

There are several ways to wake up the server: !!! For all this examples you need to config your Server-BIOS for WOL first !!! 1) Over a magic packet within your LAN (WOL - Wake on LAN) or over the internet (WOW - Wake on WAN) 2) Over an App like "Wake On Lan" (Android) - works with WOL and WOW https://play.google.com/store/apps/details?id=co.uk.mrwebb.wakeonlan 3) Directly, when you start your program (Plex, Kodi) on your PC - for this you can use a *.bat file which starts your client and then send the magic packet. You can do this over wolcmd.exe (Windows) If you use a Raspberry (like me) for Plex (or Kodi), you have to use the Phone-App because Plex doesnt have a WOL-function integrated! Broadcast Example (within a *.bat File) for a Windows machine to send a WOW (Wake on WAN): wolcmd 0A0A0A0A0A0A 199.199.199.199 255.255.255.255 66666 The 0As are the MAC of your server The 199s are your IP on the Internet The 255s are the broadcast adress 66666 is the Port where the WOL-Packed comes in. The Router must take it and forward it to port 9 (Firewall rule needed) For a dynamic DNS entry replace the 199s with your dynDNS entry like xyz.dyndns.org (example). The App can also remotely wake your Server over WAN (internet) but only with a propper config on your Router (Broadcast) And here is an example for a *.bat file (with wake.exe) - this works only within your LAN: d: cd \ cd "000 - SUPPORT" cd "WOL Tool" wake FF-FF-FF-FF-FF-FF 192.168.x.x cd \ cd "Program Files (x86)" cd "Plex Home Theater" "Plex Home Theater.exe" When you execute the *.bat, it sends an WOL to the server and starts the Plex-Client.

I know this terrible problem from old S775 Boards (Core2Duo)... Gigabyte never fixed this problem...