mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Christian Pernegger" <pernegger@gmail.com>
To: "Tvrtko A. Ursulin" <tvrtko@ursulin.net>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Western Digital GreenPower drives and Linux
Date: Thu, 10 Apr 2008 17:01:38 +0200	[thread overview]
Message-ID: <bb145bd20804100801y157b4a34m82f084d27f1e0586@mail.gmail.com> (raw)
In-Reply-To: <1207831481.1514.8.camel@localhost>

[ Keep me CCd on this, please. ]

>  Those fancy new WD GreenPower drives seem to be heavily suffering from the
>  rapidly increasing head load/unload problem. [...] I got one of them
>  (WD5000AACS) recently and to my horror [...]

I have the same disks, only with more warranty and supposedly
"enterprise" firmware (WD1000FYPS). The bug is the same, though, on
all four of them (~ 9 cycles /hour):

  9 Power_On_Hours          0x0032   099   099   000    Old_age
Always       -       917
193 Load_Cycle_Count        0x0032   198   198   000    Old_age
Always       -       8025

  9 Power_On_Hours          0x0032   099   099   000    Old_age
Always       -       906
193 Load_Cycle_Count        0x0032   198   198   000    Old_age
Always       -       7908

  9 Power_On_Hours          0x0032   099   099   000    Old_age
Always       -       907
193 Load_Cycle_Count        0x0032   198   198   000    Old_age
Always       -       8051

  9 Power_On_Hours          0x0032   099   099   000    Old_age
Always       -       918
193 Load_Cycle_Count        0x0032   198   198   000    Old_age
Always       -       7869

>  I got the _DOS_ utility from WD which issues vendor specific commands to
>  control that feature.

Have they confirmed it's a bug? I have no idea how often the disks
should do that.

>  [...] With it the unload feature can be either disabled or timer set from
>  100ms to 25.5 seconds. But obviously I can't try it...

Why? Using a DOS boot disk once would not be that bad as a workaround,
would it? Or is the setting not persistent? Either way I'd prefer to
be able to leave the feature on (in usable form), eventually.

The bigger question is - why the rapid loads / unloads? In my case the
disks are idle hours at a time. No system files on there, just bulk
data. Does / could the controller (sata_sil24 in my case) have any
influence on this kind of power management?

Thanks,

C.

  reply	other threads:[~2008-04-10 15:02 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-09 20:18 Tvrtko A. Ursulin
2008-04-10  7:48 ` Tvrtko A. Ursulin
2008-04-10 12:44   ` Kasper Sandberg
2008-04-10 15:01     ` Christian Pernegger [this message]
2008-04-12 17:11       ` Jan Engelhardt
2008-04-13 15:41         ` Mark Lord
2008-04-16 11:40 ` Helge Hafting
2008-04-16 17:59   ` Christian Pernegger
2008-04-16 18:18     ` Mark Lord
2008-04-16 19:44     ` Tvrtko A. Ursulin
2008-04-16 19:46   ` Tvrtko A. Ursulin
2008-04-10 22:36 devzero
2008-04-11 21:00 ` Tvrtko A. Ursulin
2008-04-12  3:19   ` Mike Snitzer
2008-04-12  7:11     ` Tvrtko A. Ursulin
2008-04-12 15:20       ` Mike Snitzer
2008-04-12 15:56         ` Mike Snitzer
2008-04-13  8:30           ` Niels
2008-04-27 17:45 devzero
2008-04-27 19:14 ` Renato S. Yamane
2008-04-29 15:22 ` Niels

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=bb145bd20804100801y157b4a34m82f084d27f1e0586@mail.gmail.com \
    --to=pernegger@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tvrtko@ursulin.net \
    /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

all inboxes | Powered by JetHome®