lvlnboot error

[UniRock]

Hi All,

Following an unofficial procedure, I just tried a procedure to change root, boot, swap etc sizes and created another VG on another disk (/dev/vgroot).
Copied everything from vg00 to vgroot (on corresponding /new_root, /new_stand etc)
Configured LIF and BDRA on c3t2d0 using below commands:
# efi_fsinit -d /dev/rdsk/c3t2d0s1
# mkboot -e -l /dev/rdsk/c3t2d0
# mkboot -a "boot /new_stand/vmunix" /dev/rdsk/c3t2d0

Everything looked fine..but next I got below errors:


==========================================
# lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c2t1d0s2 (0/1/1/0.1.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c2t1d0s2
Root: lvol3 on: /dev/dsk/c2t1d0s2
Swap: lvol2 on: /dev/dsk/c2t1d0s2
Dump: lvol2 on: /dev/dsk/c2t1d0s2, 0

lvlnboot: The Boot Data Area is empty.
Boot Definitions for Volume Group /dev/vgroot:
The Boot Data Area is empty.


# lvlnboot -r /dev/vgroot/lvol3
lvlnboot: LIF information corrupt or not present on "/dev/dsk/c3t2d0".
Use the "mkboot" command to initialize the LIF area.
lvlnboot: LIF information corrupt or not present on "/dev/dsk/c3t2d0".
Use the "mkboot" command to initialize the LIF area.
lvlnboot: WARNING !! Creating a separate root volume, Use the -b option to the lvlnboot command to create a separate boot volume
lvlnboot: LIF information corrupt or not present on "/dev/dsk/c3t2d0".
Use the "mkboot" command to initialize the LIF area.
==========================================

(This is only a test box. Server is booting fine with vg00.)
I want to get the box boot from vgroot.

What shall I do next??

Thanks..

[Duncan Edmonstone]

>> What shall I do next??


Stop trying to do something by hand for which there is a tool:

http://www.hp.com/go/drd

HTH

Duncan

[Michael Steele_2]

Hi

There's an EFI partition that preceeds /stand and it won't be copied over unless you use dd or similar special EFI command.

When the firmware finishes up its POST, etc., it starts out at address zero on the boot disk. Address zero is the beginning of the EFI partition. The EFI contains all the boot disk metadata including the starting address of /stand.

So its, EFI, /stand, swap, /root. All read in sequencial order, all contiguous.

If you look on your copied over /vgroot, verify sequential / contiguous written data. Probably not, but maybe, and critical.

[sujit kumar singh]

hi

lvlnboot -b /d/ev/vgroot/lvol1
lvlnboot -s /dev/vgroot/lvol2
lvlnboot -r /dev/vgroot/lvol3
lvlnboot -d /dev/vgroot/lvol2
lvlnboot -vR
lvlnboot -v

this would create a lvlnboot informations for the /dev/vgroot.

yes as earlier said you can use DRD for the same.

regards
sujit

[UniRock]

Hi Again,

@Duncan
Thanks but I am aware of DRD, just wanted to know what went wrong in "unofficial procedure" that am trying to follow.

@Sujit
I tried same and got errors as can be seen in the initial thread.

@Michael
I have NOT copied slice s1 by dd but I did following:
#efi_fsinit -d /dev/rdsk/c3t2d0s1
#mkboot -e -l /dev/rdsk/c3t2d0
#mkboot -a "boot /new_stand/vmunix" /dev/rdsk/c3t2d0

Are these commands sufficient??
Or do I need to run dd to copy slice s1??

Thanks

[sujit kumar singh]

Hi
after
# efi_fsinit -d /dev/rdsk/c3t2d0s1
# mkboot -e -l /dev/rdsk/c3t2d0
please do this also first

pvcreate -B /dev/rdsk/c3t2d0s2



can you please post the O/P of following:
efi_ls -d /dev/rdsk/c2t1d0s1
vgdisplay -v /dev/vgroot
lvdisplay /dev/vgroot/lvol1
lvdisplay /dev/vgroot/lvol2
lvdisplay /dev/vgroot/lvol3
all these three should be Contiguous LVs.

[Torsten.]

You talk about an "unofficial procedure" - but what have you done? On what kind of server?

We can tell you about a missing step only, if we know what steps are done ...

[Michael Steele_2]

Hi

Yes, I would also like to see the unofficial procedure.