boot from vg00 disk image that has a different path

[Adam Garsha]

I've got a block level copy of my original root/boot disk. The disk that holds the image has a different hardware path then the original root/boot disk.

I am working on an integrity system.

I can boot the image disk with 'boot vmunix -lm', and I have exported vg00 and imported vg00 with the correct device name.

If I try to boot from the image using 'boot vmunix' from the image disks hpux boot loader, (after having corrected LVM on the image), the system will boot the original disk rather then my image... even when I explicitly choose my image disk in EFI boot config options -> boot from file -> pick the hpux boot loader -> 'boot vmunix'

This leads me to think that some metadata on the image is pointing over to the path of the original disk's OS partition(?) or that I didn't fully fix LVM so it is going back to the default??

Any ideas how I can boot from an disk image that has a different path then the original disk when using Integrity/EFI ?

Note: when booted from the image (via 'boot vmunix -lm, I can mount-up and activate the image's version of vg00 lvols without any issue).

This is obviously a test box that I am screwing around with here.

[Robert-Jan Goossens]

Adam,

Check this doc.

Title: How do I boot from an alternate path on an IA64 box ?
Document ID: KBRC00013198

http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000080024216

Regards,
Robert-Jan

[Adam Garsha]

Maybe to make this more clear:

1.) I dd'd my vg00's physical disk to a copy disk.
2.) The copy disk has a different path then the source disk
3.) How can I boot from my copy disk without having to physically move it to the original path

This is what I thought I had to do:
a.) using EFI boot into LVM maint mode using the EFI/HPUX boot loader on the image disk
b.) change LVM vg00 using export/import to point to the correct copy disk's device file
c.) ok, now reboot with just a regular 'boot vmunix'....

The problem is that "c." always results with me actually booting the original image... even when I explicity choose the image's EFI/HPUX boot loader.

[Torsten.]

Sounds reasonable. vgexport / vgimport is the right way to do this.

Make sure you don't mix up the disks while doing your actions.

After booting the "new" disk in lm mode, run "insf -e" and vgexport/import it. This should work - Inever done this with Integrity yet.

Did you the "dd" with cxtxdx or cxdxtxsx device? (note "sx")

You can also try to make the partitions ("idisk" command) and copy only partition 2. Make the first bootable with "mkboot -l -e ..."

[Eric SAUBIGNAC]

Hi all,

I think that you have miss lvlnboot -R after reimporting vg00, no ?

Hope this will help

Eric

[Adam Garsha]

I had made the partitions with idisk, then dd'd the whole raw/char device to the copy disk.

I think that maybe I need to do something with lvlnboot when I am in '-lm' mode (while booted off the copy)?

remember that I started with an ~exact block level image of my source drive. So all the meta data on the source is on the image. I am trying to fix any meta data that cares about physical disk path.

[Adam Garsha]

real bad perf with itrc today... sorry. I will try that lvlnboot -R deal and let you know.

[Eric SAUBIGNAC]

Adam, that's exactly my suggestion ... ;-)

[Torsten. · Accepted solution]

I guess you should only copy cxtxdx**s2** to cydyty**s2** and populate the "s1" section manually.

e.g.

efi_fsinit -d /dev/rdsk/c2t1d0s1

mkboot -e -l /dev/rdsk/c2t1d0

check:

efi_ls -d /dev/rdsk/c2t1d0s1

set the needed values after booting and importing the disk:

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

This should work.