From: Raffaele BELARDI <raffaele.belardi@st.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: not amd64 specific - disk failure
Date: Tue, 20 Nov 2007 11:25:10 +0100 [thread overview]
Message-ID: <4742B606.4000104@st.com> (raw)
In-Reply-To: <pan.2007.11.20.09.41.54@cox.net>
Duncan wrote:
> Raffaele BELARDI <raffaele.belardi@st.com> posted 47429114.5030102@st.com,
> excerpted below, on Tue, 20 Nov 2007 08:47:32 +0100:
>
> ... You never mentioned exactly what happened to the disk. Mine was
> overheating. I live in Phoenix, AZ, and my AC went out in the middle of
> the summer, with me gone and the computer left running. With outside
> temps often reaching close to 50 C (122 F), the temps inside with the AC
> off could have easily reached 60 C (140 F). Ambient case air temps could
> therefore have reached 70 C, and with the drive spinning in that... one
> can only guess what temps it reached!
Duncan,
I never get those high temperatures here, the highest I've seen at home
is ~30 C (86 F), no AC. I don't think the failure is temperature
related, I always mount a 12cm fan in front of the the HD enclosure, and
the HDs aren't even warm.
Previously the same HD was mounted in a different box, still AUSUS mobo
but VIA chipset instead of NVidia, and different BIOS. In that box the
disk was not automounted from fstab and if not mounted manually it was
normally completely cold even without the 12cm fan running, so I suspect
it was not even spinning (low power mode from BIOS?). I mounted it only
to archive movies after viewing them. In the Nvidia box behavior is
different, the disk warms up even if not mounted, but with the 12cm fan
always running the temp is low.
I have no explanation for this failure. The disk was used really little.
After (if) I recover data I'll try to read the HD SMART database, if I
remember well there are some useful counters there.
The HD is less than 3 years old and should still be under warranty, I'll
try to get a replacement from Seagate. But my movies are more important
now!
I'm sure it's not related, but the irony is that just few hours before
the failure I had run an e2fsck on that partition, not an error did it
report.
raffaele
PS Thanks for the hint on block size.
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2007-11-20 10:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-19 10:05 [gentoo-amd64] not amd64 specific - disk failure Raffaele BELARDI
2007-11-19 11:52 ` Beso
2007-11-19 13:27 ` Raffaele BELARDI
2007-11-19 13:56 ` Beso
2007-11-19 17:14 ` [gentoo-amd64] " Duncan
2007-11-20 7:47 ` Raffaele BELARDI
2007-11-20 9:01 ` Beso
2007-11-20 10:06 ` Raffaele BELARDI
2007-11-20 9:41 ` Duncan
2007-11-20 10:25 ` Raffaele BELARDI [this message]
2007-11-21 9:24 ` Raffaele BELARDI
2007-11-21 10:20 ` Raffaele BELARDI
2007-11-22 9:36 ` [gentoo-amd64] Re: not amd64 specific - disk failure - SUCCESS Raffaele BELARDI
2007-11-23 10:07 ` Duncan
2007-11-21 14:45 ` [gentoo-amd64] Re: not amd64 specific - disk failure Billy Holmes
2007-11-21 15:24 ` Raffaele BELARDI
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=4742B606.4000104@st.com \
--to=raffaele.belardi@st.com \
--cc=gentoo-amd64@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