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:
>
>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 the linux driver simply doesn't report
> the errors but, as FreeBSD does, retries the failing operations.
> This would result in a system which appeared to work just fine,
> just more slowly at times (which would probably not even be
> noticed).
FreeBSD was also perfectly happy with this drive (and controller) for
weeks... up until last night.
>3. Any system I saw spitting out errors like this would get the following
> treatment, in roughly this order:
(I now think that my first order of business should be to start making
backup tapes as quick as I can. :-)
> 3a) Complete check of all cables and the seating of connectors.
>
> 3b) Examination of the drive(s) in question for any cooling or
^^^^^^^
The drive is mounted in a crappy external box with perfectly lousy
ventilation.
I just touched the drive and guess what... It's hot as Hades.
I think I found my answer.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
