Table of Contents
Advertisement
.
mptsas
37321
If a particular driver module is not listed as above use the modprobe utility to load it. For example
if the st driver is missing, execute:
modprobe st
NOTE:
Loading of the st driver should happen naturally if your system is rebooted after attaching the drive.
Determining the attached devices
HBAs which use the cciss driver may require an explicit scan procedure to allow the attached tape
drive to be discovered after each reboot; execute the following from the command line (or from a
shell script):
for x in /proc/driver*/cciss/c*;do echo engage scsi > $x; done; dmesg
Check the contents of the file /proc/scsi/scsi to determine whether the system discovered the
tape drive at module load time:
cat /proc/scsi/scsi
Examine the contents for something like:
Host: SCSI0 Channel: 00 Id:00 Lun:00
Vendor: HP
Type: Sequential-Access ANSI SCSI Revision 06
Look through the output of dmesg to discover which tape drive instance is used (st0 in the example
below) and to review the SCSI HBA driver (cciss in the extract below).
NOTE:
The exact format and style of the listing may vary with different Linux distributions and versions.
TIP:
You may prefer to redirect a lengthy dmesg output to a file for browsing at your convenience:
dmseg > my_boot_messages.txt
or pipe the output of dmesg to a page scrolling utility
dmesg | more
Extract from dmesg output:
.
.
scsi3 : cciss
Vendor: HP
Type:
Sequential-Access
scsi 3:0:0:0: Attached scsi generic sg0 type 1
18
Linux servers and workstations
0
Model: Ultrium 5-SCSI Rev: ZxxD
Model: Ultrium 5-SCSI
Rev: ZxxD
ANSI SCSI revision: 06
Advertisement
Table of Contents
