06-16-2009
configure tape drive to sun solaris 10
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 trouble starting up as most resources on the internet is thru Sun Solaris 9 and the only available version from sun is version 10.
I installed it already but had trouble connecting an external tape drive.i did probe-scsi-all, but it says not found.so i thought,maybe i need boot -r command to detect the newly installed device, but boot -r is not found also, i tried touch /reconfigure ;reboot, but when i tried devfsadm, still no result. there is no dev/rmt directory either.the system is on dual-boot with windows so i know that the tape drive and scsi device is working fine.
sorry,for the very detailed explanation, im really new to this one.
any suggestion is very much appreciated.thanks a lot.
10 More Discussions You Might Find Interesting
1. 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
2. Filesystems, Disks and Memory
I have a Sun Ultra 10/Solaris 2.7 with a differential SCSI card connected to a Supter DLt1 Tape Drive. When I boot the machine, and I do a probe-scsi-all in the very beginning of the boot process. It shows up correctly. If I wait for the boot process to proceed and then I do a probe-scsi-all, I get... (1 Reply)
Discussion started by: brv
1 Replies
3. Filesystems, Disks and Memory
Hi all, please help I am stuck.
I have installed a external unipack scsi tape drive. The tape drive is Exabyte Eliant 820. All I did was connected scsi cable and power it on. When issued "probe-scsi-all" command, the tape is correctly identified. However, when issued "dmesg | more" command, the... (4 Replies)
Discussion started by: dennis
4 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,
need your help mentors I have external SCSI tape DRIVE COmpaq 15/30 GB DLT and I dont know how to install these and how to view if it is working. I'm also have another disk taken form my old sun and I want to use these also but my problem how I able to mount.
hope anyone can help me
... (9 Replies)
Discussion started by: eykyn17
9 Replies
6. AIX
Hi,
Help required!
How to mount internal tape drive of sun machine in AIX 5.3 (0 Replies)
Discussion started by: ashwin.krishna
0 Replies
7. Solaris
Can I do this live? Or, do I need to do a probe-scsi-all after doing a stop/A? (10 Replies)
Discussion started by: jgordon
10 Replies
8. 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
9. Solaris
Hi all,
this time I'd need a help from an advanced Solaris system admin :rolleyes:
I attached a HP StorageWorks Ultrium 215 Tape Drives - Overview - c00059530 - HP Business Support Center to my Sun E220R and it got recognized immediately (probe-scsi-all).
Now the operating system boot process... (8 Replies)
Discussion started by: pseudocoder
8 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 - TM-03/TE-16,TU-45,TU-77 MASSBUS magtape interface
SYNOPSIS
/sys/conf/SYSTEM:
NHT ht_drives # TE16, TU45, TU77
/etc/dtab:
#Name Unit# Addr Vector Br Handler(s) # Comments
ht ? 172440 224 5 htintr # tu 16 massbus tape
major device number(s):
raw: 6
block: 0
minor device encoding:
bits 0003 specify HT drive
bit 0004 specifies no-rewind operation
bit 0010 specifies 1600BPI recording density instead of 800BPI
DESCRIPTION
The tm-03/transport combination provides a standard tape drive interface as described in mtio(4). All drives provide both 800 and 1600
bpi; the TE-16 runs at 45 ips, the TU-45 at 75 ips, while the TU-77 runs at 125 ips and autoloads tapes.
FILES
/dev/MAKEDEV script to create special files
/dev/MAKEDEV.local script to localize special files
SEE ALSO
mt(1), tar(1), tp(1), mtio(4), tm(4), ts(4), dtab(5), autoconfig(8)
DIAGNOSTICS
tu%d: no write ring. An attempt was made to write on the tape drive when no write ring was present; this message is written on the termi-
nal of the user who tried to access the tape.
tu%d: not online. An attempt was made to access the tape while it was offline; this message is written on the terminal of the user who
tried to access the tape.
tu%d: can't change density in mid-tape. An attempt was made to write on a tape at a different density than is already recorded on the
tape. This message is written on the terminal of the user who tried to switch the density.
tu%d: hard error bn%d er=%b ds=%b. A tape error occurred at block bn; the ht error register and drive status register are printed in
octal with the bits symbolically decoded. Any error is fatal on non-raw tape; when possible the driver will have retried the operation
which failed several times before reporting the error.
BUGS
If any non-data error is encountered on non-raw tape, it refuses to do anything more until closed.
The system should remember which controlling terminal has the tape drive open and write error messages to that terminal rather than on the
console.
3rd Berkeley Distribution January 28, 1988 HT(4)