From: Ishikawa <ishikawa@yk.rim.or.jp>
To: linux-scsi@vger.kernel.org, Kai.Makisara@metla.fi,
dc390@garloff.de, garloff@suse
Subject: Re: Ungraceful handling of scsi tape drive error condition
Date: Fri, 26 Jul 2002 11:52:56 +0900 [thread overview]
Message-ID: <3D40B988.6D24ACF@yk.rim.or.jp> (raw)
In-Reply-To: m17Vcsl-000HcIC@standard.erephon
Hi,
My own followup:
After a few e-mail exchanges with Kai Makisara,
- I tried cleaning tape,
- swapped SCSI card, etc..
I still saw strange errors.
The drive seemed to emit UNIT_ATTENTION
at unexpected times and the driver thought
the tape was gone and stopped writing.
Then I found out that the power supply
of the external SCSI enclosure that houses the
DDS2 tape drive has become unreliable.
Once I put the drive into another enclosure (with
presumably a good power supply), I could
archive files successfully.
Obviously, the drive
behaved erratically due to the dying power
supply( the power was there, but presumably
the voltage was fluctuating. ),
and even the best intention of the
drivers could not cope with such
dire situation.
The transient nature of the bad power supply
made it difficult to catch the real cause of
the problem initially.
(SCSI cable and terminator were suspected
but they are good after all.)
Honestly speaking this is the first time a power
supply of an external SCSI enclosure went bad
for me (I have used SCSI devices more than 15 years)
and so somehow I suspected power-supply very little
initially.
So maybe we should ask if power-supply
is flakey when we see SCSI errors on top of the
usual suspects (cable, terminator, etc..).
Thank you all for helpful tips.
Chiaki
prev parent reply other threads:[~2002-07-26 2:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-19 18:53 Ungraceful handling of scsi tape drive error condition ishikawa
2002-07-26 2:52 ` Ishikawa [this message]
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=3D40B988.6D24ACF@yk.rim.or.jp \
--to=ishikawa@yk.rim.or.jp \
--cc=Kai.Makisara@metla.fi \
--cc=dc390@garloff.de \
--cc=garloff@suse \
--cc=linux-scsi@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