PRIMECLUSTER DR/PCI Hot Plug User's Guide 4.5

2.2.3 Re-attaching the disk

1. Check the name of the disk device that is connected to the system board. For details, see "Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 Domain Configuration Guide" or "DR User's Guide."

2. When the target disk is the SPARC M10 and M12 internal disk (other than ZFS mirroring)

   1. Registering a disk in the disk class

      Register the target disk in the disk class again.

      # sdxdisk -M  -c class01  -d c1t1d0=disk01

      You can check if the disk has been registered using the following command.

      # sdxinfo  -D
       OBJ    NAME    TYPE   CLASS   GROUP   DEVNAM  DEVBLKS  DEVCONNECT       STATUS
       ------ ------- ------ ------- ------- ------- -------- ---------------- -------
       disk   disk01   undef  class01  *     c1t1d0  8493876   *               ENABLE
       disk   disk02   mirror class01  grp01 c1t2d0  8493876   *               ENABLE
       #

   2. Adding a disk to the mirror disk croup

      Add the target disk to the mirror disk group again.

      # sdxdisk -C  -c class01  -g grp01  -d disk01

      Check if the disk has been registered using the following command.

      # sdxinfo  -D
       OBJ    NAME    TYPE   CLASS   GROUP   DEVNAM  DEVBLKS  DEVCONNECT       STATUS
       ------ ------- ------ ------- ------- ------- -------- ---------------- -------
       disk   disk01   mirror class01  grp01 c1t1d0  8493876   *               ENABLE
       disk   disk02   mirror class01  grp01 c1t2d0  8493876   *               ENABLE
       #

3. When the target disk is not the SPARC M10 and M12 internal disk (other than ZFS mirroring)

   1. Check the disk class and the SDX disk name after confirming that the disk is under the GDS control and in the SWAP state.

      # sdxinfo  -D | grep c1t1d0
      disk   disk01  mirror class01    grp01 c1t1d0   8493876 *            SWAP

   2. Attach the disk again using the "sdxswap" command.

      # sdxswap  -I  -c class01  -d disk01

   3. Check if the disk has been attached (whether the disk has entered ENABLE).

      # sdxinfo  -D  -o disk01 
      OBJ     NAME     TYPE    CLASS   GROUP   DEVNUM  DEVBLKS  DEVCONNECT STATUS
        ------ ------- ------ ------- ------- ------ -------- ---------- ------
      disk    disk01   mirror class01  grp01  c1t1d0  8493876    *         ENABLE

4. When system disk was mirrored by using GDS (ZFS mirroring)

   1. Register the target disk in the disk class again.

      # sdxdisk -M -c class01 -a type=root -d c1t1d0=disk01:keep

   2. Attach the target disk to the disk group again.

      # sdxdisk -C -c class01 -g grp01 -d disk01 -v 0=v01:on

   3. Add the GDS volume to the ZFS mirroring configuration.

      # zpool attach rpool /dev/sfdsk/class01/dsk/v02 /dev/sfdsk/class01/dsk/v01

   4. Check the status of the mirror configuration. Check if all STATEs are ONLINEs.

      # zpool status rpool
        pool: rpool
       state: ONLINE
        scan: resilvered 17.8G in 0h3m with 0 errors on Wed Apr 16 14:05:30 2014
      config:
      
              NAME                               STATE     READ WRITE CKSUM
              rpool                              ONLINE       0     0     0
                mirror-0                         ONLINE       0     0     0
                  /dev/sfdsk/class01/dsk/v02     ONLINE       0     0     0
                  /dev/sfdsk/class01/dsk/v01     ONLINE       0     0     0
      
         errors: No known data errors

   5. Install the boot block to the GDS volume.

      For the following environments, do not perform this procedure:

      • Using Solaris 10 and the applying the kernel patch 144500-19 or later

      • Solaris 11 11/11 or later

      # installboot -F zfs /usr/platform/`uname -i`/lib/fs/zfs/bootblk /dev/sfdsk/class01/rdsk/v01