Hi Paul,
I tried to read the tape without being recognized. I wrote a tar-archive
to it under Solaris 2.5.1 DU11 (booted from harddisk).
When trying to read it after the CDROM boot ( tar tvf /dev/rmt/0)
I received the error message:
st6: fixed record length (512 byte blocks) I/O
WARNING:/pci..blabla
...
Vendor: SONY
Incorrect Length Indicator Set
The output from "mtinfo /dev/rmt/0" was:
mtinfo V2.1 26-Mar-97
Type : 0x2d
Status : 0
Error : 0
Residual Count : 0
FileNo curr. Pos. : 0
BlokNo curr. Pos. : 0
Flags : 0x5
Opt. Blocking Factor: 126
Name :Vendor 'SONY ' Product 'SDT-7000 '
VID :
Type :0x2d
BlockSize :512
Options :0x2478
ST_BSF (0x8)
ST_BSR (0x10)
ST_LONG_ERASE (0x20)
ST_AUTODEN_OVERRIDE (0x40)
ST_UNLOADABLE (0x400)
ST_DYNAMIC (0x2000)
Max read Retries :1000
Max. write Retries :1000
Densities :0x00,0x00,0x00,0x00
Default density :0 (0)
Speeds :0,0,0,0
/kernel/drv/st.conf entry:
tape-config-list =
"","Vendor 'SONY ' Product 'SDT-7000 '","tape-data";
tape-data = 1,0x2d,512,0x2478,4,0x00,0x00,0x00,0x00,0;
Density bytes used by device entry:
/dev/rmt/0 major=129 minor=130 density=0 density byte=0x00
/dev/rmt/0l major=129 minor=130 density=0 density byte=0x00
/dev/rmt/0m major=129 minor=138 density=1 density byte=0x00
/dev/rmt/0h major=129 minor=146 density=2 density byte=0x00
/dev/rmt/0c major=129 minor=154 density=3 density byte=0x00
/dev/rmt/0u major=129 minor=154 density=3 density byte=0x00
To be honest I can't interpret the tape-data-line above and I
even couldn't find the SDT-7000 line in /kernel/drv/st.conf.
From /tmp/st.conf:
------------------
tape-config-list=
"EXABYTE EXB-4200", "Exabyte 4mm Helical Scan","DAT",
"HP HP35470A", "HP 35470A 4mm DAT", "HP70",
"HP HP35480A", "HP 35480A 4mm DAT", "DAT",
"HP C1533A", "HP JetStore 6000 C1533","DAT",
"SONY SDT-5000", "SONY 4mm DAT", "DAT",
"SONY SDT-5200", "SONY 4mm DAT", "DAT",
"SONY SDT-7000", "Sony DDS-2 4mm DAT", "DAT2",
"TANDBERG 4100", "Tandberg 4100 QIC", "TANDBERG_4100_QIC",
"TANDBERG 4200", "Tandberg 4200 QIC", "TANDBERG_4200_QIC",
"WANGTEK 5525ES SCSI", "Wangtek 525MB QIC", "WT_5525ES_QIC";
"ARCHIVE Python 28388", "Archive/Conner CTDX004 4mm DAT", "Conner2-DAT",
"DEC DLT2", "DEC 15/30GB DLT","DLT",
"HP C1537A", "HP DDS3 DAT", "HPdds3",
"TANDBERGMLR1", "Tandberg MLR1 QIC", "TANDBERG_MLR1",
DAT = 1,0x34,0,0x0439,1,0x00,0;
DAT2 = 1,0x34,0,0x1439,1,0x00,0;
HP70 = 1,0x34,0,0x1679,1,0x0,0;
From /kernel/drv/st.conf:
-------------------------
tape-config-list=
"EXABYTE EXB-4200", "Exabyte 4mm Helical Scan","DAT",
"HP HP35470A", "HP 35470A 4mm DAT", "HP70",
"HP HP35480A", "HP 35480A 4mm DAT", "DAT",
"HP C1533A", "HP JetStore 6000 C1533","DAT",
"SONY SDT-5000", "SONY 4mm DAT", "DAT",
"SONY SDT-5200", "SONY 4mm DAT", "DAT",
"TANDBERG 4100", "Tandberg 4100 QIC", "TANDBERG_4100_QIC",
"TANDBERG 4200", "Tandberg 4200 QIC", "TANDBERG_4200_QIC",
"WANGTEK 5525ES SCSI", "Wangtek 525MB QIC", "WT_5525ES_QIC";
DAT = 1,0x34,0,0x0439,1,0x00,0;
HP70 = 1,0x34,0,0x1679,1,0x0,0;
Stefan
=========================================================================================
> I wanted to ask a similar question (s/SDT-7000/DLT7000) recently,
> but then I tried it before posting, and found out that although
> the drive was not correctly recognized by the CD-boot the ufsrestore
> worked. mtinfo showed type 0x12 (default), and the density codes were
> wrong, too.
> This was Solaris 2.6, under 7 there's a correct entry for the DLT 7000
> in st.conf, and there the drive is correctly identified when booting
> the CDROM.
> hm, so, either simply try to restore even though the tape is not
> recognized, or try to boot the most recent Solaris version and hope
> that it has a correct st.conf entry.
> I'm still interested why tape reading works from an unknown device,
> though. It wasn't even slower. Could anybody fill me in ?
> hth, mp.