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, 15 Feb 2008 08:32:01 +0900 [thread overview]
Message-ID: <47B4CF71.5070408@gmail.com> (raw)
In-Reply-To: <005c01c86f5d$b050b4e0$4d0fa8c0@M2007>
Gabor FUNK wrote:
> To be honest, I didn't believe that doing anything with the PSU
> would do something.
> However, seemingly it did.
> I have also updated the BIOS, but I guess this has not much
> to do with it.
I too am amazed at the number of PSU problems getting reported here. It
seems most hardware problems turn out to be power related.
> So a different brand PSU was additionally installed, and this
> one got the motherboard and the 4 disk which were failing.
> The "old" PSU got the second 4 hdds and the 2 other system
> HDDs.
> Test was started yesterday (Feb 13) about 16:30 CET including
> array building up and file copies. About today (14) 20:22 the
> problem appeared, but seemingly "moved" with the PSU to the
> other 4 disks bunch (on nvidia controller) - more precisely, only
> 2 of them (array is still operational).
Hmmm..
> So it seems that there is definitely something with the "old" PSU.
>
> Also, I tried to mount the failed drives, without success.
>
> Thought I let you know.
> Now I will try with the only one, "new" PSU to see what happens...
Yeah, please keep us posted. Thanks.
--
tejun
next prev parent reply other threads:[~2008-02-14 23:32 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 [this message]
2008-02-21 21:45 ` Gabor FUNK
2008-02-22 2:03 ` Tejun Heo
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=47B4CF71.5070408@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).