1 hour ago, 2twisty said:

 

How can I track down where the failure is?

 

 Have you recently made any notable changes to your system setting or configurations wise? Or have you made any major upgrades to the OS or plugins or added new apps? My first guess would be that something new is keeping the array active. 

Since posting, I reinstalled the plugin and it seems to be working now.

 

But to answer your question, I hadn't made any significant changes.

 

If it acts up again, I'll come back and post again.

On 6/22/2017 at 8:52 AM, bonienl said:

When time permits I will introduce mutti-processor and multi-nics in the graphs. Until then you need to have patience... rather busy at the moment.

 

 

Thanks, glad you're thinking about it. My problem is too many NICs and trying to see them all easily at a glance.

Well....I'm back.

 

It's not working again.  And this time, reinstalling the plugin didn't work.

 

I have the plugin set to wait for array inactivity and then shut down after 15 minutes.

 

It never seems to shut down.  

 

Where should I look in the logs to find out why?

 

When I log into the webUI, I see no activity on the drives for long periods, then a tiny little spike.  I think that may be what's causing this, but I'd  like to nail it down rather than keep guessing.

Update: I think the culprit is Sonarr and Radarr.  They just love to scan the array all the time, and there's no way (per the devs) to change the intervals at which is scans.

So, I am testing the following:

 

I wrote a user script that runs hourly that checks to see if its between the hours of 5pm and 9am.  If it is, it runs a docker stop command to end both Sonarr and Radarr.  Hopefully, this will allow the array to settle down long enough if there is no other activity to perform the shutdown.

Since most of  what my array does is serve video to Kodi and I've got wakeonlan configured, this may be a workable solution for me.

 

Wish me luck!

Is powerdown-x86_64.plg not supported anymore?  If so what's the alternative?

Is powerdown-x86_64.plg not supported anymore?  If so what's the alternative?

It's been built in for a long time now. That plugin should be uninstalled

Hi there,

 I'm having some probs with autofan 1.5 on 6.4.0_rc15e - it's not recognising my PWM controller any more.

I'm running on a Gigabyte H97N-Wifi ,  ITE87 . It wasn't working anyway with last unRAID stable.

Any ideas where I could search for more infos?

tnx,

Marco

 

 

EDIT: SOLVE! Had to modprobe the ITE87 module manually.

Edited December 11, 20178 yr by ghiglie

On 1.12.2014 at 6:40 AM, bonienl said:

This plugin requires PERL, this package needs to be installed separately.

 

Hi, where and how?

1 hour ago, nuhll said:

 

Hi, where and how?

I think it’s included in Nerd Pack.

Thanks, worked.

I have the auto fan plugin installed. How do i configure multiple PWR thingys? Or is it for all of them shown?

 

I mean i can select multiple pwr controllers!? On Mainboard i see 2 of them. 1 is cpu, 1 is chassis but it shows 3

Edited December 14, 20178 yr by nuhll

Dynamix System Statistics
v2017.10.02b

Does anyone know why my Total Space Used only amounts to 42TB when there is 6 drives of 8 TB full (+2TB on drive 22)
Did not notice until now, that 6 * 8 is more than 42   it should say 50 TB used

The total array size is correct

When I reload the STATS page, it shortly writes 50 TB, but right away it changes to 42 TB, and then the green "progress-bar" from the top, starts to animate to it's position. (using Firefox) (Chrome does the same)

unraid-diagnostics-20171216-1228.zip

Edited December 16, 20178 yr by palmio

Can you post your diagnostics (see Tools -> Diagnostcis).

 

Edited December 16, 20178 yr by bonienl

diagnostics-zip added to the post.
Also noticed that it actually writes the correct total for 1/2 second after reload, then changes the value.

How do you get the stats tab?

For the System Info plugin, would it be possible to add the capability to download the generated information as an html file?  

2 hours ago, mbc0 said:

How do you get the stats tab?

It's made by Dynamix System Statistics. You can set in it's settings if it should be a TAB or not.
 

18 hours ago, palmio said:

It's made by Dynamix System Statistics. You can set in it's settings if it should be a TAB or not.
 

 

Thanks!

 

Is there anyway to get multiple network interfaces to appear in the stats page? I only see a single interface and want to have all 4 that I currently use displayed.

 

Sorry for not searching this thread it's 75 pages long

3 hours ago, Bigdady92 said:

Is there anyway to get multiple network interfaces to appear in the stats page? I only see a single interface and want to have all 4 that I currently use displayed.

 

Sorry for not searching this thread it's 75 pages long

 

On page 69: this reply.

 

Tip: You can search within the current topic using the search box at the top right corner of the page.

The SSD Trim plugin on my backup server seems to be doing more trim than the cache drive:

Dec 30 05:30:02 BackupServer root: /etc/libvirt: 920.7 MiB (965451776 bytes) trimmed
Dec 30 05:30:02 BackupServer root: /var/lib/docker: 13.3 GiB (14318682112 bytes) trimmed
Dec 30 05:30:02 BackupServer root: /mnt/cache: 474.1 GiB (509044609024 bytes) trimmed

I'm not sure how the libvirt and docker loop files got into the trim.

 

My main server with the SSD trim plugin only does the cache drive:

Dec 30 05:30:57 MediaServer root: /mnt/cache: 564.3 GiB (605934116864 bytes) trimmed

Where can I look to see why this is happening?

This is expected behavior. When docker and libvirt images exist, they will get trimmed too (when placed on a SSD).

 

Edited December 30, 20178 yr by bonienl

Hey, i use the cache thingy, but doesnt seem to work correct.

 

I added /Archiv/ and /downloads/

 

If i visit /Archiv/ a drive spinns up...

1 hour ago, bonienl said:

This is expected behavior. When docker and libvirt images exist, they will get trimmed too (when placed on a SSD).

 

Both servers are the same setup.  Cache is an SSD and system share is on cache as 'Prefer' cache setting.  Why would there be a difference?