Platform Notes: Sun Enterprise 250 Server

Adding a Hot-Pluggable Disk Drive

This section contains information on how to configure your system when you add a disk drive while the power is on and the operating system is running.

The way in which you add a disk drive depends on the application you are using. Each application requires that you decide where to install the new disk drive, add the drive, and then reconfigure the operating environment.

In all cases, you must select a slot, physically install the disk drive, and configure the Solaris environment to recognize the drive. Then you must configure your application to accept the new disk drive.

  1. Select a slot for the new disk drive.

    The Enterprise 250 server's internal disk array can accommodate up to six UltraSCSI disk drives. The figure below shows the system's six internal disk slots. Disk slots are numbered from 0 to 5. Select any available slot for the new disk drive.

    Figure 2-1 Slot Numbers for Internal Disk Array

    Graphic

  2. Insert the new disk drive into the selected slot.

    Refer to the Sun Enterprise 250 Server Owner's Guide for drive installation instructions.

  3. Use the drvconfig command to create a new device entry for the drive in the /devices hierarchy:


    # drvconfig
    

  4. Determine the raw physical device name for the slot that you selected.

    Consult the following table.

    Table 2-1 Slot Physical Device Names

    Disk Slot Number 

    Raw Physical Device Name  

    /devices/pci@1f,4000/scsi@3/sd@0,0:c,raw

    /devices/pci@1f,4000/scsi@3/sd@8,0:c,raw

    /devices/pci@1f,4000/scsi@3/sd@9,0:c,raw

    /devices/pci@1f,4000/scsi@3/sd@a,0:c,raw

    /devices/pci@1f,4000/scsi@3/sd@b,0:c,raw

    /devices/pci@1f,4000/scsi@3/sd@c,0:c,raw

  5. Use the ssaadm insert_device command to add the new device:


    # ssaadm insert_device physical_device_name
    ssaadm: warning: can't quiesce "/devices/pci@1f,4000/scsi@3/sd@b,0:c,raw": I/O error
    Bus is ready for the insertion of device(s)
    Insert device(s) and reconfigure bus as needed
    Press RETURN when ready to continue

    Here, physical_device_name is the full physical device name determined in Step 4.

    You can safely ignore the warning message since the Enterprise 250 SCSI bus does not require quiescing.

  6. Press Return to complete the hot-plug operation.

    The ssaadm command creates a new device entry for the drive in the /dev/dsk, and /dev/rdsk hierarchies. The new drive is assigned a logical device name of the form cwtxdysz, where:

    w corresponds to the SCSI controller for the disk drive x corresponds to the SCSI target for the disk drive y is the logical unit number for the disk drive (always 0) z is the slice (or partition) on the disk

    The logical device name assigned to the drive depends on the disk slot number where the drive is installed.

  7. To verify that the new disk has been created, type:


    # ls -lt /dev/dsk | more
    lrwxrwxrwx   1 root     root          41 Jan 30 09:07 c0t11d0s0 -> ../../devices/pci@1f,4000/scsi@3/sd@b,0:a
    lrwxrwxrwx   1 root     root          41 Jan 30 09:07 c0t11d0s1 -> ../../devices/pci@1f,4000/scsi@3/sd@b,0:b
    lrwxrwxrwx   1 root     root          41 Jan 30 09:07 c0t11d0s2 -> ../../devices/pci@1f,4000/scsi@3/sd@b,0:c
    lrwxrwxrwx   1 root     root          41 Jan 30 09:07 c0t11d0s3 -> ../../devices/pci@1f,4000/scsi@3/sd@b,0:d
    lrwxrwxrwx   1 root     root          41 Jan 30 09:07 c0t11d0s4 -> ../../devices/pci@1f,4000/scsi@3/sd@b,0:e
    lrwxrwxrwx   1 root     root          41 Jan 30 09:07 c0t11d0s5 -> ../../devices/pci@1f,4000/scsi@3/sd@b,0:f
    lrwxrwxrwx   1 root     root          41 Jan 30 09:07 c0t11d0s6 -> ../../devices/pci@1f,4000/scsi@3/sd@b,0:g
    lrwxrwxrwx   1 root     root          41 Jan 30 09:07 c0t11d0s7 -> ../../devices/pci@1f,4000/scsi@3/sd@b,0:h
    --More--(13%)

    The new disk and its logical device name appear at the top of the list. Check the file creation date to make sure it matches the current time and date. In the example above, the logical device name for the new disk is c0t11d0.

Configuring the New Disk Drive Within Your Application

Configure the new disk drive by following the instructions for your specific application:


Caution - Caution -

These procedures should be performed only by a qualified system administrator. Performing hot-plug operations on an active disk drive may result in data loss if performed incorrectly.


Configuring the New Disk Drive for a UNIX File System (UFS)

Use the following procedure to configure a slice (single physical partition) on a disk to be used with a UFS file system. For instructions about adding a file system to a Solstice(TM) DiskSuite(TM) (SDS) logical disk, refer to the documentation that came with your application.

  1. Verify that the device label meets your requirements.

    You can use the prtvtoc command to inspect the label for your disk. To modify the label, use the format command. Refer to the prtvtoc(1M) and format(1M) man pages for more information.

  2. Select a disk slice for your UFS file system and create a new file system on the slice:


    # newfs /dev/rdsk/cwtxdysz
    

    For example: newfs /dev/rdsk/c0t11d0s2

    Refer to the newfs(1M) man page for more information.

  3. If necessary, create a mount point for the new file system:


    # mkdir mount_point
    

    where mount_point is a fully qualified path name. Refer to the mount(1M) man page for more information.

  4. After the file system and mount point have been created, modify the /etc/vfstab file to reflect the new file system.

    See the vfstab(4) man page for more details.

  5. Mount the new file system using the mount command:


    # mount mount_point
    

    where mount_point is the directory you created.

The file system is ready to be used.

Adding a Disk to a Solstice DiskSuite Disk Set

You can use any disk you add to the system for Solstice DiskSuite (SDS) new or existing metadevices.

Refer to the Solstice DiskSuite documentation for information on configuring the disk drive.