Scsi Disk Problem Identification And Resolution; Support For Fibre-Channel Boot; Creating A Modules Disk For Suse Linux Enterprise Server 9.0; Installing Linux Over The San Without An Ibm Subsystem Device Driver - IBM TotalStorage DS6000 Attachment Manual

SCSI disk problem identification and resolution

This section describes a few problems that might occur on your storage unit when
you are using SCSI disks.
v In response to errors, the kernel might permanently disable a LUN and log a
v The system might periodically list processes in the D-state (see the ps command
v The Linux kernel buffer cache is designed to discard dirty buffers after an

Support for fibre-channel boot

The following sections contain support information for fibre-channel boot.

Creating a modules disk for SUSE LINUX Enterprise Server 9.0

Use this process to create a modules disk for SUSE LINUX Enterprise Server 9.0.
1. Boot the server using the SLES 9 SP1 CD.
2. When you are prompted, select Rescue System.
3. Insert the SLES 9 CD 1 CD when you are prompted.
4. After the system boots, the Rescue login prompt appears. Log in as "root" and
5. Remove the SLES 9 CD 1 CD, and insert the SLES 9 SP1 CD.
6. If you are using IDE CD-ROM drives, type mount /dev/hda /cdrom at the
7. Change to the CD-ROM boot directory by typing cd /cdrom/boot.
8. Insert a diskette into the diskette drive. Create the modules disk by typing dd
9. Reboot with the SLES 9 SP1 CD in the CD-ROM drive.

Installing Linux over the SAN without an IBM Subsystem Device Driver

This topic provides instructions for installing Linux over the SAN without an IBM
Subsystem Device Driver.
114
DS6000 Host Systems Attachment Guide
message stating "device set offline" and the specific device. If this happens, there
is no way to bring the LUN online. It might be possible to remove the LUN and
add it back through the /proc/scsi/scsi directory or reload the host adapter driver.
If those fail, it is necessary to reboot the host.
help page), which corresponds to an uninterruptible sleep. In error situations, a
process might become permanently stuck in this state, and require a system
reboot to recover.
input/output (I/O) error when the system memory resources are constrained. An
application that is attempting to use the fsync() command to verify that its writes
have completed successfully will receive an indication of success from the
command once the writes successfully complete. Some kernels have a bug in
the kswapd daemon, that makes it likely that the system will perceive itself to be
in a state of constrained memory. Multipathing can reduce the risk of this silent
data loss by providing a means to retry failed I/O operations and hide the failure
from the buffer cache.
Note: If you are using the x360/x440 servers, append "apic" to the kernel boot
options string at the bottom of the menu screen.
do not enter a password.
command line. If you are using SCSI, type /dev/sda instead of hda, or /dev/sdb,
and so forth.
if=modules2 of=/dev/fd0u1440. When this is completed, a message is
displayed that says "2880+0 records in 2880+0 records out".