Identifying The Faulty Disk Drive - Sun Microsystems Ultra 450 Manual

3. Reconfigure the operating environment
In all cases you must select the disk and stop any activity or applications on it,
unmount it, physically remove the drive, and configure the Solaris environment to
recognize that the drive is no longer there. Then you must configure your application
to operate without this device in place.

Identifying the Faulty Disk Drive

Disk errors may be reported in a number of different ways. Often you can find
messages about failing or failed disks in your system console. This information is
also logged in the /usr/adm/messages files. These error messages typically refer
to a failed disk drive by its UNIX physical device name (such as
/devices/pci@6,4000/scsi@4,1/sd@3,0) and its UNIX device instance name
(such as sd14). In some cases, a faulty disk may be identified by its UNIX logical
device name, such as c2t3d0. In addition, some applications may report a disk slot
number (0 through 19) or activate an LED located next to the disk drive itself (see
Figure 3–3).
Figure 3–3 Disk Slot Numbers and LED Locations
In order to perform a disk hot-plug procedure, you need to know the slot number of
the faulty disk (0 through 19) and its logical device name (for example, c2t3d0). If
you know the disk slot number, it is possible to determine the logical device name,
and vice versa. It is also possible to determine both the disk slot number and the
♦ September 1998, Revision A
28