Temperature hook?

[mdi]

Hi,
I have a NWSP2 and during summer it gets hot as much as 56-57C. I had to increase the threshold level of max temp, as it was set to 55 and the NAS started to shutdown and wake up repeatedly.

I now got a small fan pointing at it, so the temp went down about 15C, which is fine.

I was thinking it it could be possible to have a sort of SW hook connected to the HDD temp. With that I could probably define a IFTTT rule to switch my fan on and off, according to a different threshold, in order not to activate it only when necessary.

To start with something, where do I read the HDD temperature from the cmdline?
Is there a way to have a script running (every minute is fine) so I can do something with that value? If I can use the crontab from the web interface, where do I place the script?
Can I use wget or curl inside the script to make web calls?

Thanks,
MDI

[fvdw]

Smartctl and hdparm command can be used to read disk temperature.

Code: Select all

smartctl -a /dev/sda | grep Temp | cut -d" " -f 2,37
Response will be something like
Temperature_Celsius 42

Code: Select all

hdparm -H /dev/sda

(The hdparm command is not supported by some disks)

I mustchave somewhere a a program that returns disk temp, I will look at that later this evening

Wget and curl can be used in shell scripts

[mdi]

Thank you, in my case both work.

What would be the best place to store a script to drive the external fan via IFTTT?
I imagine i could run it via the crontab available from the web interface.

Thanks.

[fvdw]

I would store it in a shared folder. If you store it in system folder it will be hone after installing a firmware upgrade.
Yes you could use cron to run your script periodically

[mdi]

Hi again, I implemented a script which is run every minute, but I have a doubt.
As it saves the actual temperature to a file in order to know when it goes above or below the temperature tresholds, I assume taht the disk won't ever spin down any longer.

To avoid this, the last-temperature data should be kept in memory, but this means that the script should be run as a sort of daemon.

Is that possible?

[fvdw]

You could make a script that has an endless loop and use sleep command to pause it in the loop. In this case no need to use cron but start the script at boot. The firmware has a feature to run user defined scripts at boot
Ps 1 minute is very short. You can safely use 10 minutes to my opinion

[mdi]

Thank you fvdw, I'll consider and test this option. Thanks a lot!