My original question (modified after knowing what the solution is):
> We've recently purchased an EXB-10e, with an Exabyte 8500
> 8mm tape drive. It's connected to our
> SparcServer 1000 which run Solaris 2.3.
> My problem is that when I try to write to the tape drive with
> 'tar cvf /dev/rmt/1m some_file', I get the following errors on
> the console:
> Dec 23 13:02:36 pluto unix: data transfer overrun
[Cut some lines...]
> Dec 23 13:02:37 pluto unix: polled command timeout
> Dec 23 13:02:37 pluto unix: esp: State=DATA Last State=DATA_DONE
> Dec 23 13:02:37 pluto unix: esp: Latched stat=0x90<IPND,XZERO> intr=0x10<BUS> fifo 0x80
> Dec 23 13:02:37 pluto unix: esp: last msg out: IDENTIFY; last msg in: COMMAND COMPLETE
> Dec 23 13:02:37 pluto unix: esp: DMA csr=0x40040010<INTEN>
> Dec 23 13:02:37 pluto unix: esp: addr=fc00f2a0 dmacnt=d90 last=fc00ca70 last_cnt=2800
> Dec 23 13:02:37 pluto unix: esp: Cmd dump for Target 2 Lun 0:
> Dec 23 13:02:37 pluto unix: esp: cdblen=6, cdb=[ 0xa 0x1 0x0 0x0 0x14 0x0 ]
> Dec 23 13:02:38 pluto unix: esp: pkt_state=0xb<XFER,SEL,ARB> pkt_flags=0x1 pkt_statistics=0x0
> Dec 23 13:02:38 pluto unix: esp: cmd_flags=0x10c22 cmd_timeout=120
> Dec 23 13:02:38 pluto unix: WARNING: /io-unit@f,e1200000/sbi@0,0/dma@0,81000/esp@0,80000/st@2,0 (st32):
> Dec 23 13:02:38 pluto unix: SCSI transport failed: reason 'data_ovr': giving
> Dec 23 13:02:38 pluto unix: up
I got two answers which solved my problem. I had to add some
lines to the /kernel/drv/st.conf file. I'm afraid I'm not an
expert on this subject (hence my question :-) so I'm not sure
what the difference is between the two solutions suggested
below. Only that the first one allow an EXB8500c on
any SCSI ID, but the second is for SCSI ID 2.
(If anyone care to explain this better, please do.)
>From Claude Scarpelli <firstname.lastname@example.org>:
> We had the same problem here, but the fix is easy: Here is the
> modification I made on my /kernel/drv/st.conf file:
> hallucinogene$ head -20 /kernel/drv/st.conf
> # Copyright (c) 1992, by Sun Microsystems, Inc.
> #ident "@(#)st.conf 1.6 93/05/03 SMI"
> # + tape_config_list Pour Exabyte 5 Giga Compresse
> # email@example.com
> # soit : 0x14 = EXB-8200 (2 Go /dev/rmt/?l??)
> # 0x15 = EXB-8500 (5 Go /dev/rmt/?m??)
> # 0x90 = EXB-8200C (2 GoComp /dev/rmt/?h??)
> # 0x8c = EXB-8500C (5 GoComp /dev/rmt/?[cu]??)
> # La densite par defaut est la 3e (a partir de 0), soit 0x8c
> # (5Go comp)
> tape-config-list =
> "EXABYTE EXB8500C", "Exabyte 8mm EXB8500C",
> EXBT-8MC = 1,0x35,1024,0x0039,4,0x14,0x15,0x90,0x8c,3
> This will allow an EXB85000C drive at any SCSI ID. The default density
> we choose (/dev/rmt/1) is 0x8c (the third), ie 5Gb + IDRC data
>From Dave Haut <firstname.lastname@example.org>:
> Does your EXB-10e have a compression drive ?? You can tell by looking at the
> eject button on the TAPE DRIVE. If there is a "C" on it, that means that its
> a compression drive ...
> If it is a compression drive, you need to add the following to your
> /kernel/drv/st.conf file. Just verify that target='s is the SCSI address
> of your tape drive ( Judging from your output, it looks like it's 2 )
> /* Sample Entry for Exabyte EXB-8500c */
> name="st" class="scsi"
> target=2 lun=0;
> tape-config-list =
> "EXABYTE EXB8500C", "Exabyte 8mm w/compression", "EXB8500C-data";
> EXB8500C-data = 1,0x35,1024,0x0039,4,0x8c,0x15,0x90,0x14,3;
> Now do a "boot -r".
-- Harald Martens Meyer | Geomatic a.s | #_O_# Powder Email:email@example.com | PO.Box 165 Skoyen | (/ _|_ \) Snow Tel: +47 22 50 43 30 | N-0212 OSLO 2 | \/ \/ Is Tfx: +47 22 50 05 55 | NORWAY | \ / Simply the Best!
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:09:17 CDT