linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tim Moore <linux-raid@nsr500.net>
To: linux-raid@vger.kernel.org
Cc: Gordon Henderson <gordon@drogon.net>
Subject: Re: [PATCH md 2 of 4] Fix raid6 problem
Date: Sat, 05 Feb 2005 19:38:31 -0800	[thread overview]
Message-ID: <42059137.4040109@nsr500.net> (raw)
In-Reply-To: <Pine.LNX.4.56.0502041031470.29133@lion.drogon.net>


Gordon Henderson wrote:
 > ...
> It seemed more stable with just one PCI card in, so I have a 4-port card
> on order as a last ditch attempt to make it work - I did try re-flashing
> the BIOS on one board, (I have 2) as it seemed to be about a year old and
> there are several updates on the Tyan web-site, however that resulted in
> wiping out the BIOS - it seemed to be going just fine, then it went beep
> and was silent forever more )-: Anyone in the SW have a flash
> programmer/copier handy???

I had this happen when flashing 2.02b.  Reboot was an endless cycle of 15 
short beeps.  Turns out the 2.02 memory configuration is so different than 
the 1.?? it couldn't boot.  Swapped the 1GB PC2700 (ATP) memory with 512MB 
modules, cleared CMOS, rebooted, reconfigured the BIOS, shut down, replaced 
the 1GB production modules, rebooted.  Perfect ever since.

The sil 3114 onboard w software RAID5 has been flawless (RH 7.3 base, 
2.4.29 kernel, SCSI/sil driver).  The only other problem was that two of 
the 4 short black SATA cables that came with the board were intermittent. 
Once replaced all is well.

I'd give 2.02 beta Bios a run and make sure PCI-X slot configuration is 
matched to the controller card.  2.02 BIOS is very different than earlier 
versions.

Iwill quad opteron boards and are quite happy to never go back to intel 
ever again.

t.
-- 


  parent reply	other threads:[~2005-02-06  3:38 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200502031145.j13Bj1fl016074@terminus.zytor.com>
2005-02-03 16:39 ` [PATCH md 2 of 4] Fix raid6 problem H. Peter Anvin
2005-02-03 16:59   ` Lars Marowsky-Bree
2005-02-03 17:06     ` H. Peter Anvin
2005-02-03 17:43   ` Guy
2005-02-03 18:07     ` H. Peter Anvin
2005-02-03 19:36       ` Gordon Henderson
2005-02-04  9:04         ` Andrew Walrond
2005-02-04 11:19           ` Gordon Henderson
2005-02-04 18:31             ` Mike Hardy
2005-02-13 21:05               ` Mark Hahn
2005-02-13 21:19                 ` Gordon Henderson
2005-02-14  4:56                   ` Tim Moore
2005-02-14  9:42                     ` Andrew Walrond
2005-02-13 22:58                 ` Mike Hardy
2005-02-13 23:14                   ` Richard Scobie
2005-02-06  3:38             ` Tim Moore [this message]
2005-02-14  4:49             ` Tim Moore
2005-02-14  8:09               ` Gordon Henderson
2005-02-14  4:27         ` Tim Moore
2005-02-14  8:05           ` Gordon Henderson
2004-11-03 23:56 A. James Lewis
2004-12-09  0:21 ` H. Peter Anvin
2004-12-09  0:35   ` Jim Paris
     [not found] ` <200412090021.iB90L4MK014200@terminus.zytor.com>
2005-01-23 14:02   ` A. James Lewis
2005-01-23 14:42     ` Kevin P. Fleming
2005-02-03  2:12     ` H. Peter Anvin
2005-02-03 17:13       ` Andy Smith
  -- strict thread matches above, loose matches on Subject: below --
2004-11-02  3:37 [PATCH md 0 of 4] Introduction NeilBrown
2004-11-02  3:37 ` [PATCH md 2 of 4] Fix raid6 problem NeilBrown

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=42059137.4040109@nsr500.net \
    --to=linux-raid@nsr500.net \
    --cc=gordon@drogon.net \
    --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).