linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Xavier Chantry <shiningxc@gmail.com>
To: linux-ide@vger.kernel.org
Subject: Re: storage fixup laptop model dependent ?
Date: Thu, 18 Feb 2010 00:30:56 +0100	[thread overview]
Message-ID: <b67489df1002171530o4bf26d00od51521d60e1473d6@mail.gmail.com> (raw)
In-Reply-To: <91752840912030533k18aa5595kbdd6bbf716ce5976@mail.gmail.com>

On Thu, Dec 3, 2009 at 2:33 PM, Xavier <shiningxc@gmail.com> wrote:
> Hello,
>
> I have a dell xps m1530 which had a seagate 320 gb (not sure which
> model exactly).
> Anyway that disk was working fine except the last part of the disk
> (~20gb or so) was bad and had many bad sectors.
> I just stopped to use the bad part of the disk, and I had no problems
> for almost one year. I finally decided to get it replaced, and got a
> WDC WD3200BEVT-75ZCT2 instead.
>
> I noticed directly that the disk was much more noisy, and also made a
> lot of annoying click. After a few days, I check load cycle count,
> which is pretty huge :
>  9 Power_On_Hours          0x0032   100   100   000    Old_age
> Always       -       36
> 193 Load_Cycle_Count        0x0032   200   200   000    Old_age
> Always       -       2481
>
> I noticed this disk, or at least the pattern BEVT appear already 4
> times in storage-fixup though the 4rd occurence seems to be either a
> bug or a typo (BEVT vs BEVE) :
> # Reported drive model: WDC WD1600BEVT-75ZCT0
> ata model                       WDC WD*BEVT*
> # Reported drive model: WDC WD3200BEVT-22ZCT0
> ata model                       WDC WD*BEVT*
> # Reported drive model: WDC WD1600BEVT-22ZCT0
> ata model                       WDC WD*BEVT*
> # Reported drive model: WDC WD3200BEVT-22ZCT0
> ata model                       WDC WD*BEVE*
>
> I am just wondering : does it really matter in which laptop that disk
> is used ? As laptop disk can be changed/replaced easily, this also
> sounds strange to me, but there might be a good reason I am missing :)
>

This disk died after two months usage.
I don't know what I am doing wrong, or if Dell just gives my crappy
disks, or if my laptop is doing crazy things with it, or ...

The new one is TOSHIBA MK3263GSX , and I get crazy loading/unloading
with an annoying noise, just like with the WD :
193 Load_Cycle_Count        0x0032   100   100   000    Old_age
Always       -       402
In half a day...

I just noticed the Power on Hours went crazy :
  9 Power_On_Hours          0x0032   100   100   000    Old_age
Always       -       603

I must have some magic power for destroying any hard drives that I touch :)
Unless Power_On_Hours actually means Power_On_Minutes , I will monitor
that field too.

And I will just live with hdparm -B254 , no big deal !

cheers
Xavier

      parent reply	other threads:[~2010-02-17 23:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-03 13:33 storage fixup laptop model dependent ? Xavier
2009-12-14 12:29 ` Xavier
2009-12-15  4:39   ` Tejun Heo
2009-12-18 13:22     ` Xavier
2009-12-21  4:34       ` Tejun Heo
2009-12-22  0:43         ` Robert Hancock
2010-01-11  8:11         ` Tejun Heo
2010-02-17 23:30 ` Xavier Chantry [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=b67489df1002171530o4bf26d00od51521d60e1473d6@mail.gmail.com \
    --to=shiningxc@gmail.com \
    --cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).