From: Jeff Garzik <jgarzik@pobox.com>
To: "Guillaume Laurès" <guillaume.laures@club-internet.fr>
Cc: linux-ide@vger.kernel.org, Erik Mouw <erik@harddisk-recovery.com>,
debian-amd64@lists.debian.org
Subject: Re: sata disk failure?
Date: Tue, 15 Feb 2005 11:50:33 -0500 [thread overview]
Message-ID: <42122859.9060609@pobox.com> (raw)
In-Reply-To: <353ee8ef7c34573b3e1322ba7502c529@club-internet.fr>
Guillaume Laurès wrote:
> Hello,
>
> Here is a small report in attachement, done with 2.6.11-rc4.
>
>
> ------------------------------------------------------------------------
>
> * Hardware is nforce3 250GB, booting debian pure64 on pata (Maxtor 30Gb 6E030L0) drive. The goal is to mount data found on a sata disk (seagate 200Gb ST3200822AS). The pata drive holds / and lvm partition with /usr, /var /tmp and /home.
> The ultimate goal is to switch all this to the sata drive, which already holds a (barely used) swap partition.
>
> * Soon after boot the console displays:
> nv_sata: Primary device removed
> nv_sata: Primary device removed
> nv_sata: Primary device removed
> nv_sata: Primary device removed
> ...
> nv_sata: Primary device removed
> nv_sata: Primary device removed
> nv_sata: Primary device removed
> nv_sata: Primary device removed
> nv_sata: Primary device removed
> nv_sata: Primary device added
> nv_sata: Primary device added
> and the sata disk seems to spin down at the same time.
> This is currently on 2.6.11-rc4, although I got the same behaviour with 2.6.10 and 2.6.11-rc3. Removing power from the drive and pluging it again seems to make te drive work some time , until it spins down again...
Seems like the hotplug code is triggering. That signals to me there is
some connection problem. Maybe you have a bad cable, or maybe the cable
is just seated improperly in one of the two SATA plugs.
It's also possible your motherboard or drive SATA plug is faulty, but I
would replace the cable first.
Jeff
next prev parent reply other threads:[~2005-02-15 16:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <420D5FAE.7040109@linux.it>
[not found] ` <20050212155420.GA13468@harddisk-recovery.com>
[not found] ` <170b0d7e63345e9b7dba9341a87a8a01@club-internet.fr>
[not found] ` <20050213150102.GB13468@harddisk-recovery.com>
2005-02-15 13:53 ` sata disk failure? Guillaume Laurès
2005-02-15 16:50 ` Jeff Garzik [this message]
2005-02-15 17:48 ` sata coldplug? Dieter Stüken
2005-02-15 18:30 ` Jeff Garzik
2005-02-15 22:38 ` sata disk failure? Guillaume Laurès
[not found] ` <421342FE.5020800@zsolt.net>
2005-02-16 14:30 ` Guillaume Laurès
2005-02-15 18:42 ` Stephen Hassard
2005-02-15 21:51 ` Guillaume Laurès
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=42122859.9060609@pobox.com \
--to=jgarzik@pobox.com \
--cc=debian-amd64@lists.debian.org \
--cc=erik@harddisk-recovery.com \
--cc=guillaume.laures@club-internet.fr \
--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).