Exabyte 8500C on SS1000

Exabyte 8500C on SS1000

Post by Anne Doare Thom » Sun, 16 Oct 1994 00:02:37



An exabyte 8500C is connected to our Sparc Server 1000 (Solaris 2.3).
Sometimes, when reading a file with a large amount of data, a timeout occurs
and an EOT is found. The message in /var/adm/messages is :


     Connected command timeout for Target 4.0

     SCSI transport failed: reason 'timeout': giving u

Any ideas ?

Thanks in advance.

------------------------------------------------------------
Anne Thomas Doare                     IFREMER/Centre de Brest          
                                            DITI/RIC
tel:98-22-45-68                             B.P 70
fax:98-22-45-46                         29280  PLOUZANE
                                            FRANCE


------------------------------------------------------------

 
 
 

Exabyte 8500C on SS1000

Post by ado.. » Sun, 16 Oct 1994 03:02:00


An exabyte 8500C is connected to our Sparc Server 1000 (Solaris 2.3).
Sometimes, when reading a file with a large amount of data, a timeout occurs
and an EOT is found. The message in /var/adm/messages is :


     Connected command timeout for Target 4.0

     SCSI transport failed: reason 'timeout': giving u

Any ideas ?

Thanks in advance.

------------------------------------------------------------
Anne Thomas Doare                     IFREMER/Centre de Brest          
                                            DITI/RIC
tel:98-22-45-68                             B.P 70
fax:98-22-45-46                         29280  PLOUZANE
                                            FRANCE


------------------------------------------------------------

 
 
 

Exabyte 8500C on SS1000

Post by Hans Werner Stru » Tue, 18 Oct 1994 22:43:35


I wonder it works at all, since usually the Exabyte 8500C requires a patch
in /kernel/drv/st : replace string EXB-8500 by EXB8500C (no hyphen).

--


 Drittes Physikalisches Institut,  Univ. Goettingen

 
 
 

1. Exabyte 8500C woes in SOlaris 2.3

I have an Exabyte 8500C that works fine when attached to a SunOS 4.1
machine. When I attach it to a Solaris 2.3 machine, I cannot read a tape I
could previously read with the same drive on the 4.1 machine (the tape must
be in a compressed format).

Does one have to do anything special to get Solaris tape drivers to read
8500C tapes properly? It seems (from <sys/mtio.h>) that Solaris knows only
the 8200 and 8500 by default, so I would understand that Solaris, by default,
would not know how to specify that one is writing in compressed mode.

In SunOS 4.1, one modified the /usr/sys/scsi/targets/st_conf.c file to
describe tape driver characteristics. In Solaris, one modifies
/kernel/drv/st.conf. I tried to specify the 8500C characteristics using the
st_conf.h 8500C entry as a guide. These are the values I have:

vendor string = "EXABYTE EXB8500C"
flags         = ST_VARIABLE | ST_BSF | ST_BSR | ST_LONG_ERASE
density codes= 0x14, 0x15, 0x90, 0x8C

The Solaris st.conf entry requires a type value (from mtio.h), and I don't
know whether to specify MT_ISEXB8500 or MT_IS8MM for the 8500C.

When I modified the st.conf file and rebooted, I could read low and hi
density tapes under Solaris, but not compressed ones.

Has anyone else had to get an 8500C working under Solaris? How was it done?
Does it make a difference to reading if the tape is accessed via the
different device names that specifify the densities (e.g. /dev/rmt/0ln,
0lbn, 0hn, 0hbn, 0cn, 0cbn)? My understanding is that is does not, and the
drive itself overides the ``requested'' density with that of the actual data
on the tape.

Wondering,
Ray Blaak

2. Wanted: SYSV tty-input-characters-waiting test

3. Here is a fix for Exabyte 8500c problem

4. PnP and NIC's

5. Exabyte 8500C, Solaris 2.6 and dd

6. setenv variable in sh script

7. Exabyte 8500C

8. 'Table is full' messges on console

9. Exabyte 8500C and Solaris 2.x

10. exabyte 8500c woes - FIXED!

11. Exabyte 8500c unusable with Solaris 2.3

12. Exabyte 8500c errors

13. Exabyte 8500C on Solaris 2.2?