From: "Rainer Fügenstein" <rfu@oudeis.org>
To: Íõ½ðÆÖ <jinpuwang@gmail.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re[2]: SATA start unit command?
Date: Tue, 19 Mar 2013 21:09:36 +0100 [thread overview]
Message-ID: <764451547.20130319210936@oudeis.org> (raw)
In-Reply-To: <CAD9gYJLkpmgSY1_U=1H6b+oJJB_R60cHKqs2NCY4wkRL9xmu5w@mail.gmail.com>
tnx for the info. looks like I need to upgrade from centos5 to centos6
to get the proper versions of the kernel and hdparm.
and also be ready to ship the drive back to WDC if its firmware also
has this bug that prevents disabling PUIS.
Í> Hi,
Í> Hdparm offer some method to control power management:
Í> -B Set Advanced Power Management setting (1-255)
Í> -s Set power-up in standby flag (0/1) (DANGEROUS)
Í> -S Set standby (spindown) timeout
Í> -y Put drive in standby mode
Í> -Y Put drive to sleep
Í> You can more info in the man page
Í> Regards,
Í> Jack
Í> 2013/3/18 Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>
>> On Mon, Mar 18, 2013 at 12:30:50AM +0100, Rainer Fügenstein wrote:
>> > hi,
>> >
>> > for some reasons I need to keep power consumption at startup as low as
>> > possible. since the server is booting from SSD, it is possible to send
>> > a "start unit" (or similar) command to all SATA drives early in the
>> > init process.
>> >
>> > as far as I've searchengined, the drives and the SATA controller need
>> > to support this feature. but my assumption is that when the drives are
>> > not needed at startup (since they would be started by the OS), the
>> > controller won't need to support "start unit". what is your
>> > experience on this matter?
>> >
>> > drives in question are WD Green 3TB drives (WDC WD30EZRX-00DC0B0), the
>> > controllers at hand are a promise SATA 300 TX4 (don't laugh ;-) ) and
>> > a supermicro AOC-SAT2-MV8.
>>
>> Hi Rainer,
>>
>> I'm facing a similar issue.
>>
>> That's what I got so far...
>>
>> Many HDDs, but it seems not all, support the so
>> called Staggered Spin Up, this means they are in
>> sleep mode, when powered up.
>> A SATA bus scan will wake them up.
>>
>> The Linux AHCI driver performs, per default, but
>> it could be changed by parameter, a serial bus
>> scan. This means it will wake up the HDDs one after
>> the other sequentially and not alltogether.
>> At least, this is what I understood, but I did not
>> tested it personally, I just trust the information
>> I found around.
>> Check "Linux AHCI SSS" with some search engine and
>> some patience.
>>
>> Other drivers I do not know.
>>
>> If you boot from SSD and you program the HDDs to
>> stay sleepy (jumper, firmware or cable select,
>> more info at https://en.wikipedia.org/wiki/Spin-up
>> and referenced links) it *should* work.
>>
>> Hope this helps,
>>
>> bye,
>>
>> pg
>>
>> >
>> > tnx.
>> >
>> > --
>> > To unsubscribe from this list: send the line "unsubscribe linux-raid" in
>> > the body of a message to majordomo@vger.kernel.org
>> > More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>> --
>>
>> piergiorgio
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
------------------------------------------------------------------------------
Unix gives you just enough rope to hang yourself -- and then a couple of more
feet, just to be sure.
(Eric Allman)
------------------------------------------------------------------------------
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-03-19 20:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-17 23:30 SATA start unit command? Rainer Fügenstein
2013-03-18 17:32 ` Piergiorgio Sartor
[not found] ` <CAD9gYJLkpmgSY1_U=1H6b+oJJB_R60cHKqs2NCY4wkRL9xmu5w@mail.gmail.com>
2013-03-19 20:09 ` Rainer Fügenstein [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=764451547.20130319210936@oudeis.org \
--to=rfu@oudeis.org \
--cc=jinpuwang@gmail.com \
--cc=linux-raid@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox