public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ian Bloss <ianlinkcd@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Hard drive noise
Date: Sat, 19 Dec 2015 00:47:27 +0000	[thread overview]
Message-ID: <CADopNUeLSt0iFQAj_RYa89NNXoW5fkCh_gZt9iC6nGxgjKNdjQ@mail.gmail.com> (raw)
In-Reply-To: <5674A782.2040008@iinet.net.au>

[-- Attachment #1: Type: text/plain, Size: 3487 bytes --]

I've had more Seagates die over time than any other brand, I would
recommend getting your money back asap and finding another brand.

I work IT at a school and we no longer purchase seagate drives for their
failure rate.

On Fri, Dec 18, 2015, 19:41 Bill Kenworthy <billk@iinet.net.au> wrote:

> On 19/12/15 08:01, Dale wrote:
> > Howdy,
> >
> > I finally got a new 3TB hard drive.  I got one on sale for under $100.
> > Anyway, I put it in, did the LVM thing and set up my backup script, very
> > basic as it is.  A little bit ago, I noticed a sound.  It's not a click
> > or a metallic type sound.  It sounds like the heads are doing random
> > reads/writes and the heads are moving but doing so noisily.  Thing is,
> > there is no drive activity according to gkrellm or iotop.  All the
> > drives should be basically idle.  I even went to single user mode to be
> > sure nothing in KDE was doing some index thingy or something.  Still,
> > nothing showed that there should be any drive activity, including the
> > hard drive light on the case.
> >
> > Also, I do not know WHICH drive is making this noise yet.  I have four
> > in there running and they are physically mounted close together.  I'm
> > not sure I would know which one it is even if I take the side off the
> > case.  I just know that it is making this odd noise.  Here is some info
> > from hdparm:
> >
> >
> > root@fireball / # hdparm -i /dev/sdd
> >
> > /dev/sdd:
> >
> >  Model=ST3000DM001-1ER166, FwRev=CC25, SerialNo=Z501R198
> >  Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
> >  RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
> >  BuffType=unknown, BuffSize=unknown, MaxMultSect=16, MultSect=off
> >  CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=5860533168
> >  IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
> >  PIO modes:  pio0 pio1 pio2 pio3 pio4
> >  DMA modes:  mdma0 mdma1 mdma2
> >  UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6
> >  AdvancedPM=yes: unknown setting WriteCache=enabled
> >  Drive conforms to: Reserved:  ATA/ATAPI-4,5,6,7
> >
> >  * signifies the current active mode
> >
> > root@fireball / #
> >
> >
> > That's the new drive up above.  Old drive that is basically the same
> > drive, different batch I would assume, is below.
> >
> >
> > root@fireball / # hdparm -i /dev/sdc
> >
> > /dev/sdc:
> >
> >  Model=ST3000DM001-1CH166, FwRev=CC29, SerialNo=W1F4C31Q
> >  Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
> >  RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
> >  BuffType=unknown, BuffSize=unknown, MaxMultSect=16, MultSect=16
> >  CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=5860533168
> >  IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
> >  PIO modes:  pio0 pio1 pio2 pio3 pio4
> >  DMA modes:  mdma0 mdma1 mdma2
> >  UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6
> >  AdvancedPM=yes: unknown setting WriteCache=enabled
> >  Drive conforms to: Reserved:  ATA/ATAPI-4,5,6,7
> >
> >  * signifies the current active mode
> >
> > root@fireball / #
> >
> >
> > The last SMART test I ran showed no problems but I have a fresh one
> > running as I type on all drives.  Will update if it shows anything.
> >
> > Thoughts?
> >
> > Dale
> >
> > :-)  :-)
> >
> >
>
> Mechanics trick - place a largish screwdriver end on each hard drive
> case in turn and the handle end to your ear.  You can hear difference in
> sound quite clearly.
>
> BillK
>
>
>
>

[-- Attachment #2: Type: text/html, Size: 4312 bytes --]

  reply	other threads:[~2015-12-19  0:47 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-19  0:01 [gentoo-user] Hard drive noise Dale
2015-12-19  0:04 ` Ian Bloss
2015-12-19  0:33   ` Dale
2015-12-19  0:40 ` Bill Kenworthy
2015-12-19  0:47   ` Ian Bloss [this message]
2015-12-19  3:07     ` wabenbau
2015-12-19  3:27       ` Ian Bloss
2015-12-19  0:49   ` Dale
2015-12-19  0:57     ` covici
2015-12-19  1:06       ` Dale
2015-12-19  3:27     ` Rich Freeman
2015-12-19  7:56       ` covici
2015-12-19 13:11         ` Rich Freeman
2015-12-19 14:48           ` covici
2015-12-20  7:15             ` [gentoo-user] btrfs strategies (wasHard drive noise) covici
2015-12-20  7:40               ` J. Roeleveld
2015-12-20  9:41                 ` Stefan G. Weichinger
2015-12-20 11:25                   ` covici
2015-12-20 12:15                     ` Rich Freeman
2015-12-19  0:51   ` [gentoo-user] Hard drive noise Adam Carter
2015-12-19  1:14     ` Dale
2015-12-19  1:18       ` Ian Bloss
2015-12-19  1:37 ` Dale
2015-12-19  3:05   ` wabenbau
2015-12-19  8:36     ` J. Roeleveld
2015-12-19 10:12       ` Thomas Mueller
2015-12-19 13:02         ` Rich Freeman
2015-12-19 14:05           ` J. Roeleveld
2015-12-19 14:01         ` J. Roeleveld
2015-12-20  8:28           ` Thomas Mueller
2015-12-20  8:49             ` Neil Bothwick
2015-12-20  4:20       ` wabenbau
2015-12-19 17:03 ` [gentoo-user] " James
2016-01-02  7:20 ` [gentoo-user] " Håkon Alstadheim
  -- strict thread matches above, loose matches on Subject: below --
2015-12-19  3:48 John Runyon

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=CADopNUeLSt0iFQAj_RYa89NNXoW5fkCh_gZt9iC6nGxgjKNdjQ@mail.gmail.com \
    --to=ianlinkcd@gmail.com \
    --cc=gentoo-user@lists.gentoo.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