[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [cobalt-developers] Onstream Tape Drives & Cobalt Qube 3?



add /dev/st0 to /etc/fstab

On Fri, 16 Feb 2001, Kevin Thomson wrote:

> Just tried the following (exactly, and get these responces:
> 
> [root /]# mount /dev/st0
> mount: can't find /dev/st0 in /etc/fstab or /etc/mtab
> [root /]#
> 
> [root /]# mount -f /dev/st0
> mount: can't find /dev/st0 in /etc/fstab or /etc/mtab
> [root /]#
> 
> [root /]# mount /dev/st0 status
> mount: /dev/st0 is not a block device
> [root /]#
> 
> and lastly:
> [root /]# mount -f /dev/st0 status
> [root /]#
> 
> Which if I type mount afterwards to see the mounting points shows me:
> [root /]# mount
> /dev/md1 on / type ext2 (rw)
> none on /proc type proc (rw)
> /dev/md3 on /var type ext2 (rw,nosuid)
> /dev/md4 on /home type ext2 (rw,usrquota,grpquota,grpid)
> none on /dev/pts type devpts (rw,gid=5,mode=0620)
> /dev/st0 on status type unknown (rw)
> [root /]#
> 
> So is this all there is to it? or am I missing something entirely? like
> where I'm mounting this to (ie dir)?
> 
> Thanks
> -Kevin
> 
> -----Original Message-----
> From: robert [mailto:rob@xxxxxxxxxxxxxxx]
> Sent: Friday, February 16, 2001 4:57 AM
> To: Kevin Thomson
> Cc: cobalt-developers@xxxxxxxxxxxxxxx
> Subject: Re: [cobalt-developers] Onstream Tape Drives & Cobalt Qube 3?
> 
> 
> 
> use 'mount' instead of 'mt'
> 
> 
> 
> On Fri, 16 Feb 2001, Kevin Thomson wrote:
> 
> > Alright, I'm definatly up against a brick wall here and I'd really really
> > appreciate some assistance if anyone knows how to install a scsi tape
> drive
> > (specificaly the Onstream ADR50 External) onto a Qube 3 using the built in
> > scsi adapter.  Initialy we plugged it in, rebooted the box and essentialy
> > funbled around looking for commands to mount the drive, then Onstream did
> > Officialy anounce their compatability with Linux and put out this info as
> > they're "installation guide":
> >
> > 	Installation
> >
> > 	The LINUX operating systems have a built in device driver called st. The
> > LINUX installation program will probe your system for SCSI >>	adapters. In
> > some cases, the installation program will ask the user if they have
> attached
> > any SCSI adapters. If you choose YES, a 	dialog box will appear to select
> > from a list of SCSI drivers. Choose the driver that most closely resembles
> > the SCSI adapter. The 	installation program may then give you the
> > opportunity to specify options for the SCSI driver you selected. Most SCSI
> > drivers detect 	your hardware automatically.
> >
> > 	Install as follows:
> >
> > 	1. Shutdown the system and remove power from the system. Connect the tape
> > peripheral to the SCSI bus, adhering to the rules of SCSI for 	bus
> > termination, cable length, and ID selection (See Users Manual for detailed
> > description)
> >
> > 	2.Power on the system, peripherals first.
> >
> > 	3. Boot the system to the system maintenance mode and login as root.
> >
> > 	4. At the command prompt, type : mt -f /dev/st0 status. This should
> display
> > information about the tape drive. If this does not occur, 	re-check your
> > set-up.
> >
> > At first I thought "great now I can continue working on the backup
> software"
> > till I actualy tried "mt -f /dev/st0 status" through telnet and get a
> > "command not found" responce for "mt".  So I'm thinking, okay, maybe they
> > meant Mount, or mnt, no go there either as far as getting the device to
> > work.  Anyways, I call Onstream, The tech support people swear up and down
> > that the mt command stands for magnetic tape drive and its part of the st
> > driver, stating that if that command isn't found that its a fault of the
> > distrobution and I need to get an updated source of the kernel and
> > recompile.
> >
> > So, any ideas/insight into this? I did a little poking around and the "st
> > driver" is present in the kernel source on the Qube 3 but I'm not sure
> > whetehr it is modularized in the compiled kernel or even if its installed
> in
> > the current configuration.  If it is a matter of recompiling the kernel
> > could someone point out a good tutorial for this proccess that works on
> the
> > cobalt procduct(s)?
> >
> > Thanks
> > Kevin Thomson
> > webservices@xxxxxxxxxxxxxx
> >
> >
> >
> > _______________________________________________
> > cobalt-developers mailing list
> > cobalt-developers@xxxxxxxxxxxxxxx
> > http://list.cobalt.com/mailman/listinfo/cobalt-developers
> >
> 
> --
> 
> Robert Abraham, CEO
> HyperAccess Communications, Co.
> 50 N. Walkup Ave
> Top Floor
> Crystal Lake, IL 60014
> 815.356.3983 - Office
> 815.621.5282 - Cell
> 
> 
> _______________________________________________
> cobalt-developers mailing list
> cobalt-developers@xxxxxxxxxxxxxxx
> http://list.cobalt.com/mailman/listinfo/cobalt-developers
> 

-- 

Robert Abraham, CEO
HyperAccess Communications, Co.
50 N. Walkup Ave
Top Floor
Crystal Lake, IL 60014
815.356.3983 - Office
815.621.5282 - Cell