What is the procedure to identify a failed hard disk and for replacing the same in LVM.

[kunjuttan]

Hi all,
What is the procedure to identify a failed hard disk and for replacing the same in LVM?Hoping step by step procedure.

[Torsten. · Accepted solution]

This helps:

http://docs.hp.com/en/5991-1236/When_Good_Disks_Go_Bad_WP.pdf

[cnb]

This should help:

http://www.docs.hp.com/en/5991-1236/When_Good_Disks_Go_Bad_WP.pdf


If it does:
http://forums.itrc.hp.com/service/forums/helptips.do?#33


Rgds,

[cnb]

LOL. Beat me to it!

[Johnson Punniyalingam]

>>What is the procedure to identify a failed hard disk and for replacing the same in LVM?Hoping step by step procedure.<<<<<

ioscan -fnC disk|grep NO -> look for not claimes Hard disk

1. vgreduce the failed disk

replace the faulty disk

2. pvcreate

3. vgextend /dev/vgxx

mirror back all the logica volumes

4.lvextend -1 /dev/vgxx/lvolxx /dev/dsk/cxtxdx



Most recommended follow official document

http://docs.hp.com/en/5991-1236/When_Good_Disks_Go_Bad_WP.pdf

[kunjuttan]

Thanks to all.I would like to ask Mr.Johson that if the ioscan output shows an unclaimed ststus for a particular disk,can we able to confirm that the particular disk is having problem?

[kunjuttan]

Thanks to all.I would like to ask Mr.Johson that if the ioscan output shows an unclaimed ststus for a particular disk,can we able to confirm that the particular disk is having problem?
And one more thing-the ioscan command will only give the H?W path of the disk.How can we able to identify the devicefile attatched to it?

[Torsten.]

We need to see

# model
# ioscan -fn

first.

Follow the steps in the document!

[Matti_Kurkela]

In general, NO_HW in ioscan means that the system can no longer get any response at all from that device: the system thinks the device is not there any more.

If the device is in fact still connected and properly powered on, and its configuration has not been changed, that usually means the device has experienced a total failure, i.e. "died".

Sometimes a NO_HW indication is because of an intentional configuration change: for example, when you unpresent LUNs from a SAN, HP-UX will show the unpresented LUNs in NO_HW state. You can use the "rmsf" command to clean up such intentionally removed devices: in effect, you're telling the system that the device isn't expected to return to a working state.

MK

[kunjuttan]

Thanks.
And one more thing-the ioscan command will only give the H?W path of the disk.How can we able to identify the devicefile attatched to it?