04-25-2004
HP DAT Drive C1533A on RH9 Problems
HELP!!
I am having some major problems at present with a HP dat drive under RH9. The drive worked fine previously under RH8, but now does not work.
I am using kernel 2.4.20-30.9 on a i686 athlon intel box.
My messages log shows the below:
Apr 23 11:39:24 devsys kernel: ahc_pci:1:6:0: Host Adapter Bios disabled. Using default SCSI device parameters
Apr 23 11:39:24 devsys kernel: scsi1 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.8
Apr 23 11:39:24 devsys kernel: <Adaptec 2902/04/10/15/20/30C SCSI adapter>
Apr 23 11:39:24 devsys kernel: aic7850: Single Channel A, SCSI Id=7, 3/253 SCBs
Apr 23 11:39:24 devsys kernel:
Apr 23 11:39:24 devsys kernel: blk: queue c1dd0a14, I/O limit 4095Mb (mask 0xffffffff)
Apr 23 11:39:24 devsys kernel: Vendor: HP Model: C1533A Rev: 9406
Apr 23 11:39:24 devsys kernel: Type: Sequential-Access ANSI SCSI revision: 02
Apr 23 11:39:24 devsys kernel: blk: queue c1dd0c14, I/O limit 4095Mb (mask 0xffffffff)
Apr 23 11:39:24 devsys kernel: scsi : 1 host left.
After this there is nothing else. I have used the hardware browser to show more information and it lists the drive as /dev/st, however when I use the command mt -f /dev/st eject I get the following:
/dev/st: No such file or directory
So I try the below and get:
/dev/st0: No such device
Doing a ls -l on /dev/st0 shows the following
crw-rw---- 1 root disk 9, 0 Jan 30 2003 /dev/st0
I am in desperate need of some help on this one, there is a gold star up for grabs..
Thanks..
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Sun Ultra 80 ...
had to connect an additional drive. connect it according to hardware manual
The problem is when i try to power on the system , it dosent start, .. like the system is dead. :(
So i remove the new drive and voila ... power starts up .
Can anyone pinpoint wats goin on here. ... (7 Replies)
Discussion started by: DPAI
7 Replies
2. Linux
Hi,
Will someone help in giving the clue to installating Travan Tape drive on Redhat 8.0
Kayode (1 Reply)
Discussion started by: kayode
1 Replies
3. Solaris
I will be honest I am quite new to UNIX and Solaris so this may be a simple thing.
I have just purchased a Sun (rebranded HP obviously) DAT DDS3 SCSI tape drive for my Sun Ultra 10 running Solaris 10.
I have previously fitted a SCSI card to the box which has configured ok and can be seen from... (1 Reply)
Discussion started by: mattw
1 Replies
4. HP-UX
Can anyone help with an HP Ignite problem please !!
We currently have 2 servers running HP-UX B.11.00 connected together and using a high availability cluster (serviceguard) running one package.
Each of the servers have 2 mirrored local disks. (also installed HP OpenviewDM B.05.03, Oracle 8.0.5,... (7 Replies)
Discussion started by: clivethegadget
7 Replies
5. SCO
my server os version is openserver 5.0.6.from past few days it is giving problem while taking backup.it is giving error such that "TAPE WRITE ERROR".anyone can help to come out of this. (3 Replies)
Discussion started by: prakrithi
3 Replies
6. AIX
Hello, we are trying to install an HP DAT drive on an IBM AIX RS6000 server. We have attached the SCSI connection and power cylced the unit, but still cannot see the device in smit.
I am only a couple months into AIX, so I am very green! The server we are working on is in a lab environment,... (2 Replies)
Discussion started by: dayinthelife
2 Replies
7. Solaris
Well I have just added new tape drive to my server (lto)
However I am getting few errors in using it. I have checked status with
#iostat -En : giving me few hard errors, few soft errors and execution error.
Also tape status is not visible as "no sense" its coming as "no additional sense".
I... (5 Replies)
Discussion started by: saurabh84g
5 Replies
8. SCO
hi all,
how i can configure a DAT drive usb under SCO os 6.0.0
thank you (0 Replies)
Discussion started by: lid-j-one
0 Replies
9. Solaris
Hi all,
I have solaris 10 sparc running and working very well
but i have problem with external SCSI tape drive DAT 72 problem
it seems to me the tape drive is manufactured by SUN microsystems
when i ran ls -l /dev/rmt/0
it reveals the following output
bash-3.00# mt -f /dev/rmt/0... (2 Replies)
Discussion started by: h@foorsa.biz
2 Replies
10. Infrastructure Monitoring
So i upgraded from Nagios version 2.6 to the latest version of nagios currently available.
but the problem is, i can't get the comments that were on my old version of nagios to show up on my new version of nagios.
has anyone else run into this issue?
the comments are extremely important.... (0 Replies)
Discussion started by: SkySmart
0 Replies
SD(4) Linux Programmer's Manual SD(4)
NAME
sd - Driver for SCSI Disk Drives
SYNOPSIS
#include <linux/hdreg.h> /* for HDIO_GETGEO */
#include <linux/fs.h> /* for BLKGETSIZE and BLKRRPART */
CONFIGURATION
The block device name has the following form: sdlp, where l is a letter denoting the physical drive, and p is a number denoting the parti-
tion on that physical drive. Often, the partition number, p, will be left off when the device corresponds to the whole drive.
SCSI disks have a major device number of 8, and a minor device number of the form (16 * drive_number) + partition_number, where drive_num-
ber is the number of the physical drive in order of detection, and partition_number is as follows:
partition 0 is the whole drive
partitions 1-4 are the DOS "primary" partitions
partitions 5-8 are the DOS "extended" (or "logical") partitions
For example, /dev/sda will have major 8, minor 0, and will refer to all of the first SCSI drive in the system; and /dev/sdb3 will have
major 8, minor 19, and will refer to the third DOS "primary" partition on the second SCSI drive in the system.
At this time, only block devices are provided. Raw devices have not yet been implemented.
DESCRIPTION
The following ioctls are provided:
HDIO_GETGEO
Returns the BIOS disk parameters in the following structure:
struct hd_geometry {
unsigned char heads;
unsigned char sectors;
unsigned short cylinders;
unsigned long start;
};
A pointer to this structure is passed as the ioctl(2) parameter.
The information returned in the parameter is the disk geometry of the drive as understood by DOS! This geometry is not the physical
geometry of the drive. It is used when constructing the drive's partition table, however, and is needed for convenient operation of
fdisk(1), efdisk(1), and lilo(1). If the geometry information is not available, zero will be returned for all of the parameters.
BLKGETSIZE
Returns the device size in sectors. The ioctl(2) parameter should be a pointer to a long.
BLKRRPART
Forces a reread of the SCSI disk partition tables. No parameter is needed.
The scsi(4) ioctl(2) operations are also supported. If the ioctl(2) parameter is required, and it is NULL, then ioctl(2) will fail
with the error EINVAL.
FILES
/dev/sd[a-h]: the whole device
/dev/sd[a-h][0-8]: individual block partitions
COLOPHON
This page is part of release 3.27 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
Linux 1992-12-17 SD(4)