From: Jon Hardcastle <jd_hardcastle@yahoo.com>
To: John Robinson <john.robinson@anonymous.org.uk>
Cc: linux-raid@vger.kernel.org
Subject: Re: Raid 5 - not clean and then a failure.
Date: Tue, 25 Aug 2009 07:11:40 -0700 (PDT) [thread overview]
Message-ID: <936259.53228.qm@web51302.mail.re2.yahoo.com> (raw)
In-Reply-To: <4A93EB59.3060408@anonymous.org.uk>
--- On Tue, 25/8/09, John Robinson <john.robinson@anonymous.org.uk> wrote:
> From: John Robinson <john.robinson@anonymous.org.uk>
> Subject: Re: Raid 5 - not clean and then a failure.
> To: Jon@eHardcastle.com
> Cc: linux-raid@vger.kernel.org
> Date: Tuesday, 25 August, 2009, 2:47 PM
> On 25/08/2009 09:40, Jon Hardcastle
> wrote:
> > --- On Tue, 25/8/09, Robin Hill <robin@robinhill.me.uk>
> wrote:
> >> On Tue Aug 25, 2009 at 12:54:49AM -0700, Jon
> Hardcastle wrote:
> >>> I have been having some problems with my
> arrays that I think i have
> >>> nailed down to a pci controller (well I say
> that - it is always the
> >>> drives connected to *a* controller but I have
> tried 2!) anyway the
> >>> latest saga is i was trying some new kernel
> options last night - which
> >>> didn't work.
> >>
> >> Did they have the same chipset? I had
> problems with PCI controllers on
> >> one of my systems, which turned out to be some
> sort of conflict between
> >> the onboard chipset and the chipset on the
> controllers. I found a PCI
> >> card with a different chipset and have had no
> issues since.
> >
> > They are/were cheapy little via ones
>
> That's your problem right there. Well, in my experience and
> therefore opinion, VIA stuff is all too often junk, or at
> least iffy enough never to be trusted with anything
> professional or important.
>
> [...]
> > I have a pci express controller but my kernel doesnt
> (yet!) support pci express.
>
> *How old* is your kernel?
>
> Cheers,
>
> John.
> --
This is what I am finding.. i plugged in a second controller and it seems to have nagered the first one such that I am getting 'port to slow to respond' from the drives connected now.
I am looking at my options. Once i get PCI-Express working I have options. I am also looking at port multipliers.
(ps support is IN my kernel code.. I just ran down a trimmed kernel. Didn't need PCI express so i didn't enable it. now i do :) )
-----------------------
N: Jon Hardcastle
E: Jon@eHardcastle.com
'Do not worry about tomorrow, for tomorrow will bring worries of its own.'
-----------------------
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-08-25 14:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-25 7:54 Raid 5 - not clean and then a failure Jon Hardcastle
2009-08-25 8:16 ` Robin Hill
2009-08-25 8:40 ` Jon Hardcastle
2009-08-25 9:34 ` Robin Hill
2009-08-25 13:47 ` John Robinson
2009-08-25 14:11 ` Jon Hardcastle [this message]
2009-08-26 11:02 ` Jon Hardcastle
2009-08-26 11:18 ` Goswin von Brederlow
2009-08-26 11:29 ` Jon Hardcastle
2009-08-26 12:47 ` John Robinson
2009-08-26 20:34 ` Goswin von Brederlow
2009-08-26 14:14 ` Ryan Wagoner
2009-08-26 14:19 ` Jon Hardcastle
2009-08-26 14:50 ` Robin Hill
2009-08-26 14:33 ` Robin Hill
2009-08-26 20:35 ` Goswin von Brederlow
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=936259.53228.qm@web51302.mail.re2.yahoo.com \
--to=jd_hardcastle@yahoo.com \
--cc=Jon@eHardcastle.com \
--cc=john.robinson@anonymous.org.uk \
--cc=linux-raid@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).