topic Re: problem with Physical volume - mirroring in Operating System - HP-UX

problem with Physical volume - mirroring

Radim Jarosek — Fri, 18 Aug 2000 09:11:51 GMT

Hi,

I have tried to install mirroring.
I did via SAM and then I found that SAM
not created boot disk.
I would like to re`move physical volume from VG. How can I do it ?

Radim

Re: problem with Physical volume - mirroring

Stefan Farrelly — Fri, 18 Aug 2000 09:26:03 GMT

to remove the physical volume from the VG do;
vgreduce vgXX /dev/dsk/cXXXXX

One you install the mirroring software, even via Sam, you still have a separate task to go ahead and mirror your boot disk. You can do this via sam or manually by simply doing; lvextend -m 1 /dev/vg00/lvolX /dev/dsk/cXXXX (the new physical volume you added). Do this in order for each lvol in vg00, eg. lvol1, lvol2.... and your done. Do an lvlnboot -v command to verify both disks are now bootable.

Re: problem with Physical volume - mirroring

Radim Jarosek — Fri, 18 Aug 2000 09:42:24 GMT

Stefan :

thanks

Radim

Re: problem with Physical volume - mirroring

James R. Ferguson — Fri, 18 Aug 2000 09:43:05 GMT

Radim:

I seem to recall that SAM can't create boot disks. You can do this manually as:

# pvcreate -B /dev/rdsk/cxtxdx
# vgextend /dev/vg00 /dev/dsk/cxtxdx
# mkboot /dev/rdsk/cxtxdx
# mkboot -a "hpux" /dev/resk/cxtxdx
...
As Stefan sadi, verify the boot info with
# lvlnboot -v

...JRF...

Re: problem with Physical volume - mirroring

Radim Jarosek — Fri, 18 Aug 2000 10:11:35 GMT

James :

I looked to manual and found :
mkboot -a "hupx (52.3.0;0)/stand/vmunix" /dev/rdsk/cxtxdx

Do you know what's mean "(52.3.0;0)" ?

Radim

Re: problem with Physical volume - mirroring

Antoanetta Naghiu — Fri, 18 Aug 2000 10:51:35 GMT

It is the hardware address (see ioscan -fnC disk) on Hardware path filed. The commands have similar result, they just as input the hw. path respectivelly the raw device for the disk.

Re: problem with Physical volume - mirroring

Radim Jarosek — Fri, 18 Aug 2000 11:10:31 GMT

Antoanetta :

So when I have output from ioscan :
--------------------------------------------

Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
disk 0 8/12.6.0 sdisk CLAIMED DEVICE HP C3325W
/dev/dsk/c0t6d0 /dev/rdsk/c0t6d0
disk 1 8/16/5.0.0 sdisk CLAIMED DEVICE DEC RRD45 (C) DEC
/dev/dsk/c1t0d0 /dev/rdsk/c1t0d0
disk 2 8/16/5.5.0 sdisk CLAIMED DEVICE DEC RZ28M (C) DEC
/dev/dsk/c1t5d0 /dev/rdsk/c1t5d0

------------------------------------------

mkboot -a "hpux -lq (5.0.0;0)/stand/vmunix" /dev/rdsk/c1t1d0

Is it correct?

Radim

Re: problem with Physical volume - mirroring

John Palmer — Fri, 18 Aug 2000 11:12:06 GMT

Radim,

You don't need to include the full hardware path or the name of the kernel file in the mkboot command.

mkboot -a "hpux" /dev/rdsk/cxtxdx

is sufficient.

You might want to consider changing that to
mkboot -a "hpux -lq" /dev/rdsk/cxtxdx

in order to ensure that the system will still boot from a mirrored disk even after the total failure of the other disk. This overrides quorum enforcement of the root volume group (see man vgchange)

see also man hpux.

Regards,
John

Re: problem with Physical volume - mirroring

James R. Ferguson — Fri, 18 Aug 2000 11:29:22 GMT

Radim:

Sorry for the delay. John is right. Add the "-lq" else if you are missing one of the two disks the quorum requirement won't be met and you won't boot. I never bother with the hardware path part. Thanks, John.

...JRF...

Re: problem with Physical volume - mirroring

Radim Jarosek — Fri, 18 Aug 2000 11:37:36 GMT

Hi all,

I've set mirroring and I hope it will be correct :-)

Thanks a lot and greetings

Radim

Re: problem with Physical volume - mirroring

Antoanetta Naghiu — Fri, 18 Aug 2000 13:23:32 GMT

The documentation that you talked about, I suppose is an old one (I guess for an E-class machine) and probably for HP-UX 9.x. It is to long to explain, if you do a search in the Technical Database for hardware address, you'll get more details. The hardware path is based on hardware architecture, the slot where the card is plug in... I have a 120 pages document (sorry, just in paper) about hardware address...