Verifying Communication With The Tape Drives; Displaying The Kernel Initialization Information; Reviewing The Kernel Initialization Information - Quantum DAT 160 Reference

Installation into a linux os
Hide thumbs Also See for DAT 160:
Table of Contents

Advertisement

Verifying Communication with the Tape Drives

Displaying the Kernel
Initialization
Information
Reviewing the Kernel
Initialization
Information
Verifying Communication with the Tape Drives
Installing a DLT, SDLT, VS, LTO, or DAT Tape Drive Into a Linux Operating System
You must ensure the
a tape device, you must verify that the
You do this by displaying and reviewing the kernel initialization information
which contains
st
You can display the kernel initialization information by using any of the
following three methods:
0
Method
View
information
st
during boot-up.
Read the Kernel
Message Buffer Log.
Execute the
dmesg
command to view
the Kernel Message
Buffer Log.
All three of the methods show you the same information. The information
looks similar to one of the following:
0
RHEL3 output looks similar to the following:
Attached scsi tape st0 at scsi2, channel 0, id 4, lun 0
st0: Block limits 4 - 16777212 bytes.
st: Version 20030406, bufsize 32768, max init. bufs 4, s/g segs 16
SuSE9 output looks similar to the following:
Attached scsi tape st0 at scsi0, channel 0, id 3, lun 0
st0: try direct i/o: yes (alignment 512 B), max page reachable by HBA 1048575
st: Version 20040318, fixed bufsize 32768, s/g segs 256
driver sees the all the tape devices. If you have added
st
driver sees the new device.
st
driver initialization and attachment of SCSI tape devices.
Instructions
At boot-up, Linux displays kernel initialization
information, including the
and attachment of the SCSI tape devices. The
information scrolls by quickly; if you miss it, try
one of the other two methods.
The kernel message buffer log contains the most
recent kernel logs. Look in
The kernel message buffer is limited in
Remember:
size; therefore, when the buffer becomes full, old
logs are discarded.
Executing the
dmesg
open the kernel message buffer log. Execute the
following command:
# dmesg | less
See "Read the Kernel Message Buffer Log" above
for more information about the log.
6464215-01, Rev B
January 2006
driver initialization
st
.
/var/log/dmesg
command is another way to
0
9

Advertisement

Table of Contents
loading

Table of Contents