From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Hard drive noise
Date: Fri, 18 Dec 2015 19:37:10 -0600 [thread overview]
Message-ID: <5674B4C6.6020907@gmail.com> (raw)
In-Reply-To: <56749E6B.1020800@gmail.com>
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.
>
> <<< SNIP >>>
>
> Thoughts?
>
> Dale
>
> :-) :-)
>
>
Well ain't this interesting. I was about to pull the side off that
monster Cooler Master HAF-932 when I moved my router, which sits on top
of the case over the top fan. When I moved it, the sound stopped. When
I sat it back down, it made that noise again but slightly different.
So, I moved the router a little further back. Now all is quiet. No
weird noises for the last several minutes now.
After finding out about this drive, now I'm nervous about depending on
it for a backup. Bad thing is, I've got two of these drives now.
Different batches but still. Since firmware seems to have some affect
on this, is this a good version to have?
Firmware Version: CC25
That's on the new drive. The old drive is:
Firmware Version: CC29
Weird, my new drive seems to have older firmware than my old drive.
How's that work I wonder? My old drive is a couple years old at least.
I think I'm leery of all drives now. I've had WDs fail, Seagate and
some other brand. I just keep buying bad stuff. :-( I'm glad I don't
have to buy pacemakers. :/
Dale
:-) :-)
next prev parent reply other threads:[~2015-12-19 1:37 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
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 [this message]
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=5674B4C6.6020907@gmail.com \
--to=rdalek1967@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