From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Roger J. Allen" Date: Tue, 01 Sep 1998 01:47:09 +0000 Subject: scsi tape access during install Message-Id: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ultralinux@vger.kernel.org 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 ptr00000017efd218 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