[[Plugin] CA Auto Turbo Write Mode]

35 minutes ago, aukaauka said:

I was hoping to try the Edit talked about above for changing from "hdparm" to "smart ctl" to see if that fixed it so I could use this plug-in  

 

 

that threw me for a loop at first as well.  

 

on the unRAID USB stick:

\config\plugins\ca.turbo\ca.turbo-2020.01.26-x86_64-1.txz  

 

is the file you are looking for, .txz is an archive like a zip or rar file (Linux people always need to do everything different, just to confuse windows users 😜 )

open it with 7-Zip (WinRAR won't work!) and inside THERE is the path you quoted.  

you can then open and edit the file with a text editor right there in the archive, no need to extract anything.

[[Plugin] CA Auto Turbo Write Mode]

On 3/30/2020 at 10:44 PM, Torben said:

The plugin uses "hdparm", which - like in my case - doesn't recognize the correct status of running Seagate Ironwolfs (it's "unknown"). Scroll up a bit in this thread and also check page 4 close to the bottom. Niklas posted some changes to use "smartctl" instead which worked fine for me, maybe also for you? The only problem is that the plugin/script is (whysoever) reset soon after, so I again stopped using it - unfortunately.

I finally got around to fiddling with it, after wrapping my windows user head around how to edit a .tgx archive and the .php file inside it editing lines 80 + 84 was the easy part. (for the record, WinRAR is not able to edit .tgx ...i had to install 7z for this.)  

 

But i can report it works fine now, yaaay, makes me wonder why this isn't the default option for the plugin.  

 

And i disabled auto updates for this plugin in CA Auto Updates, just so the changes don't get randomly overwritten, however unlikely that seems at this point.  

[[Plugin] CA Auto Turbo Write Mode]

Hi,

this plugin just got pointed out to me on reddit and of course i instantly installed it, now i'm a bit confused.

 

see picture:

 

edit:

some more tesing shows that Disk 1, 2 and 3 get counted individually as you would expect.

Parity, 4, 5 and 6  ... = my four 8TB Seagate Iron Wolves, do not count up or down at all. (i intend to replace the small disks with more of these eventually).

 

edit 2:

i turned the server off and on again, did not help lol

 

edit 3:

i did read through the thread just now, seems to be a kind of common problem (some of them reported in 2017, so i don't suppose this will get fixed anytime soon).  

 

i did enable the log and it keeps saying  

 

Mar 30 15:19:38 UNRAID root: #012/dev/sdf:#012 drive state is: active/idle
Mar 30 15:19:38 UNRAID root: #012/dev/sdd:#012 drive state is: active/idle
Mar 30 15:19:38 UNRAID root: #012/dev/sde:#012 drive state is: active/idle
Mar 30 15:19:38 UNRAID root: #012/dev/sdc:#012 drive state is: unknown
Mar 30 15:19:38 UNRAID root: #012/dev/sdg:#012 drive state is: unknown
Mar 30 15:19:38 UNRAID root: #012/dev/sdh:#012 drive state is: unknown
Mar 30 15:19:38 UNRAID root: Total Spundown: 3

 

it does not list the parity disk here... i guess that needs to spin up when writing anyway so no need polling that.  

 

i'm just wondering, if the unRAID GUI reports properly which disks are spinning (the green icons are always on point as far as i can tell), why not hook in there instead?  

i've read 2 times the comment that the unRAID gui is "not real time" not sure what that means exactly, looks pretty real time to me when i'm looking at it, and what does it matter if the polling interval is by default set to 5 minutes (an eternity if you ask me).  

 

Soooo, i got these disks connected to my motherboard, ASUS P8Z68-V Pro/GEN3 (90-MIBFIA-G0EAY00Z) ...that thing has 3 SATA controllers on it for its 8 ports, two controllers for SATA 3 (4 ports) and one for SATA 2 (4 ports), i most likely connected the 4 Seagate disks to the SATA 3 ports because they are the biggest fastest, that means the SATA 3 controllers both might not be reporting the HDD status OR the HDDs just don't support that info, which would be weird because those are specifically NAS drives and the newest of the bunch, if anything i'd expect old stuff not to support something like this, the board is over 5 years old, so ... hmmh.  

 

Welp, i guess i leave the setting at 3 then.  

That should be enough for me to enable Turbo mode when i have a few 100GB to dump on the server by just spinning everything up manually and then spin down manually after to disable it again. ...not the cleanest solution but it will do the job i wanted it to do i hope.  

[Dynamix - V6 Plugins]

Cache Directories plugin 

 

Can somebody explain to me (in dumbed down terms) how the Cache Directories plugin actually works?  

 

What i specifically don't understand is why it produces so much CPU load (15%-ish overall load, spikes up to 70% on random cpu cores every few seconds) while the system is IDLE for hours with all HDDs spun down.  

What could it possibly be doing that needs so much CPU cycles when absolutely nothing is going on?  

 

  

 

With the plugin uninstalled CPU load stays below 2%...  

 

Also, if somebody could point me to some foolproof settings so it actually keeps the disks spun down, that would be nice because i can't seem to get it to even do its intended job right. Disks are still spinning up, just looking at folders in Windows Explorer, without even opening anything.  

 

Thanks.