Disk Replacement - Integrity (Itanium) - SAS Disk Replacement
Please follow these instructions. In this example, the failed
drive is c1t4d0 and it's corresponding SAS controller name sasd0:
1.
Check current configuration state:
#
ioscan -fnH 0/4/1/0
Class I
H/W Path Driver S/W State H/W Type Description
===============================================================================
escsi_ctlr 0
0/4/1/0 sasd CLAIMED INTERFACE HP
PCI/PCI-X SAS MPT Adapter
/dev/sasd0
ext_bus 1
0/4/1/0.0.0 sasd_vbus CLAIMED INTERFACE SAS Device Interface
target 4
0/4/1/0.0.0.4 tgt NO_HW DEVICE
disk 5
0/4/1/0.0.0.4.0 sdisk NO_HW DEVICE HP
DG036A8B5B
/dev/dsk/c1t4d0 /dev/rdsk/c1t4d0
/dev/dsk/c1t4d0s1
/dev/rdsk/c1t4d0s1
/dev/dsk/c1t4d0s2
/dev/rdsk/c1t4d0s2
/dev/dsk/c1t4d0s3
/dev/rdsk/c1t4d0s3
target 5
0/4/1/0.0.0.7 tgt CLAIMED
DEVICE
disk 8
0/4/1/0.0.0.7.0 sdisk CLAIMED DEVICE HP
DG036A9BB6
/dev/dsk/c1t7d0
/dev/rdsk/c1t7d0
/dev/dsk/c1t7d0s1
/dev/rdsk/c1t7d0s1
/dev/dsk/c1t7d0s2 /dev/rdsk/c1t7d0s2
/dev/dsk/c1t7d0s3
/dev/rdsk/c1t7d0s3
|
Note: It's important to save also the output of "sasmgr get_info -D
/dev/sasd# -q raid=all", this way you can compare the original disk with
the replacement disk using the bay number, since the target id will always
change and can't be used as a comparison strategy when replacing SAS disks.
2.
If the physical volume is part of an
existing volume group, temporaly disable LVM I/O to the drive:
#
pvchange -a n /dev/dsk/c1t4d0
|
3.
Turn on the disk’s locator LED to
ensure the remove the correct disk from the sas bay.
#
sasmgr set_attr -D /dev/sasd0 -q lun=/dev/rdsk/c1t4d0 -q locate_led=on
Verify
that only the failed drive locate LED is set to ON.
#
sasmgr get_info -D /dev/sasd0 -q lun=all -q lun_locate
/dev/rdsk/c1t2d0 0/4/1/0.0.0.2.0 1 3
OFF
/dev/rdsk/c1t3d0 0/4/1/0.0.0.3.0 1 4
OFF
/dev/rdsk/c1t4d0 0/4/1/0.0.0.4.0 1
5 ON
/dev/rdsk/c1t7d0 0/4/1/0.0.0.7.0 1 8
OFF
RAID
VOL ID is 4 :
/dev/rdsk/c1t10d0 0/4/1/0.0.0.10.0
Physical
disks in volume are :
1
1 OFF HP DG072A9BB7 HPD0
1
2 OFF HP DG072A9BB7 HPD0
|
4.
At this point the drive in bay 5 can
be physically remove and replace with the new drive.
5.
Running ioscan again will output the
new disk HW path, 0/4/1/0.0.0.11.0 in this example. Failed drive will still
show NO_HW. This behavior is normal:
#
ioscan -fnH 0/4/1/0
Class I
H/W Path Driver S/W State H/W Type Description
===============================================================================
escsi_ctlr 0
0/4/1/0 sasd CLAIMED INTERFACE HP
PCI/PCI-X SAS MPT Adapter
/dev/sasd0
ext_bus 1
0/4/1/0.0.0 sasd_vbus
CLAIMED INTERFACE SAS Device Interface
target 4
0/4/1/0.0.0.4 tgt NO_HW DEVICE
disk 5
0/4/1/0.0.0.4.0 sdisk NO_HW DEVICE HP
DG036A8B5B
/dev/dsk/c1t4d0
/dev/rdsk/c1t4d0
/dev/dsk/c1t4d0s1
/dev/rdsk/c1t4d0s1
/dev/dsk/c1t4d0s2 /dev/rdsk/c1t4d0s2
/dev/dsk/c1t4d0s3
/dev/rdsk/c1t4d0s3
target 5
0/4/1/0.0.0.7 tgt CLAIMED DEVICE
disk 8
0/4/1/0.0.0.7.0 sdisk CLAIMED DEVICE HP
DG036A9BB6
/dev/dsk/c1t7d0
/dev/rdsk/c1t7d0
/dev/dsk/c1t7d0s1
/dev/rdsk/c1t7d0s1
/dev/dsk/c1t7d0s2
/dev/rdsk/c1t7d0s2
/dev/dsk/c1t7d0s3 /dev/rdsk/c1t7d0s3
target 7
0/4/1/0.0.0.11 tgt CLAIMED DEVICE
disk 12
0/4/1/0.0.0.11.0 sdisk CLAIMED DEVICE HP
DG036A8B5B
|
6.
The new disk will use a different SAS
address (Similar to WWN on fibre channel connections). The old device special
file name must be redirected to the new HW path. Issue the following command to
update the configuration:
#
sasmgr replace_tgt -D /dev/sasd0 -q old_dev=/dev/dsk/c1t4d0 -q
new_tgt_hwpath=0/4/1/0.0.0.11.0
WARNING:
This is a DESTRUCTIVE operation.
This
might result in failure of current I/O requests.
Do
you want to continue ?(y/n) [n]...
LUN
has been replaced with new Target.
|
7.
Verify the system state with ioscan:
#
ioscan -fnH 0/4/1/0
Class I
H/W Path Driver S/W State H/W Type Description
===============================================================================
escsi_ctlr 0
0/4/1/0 sasd CLAIMED INTERFACE HP
PCI/PCI-X SAS MPT Adapter
/dev/sasd0
ext_bus 1
0/4/1/0.0.0 sasd_vbus
CLAIMED INTERFACE SAS Device Interface
target 4
0/4/1/0.0.0.4 tgt CLAIMED DEVICE
disk 5
0/4/1/0.0.0.4.0 sdisk CLAIMED DEVICE HP
DG036A8B5B
/dev/dsk/c1t4d0
/dev/rdsk/c1t4d0
/dev/dsk/c1t4d0s1
/dev/rdsk/c1t4d0s1
/dev/dsk/c1t4d0s2
/dev/rdsk/c1t4d0s2
/dev/dsk/c1t4d0s3 /dev/rdsk/c1t4d0s3
target 5
0/4/1/0.0.0.7 tgt CLAIMED DEVICE
disk 8
0/4/1/0.0.0.7.0 sdisk CLAIMED DEVICE HP
DG036A9BB6
/dev/dsk/c1t7d0
/dev/rdsk/c1t7d0
/dev/dsk/c1t7d0s1 /dev/rdsk/c1t7d0s1
/dev/dsk/c1t7d0s2
/dev/rdsk/c1t7d0s2
/dev/dsk/c1t7d0s3
/dev/rdsk/c1t7d0s3
target 7
0/4/1/0.0.0.11 tgt NO_HW DEVICE
disk 12
0/4/1/0.0.0.11.0 sdisk NO_HW
DEVICE HP DG036A8B5B
|
Note: The S/W State of the H/W Path 0/4/1/0.0.0.4.0 changed to
CLAIMED, and the S/W State of the H/W Path 0/4/1/0.0.0.11.0 changed to NO_H/W.
The hardware path 0/4/1/0.0.0.11.0 will remain as NO_HW in the ioscan output
until the system next reboot.
8.
Now you must restore LVM mirroring to
the new disk. If this is a bootable volume group, it involves creating the EFI
partitions and formatting partition 1; changing the autoboot file if this was
the mirror (not necessary for the primary disk); and, restoring the LVM
information to EFI partition 2.
9.
Note: Only necessary for vg00.
Rewrite the boot information to the EFI Boot Menu so the system will be able to
boot from the new path.
#
setboot
Primary
bootpath : 0/4/1/0.0.0.7.0
HA
Alternate bootpath : <none>
Alternate
bootpath : <none>
Autoboot
is ON (enabled)
#
setboot -h 0/4/1/0.0.0.4.0
#
setboot
Primary
bootpath : 0/4/1/0.0.0.7.0
HA
Alternate bootpath : 0/4/1/0.0.0.4.0
Alternate
bootpath : 0/0/2/0
Autoboot
is ON (enabled)
|
No comments:
Post a Comment