Perhaps a stupid question: What is the benefit of S3 sleep compare to powerdown the system. A few seconds less wake up/boot time? Or is there something i don´t see?

With sleep, another computer can power up the server when it needs it

I use WOL from fully shut down on a regular basis.

@ squid: By accessing a user share or by using wake on lan?

If I have to use wake on Lan I don't see any advantage, because I always boot my unraid box that way.

 

Gesendet von meinem LG-H815 mit Tapatalk

 

Perhaps a stupid question: What is the benefit of S3 sleep compare to powerdown the system. A few seconds less wake up/boot time? Or is there something i don´t see?

With sleep, another computer can power up the server when it needs it

I use WOL from fully shut down on a regular basis.

 

When the system goes to sleep it keeps its uptime (if you care about that of course)

Perhaps a stupid question: What is the benefit of S3 sleep compare to powerdown the system. A few seconds less wake up/boot time? Or is there something i don´t see?

With sleep, another computer can power up the server when it needs it

I use WOL from fully shut down on a regular basis.

Not all mobo's support that.

Perhaps a stupid question: What is the benefit of S3 sleep compare to powerdown the system. A few seconds less wake up/boot time? Or is there something i don´t see?

 

Having Kodi automatically wake the server

This post relates to SSD TRIM Plugin.

 

I have just upgraded my Main Server from 6.1.9 to 6.2.0 RC3.

 

This morning I received a notification of the following error:

 

fstrim: /mnt/cache: the discard operation is not supported

 

This never happened on 6.1.9 but also I'm appreciative of the fact that no-one else has reported this (based on a forum search of the error) but can't be the only person running this Plugin on 6.2.0 RC3.

 

I've checked the Plugin and it is up to date.

 

I'm running the cache in raid0 configuration:

 

dconvert=raid1 -mconvert=raid1

 

The pool contains 3 SSD drives:

 

CT250BX100SSD1_1514F00579EC - 250 GB (sdb)
CT250BX100SSD1_1514F0057C13 - 250 GB (sdc)
Samsung_SSD_850_EVO_250GB_S21MNXAGA24112P - 250 GB (sdi)

 

Btrfs Pool: 750GB capacity - 47.5GB used - 703 GB free

 

Can anyone help please!?

One more question to the S3 Plugin. After waking up, the connected monitor stays of with no video signal. How can i solve this little problem?

SCSI Devices plug-in errors. My drives picked up as before so it is working.

 

first install: installed plug-in using URL. Commented out existing lines in Go file, rebooted.

 

awk: fatal cannot open file '/var/log/packages/dynamix.scsi.devices' for reading (no such file or directory)
chmod: missing operand after '644'

Tower login: basename: missing operand

 

You can ignore that warning. There are no files created hence the "missing" file message.

 

I am still getting this on every reboot. Can it be cleaned up? Thanks

SCSI Devices plug-in errors. My drives picked up as before so it is working.

 

first install: installed plug-in using URL. Commented out existing lines in Go file, rebooted.

 

awk: fatal cannot open file '/var/log/packages/dynamix.scsi.devices' for reading (no such file or directory)
chmod: missing operand after '644'

Tower login: basename: missing operand

 

You can ignore that warning. There are no files created hence the "missing" file message.

 

I am still getting this on every reboot. Can it be cleaned up? Thanks

 

+1

SCSI Devices plug-in errors. My drives picked up as before so it is working.

 

first install: installed plug-in using URL. Commented out existing lines in Go file, rebooted.

 

awk: fatal cannot open file '/var/log/packages/dynamix.scsi.devices' for reading (no such file or directory)
chmod: missing operand after '644'

Tower login: basename: missing operand

 

You can ignore that warning. There are no files created hence the "missing" file message.

 

I am still getting this on every reboot. Can it be cleaned up? Thanks

 

+1

 

Made a update with the correction.

 

thanks bonienl

When trying to update rc4 I get

 

plugin: updating: dynamix.scsi.devices.plg

plugin: installed unRAID version is too low, require at least version 6.2.0..

 

thanks

When trying to update rc4 I get

 

plugin: updating: dynamix.scsi.devices.plg

plugin: installed unRAID version is too low, require at least version 6.2.0..

 

thanks

 

I added a minimum version check, changed it now to minimum 6.2.0rc1 (6.2.0 is considered later than a rc release).

 

Do a check for updates and update once again.

 

Worked like a charm.  Thanks for the quick response..

 

 

SCSI Devices plug-in errors. My drives picked up as before so it is working.

 

first install: installed plug-in using URL. Commented out existing lines in Go file, rebooted.

 

awk: fatal cannot open file '/var/log/packages/dynamix.scsi.devices' for reading (no such file or directory)
chmod: missing operand after '644'

Tower login: basename: missing operand

 

You can ignore that warning. There are no files created hence the "missing" file message.

 

I am still getting this on every reboot. Can it be cleaned up? Thanks

 

+1

 

Made a update with the correction.

 

So how does one get this update?  (I am already on rc4 and checking for updates shows that everything is up-to-date.)

Latest version is 2016.08.18b, the plugin page shows the installed version. If yours isn't the latest it should become available after a "Check for updates"

 

Latest version is 2016.08.18b, the plugin page shows the installed version. If yours isn't the latest it should become available after a "Check for updates"

 

Not happening!  Mine is showing:      2016.08.18 up-to-date

 

I even restarted the browser (Firefox) and cleared the cache.  Here is the output in the Plugin Update Check popup window: 

 

plugin: checking tips.and.tweaks.plg ...
plugin: checking preclear.disk.plg ...
plugin: checking preclear.disk.beta.plg ...
plugin: checking powerdown-x86_64.plg ...
plugin: checking fix.common.problems.plg ...
plugin: checking dynamix.system.temp.plg ...
plugin: checking dynamix.system.info.plg ...
plugin: checking dynamix.system.buttons.plg ...
plugin: checking dynamix.schedules.plg ...
plugin: checking dynamix.local.master.plg ...
plugin: checking dynamix.cache.dirs.plg ...
plugin: checking community.applications.plg ...
plugin: checking unRAIDServer.plg ...
plugin: checking dynamix.plg ...

 

It has the 'Done' button but I don't see where it has checked for the unRAID OS...

It has the 'Done' button but I don't see where it has checked for the unRAID OS...

plugin: checking unRAIDServer.plg

It has the 'Done' button but I don't see where it has checked for the unRAID OS...

plugin: checking unRAIDServer.plg

 

I presume you mean "dynamix.scsi.devices.plg"...

 

Not sure why it doesn't appear in your list, but you can always re-install using the URL:

https://raw.githubusercontent.com/bergware/dynamix/master/unRAIDv6/dynamix.scsi.devices.plg

Latest version is 2016.08.18b, the plugin page shows the installed version. If yours isn't the latest it should become available after a "Check for updates"

 

I updated to 2016.08.18 yesterday right after you posted. Just checked for updates and 2016.08.18b shows as available.

I've installed AutoFan but I'm having problems. It detects my PWM, it detected my minimum PWM where it throttled all the fans down and ramped them back up. I can reset the minimum PWM manually and that works as well. I have system temp installed and its reading the CPU temp. BUT when my CPU temp reaches my maximum threshold auto fan doesn't do anything. It will just stay at whatever minimum PWM is set.

 

Any ideas?

 

When I turn off auto fan my fans run near 100% even with fan control set in bios. Ive tried turning fan control on and off in the bios and AutoFan still doesn't work.

 

Maybe I have the wrong temp set for CPU?

In system temp plugin I see:

k10temp temp 1

it8721 temp 1

it8712 temp 2

it8712 temp 3

 

I have an Asus Sabertooth 990FX V2 with AMD fx8350 if that matters.

BUT when my CPU temp reaches my maximum threshold auto fan doesn't do anything.

 

Autofan changes fan speeds according to the highest HDD temp, in doesn't care for MB or CPU temps.

This post relates to SSD TRIM Plugin.

 

I have just upgraded my Main Server from 6.1.9 to 6.2.0 RC3.

 

This morning I received a notification of the following error:

 

fstrim: /mnt/cache: the discard operation is not supported

 

This never happened on 6.1.9 but also I'm appreciative of the fact that no-one else has reported this (based on a forum search of the error) but can't be the only person running this Plugin on 6.2.0 RC3.

 

I've checked the Plugin and it is up to date.

 

I'm running the cache in raid0 configuration:

 

dconvert=raid1 -mconvert=raid1

 

The pool contains 3 SSD drives:

 

CT250BX100SSD1_1514F00579EC - 250 GB (sdb)
CT250BX100SSD1_1514F0057C13 - 250 GB (sdc)
Samsung_SSD_850_EVO_250GB_S21MNXAGA24112P - 250 GB (sdi)

 

Btrfs Pool: 750GB capacity - 47.5GB used - 703 GB free

 

Can anyone help please!?

 

Are your disks directly attached to the motherboard or do you use a HBA or RAID controller?

 

Btw Do you see this error when trying first time (e.g. after system reboot) ?

fstrim: /mnt/cache: FITRIM ioctl failed: Remote I/O error

 

BUT when my CPU temp reaches my maximum threshold auto fan doesn't do anything.

 

Autofan changes fan speeds according to the highest HDD temp, in doesn't care for MB or CPU temps.

 

That explains everything thanks. I guess ill connect all my case fans to the pwm hub and run them separately through AutoFan and hook my CPU cooler separately and run from Bios.

Perhaps a stupid question: What is the benefit of S3 sleep compare to powerdown the system. A few seconds less wake up/boot time? Or is there something i don´t see?

With sleep, another computer can power up the server when it needs it

I use WOL from fully shut down on a regular basis.

Not all mobo's support that.

 

I have 14 PCs here from 2008 till today and "all" of them support WOL