October 23, 201312 yr Hello there! I'm new to unRaid and PLEX... And I'm having problems with my disks spinning down. I don't have a cache drive. I have 3TB drives (one is for parity). Just tested... Disabled the PLEX, waited and all my drives spinned down! Started PLEX, and even after 1h (my setting), the Drive where my PLEX library and temp files are (Disk2), and the parity can't spin down... It's strange, because it has reads and writes! Device Identification Temp. Size Used Free Reads Writes Errors View Parity (sdb) 2930266532 32 °C 3 TB - - 31 620 Disk 2 (sdd) 2930266532 32 °C 3 TB 1 TB 2 TB 77 64 Just checked my unRaid logs: The disks spinned down at 07:58, I just checked (08h35) and they're up again... From syslog: Oct 23 07:58:50 Optimus kernel: mdcmd (18): spindown 0 Oct 23 07:58:50 Optimus kernel: mdcmd (19): spindown 2 Oct 23 08:08:06 Optimus transmission-daemon[12710]: Port Forwarding (NAT-PMP) readnatpmpresponseorretry succeeded (0) (natpmp.c:72) Oct 23 08:08:06 Optimus transmission-daemon[12710]: Port Forwarding (NAT-PMP) Port 51413 forwarded successfully (natpmp.c:221) Oct 23 08:33:16 Optimus su[13941]: Successful su for unraid-plex by root Oct 23 08:33:16 Optimus su[13941]: + ?? ? root:unraid-plex And from /mnt/user/Config/Plex/library/Application Support/Plex Media Server/Logs/Plex Media Server.log Oct 23, 2013 06:30:06 [0xab0b3b70] DEBUG - Request: GET /library/sections [127.0.0.1:60933] (2 live) Oct 23, 2013 06:30:06 [0xab0b3b70] DEBUG - It took 0.000000 sec to serialize a list with 3 elements. Oct 23, 2013 06:30:06 [0xaba77b70] DEBUG - Request: GET /channels/all [127.0.0.1:60934] (2 live) Oct 23, 2013 06:30:06 [0xaba77b70] DEBUG - It took 0.000000 sec to serialize a list with 0 elements. Oct 23, 2013 08:28:10 [0xaba77b70] DEBUG - Sync: refreshChannelContent Can anyone help me?
October 23, 201312 yr Without a cache drive you are going to have to deal with this. PLEX likes to scan the library for changes, which requires reads (and maybe some writes). You also have Transmission running it looks like which is going to cause the same problem.
October 23, 201312 yr Author Without a cache drive you are going to have to deal with this. PLEX likes to scan the library for changes, which requires reads (and maybe some writes). You also have Transmission running it looks like which is going to cause the same problem. I made some tests, and it's Plex that it's keeping the disks awake... I disabled all the automatic scan and check options, but it still scans for something. I guess I'll have to buy a HD for cache...
Archived
This topic is now archived and is closed to further replies.