From: Justin Rush <jrush@scout.wisc.edu>
To: linux-kernel@vger.kernel.org
Subject: ide tape drive not working
Date: Wed, 2 Jul 2003 08:29:12 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0307020825310.3426-100000@hundo.scout.wisc.edu> (raw)
Hi,
I am getting a strange error while trying to use my ide-tape drive in
kernel 2.4.20-18.9. In dmesg I see that the kernel sees the tape drive:
hdf: Seagate STT8000A, ATAPI TAPE drive
ide-tape: hdf <-> ht0: Seagate STT8000A rev 5.02
ide-tape: hdf <-> ht0: 600KBps, 14*26kB buffer, 5850kB pipeline, 80ms
tDSC, DMA
However, when I try and do a mt -f /dev/ht0 status , I get a device or
resource busy error, and the following gets spit into dmesg:
ide-tape: ht0: I/O error, pc = 34, key = 3, asc = 30, ascq = 0
ide-tape: ht0: I/O error, pc = 1, key = 3, asc = 30, ascq = 0
ide-tape: ht0: I/O error, pc = 0, key = 3, asc = 30, ascq = 0
ide-tape: ht0: drive not ready
What could be the problem here?
Thanks,
Justin
reply other threads:[~2003-07-02 13:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.LNX.4.44.0307020825310.3426-100000@hundo.scout.wisc.edu \
--to=jrush@scout.wisc.edu \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).