After mirror why we are making the auto file entry as "hpux -lq"

[Guna_2]

hi all

I have one doubt

By default the auto file entry in lif area is just hpux. But after root mirror why we are changing the entry to "hpux -lq"

Can any one explain me please.


Procedure for root mirror
The steps to mirror your boot volume are (PA-RISC):

1. Create a physical volume with a boot reserved area
"pvcreate -B /dev/rdsk/c1t6d0"

2. Add the physical volume to the root VG
"vgextend /dev/vg00 /dev/dsk/c1t6d0"

3. Use mkboot to place the boot utilities in the boot area and add the AUTO file
"mkboot /dev/rdsk/c1t6d0"
"mkboot -a "hpux -lq" /dev/rdsk/c1t6d0"

4. Use mkboot to update the AUTO file on the primary boot disk
"mkboot -a "hpux -lq" /dev/rdsk/c0t6d0"

5. Mirror the stand, root and swap logical volumes in order
"lvextend -m 1 /dev/vg00/lvol1 /dev/dsk/c1t6d0"
"lvextend -m 1 /dev/vg00/lvol2 /dev/dsk/c1t6d0"
"lvextend -m 1 /dev/vg00/lvol3 /dev/dsk/c1t6d0"

6. Then mirror the rest of your root logical volumes
"lvextend -m 1 /dev/vg00/lvol4 /dev/dsk/c1t6d0"
etc.

7. Modify your alternate boot path
"setboot -a 8/8.6.0 # use the path of your new boot disk"

8. Edit /stand/bootconf and add your new mirrored boot disk.

That's all there is to it. You may notice that I left out any
lvlnboot commands. That is because they are not
necessary - see the man page:

"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."

[Mridul Shrivastava · Accepted solution]

Hi Guna,

We change the auto file entry to hpux -lq because if one disk goes down or is no e operational, system can boot without quorum.

Quorum means more than 50% disks sould be available at the time of vg activation. So suppose if one of the root disk gone bad then system won't be able to boot since quorum is not present. If we change it with hpux -lq, in this case system will still boot and will not check the quorum.

If we don't specify the -lq then there is no use of mirroring, since if one of the disk goes down, system won't be able to boot.

I hoope this answers ur query.

[Guna_2]

Hi Mridul Shrivastava

Thank You

I understood now.

But even after mirroring if i put hpux only in my auto file my machine will not boot when one harddik fails.

But i think i can able to login in maintanance mode and i can reduce mirror.

Then my machine can boot as well as i can get the data also. Am i right?


Regards,
Guna

[Patrick Wallek]

If one disk fails and you have to reboot your machine, then you can still bring it all the way up without going into LVM maintenance mode.

When you 'bo pri' or 'bo alt' you are asked "Interact with IPL?" . In this case you want to answer yes. When you get the IPL prompt you type in 'hpux -lq'. This will now boot the system as if you had 'hpux -lq' as the AUTO string.

[Guna_2]

Thnks to both of u.

Now i understood very clearly

Thanks once again

Regards,
Guna

[Torsten.]

Hi,

this is totally up to you.

If you put only "hpux" in the AUTO file, your server will not boot if one of the 2 boot disks fail.
In this case you need to start the OS manually with
ISL> hpux -lq

Some admins wants the server to start by itself (using the "-lq" switch in the AUTO file).

Others wants to be alarmed by a stopped boot and want to start the server manually.

As said before, this is up to you.