HDD temperature reached in LaCie Cloudbox, safe temp?

[Jocko]

Maybe a functionality in the CloudBox that prevents it to return to an active state after too long a wait time?

I don't think so if you still wake up the nas with a magic packet (=> wol-fvdw-sl is still running).

You can check that by doing a standby with wol with a big value instead of the test with 5min

[Cubytus]

Ok, I put 120 instead of 5, and will wait for it to restart on its own. The LED briefly turned off, then back on again, but the web interface is unavailable. The disk is off.

A different approach could be used: if a GPIO port is available somewhere on the board, it could be used to trigger a very small fan through a transistor, and turn it off when a suitable temperature is reached.

[Cubytus]

It finally restarted on its own when bypassing the script. I guess I should retry to let it go overheat, then restart on its own?

Interestingly, the automatic email message still had a spam marker, although I used the DDNS name and not the IP:

Code: Select all

Content analysis details:   (9.3 points, 5.5 required) pts rule name              description ---- ---------------------- -------------------------------------------------- 0.7 DNS_FROM_AHBL_RHSBL    RBL: Envelope sender listed in dnsbl.ahbl.org 3.5 BAYES_99               BODY: Bayesian spam probability is 99 to 100% [score: 1.0000] 1.9 TVD_RCVD_IP            TVD_RCVD_IP 0.1 RDNS_DYNAMIC           Delivered to trusted network by host with dynamic-looking rDNS 3.1 AWL                    AWL: From: address is in the auto white-list
X-Spam-Status: Yes, score=9.3


[fvdw]

That would be nice a g,pio pin to start a fan, but there is (to my knowledge) not an easy accesible gpio pin on this device. The pins are on the cpu chip but to start soldering there I would no do. Anyhow in the daemon a timer is running using the internal system clock to calculate the time. Normally the internal clock will always run. What it does is asking system time when the daemon is loaded en then with interval ask again sytem time, calcultes the difference with time ar start and if is bigger then the value set it will continue boot and wake up. If it smaller it loops again to as system time while waiting 0.1 second.

You said that it wake up, was that after 120 minutes?

[Cubytus]

I got the email boot alert (complete with spam mark!) at 17:34, just 4 minutes after the intended 17:30, which seems reasonable for this small NAS. Is there a RTC in that NAS?

[Jocko]

Hi Cubytus,

It was not fvdw's ask...:
your NAS did it wake-up at ~19:34 (17:34 +2h) ? (If I understand well your previous post, it do it)

Interestingly, the automatic email message still had a spam marker, although I used the DDNS name and not the IP:

Pour la 3ème fois, you do not use your DDNS in the HELO command according with your previous tests!

[Cubytus]

No, it was sent on standby WoL at 15:30, then sent the boot email at 17:34.

The EHLO line is:

Code: Select all

echo "EHLO nas2345.no-ip.org"

[Jocko]

I misunderstood you....
So there is no reason so that the temp-guard may not run with an auto-wake up.

Maybe you should make another try

About email feature, can you attach your mail file. I go to edit it so that it uses your public IP.

[Cubytus]

Sure, here it is:

mail.zip

[Jocko]

attached the updated mail script

In fact, I already send you a version which detects the public ip.

So I made a small change (restore the helo command to use the public ip instead of your DDNS)