topic Re: Moving Disk to another server in Operating System - HP-UX

Moving Disk to another server

ben10_1 — Wed, 25 May 2011 09:34:58 GMT

Hello forum,

I have moved the disk from rx2600 server(hpux 11.31)and insert it into another server with same specs.(only one disk exist on the server)

I ended up by crashing the OS. Don't worry it's a LAB :)

My question:
Is there a document or procedure that allow to prepare a new disk in the lab, and later on to just plug the disk in the client server and boot successfully.

If yes,this will be the fastest installation I have ever performed on site.

Thank you.

Re: Moving Disk to another server

Hakki Aydin Ucar — Wed, 25 May 2011 11:49:48 GMT

I am not sure what exactly you are looking for but, You can use this famous doc:
When_Good_Disks_Go_Bad_WP
http://bizsupport2.austin.hp.com/bc/docs/support/SupportManual/c01911837/c01911837.pdf

besides, in short, you have to see the new disk(s) by issuing command ;
# ioscan -fnCdisk
if you cannot see try ;
# insf -e

Re: Moving Disk to another server

klb — Wed, 25 May 2011 14:05:43 GMT

Build your system the way you want it, then mirror vg00 OS boot disk ( must prepare the disk first as a boot disk and place the boot images on it ), sync that mirror, shutdown.

Take out the new disk you just mirrored to and go install it into another identical piece of hardware and boot it, stop the boot and do a search for bootable drives, find it and boot.

That will work on PA-RISC architecture. You may need to tweek it a bit to make it work on Itanium.

See attached file for details on doing the above.

-klb

Re: Moving Disk to another server

klb — Wed, 25 May 2011 14:11:31 GMT

file attachment didn't seem to work so....

mirror OS:

Assuming your new disk is c0t5d0:

# pvcreate -B /dev/rdsk/c0t5d0
# vgextend /dev/vg00 /dev/dsk/c0t5d0

Use mkboot to place boot utilities in the boot area:

# mkboot -l /dev/rdsk/c0t5d0

Use mkboot to add an AUTO file in boot LIF area:

# mkboot -a "hpux" /dev/rdsk/c0t5d0

Or, use the -lq option to allow your system to boot in the event that one of your disks is unavailable, resulting in a loss of quorum.

# mkboot -a "hpux -lq" /dev/rdsk/c0t5d0

NOTE: Use the -lq option when your root volume group contains only 2 disks. If more than 2 disks are in the root volume group, the -lq option is not needed as quorum will be maintained even if 1 disk fails.

You can check the contents of the AUTO file with

# lifcp /dev/rdsk/c0t5d0:AUTO -

If you choose, you can set the alternate boot path variable according to e.g.

# setboot -a 8/0/19/0.5.0

You can determine the hardware address of the disk that will become the mirror disk with 'ioscan -fnC' disk. To check use setboot without any arguments.

Mirror the boot logical volume, primary swap logical volume, root logical volume and other logical volumes as needed, to the above disk in the following sequence

# lvextend -m 1 /dev/vg00/lvol1 /dev/dsk/c0t5d0
# lvextend -m 1 /dev/vg00/lvol2 /dev/dsk/c0t5d0
# lvextend -m 1 /dev/vg00/lvol3 /dev/dsk/c0t5d0
# lvextend -m 1 (additional LV)

To check use lvdisplay -v.

Update all physical volumes in the volume group so that the logical volume become the root, boot, primary swap, or a dump volume when the system is next booted:

11.X only:

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

In order to test your mirror configuration, shut down the system and boot from the mirror disk.

# shutdown -ry 0

The system will shut down and reboot. As the system starts to come back up, look for the message (system's output may vary):

TO INTERRUPT THE BOOT SEQUENCE, PRESS ...

Interrupt the boot sequence. This will display the Boot Admin display. At the boot_admin> prompt type:

bo Mirror_disk_hardware_address or
bo alt

if the alternate boot device has been configured. The system will prompt to interact with IPL, answer 'no', and the system will boot from the mirror root disk.

NOTE: This example includes creating a mirror copy of the primary swap logical volume. The primary swap mirror does not need to be on a specific disk or at a specific location, but it does need to be allocated on contiguous disk space. The recommended mirror policy for primary swap is to have the Mirror Write Cache and the Mirror Consistency Recovery mechanisms disabled.

When primary swap is mirrored and your primary swap device also serves as a dump area, you must make sure that Mirror Write Cache and Mirror Consistency Recovery is set to off at boot time to avoid loss of your dump. To reset these options, you will need to reboot your system in maintenance mode. Then use the lvchange(1M) command with the -M n and -c n options.

Re: Moving Disk to another server

Torsten. — Wed, 25 May 2011 17:28:12 GMT

>> I ended up by crashing the OS

Any capture of this?

Did you install in the same slot? This would be important.

Re: Moving Disk to another server

Rita C Workman — Thu, 26 May 2011 15:03:33 GMT

You might try reading about this very handy utility. It looks like what your wanting to do would be a very fit.

http://docs.hp.com/en/5900-0578/ch05s01.html

It's called DRD.

Kindest Regards,
Rita