All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tvrtko A. Ursulin" <tvrtko@ursulin.net>
To: linux-ide@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: Western Digital GreenPower drives and Linux
Date: Thu, 10 Apr 2008 08:48:08 +0100	[thread overview]
Message-ID: <200804100848.08442.tvrtko@ursulin.net> (raw)
In-Reply-To: <200804092118.35501.tvrtko@ursulin.net>

On Wednesday 09 April 2008 21:18:35 Tvrtko A. Ursulin wrote:
> I got one of them (WD5000AACS) recently and to my horror after less than
> three days of being power on this is what I saw:
>
> 9 Power_On_Hours       0x0032 100 100 000 Old_age Always  - 66
> 193 Load_Cycle_Count 0x0032 197 197 000 Old_age  Always  - 10233
>
> At this rate the disk would reach it's design limit for load/unload cycles
> in around 80 days. Not good - so I implemented a lame workaround of keeping
> disk busy every couple of seconds - hopefully that won't kill it sooner
> that unloads would..
>
> I am also currently talking with first line of WD's tech support trying to
> get some data on how exactly those drives manage head unloading, but that
> may not lead anywhere useful.

I got back from WD's tech support and received a DOS utility which can control 
this drive feature, apparently using vendor specific commands. With it head 
unload timer can be disabled or set to a period between 100ms and 25.5s. 

Of course I asked for more than a DOS utility, but the question really is how 
was this feature intended to work with Windows for example, is there 
something there which would prevent such rapid load/unload cycle growth, and 
why isn't it documented somewhere?

I am kind off hoping that someone from WD is reading this list and will notice 
this in case my effort with tech support fails.

Tvrtko

  reply	other threads:[~2008-04-10  7:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-09 20:18 Western Digital GreenPower drives and Linux Tvrtko A. Ursulin
2008-04-10  7:48 ` Tvrtko A. Ursulin [this message]
2008-04-10 12:44   ` Kasper Sandberg
2008-04-10 15:01     ` Christian Pernegger
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
  -- strict thread matches above, loose matches on Subject: below --
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=200804100848.08442.tvrtko@ursulin.net \
    --to=tvrtko@ursulin.net \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.