From: "Roger J. Allen" <rja@sispro.sis.rpslmc.edu>
To: ultralinux@vger.kernel.org
Subject: scsi tape access during install
Date: Tue, 01 Sep 1998 01:47:09 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-90462589332083@msgid-missing> (raw)
Here are the error messages that show up on the Alt-F4 virtual screen
when I try to cpio from a scsi tape drive. It is on scsi id 4, and I
used:
mknod /tmp/st0 c 9 0
to create the device. I had to do a STOP-A to get it to stop sending
error messages. I was fast enough to catch the first error messages. I
wrote these down and am typing them from my scribbles, so there may be a
few spaces missing or extra.
<6>esp0: Disabling DISCONNECT for target 4 lun 0
<4>esp0: data bad parity detected.
<4>esp0: data bad parity detected.
<4>esp0: yiee, bytes_sent < 0!
<4>esp0: csz=0 fifocount=0 ecount=0
<4>esp0: use_sg=0 ptr\000000017efd218 this_residual=0
<4>esp0: got status only, esp0: bad parity somewhere mout=5
<4>esp0: still in msgout, parity error assumed
<4>esp0: Gross error sregG
And then it starts repeating with the double "data bad parity detected."
with the ptr value different each time. The LED's on the tape drive are
on as if it is being accessed.
This time, I tried a different tape density, but the same thing
happened. I tried it after the swap space was created, when it asked
where the RedHat directory was on the hard disk.
I hope this helps.
Roger J. Allen Rush-Presbyterian-St. Luke's Medical Center
System Administrator Chicago, IL USA
Surgical Information Systems Voice: (312)-942-4825
Internet: rja@sis.rpslmc.edu FAX: (312)-733-6921
reply other threads:[~1998-09-01 1:47 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=marc-linux-ultrasparc-90462589332083@msgid-missing \
--to=rja@sispro.sis.rpslmc.edu \
--cc=ultralinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.