bonienl

Understood, so I added a "refresh" button which allows individual rows to be recomputed (works very nifty!)

Correct.

Each time the "Compute All" button is pressed it will recalculate all shares. That way you can "refresh" the information without the need to leave and re-enter the page.

I have added an automatic disable/enable of the disk spindown delay when a SMART self-test is started from the GUI. This will prevent the running self-test to get aborted unintentionally. I also have created a script which allows to change the setting of a disk spindown delay outside the GUI, and this can be used in a bash script or cron entry. This script is called "spindowndelay". It's syntax is: spindowndelay <device> [<delay>] To set a new spindown delay value, include the parameter <delay> (e.g. 0 = disable delay). To restore the original spindown delay value, omit the second parameter. A rudimentary example of the script test.sh below: #!/bin/bash spindowndelay $1 0 smartctl -t $2 /dev/$1 while true; do sleep 30 if ! smartctl -c /dev/$1|grep -Pom1 '\d+%'; then spindowndelay $1 break fi done The above script is called as: test.sh sdb short and performs a 'short' self-test on disk 'sdb'. Prior to the self-test it will disable the disk spindown delay, and restores it when the self-test is finished. Is this helpful for your situation?

dmidecode version which is currently installed with unRAID dates from 2011, recommend to use the latest slackware version 2.12 instead.

These are NOT the standard versions installed with unRAID. Check the folder /extra on your flash drive or perhaps some non-compatible plugins are installed, see folder /config/plugins on your flash drive. And if you are using unMenu, ensure you have the latest version running.

The oldest version which supports the current webGUI update model is v6.0-beta12. Any version before requires a manual update.

Have included the message contents as well for archived notifications. Upon opening these messages are hidden, but clicking on an individual notification will open (or close) this extra information. This way the list stays compact while the extra information is available.

Have added a "Compute All" button for both user shares and disk shares. These can be used independently. Tip: when cache_dirs is used it will speed up the calculation.

You might want to check your cabling, since the speed is negotiated down to 100 Mb/s.

I've set it to once a week, that seems to be a good compromise for me.

You only need to press save once, to store the driver information (names are displayed in the box). After selecting the sensors, press Apply and all should work.

Eric, no worries, we all know it was you

Thanks

I am using a SSD cache pool myself, and the trim operation works for me.

As an intermediate step I have created a new plugin "SSD TRIM", which allows to set a schedule for the TRIM operation. The set up can be found under Settings -> Scheduler -> SSD TRIM Settings See Dynamix plugins for installation. Thanks dlandon for all the research.

Also logic has been added to send notifications for SMART attributes of unassigned devices...

The regular spin-up/spin-down control only applies to devices in the array. An extension to the webGUI has been made which allows spin-up/spin-down control of any unassigned devices, should become available in a future release.

Is this service available overseas as well, think of time differences ?

Maybe the web keeps a running average where the script window is an instantaneous?? Both speeds are calculated by the preclear script. The one displayed in the window is the average speed between two screen updates, while the one displayed in the GUI is the overall average speed since the start of the operation.

None of the standard unRAID jobs start at 03:15:00, perhaps one of your plugins? Since version 6.1 unRAID is more strict on accessing the webGUI, anything trying to access the GUI on an address different as the localhost, requires authorization from emhttp.

In all testing, did anyone play with the disk setting Force NCQ disabled? Changing it from default Yes to No, does that make a difference for those experiencing performance issues?

Can you check if the tail_log script has execution rights #ls -l /usr/local/emhttp/webGui/scripts -rwxr-xr-x 1 root root 481 Aug 18 10:30 agent -rwxr-xr-x 1 root root 346 Aug 20 04:59 btrfs_balance -rwxr-xr-x 1 root root 817 Aug 20 05:22 btrfs_scrub -rwxr-xr-x 1 root root 4329 Aug 29 23:03 diagnostics -rwxr-xr-x 1 root root 710 Aug 21 01:18 disk_size -rwxrwxrwx 1 root root 565 Sep 26 09:31 ftpusers -rwxrwxrwx 1 root root 678 Sep 26 03:01 localmaster -rwxrwxrwx 1 root root 10394 Sep 27 11:32 monitor -rwxr-xr-x 1 root root 1425 Aug 21 02:37 newperms -rwxr-xr-x 1 root root 7953 Aug 8 02:16 notify -rwxr-xr-x 1 root root 404 Aug 31 2014 pre -rwxr-xr-x 1 root root 585 Aug 20 07:43 reiserfs_check -rwxr-xr-x 1 root root 708 May 27 22:41 share_size -rwxrwxrwx 1 root root 7010 Sep 27 11:33 statuscheck [color=red]-rwxr-xr-x 1 root root 55 Aug 7 23:31 tail_log[/color] -rwxr-xr-x 1 root root 487 Aug 20 07:43 xfs_check

It is possible to manually stop the mover. Do the following from the command line: rm /boot/config/plugins/dynamix/mover.cron update_cron

I'll have a look.