From: Tejun Heo <htejun@gmail.com>
To: Gabor FUNK <FUNK.Gabor@hunetkft.hu>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: JMicron - hard resetting link
Date: Fri, 22 Feb 2008 11:03:22 +0900 [thread overview]
Message-ID: <47BE2D6A.6060603@gmail.com> (raw)
In-Reply-To: <008901c874d3$10731c80$4d0fa8c0@M2007>
Hello,
Gabor FUNK wrote:
> To sum it up:
> - 1st the 4 disks on the Jmicron controller failed with 1 [chieftek] PSU
> - then it failed with 2 PSU too, but this time the chieftek was only
> connected to the different 4 disks - on the nvidia controller. MB
> and other disks were on the other, non-chieftek [650W] PSU.
> - Then I started the tests with only this second PSU, and it ran
> for about 6 days under heavy testing and array rebuilding and
> guess what: it failed again.
Eeekk..
> Full kernel log at:
> http://www.huweb.hu/maques/tmp/jmicron/kern0221.log
>
> Since it is not a "switch on and see" problem, I'm not in too good
> position, so unless someone have a really great idea or observation,
> I seriously have to consider to replace the MB and probably add
> some extra sata controllers.
If you can still do some testing, what happens if you unplug power to
the failed drive and replug it while the system is still running? Does
hotplug event get triggered and the drive gets recognized again? If so,
does unplugging and replugging the SATA controller only (w/o powering
down the drive) achieve the same thing?
Thanks.
--
tejun
next prev parent reply other threads:[~2008-02-22 2:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 9:48 JMicron - hard resetting link Gabor FUNK
2008-02-12 13:05 ` Tejun Heo
2008-02-12 14:38 ` Gabor FUNK
2008-02-12 14:52 ` Tejun Heo
2008-02-12 17:27 ` Gabor FUNK
2008-02-12 23:50 ` Tejun Heo
2008-02-14 23:02 ` Gabor FUNK
2008-02-14 23:32 ` Tejun Heo
2008-02-21 21:45 ` Gabor FUNK
2008-02-22 2:03 ` Tejun Heo [this message]
2008-02-24 9:04 ` Gabor FUNK
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=47BE2D6A.6060603@gmail.com \
--to=htejun@gmail.com \
--cc=FUNK.Gabor@hunetkft.hu \
--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).