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 there should be
> *nothing* that you can do in software that would cause hardware to
> die, occasional oddball stories about HD drivers notwithstanding ;)
Just as a note, the hardware didn't die :-) I'm quite aware of software
_very_ rarely being in the position of killing hardware - the drives were
just set by the controller as failed, but I had been running them for
weeks and after I reset the controller configuration data, I formatted
them and they worked fine. They are running fine, ATM. It's just the ..
flakiness.
>
> I doubt that termination is your problem - let's look at this
> logically, shall we? Did you change anything right before the problem
> surfaced? No? The fickle finger of fate points directly at hardware
> ;)
Nothing changed, you're quite right. I suspected hardware from the start,
but since it's something that's always a bother to go and change, I was
reluctant to have that set in stone. I have since rearranged the drives in
the lower bays (the first and second bays on the Astor II), flashed the
backplane / server board, and have it testing. It's hard to say who's to
blame, but if the problem recurrs, I'll say it's the backplane. The drives
don't seem to be flaky at all.
Performance isn't the best, but okay for RAID1.
Cheers,
--
_/\ Christian Reis is sometimes [EMAIL PROTECTED]
\/~ suicide architect | free software advocate | mountain biker
