From: Stefan Smietanowski <stesmi@stesmi.com>
To: linux-ide@vger.kernel.org
Subject: Known problems with Maxtor 120GB SATA?
Date: Fri, 05 Mar 2004 15:49:37 +0100 [thread overview]
Message-ID: <40489381.6010601@stesmi.com> (raw)
Hi people.
Are there any knows problems with Maxtor's line of SATA drives,
maybe specifical to the 120GB units?
I've had 3 (out of 3) die on me in the course of 2 weeks and
it's feeling spooky.
They've been connected to different motherboards but the
motherboards have had the same SATA chipset, namely the VIA
8237.
Motherboards :
Soyo SY-KT600 (VIA 8237 + SiI 3112A)
Asus K8V Deluxe (VIA 8237 + Promise 20368)
MSI K8M (VIA 8237 + Promise 20368).
The machines have run both linux (RH FC1 latest updates with libata
replaced by latest) and Windows (the included VIA SATA driver)
and what has happened was that all of a sudden the machines won't
boot into windows but just reboots after showing the moving
dots on the screen. Using powermax on the drives have shown
error XXXS57 on all of them. Most data have been rescuable
but not all and in two cases a full lowlevel format (in powermax)
has cured the problem, at least temporarly. The third one
is currently being formatted.
Powermax refuses to redognize the drives if they are connected
to the VIA 8237 controller so all tests using powermax have
been using the alternate controller on the same board (meaning
SiI 3112A or Promise 20368).
Is there any errata or steps one should take or anything one can do?
Three drives in this sort time feels spooky. The third drive was
bought just one week ago.
Any more info needed, let me know.
When a drive has failed, running 'badblocks -sv' on the drive
makes it either a) fail (if on VIA 8237) b) lock up the system
but the system can be rebooted (if on Promise 20386) or
c) lock up the system so that it can't even be rebooted,
linux is dead (a few times on Promise 20386).
Tests have been done in both 32bit mode and 64bit mode.
Same revision kernel with same patches.
// Stefan
reply other threads:[~2004-03-05 14:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=40489381.6010601@stesmi.com \
--to=stesmi@stesmi.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).