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
ESP(4) BSD Kernel Interfaces Manual ESP(4)
NAME
esp -- Qlogic FEPS and FAS366 SCSI driver
SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file:
device scbus
device esp
HARDWARE
The esp driver provides support for the Qlogic FAS216 and FAS408 SCSI controller chips found in a wide variety of systems and peripheral
boards. This includes the Qlogic SCSI cards found in most Sun Ultra 1e and Ultra 2 machines.
For Qlogic PCI SCSI host adapters, the isp(4) driver should be used in place of the esp driver.
IMPLEMENTATION NOTES
During the boot sequence, the esp driver searches the linked list for LUN info by LUN ID. At this point the driver will attach on that
instance, and then attempt to attach every sub-device.
There are at least 4 variations of the configuration 3 register. A second config register must be loaded to inquire the chip revision, oth-
erwise the ncr53c9x_reset() function will not set the defaults correctly.
The drive attach routine attempts to set the appropriate bit to put the chip into Fast SCSI mode so that it does not have to be figured out
each time. This will then be stored in the NCR registers for later use.
The esp driver makes use of the LSI 64854 DMA engine which contains three independent channels designed to interface with an NCR539X SCSI
controller; an AM7990 Ethernet controller; and certain types of parallel port hardware. As such this driver may eventually replace the
amd(4) driver for network hardware.
DIAGNOSTICS
The following driver specific error messages may be reported:
esp: cannot map %d segments The device was unable to map segments while mapping the SCSI devices in DMA mode.
unknown variant %d, devices not attached An unknown version of the card was found and devices will not be attached.
Unhandled function code %d The device returned a function code which the driver is unable to handle, most likely during negotiation.
esp:%d:%d: selection failed %d left in FIFO The target left the command phase prematurely. If a command did not reach the device then it
will be reported as shown above.
invalid state: %d The device has reached an invalid state.
SEE ALSO
amd(4), isp(4), scbus(4), camcontrol(8)
http://www.qlc.com/
http://www.sun.com/
HISTORY
The esp driver was written for NetBSD by Eric S. Hvozda. The esp driver was then ported to FreeBSD 5.3 by Scott Long <scottl@FreeBSD.org>.
AUTHORS
This manual page was written by Tom Rhodes <trhodes@FreeBSD.org> instead of porting the original from NetBSD.
BUGS
The esp driver includes the sbus front-end but lacks the PCI front-end. Thus it can only support the FEPS/FAS366 SCSI found in Sun Ultra 1e
and Ultra 2 machines at this time.
This driver should eventually replace the amd(4) driver, but that requires porting the PCI front-end mentioned above.
BSD
September 18, 2005 BSD