XigmaNAS

Posted: **23 Feb 2014 13:19**

Is there any place on the GUI where I can see the power state of my hdds?

Posted: **23 Feb 2014 16:04**

no, but there are some attempts: viewtopic.php?f=56&t=5007

Posted: **23 Feb 2014 21:45**

looks complicated

Posted: **26 Feb 2014 08:52**

drnicolas wrote:looks complicated

Currently I'm working on an extension (named Extended GUI = eGUI) which incorporates inter alia the spinup/down states of hdds. The work is in progress but if you want you can try it, it is easy to install and to remove if it's not worth for you at all.

As you saw in the topic raulfg3 referes to, the thing is a bit tricky and highly dependend on your hardware and also the used FreeBSD version. In my case it worked very well but if your are using ATA drives beginning with FreeBSD 9.1 the state for ATA drives are perhaps not correct.

Installation:

1. Prior to the installation make a backup of the N4F configuration via SYSTEM | BACKUP/RESTORE | Download configuration
2. Use the system console shell or connect via ssh to your N4F server - for the installation you must be logged in as root
3. Change to a persistant place / data directory which should hold the extensions, in my case /mnt/DATA/extensions
4. Download the extension with the fetch command, extract files, remove archive, run the installation script and choose option 1 to install

Code: Select all

cd /mnt/DATA/extensions
fetch https://dl.dropboxusercontent.com/u/36565301/shared/extensions/extended-gui.tar.gz
tar xzvf extended-gui.tar.gz
rm extended-gui.tar.gz
./extended-gui-install.php

After the installation you can manage eGUI via the WebGUI SYSTEM | EXTENSIONS | Extended GUI (don't forget to refresh the WebUI to see the new extension). Just click Enable, choose Extended type and Save. After that you see the modified index page of the N4F webGUI with additional information for the drive state (standby/active) and temperature (SMART must be enabled). This you can see also in STATUS | DISKS.

Btw, in DIAGNOSTICS | LOG I implemented a serach function which could be useful sometimes ...

Posted: **26 Feb 2014 11:10**

Hi, crest, just tested your extension, but unfortunately it does not work for me. In index I see no temperatures and also no disk activity. Only search function in logs work

Perhaps due to different device names?

Code: Select all

 # camcontrol devlist | awk -F\( '{print $2'} | awk -F\, '{print $1}'
pass0
pass1
pass2
pass3
pass4
pass5
pass6
pass7
pass8

I had seen in the past your hd_status.sh script and had modified it a bit to work in my system (not in a gui, simply as a script to be executed from advanced|command
I am posting here in case it helps you to modify it to work with wider range systems.

Code: Select all

#!/bin/sh
# filename:		hd_status.sh
# author:		Andreas Schmidhuber

camcontrol devlist | awk -F\( '{print $2'} | awk -F\, '{print $1}' |while read LINE
do
DEVICE_NAME=`echo $LINE`
if [ $? != 0 ]; then
        DEVICE_NAME=`echo $LINE`;
fi

smartctl -n standby -q silent /dev/$DEVICE_NAME
case $? in
        2) MSG="STANDBY";;
        0) MSG="ACTIVE";;
esac;

echo "Disk: $DEVICE_NAME -> $MSG "
done

It sure is a draft thing, but I stopped when it started working..

Scrrenshot

hd.jpg

I hope it will help you improve the extension.
Regards

LATER EDIT:
Polished it a bit, in case someone else finds it useful in the meantime:

Code: Select all

#!/bin/sh
camcontrol devlist | awk -F\( '{print $2'} | awk -F\, '{print $1}' |while read LINE
do

DEVICE_NAME=`echo $LINE`

smartctl -n standby -q silent -A /dev/$DEVICE_NAME
case $? in
        2) MSG=" Standby"; MSG_TEMP="n/a";;
        0) MSG="Spinning"; MSG_TEMP=`smartctl -n standby -A /dev/$DEVICE_NAME | awk '/Temperature_Celsius/ {print $10}'`;;
esac;

echo "Disk: $DEVICE_NAME -> $MSG | Temperature: $MSG_TEMP  "
done

and the output is:

hd1.jpg

Posted: **27 Feb 2014 11:19**

ChriZathens wrote:Hi, crest, just tested your extension, but unfortunately it does not work for me. In index I see no temperatures and also no disk activity. Only search function in logs work
Perhaps due to different device names?

Thank you for the feedback!

Hmm, should not be a problem of the used drivers because the script gets the device names which comes from the original index.php, as in the following code snippet ...

Code: Select all

echo exec("sh /var/scripts/hd_status.sh {$diskusagev['filesystem']}");

... so $diskusagev['filesystem'] is used by the script which is in my case e.g. /dev/ada1p1

Since I am currently στην Κρήτη I only can use Virtualbox which do not reply to smartcontrol so perhaps you can try at the CLI

Code: Select all

./hd_status.sh /dev/ada1p1

and send me the output to see what happens - would really appreciate!

The output of camcontrol devlist shows me:

Code: Select all

 # camcontrol devlist
<VBOX HARDDISK 1.0>                at scbus0 target 0 lun 0 (ada0,pass0)
<VBOX HARDDISK 1.0>                at scbus0 target 1 lun 0 (ada1,pass1)
<VBOX CD-ROM 1.0>                  at scbus1 target 0 lun 0 (cd0,pass2)
<VBOX HARDDISK 1.0>                at scbus1 target 1 lun 0 (ada2,pass3)
<VBOX HARDDISK 1.0>                at scbus2 target 0 lun 0 (ada3,pass4)
<VBOX HARDDISK 1.0>                at scbus3 target 0 lun 0 (ada4,pass5)
<VBOX HARDDISK 1.0>                at scbus4 target 0 lun 0 (ada5,pass6)
<VBOX HARDDISK 1.0>                at scbus5 target 0 lun 0 (ada6,pass7)
<VBOX HARDDISK 1.0>                at scbus6 target 0 lun 0 (ada7,pass8)

and

Code: Select all

 # camcontrol devlist | awk -F\( '{print $2'} | awk -F\, '{print $1}'
ada0
ada1
cd0
ada2
ada3
ada4
ada5
ada6
ada7

Thank you in advance!

Posted: **27 Feb 2014 11:43**

Hello again, crest!
You are in Crete? Lucky you!
Nice to have you in Greece, I hope it is not strictly business; and some pleasure is included.

Regarding the disks:
Running sh hd_status.sh returns this:

Code: Select all

# sh hd_status.sh /dev/da0
[: 38: unexpected operator
df: /dev/da0: Invalid argument
[: -lt: unexpected operator
[: -lt: unexpected operator
</td><td style='width:90px'>|| Disk: /dev/da0 </td><td style='width:70px'>-> <font color=red><b>Spinning</b></font> </td><td style='width:105px'>| Temperatur: <font color=darkblue><b>38 &deg;C &deg;C</b></font> </td><td>

The script itself seems to retrieve the info, but the extension won't show anything, unfortunately...
When I run my script I get this:

Code: Select all

$ /mnt/hd_status
Disk: pass0 -> Spinning | Temperature: 40  
Disk: pass1 -> Spinning | Temperature: 39  
Disk: pass2 -> Spinning | Temperature: 37  
Disk: pass3 -> Spinning | Temperature: 28  
Disk: pass4 -> Spinning | Temperature: 31  
Disk: pass5 -> Spinning | Temperature: 33  
Disk: pass6 -> Spinning | Temperature: 34  
Disk: pass7 -> Spinning | Temperature: 34

After installing the extension (and enabling all features, just to be sure), If I go to status|disks, this is what I get:

disks.jpg

So temps are retrieved correctly, activity however cannot be retrieved.

But as you can see above, my disks are shown as passx
If I run hd_status.sh /dev/pass7 for example, I get this

Code: Select all

/hd_status.sh /dev/pass7
df: /dev/pass7: Block device required
[: -lt: unexpected operator
[: -lt: unexpected operator
</td><td style='width:90px'>|| Disk: /dev/pas </td><td style='width:70px'>-> <font color=black><b>Unknown</b></font> </td><td style='width:105px'>| Temperatur: n/a </td><td>

It cannot read passx devices. This would be an explanation, but if it could not read the info, then it would not display the temperatures. However it does display them correctly, it is just the activity that is shown n/a. So my best guess is that the script somehow does manage to retrieve dax devices correctly, but cannot get the activity somehow?

EDIT
I also noticed that running hd_status does not spinup the disks. If using the status|disks after installing the extension the disks that are on standby spin up.
Since this is happening, could the case be that your script does not work at all and the temperature is retrieved by the original na4free code? (I am asking because your script is supposed to not weak the disks to retrieve the temperature, right?)
So the assumption here is that it does not work at all, that is why activity won't show and since the disks wake up in status|disks, the temperature display is working using the original code...

I hope I haven't comfused you more..

Thanks a lot for your efforts!

Posted: **28 Feb 2014 07:59**

ChriZathens wrote:Hello again, crest!
You are in Crete? Lucky you!
Nice to have you in Greece, I hope it is not strictly business; and some pleasure is included.

First of all a big THANK YOU for your great support and - yes, I enjoy staying here for another 2 month, left the cold time at home, thanks to Skype and Teamviewer ...

Regarding your tests

Code: Select all

# sh hd_status.sh /dev/da0
[: 38: unexpected operator
df: /dev/da0: Invalid argument
[: -lt: unexpected operator
[: -lt: unexpected operator
</td><td style='width:90px'>|| Disk: /dev/da0 </td><td style='width:70px'>-> <font color=red><b>Spinning</b></font> </td><td style='width:105px'>| Temperatur: <font color=darkblue><b>38 &deg;C &deg;C</b></font> </td><td>

... please can you try this again with sh hd_status.sh /dev/da1p1 or sh hd_status.sh /dev/da1s1 (depending on your hardware) because the script expects also the partition number (which is provided by the original index.php).

The script itself seems to retrieve the info, but the extension won't show anything, unfortunately...

... I'm a bit puzzled because the script output goes straight to the index page (beside the unexpected errors above which comes from the /dev/da0 without the partition ...), there is nothing in the output after the free space values, like this?

But as you can see above, my disks are shown as passx

... this I don't understand too, because when I tried your suggested command

Code: Select all

camcontrol devlist | awk -F\( '{print $2'} | awk -F\, '{print $1}'

I got all adaX as you can see in my former posting. Do you get a similiar output as me if you only use camcontrol devlist (perhaps not because of you LSI 3081E-R SAS Controller)?

It cannot read passx devices. This would be an explanation, but if it could not read the info, then it would not display the temperatures. However it does display them correctly, it is just the activity that is shown n/a. So my best guess is that the script somehow does manage to retrieve dax devices correctly, but cannot get the activity somehow?

True, passx is not possible but I supposed that the index page handover is the adaXY instead of passX, weired.
The activity comes from the smartctl -n standby exit code and SHOULD not spinup the disks, as far as smartcontrol do not ignore the standby parameter ...

I am asking because your script is supposed to not weak the disks to retrieve the temperature, right?

Yes, sure.

A last test to clarify things - could you please replace the line 541 in YOUR_EXTENSION_DIRECTORY/extended-gui/files/index_opt.php

Code: Select all

echo exec("sh {$config['extended-gui']['rootfolder']}files/hd_status.sh {$diskusagev['filesystem']}");

with

Code: Select all

echo " | DEVICE: {$diskusagev['filesystem']}";

and change in WebGUI Extensions | Extended GUI the type to standard, then save and again the type to Extended and save to activate the changes and send me the part of the index screen which shows now the device names.

Thank you in advance!!!

Regards
crest

Posted: **28 Feb 2014 10:54**

crest wrote: ... please can you try this again with sh hd_status.sh /dev/da1p1 or sh hd_status.sh /dev/da1s1 (depending on your hardware) because the script expects also the partition number (which is provided by the original index.php).

The only device I have with partition is da8 (da8a1). But it is the usb stick for the embedded OS which cannot provide its info anyway. All the other disks have no partitions
I am using 2 raidz pools and in index I see the pools, not devices (OMG, does it actually work with ZFS pools yet, or am i giving you headaches for nothing???)

... I'm a bit puzzled because the script output goes straight to the index page (beside the unexpected errors above which comes from the /dev/da0 without the partition ...), there is nothing in the output after the free space values, like this?

No, this is what I see normally(extension not installed):

normal.jpg

and this is what I see after I install the extension and activate "extended"

after_ext.jpg

I got all adaX as you can see in my former posting. Do you get a similiar output as me if you only use camcontrol devlist (perhaps not because of you LSI 3081E-R SAS Controller)?

Here is the output:

Code: Select all

 # camcontrol devlist
<ATA ST31500541AS CC34>            at scbus4 target 25 lun 0 (pass0,da0)
<ATA ST1500DL003-9VT1 CC3C>        at scbus4 target 26 lun 0 (pass1,da1)
<ATA ST31500541AS CC34>            at scbus4 target 27 lun 0 (pass2,da2)
<ATA SAMSUNG HD154UI 1118>         at scbus4 target 28 lun 0 (pass3,da3)
<ATA SAMSUNG HD204UI 0001>         at scbus4 target 29 lun 0 (pass4,da4)
<ATA SAMSUNG HD204UI 0001>         at scbus4 target 30 lun 0 (pass5,da5)
<ATA SAMSUNG HD204UI 0001>         at scbus4 target 31 lun 0 (pass6,da6)
<ATA SAMSUNG HD204UI 0001>         at scbus4 target 32 lun 0 (pass7,da7)
<Kingston DataTraveler 2.0 1.00>   at scbus6 target 0 lun 0 (pass8,da8)

A last test to clarify things - could you please replace the line 541 in YOUR_EXTENSION_DIRECTORY/extended-gui/files/index_opt.php
Code: Select all
echo exec("sh {$config['extended-gui']['rootfolder']}files/hd_status.sh {$diskusagev['filesystem']}");
with
Code: Select all
echo " | DEVICE: {$diskusagev['filesystem']}";
and change in WebGUI Extensions | Extended GUI the type to standard, then save and again the type to Extended and save to activate the changes and send me the part of the index screen which shows now the device names.

In line 541 this is what I have :

Code: Select all

echo exec("sh /var/scripts/hd_status.sh {$diskusagev['filesystem']}");

What the heck... am I using wrong script version???? (I got it from

Code: Select all

https://dl.dropboxusercontent.com/u/36565301/shared/extensions/extended-gui.tar.gz

)

These are lines 539-542 in files/index_opt.php (located in /mnt/Media/ext directory in my NAS)

Code: Select all

 539                                                                                 "<span name='diskusage_{$ctrlid}_used' id='diskusage_{$ctrlid}_used' class='used' style='display:inline-block; width:30px; text-align:right; font-wei
ght:bold; color:blue'>{$diskusagev['used']}</span>",
    540                                                                                 "<span name='diskusage_{$ctrlid}_free' id='diskusage_{$ctrlid}_free' class='free' style='display:inline-block; width:30px; text-align:right; font-wei
ght:bold; color:green'>{$diskusagev['avail']}</span>");
    541                                     echo exec("sh /var/scripts/hd_status.sh {$diskusagev['filesystem']}");
    542                                                                         echo "</div></td></tr>";

I am doing the following:

I go to extensions| change extended to standard

Edit index_opt.txt Replace

Code: Select all

 echo exec("sh /var/scripts/hd_status.sh {$diskusagev['filesystem']}");

with

Code: Select all

echo exec("sh {$config['extended-gui']['rootfolder']}files/hd_status.sh {$diskusagev['filesystem']}");

(since this is the supposed correct code)

Re-enable extended gui
Verified that the change I made also exists in /usr/local/www/index.php

What I see now:

after1stchange.jpg

As you can see no change...
Let's do the other change:

I go to extensions| change extended to standard

Edit index_opt.txt Replace

Code: Select all

echo exec("sh {$config['extended-gui']['rootfolder']}files/hd_status.sh {$diskusagev['filesystem']}");

with

Code: Select all

echo " | DEVICE: {$diskusagev['filesystem']}";

Re-enable extended gui
Verified that the change I made also exists in /usr/local/www/index.php

I see the same as before: (not even attaching additional screenshot)

after1stchange.jpg

What am I doing wrong???

Thank you in advance!!!

Regards
crest

Thank YOU for your efforts!

Posted: **28 Feb 2014 12:31**

ChriZathens wrote: OMG, does it actually work with ZFS pools yet, or am i giving you headaches for nothing???

YES, you got it, this was the reason! On the index page the drive states are not implemented for ZFS because behind one pool there are usally more than one drive.
But don't worry about headaches, of course it was my fault not to mention this

What the heck... am I using wrong script version???? (I got it from ...

my second fault, I fiddled around searching for the reason and copied the wrong string ...

The output of

Code: Select all

# camcontrol devlist

is for some reason different - (adaX, passX) on my system and vice versa on yours. Strange ...
Could be the reason why the Activity in Status | Disks is not working ... hmm, I must postbone this issue until May (back home from Crete)

Btw, can you confirm that after running your script -

several times the drives are still in standby and not spinning up? This was a discussion in the other topic viewtopic.php?f=56&t=5007 we had and for me it is still unpredictable when and why this happen ...

Posted: **28 Feb 2014 12:56**

crest wrote: YES, you got it, this was the reason! On the index page the drive states are not implemented for ZFS because behind one pool there are usally more than one drive.
But don't worry about headaches, of course it was my fault not to mention this

Oh, OK, I see.. At least we now know what is wrong!

The output of
Code: Select all
# camcontrol devlist
is for some reason different - (adaX, passX) on my system and vice versa on yours. Strange ...
Could be the reason why the Activity in Status | Disks is not working ... hmm, I must postbone this issue until May (back home from Crete)

No worries! Enjoy your stay at Greece and it will be ready when it is ready..

Btw, can you confirm that after running your script -
several times the drives are still in standby and not spinning up? This was a discussion in the other topic viewtopic.php?f=56&t=5007 we had and for me it is still unpredictable when and why this happen ...

Yes I can confirm it .
Just run it over 20 times...
However I saw that there is some kind of bug with it - almost like mixing da3 with da8 . I will look into it...
But it won't spinup the drives (at least in my NAS) - that's for sure!!!
Just FYI, I would like to add, that due to my LSI, my disks do not spin down automatically. I have a cron job which issues a "camcontrol stop dax" command every 30 minutes.
I don't know if it makes any difference, but I thought I should mention it

Posted: **01 Mar 2014 08:20**

ChriZathens wrote: Yes I can confirm it .
Just run it over 20 times...
However I saw that there is some kind of bug with it - almost like mixing da3 with da8 . I will look into it...
But it won't spinup the drives (at least in my NAS) - that's for sure!!!
Just FYI, I would like to add, that due to my LSI, my disks do not spin down automatically. I have a cron job which issues a "camcontrol stop dax" command every 30 minutes.
I don't know if it makes any difference, but I thought I should mention it

Ok, that's good to know. I will try to include ZFS pool drives to the index page, perhaps you can give it a try too, when I'm finished with it.

Posted: **11 Mar 2014 15:07**

ChriZathens wrote:
crest wrote: Btw, can you confirm that after running your script -
several times the drives are still in standby and not spinning up? This was a discussion in the other topic viewtopic.php?f=56&t=5007 we had and for me it is still unpredictable when and why this happen ...
Yes I can confirm it .
Just run it over 20 times...
However I saw that there is some kind of bug with it - almost like mixing da3 with da8 . I will look into it...
But it won't spinup the drives (at least in my NAS) - that's for sure!!!
Just FYI, I would like to add, that due to my LSI, my disks do not spin down automatically. I have a cron job which issues a "camcontrol stop dax" command every 30 minutes.
I don't know if it makes any difference, but I thought I should mention it

Hello again ChriZathens!

Please can you do me a favour and try the following command

Code: Select all

zpool list -vH

this should (hopefully) work without spinning up the drives. If this works without spinning up the drives please try the version of eGUI I attached below.

extended-gui.tar.gz

Thank you in advance for your support!
crest

Posted: **11 Mar 2014 16:30**

Hello again, crest! zpool list -vH does not spinup the drives.
So I just tried your new extension and in main page I can now see my drives!

zfsdisks.jpg

I bit high temps - Media2 was just finishing a scrub atm
I cannot see the activity (shows as n/a) in Status|Disks, though..
Don't know if it was supposed to work there, yet, though..
In 17:30 my script for stopping the disks run and now this is what I see:

disksstopped.jpg

I needed to refresh the webui in order to see the change, however (just FYI)
Nice work!!

P.S.: As you can see, the da devices are not in order. It is not your scripts fault.
Zpool status:

Code: Select all

  pool: Media
 state: ONLINE
  scan: scrub repaired 0 in 6h23m with 0 errors on Mon Mar 10 20:10:58 2014
config:

	NAME        STATE     READ WRITE CKSUM
	Media       ONLINE       0     0     0
	  raidz1-0  ONLINE       0     0     0
	    da1     ONLINE       0     0     0
	    da0     ONLINE       0     0     0
	    da2     ONLINE       0     0     0
	    da3     ONLINE       0     0     0

errors: No known data errors

  pool: Media2
 state: ONLINE
  scan: scrub repaired 0 in 7h7m with 0 errors on Tue Mar 11 17:24:17 2014
config:

	NAME        STATE     READ WRITE CKSUM
	Media2      ONLINE       0     0     0
	  raidz1-0  ONLINE       0     0     0
	    da5     ONLINE       0     0     0
	    da7     ONLINE       0     0     0
	    da6     ONLINE       0     0     0
	    da4     ONLINE       0     0     0

errors: No known data errors

Posted: **11 Mar 2014 18:19**

ChriZathens wrote: zpool list -vH does not spinup the drives.
So I just tried your new extension and in main page I can now see my drives!

GREAT, THANKS A LOT FOR TRYING AND THIS FAST FEEDBACK

ChriZathens wrote: I cannot see the activity (shows as n/a) in Status|Disks, though.
Don't know if it was supposed to work there, yet, though..

Yes, I know. I didn't work on this page, this will be one of my next steps.

ChriZathens wrote: I needed to refresh the webui in order to see the change, however (just FYI)
Nice work!!
P.S.: As you can see, the da devices are not in order. It is not your scripts fault.

Yes, the live view is also on my list

You can adjust the width of the disk and zpool tables in the extension - I decided to do it like this because of the different length of words in different languages (and a lack of knowledge in HTML ...

). The thresholds for (high) disk temperatures and also for the disk/pool capacity warning indicator (the icon on the right hand side) will be configurable in the next version (at the moment hard coded values) as well as optional information via email.

What is/will be included in the extension:

ACCESS | USERS & GROUPS | USERS (access_users.php)
- CHANGED: column "GROUP" now shows all groups a user belongs to (originally shows only the primary group of a user).

DIAGNOSTICS | LOG (diag_log.php)
- NEW: search (case insensitive) in all logs
- CHANGED: column "USER" now shows user / processes (originally shows always the host name)

STATUS | DISKS (status_disks.php)
- NEW: column "ACTIVITY" shows disk status "spinning / standby" (SMART must be enabled)

STATUS | SYSTEM (index.php)
- NEW: compact display for disks to show all information on one webpage - "dashboard" like - without scrolling
- NEW: hide/show multicore CPU usage bars
- NEW: show system drive (md0 ???)
- NEW: support for temporarly (not via WebGUI) mounted disks (USB disks, Flash drives, ...)
- NEW: compact disks view (SMART must be enabled to get temperature and activity) with drive status/temperature
and disk/pool capacity warning indicator (optional information via email)
The width of the disks view can be adjusted via Extended GUI for optimal display:
- Disk table width -> for single disks
- ZFS table width -> for ZFS pools
- NEW: automount for USB disks, Flash drives, ...
- NEW: display of logged in users (SSH, FTP, SMB/CIFS -> user/ip@/port) and clients (for Autoshutdown detection based on IP@)
- NEW: display of services / service status (ON/OFF) / quick links
- Autoshutdown, SubSonic, miniDLNA, pyLoad, BitTorrent, udpxy, Webserver, BitTorrent Sync
- NEW: implementation of additional functions:
- Autoshutdown ON/OFF: disable/enable autoshutdown (script)
- Purge: purge of files in CIFS/SMB recycle bin
- unmount / remount USB disks
- unmount ATA (adaX) disks
- FSCK All: run fsck script online

All changes in the WebGUI pages are already implemented but the configuration for the additional functions in the extension need some work.

Regards from Crete,
crest

Posted: **11 Mar 2014 20:07**

thanks a lot, your hard work is very promissing.

some new blood are always welcome....

Posted: **13 Mar 2014 08:02**

raulfg3 wrote:thanks a lot, your hard work is very promissing.

some new blood are always welcome....

Thank you very much

I just try to share the experience I got since the days of FreeNAS 0.68... and I hope some people find these things useful too ...

Posted: **13 Mar 2014 10:29**

You rock, man!

Posted: **14 Mar 2014 06:19**

ChriZathens wrote:You rock, man!

Posted: **21 Mar 2014 17:22**

Hi Crest,

nice extension, thanks a lot for your work!

Cheers,

Crowi

Posted: **21 Mar 2014 17:36**

crowi wrote:Hi Crest,

nice extension, thanks a lot for your work!

Cheers,

Crowi

THANK YOU!

The work on the extension is still in progress, at the moment I'm struggling to make all values live (lack of Javascript knowledge

). When I've manegd this then I think it will be ready with all features soon ...

Regards
crest

Posted: **16 Apr 2014 09:20**

drnicolas wrote:looks complicated

I released just now an extension where you can see the drive states, see viewtopic.php?f=71&t=6405#p35442

XigmaNAS

Can I see the spinup/down state on GUI ?

Can I see the spinup/down state on GUI ?

Re: Can I see the spinup/down state on GUI ?

Re: Can I see the spinup/down state on GUI ?

Re: Can I see the spinup/down state on GUI ?

Re: Can I see the spinup/down state on GUI ?

Re: Can I see the spinup/down state on GUI ?

Re: Can I see the spinup/down state on GUI ?

Re: Can I see the spinup/down state on GUI ?

Re: Can I see the spinup/down state on GUI ?

Re: Can I see the spinup/down state on GUI ?

Re: Can I see the spinup/down state on GUI ?

Re: Can I see the spinup/down state on GUI ?

Re: Can I see the spinup/down state on GUI ?

Re: Can I see the spinup/down state on GUI ?

Re: Can I see the spinup/down state on GUI ?

Re: Can I see the spinup/down state on GUI ?

Re: Can I see the spinup/down state on GUI ?

Re: Can I see the spinup/down state on GUI ?

Re: Can I see the spinup/down state on GUI ?

Re: Can I see the spinup/down state on GUI ?

Re: Can I see the spinup/down state on GUI ?

Re: Can I see the spinup/down state on GUI ?