As Matthew Jacob wrote ...
>
> > Another interesting cause for problems is duff powersupplies. As the
> > proverb goes "every machine is as good as it's PSU". E.g. I just struggeled
> > with a DLT tape unit that inexplicable reset itself. After examining the
> > 5Volts rail with a scope I found g
:>treatment, in roughly this order:
:>
:>3a) Complete check of all cables and the seating of connectors.
:>
:>3b) Examination of the drive(s) in question for any cooling or
:>mounting deficiencies. Depending on the SCSI errors in question,
:>I might even investigate
On Mon, 6 Dec 1999, Leif Neland wrote:
>
> >
> > If it already hasn't been done, we should capture the procedure that
> > Jordan posted, added to by Matt and maybe post it to the troubleshooting
> > part of the guide(s).
> >
> >
> > Unlike some of us who've been fooling with computers since
>
> If it already hasn't been done, we should capture the procedure that
> Jordan posted, added to by Matt and maybe post it to the troubleshooting
> part of the guide(s).
>
>
> Unlike some of us who've been fooling with computers since pre-1985, this
> standard operating procedure may not be
In message <[EMAIL PROTECTED]>,
Kelly Yancey <[EMAIL PROTECTED]> wrote:
>>
>>3b) Examination of the drive(s) in question for any cooling or
>>mounting deficiencies. Depending on the SCSI errors in question,
>>I might even investigate firmware updates for the drive(s).
>>
> Another interesting cause for problems is duff powersupplies. As the
> proverb goes "every machine is as good as it's PSU". E.g. I just struggeled
> with a DLT tape unit that inexplicable reset itself. After examining the
> 5Volts rail with a scope I found glitches on it whenever the drive did
As Kelly Yancey wrote ...
> >
> >3b) Examination of the drive(s) in question for any cooling or
> >mounting deficiencies. Depending on the SCSI errors in question,
> >I might even investigate firmware updates for the drive(s).
> >
>
> I actually used to get these *exact*
> >1. It's quite possible that the drive and/or the cabling in this
> > system has been defective all along.
>
> I suspect not, based upon the history.
>
> I think that the drive and/or controler has just developed this sickness
> within the past 24 hours.
>
> >2. It's equally possible that
In message <[EMAIL PROTECTED]>,
"Jordan K. Hubbard" <[EMAIL PROTECTED]> wrote:
>> "... even though I used it on Linux for several months."
>>
>> I read that as meaning "the drive worked despite the fact that it was on
>> Linux".
>
>Well, just to inject a note of reality into this discussion:
>
In message <[EMAIL PROTECTED]>,
Bill Fumerola <[EMAIL PROTECTED]> wrote:
>On Sun, 5 Dec 1999, Ronald F. Guilmette wrote:
>
>> The controller is an AHA-2940U (not wide). The da0 disk is a Quantum
>> Viking 4.5GB SCSI. I have never had any problem with this drive before,
>> even though I used it
> 3. Any system I saw spitting out errors like this would get the following
>treatment, in roughly this order:
>
>3a) Complete check of all cables and the seating of connectors.
>
>3b) Examination of the drive(s) in question for any cooling or
>mounting deficiencies. Dependi
>
>3b) Examination of the drive(s) in question for any cooling or
>mounting deficiencies. Depending on the SCSI errors in question,
>I might even investigate firmware updates for the drive(s).
>
I actually used to get these *exact* errors a couple of years ago on
various
> "... even though I used it on Linux for several months."
>
> I read that as meaning "the drive worked despite the fact that it was on
> Linux".
Well, just to inject a note of reality into this discussion:
1. It's quite possible that the drive and/or the cabling in this
system has been defe
On Sun, 5 Dec 1999, Bill Fumerola wrote:
> On Sun, 5 Dec 1999, Ronald F. Guilmette wrote:
>
> > The controller is an AHA-2940U (not wide). The da0 disk is a Quantum
> > Viking 4.5GB SCSI. I have never had any problem with this drive before,
> > even though I used it on Linux for several mo
On Sun, 5 Dec 1999, Ronald F. Guilmette wrote:
> The controller is an AHA-2940U (not wide). The da0 disk is a Quantum
> Viking 4.5GB SCSI. I have never had any problem with this drive before,
> even though I used it on Linux for several months.
>
> This (FreeBSD) system has been running just f
My apologies for posting this digression from the usual weighty
matters that are discussed here on -hackers, but I'm really in
a tizzy about this.
Going through my waiting mail this morning (on my personal desktop
system named `segfault.monkeys.com') I found the following message
from the nightl
16 matches
Mail list logo
