sata_mars : Investigation to get hd-idle to work in all hard disks

Keltek escribió:It works now
I have to set the timeout to 20. I listen spinup the HDD and yes, it takes veeeeeeery long time. (with timeout 10 it not works )

Hello Keltek
What kind of hard disk you have... does it have a handle to manually start just kidding.

Guys, you really doing a great job.
So far so good, I mean I have hd-idle activated from always , and it is fine;
I just had a couple of OFF blocking when swithching off, but that is a pending issue, which might be or not be related...

So we are in good directions. thanks for your great work.

I have installed this IBM unit
Only the label is wrong - it should be 1.5TB

Ok, it is WESTERN DIGITAL Caviar AV Green Power 1500GB 32MB cache (WD15EVDS)

The best way to found a parameter in kernel, which is like a "default value" for all drives which appears in system in future. And activate it on boot, not in hdidle script.

Keltek escribió:I have installed this IBM unit

[...]

Only the label is wrong - it should be 1.5TB ;)

Yea! Nice sample of early Winchester technology!!! I had never seen one with so much capacity; ... it must be very recent ;)) the bigest one I've ever seen did have 256MB!!

Ok, it is WESTERN DIGITAL Caviar AV Green Power 1500GB 32MB cache (WD15EVDS) :)

I'm thinking in buying one of these Greens (threre are up to 3GB, 167 Euros, but I'll be content with just 1GB, 50 Euros).

The best way to found a parameter in kernel, which is like a "default value" for all drives which appears in system in future. And activate it on boot, not in hdidle script.

Yes, that would be ideal, but soo far I have not found how to do it ...

Best,

evr escribió:I think a more direct, simple and safe way is: [...] This also takes into account the case that no timeout hooks ar found.

Even simpler:

Código:

USBTIMEOUTS=`ls /sys/block/sd?/device/timeout`
for T in $USBTIMEOUTS ; do echo 30 > $T ; done

BTW, I've just seen in a few linux systems and all have these timeouts set to 30 or larger!

[...] this does not work if the USB disk is plugged after the hd-idle service script has been executed. So, ideally, I think the USB timeout setting should be set by means of hotpulg...

The best way to found a parameter in kernel, which is like a "default value" for all drives which appears in system in future. And activate it on boot, not in hdidle script.

Yes, that would be ideal, but soo far I have not found how to do it ...

If we do not find a solution for this, another option is to include in into the hd-idle code: As soon as it detects a new disc to monitor, check its timer and ajust it if needed. I think I can do it easyly.

Best,

evr escribió:Even simpler:

Código:

USBTIMEOUTS=`ls /sys/block/sd?/device/timeout`
for T in $USBTIMEOUTS ; do echo 30 > $T ; done

Do this code for both SATA and USB discs?

evr escribió:BTW, I've just seen in a few linux systems and all have these timeouts set to 30 or larger!

Ok, I vote for 30.

evr escribió:If we do not find a solution for this, another option is to include in into the hd-idle code: As soon as it detects a new disc to monitor, check its timer and ajust it if needed. I think I can do it easyly.

Agree, it is a clean solution and the number of seconds can be passed to hdidle and the hdidle can set it automatically for all (existing and for future connected) discs.

evr escribió:Even simpler:

Código:

USBTIMEOUTS=`ls /sys/block/sd?/device/timeout`
for T in $USBTIMEOUTS ; do echo 30 > $T ; done

Keltek escribió:Do this code for both SATA and USB discs?

Yes. I forgot to mention...

evr escribió:BTW, I've just seen in a few linux systems and all have these timeouts set to 30 or larger!

Keltek escribió:Ok, I vote for 30.

O.K.

evr escribió:If we do not find a solution for this, another option is to include in into the hd-idle code: As soon as it detects a new disc to monitor, check its timer and ajust it if needed. I think I can do it easyly.

Keltek escribió:Agree, it is a clean solution and the number of seconds can be passed to hdidle and the hdidle can set it automatically for all (existing and for future connected) discs.

O.K. I'll see it along this week. Meanwhile, I think we can already post in SF a patch to enable hd-idle (fixed disks) as a normal service.

Best,

Acknowledge
Victor, did you plan to make some changes in PM?
I should release a fix for LGMenu (as I mentioned some time before about wrong recording directories for external storage), new PM (only binary of course) and this fix for hdidle with timeout set to 30, fully controlled service enabled at startup.

evr escribió:[...]another option is to include in into the hd-idle code: As soon as it detects a new disc to monitor, check its timer and ajust it if needed. I think I can do it easyly.

Keltek escribió:Agree, it is a clean solution and the number of seconds can be passed to hdidle and the hdidle can set it automatically for all (existing and for future connected) discs.

evr escribió:O.K. I'll see it along this week. [...]

Done! Please find it at SF:

http://sourceforge.net/projects/lgmenu/files/Services/hd-idle-1.03a.tgz/download

Best,

evr escribió:[...] Meanwhile, I think we can already post in SF a patch to enable hd-idle (fixed disks) as a normal service.

Well, not anly for fixed disks, but all disks (internal, cradle and USB) -- looks like it works well in all the cases (so far ;).

Best,

Keltek escribió:Acknowledge
Victor, did you plan to make some changes in PM?
I should release a fix for LGMenu (as I mentioned some time before about wrong recording directories for external storage), new PM (only binary of course) and this fix for hdidle with timeout set to 30, fully controlled service enabled at startup.

No, no modification to PM.
I am fine with actual release. thanks.

Some positive reaction today I have sleeping HDD for about 21h and after that the wakeup was without any problems.

Just one notice - I check here in my work some Linux boxes with RHEL 5.4 installed and all devices have 60s timout so I change my mind and set default timeout to 60.

Keltek escribió:Some positive reaction today :) I have sleeping HDD for about 21h and after that the wakeup was without any problems.

Glad to hear about it ;) Did you notice a difference in the temperature of the LG (before awakening the disk) with respect to previous extended use periods with the disk running?

Just one notice - I check here in my work some Linux boxes with RHEL 5.4 installed and all devices have 60s timout so I change my mind and set default timeout to 60.

I think it is exagerated, bu anyway I don't think it may harm, so let's set it to 60 (in any cae, it is easy to change).

Best,

I forgot to test one very important function - start recording while disk is sleeping. So stay tuned to this test...

Working fine!
I am happy with this service.
thanks.

Keltek escribió:I forgot to test one very important function - start recording while disk is sleeping. So stay tuned to this test...

Hope the test has gone well (it should ;)

vic1972 escribió:Working fine! I am happy with this service.

Glad to hear.

Have any of you already tried the new hd-idle binary which sets by itslef the timeout of every new disk detected (i.e., this one)?

Best,

Hi,

I have been measuring the power consumption of my MS450H under various working conditions, including disks spun-up and -down. See:

https://ms450.forosactivos.net/t705-ms450h-power-consumtion#6376

Taking into account only the standard 250GB internal disk, the consumption goes from 16-18 watts with the disk spun-up to 13-15 with the disk spun-down.

Best,

Hello,
I would like to retake this nice thread.
To check if we can make hd-idle work for all or most of the hd devices.

I have check that some of the paths explained at the begining of this thread,
containing filename : timeout,
now they are not there.
I think i will have to re-read the thread.
regards

vic1972 escribió:Hello,
I would like to retake this nice thread. To check if we can make hd-idle work for all or most of the hd devices.

I have check that some of the paths explained at the begining of this thread, containing filename : timeout, now they are not there. I think i will have to re-read the thread.

Hi Vic,
I do not really understand what do you mean. What are no longer there? messages of this thread? or files under /sys ?

Best,

I meant files . I willl. Check later again