bootable mirror does not boot

[Ceesjan van Hattum]

Hi,

I know that similair questions are already posted, but i just can't get it working.

My config is like this:
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c0t1d0 (14/0/0.1.0) -- Boot Disk
/dev/dsk/c1t1d0 (14/0/1.1.0) -- Boot Disk
/dev/dsk/c0t3d0 (14/0/0.3.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c0t1d0
/dev/dsk/c1t1d0
Root: lvol3 on: /dev/dsk/c0t1d0
/dev/dsk/c1t1d0
Swap: lvol2 on: /dev/dsk/c0t1d0
/dev/dsk/c1t1d0
Dump: lvol2 on: /dev/dsk/c0t1d0, 0

As you can see, the DUMP is (and cannot?) be mirrored.

Inserting the c0t3d0 into a
new system results in a panic,
because it says not to understand the dump-space.

I tried several things, know almost all commands available, but just can't get it working....

Please... get me smiling again ..
Regards,
Ceesjan

[Stefan Farrelly]

Removing c0t3d0 and putting it into another system and trying to boot from it will not work. Its not designed to work that way. Booting off c0t3d0 is knows its a mirror and will be looking for c0t1d0 and c1t1d0 - which arent present. Its not to do with the dump space, its perfectly normal for the Dump from lvlnboot to ONLY show the 1st boot device (primary - not mirrors).

To do what you want use Ignite to build a bootable tape which you can then use on your new system to create a working boot disk.

[Christopher McCray_1]

Hello,

Swap can be mirrored, and I do have this on my systems.

What is the output of setboot?

Chris

[Ceesjan van Hattum]

Ooops..
above information not correct. Ofcourse boot,root,swap on 3 disks, but Dump stays just like it is...

[S.K. Chan]

Your lvlnboot output looks ok. Dump LV is not suppose to be mirrored anyway and it uses lvol2 which is your primary swap I think. The c0t3d0 shows up in lvlnboot because it's a bootable disk. My question is how was c0t3d0 created as a bootable disk ?

[S.K. Chan]

I see ... that's because your dump was defined in c0t1d0, so obviously when c0t3d0 by itself on another system would not understand where to find the dump space. You have to define/set your dump space again by ..
# lvlnboot -d /dev/vg00/lvol2 /dev/vg00
so that the BDRA is updated (on the new system).

[Ceesjan van Hattum]

Staring with 2 mirrored-disks in vg00.
1. Insert 3rd disk
2. ioscan -fCdisk
3. insf -H 14/0/0.3
4. dd if=/dev/null of=/dev/dsk/c0t3d0 bs=1024k
5. vgextend /dev/vg00 /dev/dsk/c0t3d0
6. mkboot -l /dev/dsk/c0t3d0
7. lvlnboot -r /dev/vg00/lvol3
8. lvlnboot -b /dev/vg00/lvol1
9. lvlnboot -s /dev/vg00/lvol2
10. lvlnboot -d /dev/vg00/lvol2
11. lvlnboot -R
12. for LVOL in `vgdisplay -v vg00 | grep lvol | awk '{print $3}'1
do
echo "lvextend $LVOL"
lvextend -m 2 $LVOL /dev/dsk/c0t3d0
done
13. lvlnboot -v

..reducing is not to difficult either...

[nancy rippey]

Cessjan,
I do not create root mirrors but create alternate boot drives instead to load new servers. The only problem I have run into with this procedure it that the drive must be placed in the same slot on server b that it was created on in server a, otherwise it will not boot. This could possibly be your problem. I would make sure that you have the disk in the same slot as it was created on.

nancy

[S.K. Chan · Accepted solution]

You missed a step, after "mkboot -l" ..
# mkboot -a "hpux -lq" /dev/rdsk/c0t3d0
==> Add AUTO file in boot LIF area, "lq" option is to bypass quorum check.

And, correct me if I'm wrong, don;t you just want to lvextend 1 mirror copy to c0t3d0 instead of 2 ?

Forgot one more step (thanks Clay).. even way before you vgextend, did you pvcreated it with -B option ?
# pvcreate -B /dev/rdsk/c0t3d0

[Ceesjan van Hattum]

Between the 'dd' and the 'vgextend' there is a 'pvcreate -f -B' indeed.

I need to have this double mirror (-m 2), because the operational system always needs 1 mirror and cannot be booted (24/7 SLA).

I will try to include the mkboot -a "hpux -lq" and i will try to place the disk into the same slot as suggested.
The results will be posted..