Zonediver

Thanks for this info - regarding the link: is this the v2.6.5 which works under unraid 6.4.1? Doesnt matter - its not working on the command line and the Plugin is not available anymore... damn

When will this Plugin arrive? I need it very much! It is the only (known to me) way to test HDDs on weak sectors. Please give me an info, when it's done - thanks a lot. In the meantime, is there a method to test a single disk over the command line?

And since when is the "Raid-Controller" a problem? Since v6 or earlier? In my case, the BIOS of both Adaptec's is deactivated, so i hope, i will never have this strange problem...

I hear that for the first time - i have two Adaptec's and never had this problem... (???)

Maybe one ore more "weak" Sectors - had this few weeks ago. Transfer collapsed to 1,5MB/sec. Try to test the Cache-Disk for this issue.

I use ssh2 over PuTTY - works as normal...

Ah - ok. This is a new info for me - glad to hear its working now.

Take the Plex-Docker from Linuxserver.io I use this too - thats the best supported one. An assigning is not necessary - the docker will do this automaticly. You can install it over the app tab at the unraid-GUI

What is your ISP connection? Cable, ADSL? and if its Cabel, do you have a Modem or a bridget router? Is your IP IPv4 or IPv6? If its v6 then you have a problem with Plex. Read the Plex-forum for setting on IPv6. If its a bridget router than you have maybe a double NAT problem. If you go into plex/web media manager Settings/Server/Network There is a checkbox for "Enable Server Support for IPV6" - if you need it.

Difficult to say because i dont know your router make. If other portforwardings on your router are working, do so with plex as well. Take a look at the router-manual as well. Protocol for Plex is TCP only - so you dont need "both". It depends really on the router - my ipfire need a firewall-setting from my WAN-IP to the Plex-Server to get it work - that means, its different on other routers.

Check the port forwarding on your router again - port 32400 is all you need. If your router supports Geoblocking (like my IPFire) then you have to open the proper region as well. Double NAT is only an issue if you have a router from your ISP plus your own router behind. In this case, Plex is not working.

Oops - thanks

XFS because of the Speed - my Server is only for Plex.

Thanks bonienl for the quick fix.

The S3-Sleep script - not working properly anymore...

As i expected this setting with network idle doesnt work. It didnt work under v5 and it doesnt work under v6. It doesnt matter what value i use (low or high), server doesnt go to sleep... At idle, the network traffic is between 12 and 16kbit/s - so what is the correct setting to put the server into sleep?

I will try to check if the setting with the network traffic work for me - thanks for this info. The other options (IP and disable) are useless for me because most of the time i contact my server from outside the LAN.

...shit... i almost suspected... Ok, thanks for this info. Shall i revert to 6.3.5. or is there a proper patch in work?

Hi folks, big problems with the S3 Sleep plugin: Since v6.4.0 the plugin ignores almost all settings. All was working well under 6.3.5 but since 6.4.0 the server went to sleep although disks are running and i cant prevent this. I tried to enlarge the extra delay time but no luck - server goes to sleep even disks are running - not good. Whats up now? Any hints? Is this behavior already known? Thans in advance

Thats an example - i need numbers greater than 99min

Tried to set this to 105min but cant... The filed is limited to 99min. Can the developer change this to put in larger number than 99min? Thanks in advance

WOL/WOW needs a packet sent to the machine to wakeup. If you do this automaticly over a cron or something else, then it could work. But beware: It depends on your router and the proper config to receive the packet over the inet (WOW). Some routers cant handle this, on others you need special tricks because the WOL-packet comes over port 9 and will be droped (WOL is not routable). But you can realise it over a broadcast over a random port - but not port 9! (if the router is able to handle this and forwards the packet). I do this with my unraid/plex-server over an Android-app which sends a WOW-broadcast to my ip, the router takes this packet (for example port 65000) and forward it to my unraid-machine on port 9 to wakeup the server - but again, the router must support this procedure! All in all a "tricky" thing which needs extended network knowledge. You can also read this article for an additional explanation http://hacking.elboulangero.com/2015/12/11/wake-on-wan.html

UPnP is a "huge" security-risk - so don't turn this on!

Also possible. Deactivate spread spectrum and see what happens.

Take a multimeter and check the voltage of the batterie.