detailed steps of rx6600 failed root disk replace(11.23)

[Torsten.]

Get the

HP 8 Internal Port SAS Controller Users Guide

document and follow the chapter

Replacing a Disk Online Using sasmgr replace_tgt or io_redirect_dsf

[Torsten. · Accepted solution]

New link (hard to find since docs.hp.com is dead):

http://h20000.www2.hp.com/bc/docs/support/SupportManual/c02017117/c02017117.pdf



Don't forget to use "idisk" to create the partitions and populate partition 1!

[stephen peng]

Torsten,
Oh, I never learn this characteristic of SAS disk. From the user guide, new SAS disk would be arranged a new HW ID, so the device file would be differed, right? and rx6600 employs this 8 Internal Port SAS Controller, right?

regards
Stephen

[Torsten.]

Yes, unless you are using hardware RAID with this default controller or you have an optional P400 smartarray. In this bozh cases you just need to swap the disks - done.

[stephen peng]

maybe much slower, but I do consider the lvreduce-vgreduce-replace failed disk- vgextend-lvextend way was a safer way when one was not an HP expert!

[Anoop Sivan]

Hello Stephen,

SAS controllers use a different addressing scheme than parallel SCSI like U320 or SCSI-2.
Where SCSI ID and therefore disk slot numbers were important, SAS uses a unique address of the disks themselves to identify
the disks as part of a LUN (logical unit) or an HP-UX special device file like /dev/dsk/cxtxdx.
You can take a disk out of one slot (referred to as bays) and put it in a different slot or bay.
The controller finds it and presents the disk to the O/S with the same special device file.
This does complicate the procedure needed for replacing a failed disk.

# sasmgr get_info -D /dev/sasd0 -q lun=all -q lun_locate

Turn on the diskâ s locator LED to ensure the correct disk is removed.

1. Deactivate the failed disk

# pvchange -a n /dev/dsk/cxtxdxs2

2. Confirm the failed disk (eg: here we use sas bay 1)

# sasmgr get_info -D /dev/sasd0 -q lun=all -q lun_locate
# sasmgr get_info -D /dev/sasd0 -q raid


3. Turn on the LED indicator of the failed disk for replacing

# sasmgr set_attr -D /dev/sasd0 -q lun=/dev/rdsk/cxtxdx -q locate_led=on
# sasmgr get_info -D /dev/sasd0 -q lun=all -q lun_locate



At this point the failed disk is pulled out of the server and new disk is inserted in the same bay.
The server should not be rebooted or taken down between the time the disk fails and the time the new disk is inserted


4.Note the necessary info, below commands will provide the current disk status.

ioscan -fnC disk

sasmgr get_info -D /dev/sasd0 -q phy=all

sasmgr get_info -D /dev/sasd0 -q raid

sasmgr get_info -D /dev/sasd0 -q lun=all -q lun_locate


5.Associate old device with a new SAS target (whenever a sas disk is replaced the target gets changed)

# sasmgr replace_tgt -D /dev/sasd0 -q old_dev=/dev/dsk/cxtxdx \
-q new_tgt_hwpath=0/4/1/0.0.0.11.0 (change the h/w path for your new disk)

Now you can proceed with the same usual integrity root disk replacement.

create EFI partision-->make s2 partision bootable --> add to vg00 -->restore pvra & vgra....

Note:
=====
If the server has been rebooted for any reason, the special device file is stale and is no longer visible with ioscan, and the
sasmgr replace_tgt will not work unless you have at least B.11.23.03.01 of the driver released January 2007.
Use swlist to check the software driver revision, and upgrade to B.11.23.03.01 or later.

# swlist -l bundle CommonIO
CommonIO B.11.23.03.01 CommonIO

# swlist -l bundle SerialSCSI-00
SerialSCSI-00 B.11.23.03.01 PCI-X SerialSCSI


This software can be obtained free from http://software.hp.com.

>>HP-UX 11i general

o HP-UX Common Bundle
o HP-UX Serial SCSI Driver


Anoop

[stephen peng]

go to my recent thread please:
http://forums13.itrc.hp.com/service/forums/questionanswer.do?threadId=1456707