Extra LIF files? Mirrored drives.

[imrichar]

I have the following on my primary boot drive:

ODE
MAPFILE
SYSLIB
CONFIGDATA
SLMOD2
SLDEV2
SLDRV2
SLSCSI2
MAPPER2
IOTEST2
PERFVER2
PVCU
SSINFO
ISL
AUTO
HPUX
PAD
LABEL

And only the following on my newly created mirror drive:

ISL
AUTO
HPUX
PAD
LABEL

I realize that the mirror drive has the necessary files to boot the system, but is there any value in bringing the other files over via lifcp? Is there any documentation you could reference that gives me detailed information about what each function is?

Thanks!

[Steven E. Protter]

Shalom,

To be certain, schedule and run a boot test.

SEP

[Torsten.]

Your setup is OK.

The "extra" files are the offline diagnostics, not needed for normal operation.


Just in case you need them one day, you need to download, use and/or install from this ISO:

http://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=PA0809

[Deepak Kr]

Torsten is absolutely right here. The remaining/extra files that you see belong to HP offline diagnostics.

Can you give a brief here how you have created mirror.

Also is it IA or PA-RISC server?

Use model to confirm....

[Torsten.]

Must be PA-Risc.

Offline diags on an Integrity looks different:

# efi_ls -d /dev/rdsk/c2t0d0s1 /EFI
FileName Last Modified Size
. 3/20/2008 0
.. 3/20/2008 0
HPUX/ 3/20/2008 0
Intel_Firmware/ 3/20/2008 0
DIAG/ 3/20/2008 0
HP/ 3/20/2008 0
TOOLS/ 3/20/2008 0

total space 523251712 bytes, free space 413958144 bytes

[imrichar]

I performed the following steps to create my mirror:

pvcreate -B /dev/rdsk/c2t2d0
vgextend /dev/vg00 /dev/dsk/c2t2d0
mkboot /dev/rdsk/c2t2d0
mkboot -a "hpux -lq" /dev/rdsk/c2t2d0
mkboot -a "hpux -lq" /dev/rdsk/c1t2d0
lvextend -m 1 /dev/vg00/lvol1 /dev/dsk/c2t2d0
lvextend -m 1 ... through lvol10
setboot -a 0/0/2/0.2.0
added "l /dev/dsk/c2t2d0" to my /stand/bootconf

If you have any additional suggestions to my procedure I'd gladly take them!

[imrichar]

Sorry, it is PA-RISC. rp5470 in particular.

Thanks!

[Torsten.]

It looks complete and right.

I would only add

lvlnboot -r /dev/vg00/lvol3
lvlnboot -b /dev/vg00/lvol1
lvlnboot -s /dev/vg00/lvol2
lvlnboot -d /dev/vg00/lvol2

Consider to boot from as a final test.


As said before, IMHO you don't need to install the offline diags.

[imrichar]

Thanks Torsten,

Based on this post from Pete Randall (http://forums12.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1220626102732+28353475&threadId=1091081) I was under the impression that lvlnboot commands were no longer required with 10.0? I am running 11.0. Could you confirm?

"This command should be run in recovery mode (-R)
whenever the configuration of the root volume group is
affected by one of the following commands: lvextend,
lvmerge, lvreduce, lvsplit, pvmove, lvremove, vgextend,
or vgreduce (see lvextend(1M), lvmerge(1M), lvreduce(1M),
lvsplit(1M), pvmove(1M), lvremove(1M), vgextend(1M), and
vgreduce(1M)). Starting with HP-UX Release 10.0, this is
done automatically."

Thanks!

[Torsten.]

All the manuals lists "lvlnboot -R", for example this:

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

(see appendix)

but I prefer the single steps.
IMHO better to do it now than having problems later ...

[Duncan Edmonstone]

Here's an excerpt from an old doc of mine on mirroring the boot disks on PA-RISC systems:


To use offline diagnostics, it is important to ensure that all the diagnostics are installed on the LIF area of both boot disks. The following short script will copy over all the relevant utilities:

for lif in $(lifls )
do
lifls | grep -q ${lif}
if [ $? -ne 0 ] ; then
lifcp :${lif} :${lif}
fi
done

so for your config we would do:

for lif in $(lifls /dev/dsk/cXtYdZ)
do
lifls /dev/dsk/c2t2d0 | grep -q ${lif}
if [ $? -ne 0 ] ; then
lifcp /dev/dsk/cXtYdZ:${lif} /dev/dsk/c2t2d0:${lif}
fi
done

Replacing cXtYdZ with your own original boot disk


HTH

Duncan