From: Josh Litherland <josh@temp123.org>
To: Neil Brown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Superblock checksum problems
Date: Wed, 06 Sep 2006 09:26:13 -0400 [thread overview]
Message-ID: <1157549173.2424.5.camel@localhost> (raw)
In-Reply-To: <1157411506.6946.1.camel@localhost>
Stranger than we dreamt it...
I got a new, identical card, the Syba 4-port PCI card and had EXACTLY
the same problems. Tried with all new cables, exact same problems.
Moved the card into each PCI slot in the system. Same problems.
I put the drives and cables into a different system onto an onboard SATA
controller, and they work fine, so drives and cables are "known good".
It seems unlikely that two identical cards would be broken in exactly
the same way, so I have to revert back to my previous suspicion: bad
interaction between the card's firmware and the driver.
This evening, I will try out the weird card in the new system's
motherboard, to see if it's something in the old mobo that doesn't like
this card.
I will hold on to this card at least until weekend for testing, and
longer if anyone thinks they might have a patch for me to test.
My thanks to everyone who's still paying attention to this thread. =)
--
Josh Litherland (josh@temp123.org)
next prev parent reply other threads:[~2006-09-06 13:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-02 22:36 Superblock checksum problems Josh Litherland
2006-09-04 5:12 ` Neil Brown
2006-09-04 16:00 ` Josh Litherland
2006-09-04 20:55 ` Josh Litherland
2006-09-04 21:13 ` Josh Litherland
2006-09-04 21:35 ` Neil Brown
2006-09-04 21:46 ` Josh Litherland
2006-09-04 23:11 ` Josh Litherland
2006-09-04 23:17 ` Neil Brown
2006-09-04 23:43 ` Henrik Holst
2006-09-06 7:07 ` Mario 'BitKoenig' Holbe
2006-09-06 13:26 ` Josh Litherland [this message]
2006-09-07 20:40 ` Josh Litherland
2006-09-04 21:54 ` Josh Litherland
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=1157549173.2424.5.camel@localhost \
--to=josh@temp123.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).