04-03-2002
Hello brv,
I have a little dilemma with your problem discription.
You perform a stop-a, and then on the OBP you execude the probe-scsi-all command ? I canīt understand the different between the two situations.
However, if you look inside the /dev/rmt/ directory you can see the tape ?
If not ? First of all try this :
drvconfig
tapes
Errors appear ?
If the tape is now on this system dir, try to write something on an empty tape.
regards joerg
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
What are the options on upgrading disk space in an Ultra 10 workstation? Sun states they are EIDE drives, are they standard or Sun specific?
Thanks (1 Reply)
Discussion started by: 98_1LE
1 Replies
2. UNIX for Advanced & Expert Users
I am trying to configure DAT Tape drive on SUN E220 system but I don't have SUN keyboard. I am using a tty terminal k/b.
What are my alternavtives?
Is there any way to send interupts to the system on OK prompt using tty kb for probe SCSI.
Thanks in advance. (2 Replies)
Discussion started by: s_aamir
2 Replies
3. Solaris
Hello. Maybe a Solaris guru can help me out.
I would like to connect a parallel QIC tape drive to an Ultra 5 to write backups.
Is this possible? If I remember my Unix edu years ago, there is a way to tell the system that there is blocking device on the parallel port.
Thanks for your... (1 Reply)
Discussion started by: Plain Person
1 Replies
4. UNIX for Dummies Questions & Answers
Hey guys,
I'm trying to mount a SUN DDS-2 tape drive on a SUN Ultra 80 machine running Solaris 9. I had the SCSI drive connected at time of install, I'm very new to Solaris so I don't know if Solaris would detect the drive like that and install some form of device driver. But, what im posting... (2 Replies)
Discussion started by: kingdbag
2 Replies
5. Solaris
Hi everyone.
Im new to Sun Solaris or the Unix environment. My only background is the DOS command in windows and a little bit of c++ programming. I always worked with troubleshooting hardware and software issues with windows.
Now that I need to configure tape drives using sun solaris, I had... (11 Replies)
Discussion started by: graboid888
11 Replies
6. AIX
I have 2 LPARs running AIX 5.3. Both are on the same VLAN. One LPAR, which I'll call LPAR2, has a 4mm SCSI tape drive connected to it, while LPAR1 does not have a tape drive connected. I am able to take mksysb backups of LPAR2 to the tape drive since it's directly connected. However, I need to... (2 Replies)
Discussion started by: need2bageek
2 Replies
7. AIX
Hi,
I have recently purchase a SUN Storage Tek desktop LTO 4 HH tape drive and connected to a IBM AIX 5.1 server.
The server can detect the tape device.
Can someone please advice urgently.
Thanks (4 Replies)
Discussion started by: Caully
4 Replies
8. Solaris
Hello all,
how can i see configured fc tapes in solaris system and how can i install a new fc shared tape device , thanks
Best Regards (2 Replies)
Discussion started by: bogacd
2 Replies
9. Solaris
Hi all...I have an old Sun Ultra 2 running SunOS 5.7 (I know old). These machines have 2 hard drives and one of my drives fried. I bought some replacement drives and wanted to a simple "dd" command from my one good drive to copy all to the new replacement drive. The new drives however give me a... (11 Replies)
Discussion started by: psantinello
11 Replies
10. Solaris
I have a SunFire V445 running Solaris 10 and am adding a Sun DLT tape drive. From the OK prompt the probe-scsi-all does see the drive and it is the proper target of 4. When I do the boot -- -r it does build the /dev/rmt directories correctly and the links to /devices appear correct as well. When I... (8 Replies)
Discussion started by: chastings
8 Replies
HT(4) Kernel Interfaces Manual HT(4)
NAME
ht - RH-11/TU-16 magtape interface
DESCRIPTION
The files mt0, mt1, ... refer to the DEC RH/TM/TU16 magtape. When opened for reading or writing, the tape is not rewound. When closed,
it is rewound (unless the 0200 bit is on, see below). If the tape was open for writing, a double end-of-file is written. If the tape is
not to be rewound the tape is backspaced to just between the two tapemarks.
A standard tape consists of a series of 512 byte records terminated by a double end-of-file. To the extent possible, the system makes it
possible, if inefficient, to treat the tape like any other file. Seeks have their usual meaning and it is possible to read or write a byte
at a time. Writing in very small units is inadvisable, however, because it tends to create monstrous record gaps.
The last octal digit of the minor device number selects the drive. The middle digit selects a controller. The initial digit is even to
select 800 BPI, odd to select 1600 BPI. If the 0200 bit is on (initial digit 2 or 3), the tape is not rewound on close. Note that the
minor device number has no necessary connection with the file name, and in fact tp(1) turns the short name x into `/dev/mtx'.
The mt files discussed above are useful when it is desired to access the tape in a way compatible with ordinary files. When foreign tapes
are to be dealt with, and especially when long records are to be read or written, the `raw' interface is appropriate. The associated files
may be named rmt0, ..., rmt7, but the same minor-device considerations as for the regular files still apply.
Each read or write call reads or writes the next record on the tape. In the write case the record has the same length as the buffer given.
During a read, the record size is passed back as the number of bytes read, provided it is no greater than the buffer size; if the record is
long, an error is indicated. In raw tape I/O, the buffer must begin on a word boundary and the count must be even. Seeks are ignored. A
zero count is returned when a tape mark is read; another read will fetch the first record of the next tape file.
FILES
/dev/mt?, /dev/rmt?
SEE ALSO
tp(1)
BUGS
The magtape system is supposed to be able to take 64 drives. Such addressing has never been tried.
Taking a drive off line, or running off the end of tape, while writing have been known to hang the system.
If any non-data error is encountered, it refuses to do anything more until closed. In raw I/O, there should be a way to perform forward
and backward record and file spacing and to write an EOF mark explicitly.
HT(4)