SUMMARY: QIC-150 Tape unit Problems

From: Joe Spanicek <joe_at_resptk.bhp.com.au>
Date: Wed, 14 Jan 1998 09:14:09 +1100

Hi,

Thanks to:
        Kraisit Vittinanon (kvittina_at_kcs.co.th)
        "Dr. Tom Blinn, 603-884-0646" <tpb_at_zk3.dec.com>

for their responses.


My Original message:

JS> I have a QIC-150 Tape unit installed on a Digital UNIX 4.0 system.
JS>
JS> '/var/adm/messages' gives it as "ARCHIVE VIPER 150 21247 -005"
JS>
JS> It's been working fine up untill now - I can read tar files from the tapes.
JS>
JS> But I get the following error when writing a tar file to it, as follows:
JS>
JS> >{joe}14: tar cvf /dev/nrmt1h QMP_PROJECT
JS> a QMP_PROJECT
JS> a QMP_PROJECT/QMP
JS> a QMP_PROJECT/QMP/DATAEXTRACT.res 11 Blocks
JS> tar: write : I/O error
JS> tar: Tape write error
JS>
JS> Would anybody know what could be causing the problem ??.
JS>
JS> I am confused in that I can read tapes but not write to it.
JS>
JS> Yes - The write-protect-tab is set correctly.


From Kraisit Vittinanon

     From your error message, it seem you have got hardware error. I
sugguest you to contact Digital System Support for problem diagnostic and
new hardware replacement in case of hardware error.

From Dr. Thomas P. Blinn

I don't have a clue what's wrong, other then the obvious possibilities that
you have bad media or a dirty drive. But I do know that even if I had some
experience with that particular drive, unless you use both uerf and dia to
get the error frame reported (they can differ in what they understand, dia
is the replacement for uerf), and use the -o full command line switch to get
the full details, no one will be able to figure it out.


I had a look at the 'dia' to see what the error was. It looks like the QIC-150
tape unit is having a hardware problem with the write-protect sensor. Am I right
about this ??

I tried the tape several times and sometimes it works and at other times it does
not work. So I'll be replacing it with a spare unit.

Thanks

Joe Spanicek



Here is the 'dia -R -o full' output:

------------------8<-------------------------8<-------------------------------

DECevent V2.1A


******************************** ENTRY 1 ********************************


Logging OS 2. Digital UNIX
System Architecture 2. Alpha
Event sequence number 17.
Timestamp of occurrence 13-JAN-1998 16:27:13
Host name goofy

System type register x0000000D AlphaStation 400
Number of CPUs (mpnum) x00000001
CPU logging event (mperr) x00000000

Event validity 1. O/S claims event is valid
Event severity 3. High Priority
Entry type 199. CAM SCSI Event Type


------- Unit Info -------
Bus Number 0.
Unit Number x0030 Target = 6.
                                     LUN = 0.
------- CAM Data -------
Class x01 Tape
Subsystem x01 Tape
Number of Packets 9.

------ Packet Type ------ 258. Module Name String

Routine Name ctape_density_set

------ Packet Type ------ 260. Hardware Error String

Error Type Hard Error Detected

------ Packet Type ------ 257. Device Name String

Device Name ARCHIVE VIPER 150 21247^XVIPER 150

------ Packet Type ------ 256. Generic String

                                     Active CCB at time of error

------ Packet Type ------ 256. Generic String

                                     CCB request completed with an error

------ Packet Type ------ 1. SCSI I/O Request CCB(CCB_SCSIIO)
Packet Revision 76.

CCB Address xFFFFFC0002821580
CCB Length x00C0
XPT Function Code x01 Execute requested SCSI I/O
Cam Status xC4 CCB Request Completed WITH Error
                                     SIM Queue Frozen with this Error
                                     Autosense Data Valid for Target
Path ID 0.
Target ID 6.
Target LUN 0.
Cam Flags x00000080 Data Direction (10: DATA OUT)
*pdrv_ptr xFFFFFC0002821228
*next_ccb x0000000000000000
*req_map x0000000000000000
void (*cam_cbfcnp)() xFFFFFC0000421C98
*data_ptr xFFFFFC0005C405D0
Data Transfer Length 12.
*sense_ptr xFFFFFC0002821250
Auotsense Byte Length 64.
CDB Length 6.
Scatter/Gather Entry Cnt 0.
SCSI Status x02 Check Condition
Autosense Residue Length x32
Transfer Residue Length x00000000
(CDB) Command & Data Buf

          15--<-12 11--<-08 07--<-04 03--<-00 :Byte Order
 0000: 00000000 0000000C 00000015 * ............*

Timeout Value x00000005
*msg_ptr x0000000000000000
Message Length 0.
Vendor Unique Flags x0000
Tag Queue Actions x00

------ Packet Type ------ 256. Generic String

                                     Error, exception, or abnormal condition

------ Packet Type ------ 256. Generic String

                                     ILLEGAL REQUEST - Illegal request or CDB
                                     parameter

------ Packet Type ------ 768. SCSI Sense Data
Packet Revision 0.

Error Code x70 Current Error
Segment # x00
Information Byte 3 x00
            Byte 2 x00
            Byte 1 x00
            Byte 0 x00
Sense Key x05 Illegal Request
Additional Sense Length x06
CMD Specific Info Byte 3 x00
                  Byte 2 x00
                  Byte 1 x00
                  Byte 0 x00
ASC & ASCQ x0000 ASC = x0000
                                     ASCQ = x0000
                                     No Additional Sense Information
FRU Code x00
Sense Key Specific Byte 0 x00 Sense Key Data NOT Valid
                   Byte 1 x00
                   Byte 2 x00

Addition Sense Data Size Allocated by Driver

Count of valid bytes: 46.


          15--<-12 11--<-08 07--<-04 03--<-00 :Byte Order
 0000: 00000000 00000000 00000000 00000000 *................*
 0010: 00000000 00000000 00000000 00000000 *................*
 0020: 00000000 00000000 00000000 00000000 *................*
------------------8<-------------------------8<-------------------------------
Received on Tue Jan 13 1998 - 23:14:21 NZDT

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:37 NZDT