On Fri, 7 Apr 2000, Christian Robottom Reis wrote:
> Well, I erased the config data, reflashed everything (and included a flash
> update for the AstorII chassis backplane we were using) and am now in the
> process of bringing back my backup from tape. This was quite inconclusive,
> and I suspect
On Sat, 8 Apr 2000, Ed Carp wrote:
> There are very few problems with software that can cause hardware to
> die. The *only* time I've heard of this happening is if you get the
> sync rate wrong on your monitor. It's an axiom of programming that is
> occasionally not understood by non-geeks that
Christian Robottom Reis ([EMAIL PROTECTED]) writes:
> Well, I erased the config data, reflashed everything (and included a flash
> update for the AstorII chassis backplane we were using) and am now in the
> process of bringing back my backup from tape. This was quite inconclusive,
> and I suspect
I have to agree with Leonard (big surprise)... we have had two large
server machines in continuous service for a while with the Mylex RAID
controllers, busy 24 hours a day, and we have never seen anything that
approaches the problems you are describing. My bet is also hardware.
-- Mike
On Fri,
Date: Fri, 7 Apr 2000 19:11:04 -0300 (EST)
From: Christian Robottom Reis <[EMAIL PROTECTED]>
Well, I erased the config data, reflashed everything (and included a flash
update for the AstorII chassis backplane we were using) and am now in the
process of bringing back my backup fr
Date: Fri, 7 Apr 2000 12:27:39 -0300 (EST)
From: Christian Robottom Reis <[EMAIL PROTECTED]>
I'm trying to reflash the controller roms ATM and wondering what went
wrong. I've been sitting here for a couple of hours with no sleep. :-) If
this works, I'm starting to believe the firmware h
On Fri, 7 Apr 2000, Ed Carp wrote:
> > Does this smell the most of hardware or software? Can the nfsv3 patches be
> > so evil? Is driver 2.2.5 silently corrupting board firmware?
>
> Sounds like hardware problems. What happened when you tried to
> reflash the firmware?
Well, I erased the confi
Christian Robottom Reis ([EMAIL PROTECTED]) writes:
> The RAID has just gone dead this morning. The system had been idle for a
> while, though it was rebooted twice about an hour before syslogd died and
> nothing worked anymore.
> Reformatting the Dead drive responds with a "Notice - Background
I'm running the Mylex driver 2.2.5 on a two-disk RAID1 production box
(racked here on an ISP). I've changed the firmware to 4.07-07 listed on
the page for the driver, and stress-tested it for a couple of days before
shipping.
The setup was a bit flaky to start off with, but the firmware switch a
Home-free? Not really. At this point I should be able to load the
os and
use fdisk to partition my new raid. Based on the docs I've been
able to
find, I should be able to address the array at /dev/rd/c0d0. It
doesn't
answer up there, or at c1, c2, e
From: [EMAIL PROTECTED]
Date: Wed, 17 Feb 1999 08:29:40 -0500
Hi folks,
This could make a pretty good howto if it has a happy ending.
I got a mylex dac960 card to drive an external rack with 5-9gb scsi
drives. RH5.2 (2.0.36) already is installed, on an ide hard drive.
Col
Hi folks,
This could make a pretty good howto if it has a happy ending.
I got a mylex dac960 card to drive an external rack with 5-9gb scsi
drives. RH5.2 (2.0.36) already is installed, on an ide hard drive.
Collected the driver and utilities from dandelion, made a new kernel and
swapped out lil
12 matches
Mail list logo
