HELP with adding tape drive

HELP with adding tape drive

Post by Jason Dinsda » Sat, 14 Jun 2003 16:48:50



Ladies & Gents,

Hope you can help me.  I've inherited a FreeBSD 4.5 system that's
installed on a Proliant.  This system has recently had a tape drive
added to it (SCSI ID 6), *but* the system has not been rebooted (not
clever I know but I had no hand in it).   So, now I'm trying to access
the drive ... I've run:

# sh /dev/MAKEDEV sa

I also took a stab at:

# sh /dev/MAKEDEV sa6 (

and have the following device files:

[root]# ll /dev/*sa*
crw-rw----  4 root  operator   14,   2 Jun 13 12:20 /dev/ersa0
crw-rw----  4 root  operator   14,   2 Jun 13 12:20 /dev/ersa0.0
crw-rw----  2 root  operator   14,   6 Jun 13 12:20 /dev/ersa0.1
crw-rw----  2 root  operator   14,  10 Jun 13 12:20 /dev/ersa0.2
crw-rw----  2 root  operator   14,  14 Jun 13 12:20 /dev/ersa0.3
crw-rw----  4 root  operator   14,  98 Jun 13 12:33 /dev/ersa6
crw-rw----  4 root  operator   14,  98 Jun 13 12:33 /dev/ersa6.0
crw-rw----  2 root  operator   14, 102 Jun 13 12:33 /dev/ersa6.1
crw-rw----  2 root  operator   14, 106 Jun 13 12:33 /dev/ersa6.2
crw-rw----  2 root  operator   14, 110 Jun 13 12:33 /dev/ersa6.3
crw-rw----  4 root  operator   14,   2 Jun 13 12:20 /dev/esa0
crw-rw----  4 root  operator   14,   2 Jun 13 12:20 /dev/esa0.0
crw-rw----  2 root  operator   14,   6 Jun 13 12:20 /dev/esa0.1
crw-rw----  2 root  operator   14,  10 Jun 13 12:20 /dev/esa0.2
crw-rw----  2 root  operator   14,  14 Jun 13 12:20 /dev/esa0.3
crw-rw----  4 root  operator   14,  98 Jun 13 12:33 /dev/esa6
crw-rw----  4 root  operator   14,  98 Jun 13 12:33 /dev/esa6.0
crw-rw----  2 root  operator   14, 102 Jun 13 12:33 /dev/esa6.1
crw-rw----  2 root  operator   14, 106 Jun 13 12:33 /dev/esa6.2
crw-rw----  2 root  operator   14, 110 Jun 13 12:33 /dev/esa6.3
crw-rw----  4 root  operator   14,   1 Jun 13 12:20 /dev/nrsa0
crw-rw----  4 root  operator   14,   1 Jun 13 12:20 /dev/nrsa0.0
crw-rw----  2 root  operator   14,   5 Jun 13 12:20 /dev/nrsa0.1
crw-rw----  2 root  operator   14,   9 Jun 13 12:20 /dev/nrsa0.2
crw-rw----  2 root  operator   14,  13 Jun 13 12:20 /dev/nrsa0.3
crw-rw----  4 root  operator   14,  97 Jun 13 12:33 /dev/nrsa6
crw-rw----  4 root  operator   14,  97 Jun 13 12:33 /dev/nrsa6.0
crw-rw----  2 root  operator   14, 101 Jun 13 12:33 /dev/nrsa6.1
crw-rw----  2 root  operator   14, 105 Jun 13 12:33 /dev/nrsa6.2
crw-rw----  2 root  operator   14, 109 Jun 13 12:33 /dev/nrsa6.3
crw-rw----  4 root  operator   14,   1 Jun 13 12:20 /dev/nsa0
crw-rw----  4 root  operator   14,   1 Jun 13 12:20 /dev/nsa0.0
crw-rw----  2 root  operator   14,   5 Jun 13 12:20 /dev/nsa0.1
crw-rw----  2 root  operator   14,   9 Jun 13 12:20 /dev/nsa0.2
crw-rw----  2 root  operator   14,  13 Jun 13 12:20 /dev/nsa0.3
crw-rw----  4 root  operator   14,  97 Jun 13 12:33 /dev/nsa6
crw-rw----  4 root  operator   14,  97 Jun 13 12:33 /dev/nsa6.0
crw-rw----  2 root  operator   14, 101 Jun 13 12:33 /dev/nsa6.1
crw-rw----  2 root  operator   14, 105 Jun 13 12:33 /dev/nsa6.2
crw-rw----  2 root  operator   14, 109 Jun 13 12:33 /dev/nsa6.3
crw-rw----  4 root  operator   14,   0 Jun 13 12:20 /dev/rsa0
crw-rw----  4 root  operator   14,   0 Jun 13 12:20 /dev/rsa0.0
crw-rw----  2 root  operator   14,   4 Jun 13 12:20 /dev/rsa0.1
crw-rw----  2 root  operator   14,   8 Jun 13 12:20 /dev/rsa0.2
crw-rw----  2 root  operator   14,  12 Jun 13 12:20 /dev/rsa0.3
crw-rw----  2 root  wheel      14, 0x20000000 Jun 13 12:20
/dev/rsa0.ctl
crw-rw----  4 root  operator   14,  96 Jun 13 12:33 /dev/rsa6
crw-rw----  4 root  operator   14,  96 Jun 13 12:33 /dev/rsa6.0
crw-rw----  2 root  operator   14, 100 Jun 13 12:33 /dev/rsa6.1
crw-rw----  2 root  operator   14, 104 Jun 13 12:33 /dev/rsa6.2
crw-rw----  2 root  operator   14, 108 Jun 13 12:33 /dev/rsa6.3
crw-rw----  2 root  wheel      14, 0x20000060 Jun 13 12:33
/dev/rsa6.ctl
crw-rw----  4 root  operator   14,   0 Jun 13 12:20 /dev/sa0
crw-rw----  4 root  operator   14,   0 Jun 13 12:20 /dev/sa0.0
crw-rw----  2 root  operator   14,   4 Jun 13 12:20 /dev/sa0.1
crw-rw----  2 root  operator   14,   8 Jun 13 12:20 /dev/sa0.2
crw-rw----  2 root  operator   14,  12 Jun 13 12:20 /dev/sa0.3
crw-rw----  2 root  wheel      14, 0x20000000 Jun 13 12:20
/dev/sa0.ctl
crw-rw----  4 root  operator   14,  96 Jun 13 12:33 /dev/sa6
crw-rw----  4 root  operator   14,  96 Jun 13 12:33 /dev/sa6.0
crw-rw----  2 root  operator   14, 100 Jun 13 12:33 /dev/sa6.1
crw-rw----  2 root  operator   14, 104 Jun 13 12:33 /dev/sa6.2
crw-rw----  2 root  operator   14, 108 Jun 13 12:33 /dev/sa6.3
crw-rw----  2 root  wheel      14, 0x20000060 Jun 13 12:33
/dev/sa6.ctl

When I try to access the tape drive I get:

[root]# mt -f /dev/sa0 status
mt: /dev/sa0: Device not configured

[root]# mt -f /dev/sa6 status
mt: /dev/sa6: Device not configured

[root]# mt -f /dev/nsa6 status
mt: /dev/nsa6: Device not configured

[root]# mt -f /dev/nsa0 status
mt: /dev/nsa0: Device not configured

... etc ...

The kernel config has the following entries in it:

# $FreeBSD: src/sys/i386/conf/GENERIC,v 1.246.2.38 2002/01/25 17:41:40
murray Exp $

machine         i386
cpu             I386_CPU
cpu             I486_CPU
cpu             I586_CPU
cpu             I686_CPU
ident           GENERIC
maxusers        0

#makeoptions    DEBUG=-g                #Build kernel with gdb(1)
debug symbols

options         MATH_EMULATE            #Support for x87 emulation
options         INET                    #InterNETworking
options         INET6                   #IPv6 communications protocols
options         FFS                     #Berkeley Fast Filesystem
options         FFS_ROOT                #FFS usable as root device
[keep this!]
options         SOFTUPDATES             #Enable FFS soft updates
support
options         UFS_DIRHASH             #Improve performance on big
directories
options         MFS                     #Memory Filesystem
options         MD_ROOT                 #MD is a potential root device
options         NFS                     #Network Filesystem
options         NFS_ROOT                #NFS usable as root device,
NFS required
options         MSDOSFS                 #MSDOS Filesystem
options         CD9660                  #ISO 9660 Filesystem
options         CD9660_ROOT             #CD-ROM usable as root, CD9660
required
options         PROCFS                  #Process filesystem
options         COMPAT_43               #Compatible with BSD 4.3 [KEEP
THIS!]
options         SCSI_DELAY=15000        #Delay (in ms) before probing
SCSI
options         UCONSOLE                #Allow users to grab the
console
options         USERCONFIG              #boot -c editor
options         VISUAL_USERCONFIG       #visual boot -c editor
options         KTRACE                  #ktrace(1) support
options         SYSVSHM                 #SYSV-style shared memory
options         SYSVMSG                 #SYSV-style message queues
options         SYSVSEM                 #SYSV-style semaphores
options         P1003_1B                #Posix P1003_1B real-time
extensions
options         _KPOSIX_PRIORITY_SCHEDULING
options         ICMP_BANDLIM            #Rate limit bad replies
options         KBD_INSTALL_CDEV        # install a CDEV entry in /dev

# To make an SMP kernel, the next two are needed
#options        SMP                     # Symmetric MultiProcessor
Kernel
#options        APIC_IO                 # Symmetric (APIC) I/O

device          isa
device          eisa
device          pci

# Floppy drives
device          fdc0    at isa? port IO_FD1 irq 6 drq 2
device          fd0     at fdc0 drive 0
device          fd1     at fdc0 drive 1
#
# If you have a Toshiba Libretto with its Y-E Data PCMCIA floppy,
# don't use the above line for fdc0 but the following one:
#device         fdc0

# ATA and ATAPI devices
device          ata0    at isa? port IO_WD1 irq 14
device          ata1    at isa? port IO_WD2 irq 15
device          ata
device          atadisk                 # ATA disk drives
device          atapicd                 # ATAPI CDROM drives
device          atapifd                 # ATAPI floppy drives
device          atapist                 # ATAPI tape drives
options         ATA_STATIC_ID           #Static device numbering

# SCSI Controllers
device          ahb             # EISA AHA1742 family
device          ahc             # AHA2940 and onboard AIC7xxx devices
device          amd             # AMD 53C974 (Tekram DC-390(T))
device          isp             # Qlogic family
device          ncr             # NCR/Symbios Logic
device          sym             # NCR/Symbios Logic (newer chipsets)
options         SYM_SETUP_LP_PROBE_MAP=0x40
                                # Allow ncr to attach legacy NCR
devices when
                                # both sym and ncr are configured

device          adv0    at isa?
device          adw
device          bt0     at isa?
device          aha0    at isa?
device          aic0    at isa?

device          ncv             # NCR 53C500
device          nsp             # Workbit Ninja SCSI-3
device          stg             # TMC 18C30/18C50

# SCSI peripherals
device          scbus           # SCSI bus (required)
device          da              # Direct Access (disks)
device          sa              # Sequential Access (tape etc) <==
This is the one I need I think???
device          cd              # CD
device          pass            # Passthrough device (direct SCSI
access)

# RAID controllers interfaced to the SCSI subsystem
device          asr             # DPT SmartRAID V, VI and Adaptec SCSI
RAID
device          dpt             # DPT Smartcache - See LINT for
options!
device          mly             # Mylex AcceleRAID/eXtremeRAID

# RAID controllers
device          aac             # Adaptec FSA RAID, Dell PERC2/PERC3
device          ida             # Compaq Smart RAID
device          amr             # AMI MegaRAID
device          mlx             # Mylex DAC960 family
device          twe             # 3ware Escalade

# atkbdc0 controls both the keyboard and the PS/2 mouse
device        
...

read more »

 
 
 

HELP with adding tape drive

Post by Lowell Gilber » Sun, 15 Jun 2003 02:52:54


comp.unix.bsd.freebsd is not widely propagated, so you won't
necessarily get much help here (in comp.unix.bsd.freebsd).
See http://www.freebsd.org/support.html for better ideas...
[followups redirected accordingly]


> Hope you can help me.  I've inherited a FreeBSD 4.5 system that's
> installed on a Proliant.  This system has recently had a tape drive
> added to it (SCSI ID 6), *but* the system has not been rebooted (not
> clever I know but I had no hand in it).   So, now I'm trying to access
> the drive ... I've run:

I'm not sure this will work on 4.5, but have you tried "camcontrol rescan"?
Quote:> Is a reboot all that is required to get this drive working and
> accessible, or is there more to this?


 
 
 

HELP with adding tape drive

Post by Jason Dinsda » Tue, 17 Jun 2003 16:01:06



> comp.unix.bsd.freebsd is not widely propagated, so you won't
> necessarily get much help here (in comp.unix.bsd.freebsd).
> See http://www.freebsd.org/support.html for better ideas...
> [followups redirected accordingly]


> > Hope you can help me.  I've inherited a FreeBSD 4.5 system that's
> > installed on a Proliant.  This system has recently had a tape drive
> > added to it (SCSI ID 6), *but* the system has not been rebooted (not
> > clever I know but I had no hand in it).   So, now I'm trying to access
> > the drive ... I've run:

> I'm not sure this will work on 4.5, but have you tried "camcontrol rescan"?

> > Is a reboot all that is required to get this drive working and
> > accessible, or is there more to this?

Lowell,

Thanks for replying, and the heads-up re: lack of traffic in this
group.  I'm a seasoned UNIX admin but a FreeBSD newbie ... hence I'm
struggling to get this tape drive up and running.  Tried the
camcontrol rescan as you suggested:

[root]# camcontrol rescan all
Re-scan of bus 0 was successful
Re-scan of bus 1 was successful
Re-scan of bus 2 was successful

and then....

[root]# camcontrol devlist -v
scbus0 on ahc0 bus 0:
<  >                               at scbus0 target -1 lun -1 ()
scbus1 on ahc1 bus 0:
<  >                               at scbus1 target -1 lun -1 ()
scbus2 on ciss0 bus 0:
<RAID 5 OK >                       at scbus2 target 0 lun 0 (da0)
scbus-1 on xpt0 bus 0:
<  >                               at scbus-1 target -1 lun -1 (xpt0)

This doesnt look too good to me .... as though it cant see the device.
Do you think it would be listed regardless of whether a driver is
bound to the device?

TIA,

Jason

 
 
 

HELP with adding tape drive

Post by David Alge » Fri, 20 Jun 2003 13:32:45


Most likely if the hardware has not been rebooted and the SCSI
device is *not* hot-swappable, then the scsi-card has
not registered the device, so the operating system will not be
able to see it until the hardware has detected it.

-Dave Alger



> > comp.unix.bsd.freebsd is not widely propagated, so you won't
> > necessarily get much help here (in comp.unix.bsd.freebsd).
> > See http://www.freebsd.org/support.html for better ideas...
> > [followups redirected accordingly]


> > > Hope you can help me.  I've inherited a FreeBSD 4.5 system that's
> > > installed on a Proliant.  This system has recently had a tape drive
> > > added to it (SCSI ID 6), *but* the system has not been rebooted (not
> > > clever I know but I had no hand in it).   So, now I'm trying to access
> > > the drive ... I've run:

> > I'm not sure this will work on 4.5, but have you tried "camcontrol
rescan"?

> > > Is a reboot all that is required to get this drive working and
> > > accessible, or is there more to this?

> Lowell,

> Thanks for replying, and the heads-up re: lack of traffic in this
> group.  I'm a seasoned UNIX admin but a FreeBSD newbie ... hence I'm
> struggling to get this tape drive up and running.  Tried the
> camcontrol rescan as you suggested:

> [root]# camcontrol rescan all
> Re-scan of bus 0 was successful
> Re-scan of bus 1 was successful
> Re-scan of bus 2 was successful

> and then....

> [root]# camcontrol devlist -v
> scbus0 on ahc0 bus 0:
> <  >                               at scbus0 target -1 lun -1 ()
> scbus1 on ahc1 bus 0:
> <  >                               at scbus1 target -1 lun -1 ()
> scbus2 on ciss0 bus 0:
> <RAID 5 OK >                       at scbus2 target 0 lun 0 (da0)
> scbus-1 on xpt0 bus 0:
> <  >                               at scbus-1 target -1 lun -1 (xpt0)

> This doesnt look too good to me .... as though it cant see the device.
> Do you think it would be listed regardless of whether a driver is
> bound to the device?

> TIA,

> Jason

 
 
 

1. Re. Problems adding tape drives to RS6000/220 Re: Problems adding tape drives to RS6000/220


Your system does not find the tape during boot phase. For IBM tapes normally
plug them, switch them on, boot up the system and AIX automatically
configures them.

The 220 uses other SCSI cabels than your 320 are they ok. Check the SCSI ID
of your tape - maybe you have other devices using the same ID. Run
'lscfg -v' to display all devices.

frank ;-)

.----------------------------------------------------------------------.
| E-Mail: FRANVM3(KRAEMERF)                 - IBM VNET  "Yes, I'm one  |
| ======  IBMMAIL(DEIBM27S)                 - IBM-Mail   of those      |
|         DE.IBMX400.IBMMAIL.KRAEMER.KRAEME - X.400      stupid IBM    |

| Voice : +49-(0)611/776-364                                           |
| Mail  : Abraham-Lincoln Street 26, 6200 Wiesbaden, Germany           |
'----------------------------------------------------------------------'

2. What is .gz file and how can I extract it?

3. using 14gb 8mm tape drive to write tapes for 2gb tape drive

4. DHCP Server Setup - where is config files location

5. Adding a Tape Drive or Second Hard Drive

6. Linux/NT

7. Need help adding tape drive

8. Configuring Linux

9. Login help needed; adding a tape drive

10. Need help adding tape drive

11. Help adding external DLT tape drive

12. HELP! added a SCSI tape drive