step by step process method to replace a FC drive

[Charles Holland]

Background L2000 running 11.00 6 A5158A FC adapters. 3 FC10s with at mixture of 18 and 36 GB drives. The drive in location c5t0d0 is having problems and is scheduled for replacement. Anyone have a tried and true method to quickly change out a FC drive? Do we have to fool with fcmsutil in any way. Drive is mirrored to c10t5d0.

P.S. This thread has been moevd from Disk to HP-UX > sysadmin. - Hp forum Moderator

[Jeff Schussele · Accepted solution]

Hi Charles,

First thing to do is determine just which td device you'll be working with - run
ioscan -fnC fc
Note the td instances - find the one in question

Next you'll need to know which N-Port-ID is assigned to that device - run

fcmsutil /dev/tdX devstat all

where X equals the td instance. Find the proper drive. You may want to do dd reads from the drive(s) to /dev/null to find it if you're not sure just which N-Port-ID is which drive.

Now replace the disk & when inserted & spun up - run

fcmsutil /dev/tdX replace_dsk Y

where X = td instance & Y = N-Port-ID

Then go about the normal procedure to restore the PV back to the VG - i.e.

vgcfgrestore vg_name /dev/dsk/cxtydz
vgchange -a y vg_name
vgsync vg_name

HTH,
Jeff

[Charles Holland]

Jeff,
Thanks for the reply. I retrieved it this morning and have been digesting it along with HP document KBRC00007265. I have also created a small 2 page file and attached it. If you would please review the file. I am going under the assumption that Loop_id 0 is synonomous with the disk of c5t0d0. From going over your response, and the HP DOC, it appears that my sequence of commands should be

replace disk a this point and allow to spin up

fcmsutil /dev/td0 replace_dsk 0x0000ef

At this point I need to do a
pvcreate -f /dev/rdsk/c5t0d0 I think

vgcfgrestore vg03 /dev/dsk/c5t0d0
vgchange -a y vg03

the vgchange should kick off a vgsync but if not

vgsync vg03

Thanks,
Charles

[Jeff Schussele]

Hi (again) Charles,

Looks good to me.
Yep I left out the pvcreate on the new PV - good catch.

I'm like you, I struggle a little determining which drive is which NPortID. But you look like you have it pinned down. You can use -l 0 (Loop Port ID)in place of the NPortID if you desire.
For ease of mind I'd still run

dd if=/dev/dsk/c5t0d0 of=/dev/null bs=2k

Just to pinpoint the drive in the array (should at least flash if not solid active) & to doublecheck that it's the failed unit - should get an error if you can't read from it.....

Rgds,
Jeff

[Iain F. Brown]

You will also get a message in syslog which will identify the nport id.
Iain