topic Re: Clone Alternative System disk - will not boot in Operating System - HP-UX

Clone Alternative System disk - will not boot

Craig Hargreaves — Tue, 29 Aug 2000 09:54:31 GMT

How do I make a bootable system disk by cloning my existing one? (HPXUX 10.20)
I have tryed the following but it hangs during boot after the memory information but before ioinit

(new disk scsi id 6 dec rz26 1gb)
(existing system scsi 5 MO rw 512Mb)

! create fs and reserve 256 MB space
newfs -F hfs -R 256 /dev/rdsk/c0t6d0
mkdir noddy
mount /dev/dsk/c0t6d0 /noddy
cd /
!copy contents of system disk to new disk
find . -xdev -print | cpio /noddy
!create boot record
mkboot /dev/rdsk/c0t6d0
! edit fstab to point to new disk
cp -p /etc/fstab /noddy/etc/fstab2
sed 's/6/5/' /noddy/etc/fstab2 > /noddy/etc/fstab2

shutdown and boot from my alternalte boot path

I have tried the reverse on a production system (HDD to RWMO) and that fails too

Re: Clone Alternative System disk - will not boot

Stefan Farrelly — Tue, 29 Aug 2000 10:11:20 GMT

The preferred method to clone a system disk is to use HP's ignite software product - although Ignite is really for disaster recovery purposes. If you dont want to use ignite then you can use dd instead. Bring up your system in single user mode, then do a raw dd from your primary boot disk to a new disk;

dd if=/dev/rdsk/cxxxxx of=/dev/rdsk/c0t6d0 bs=1024k

Then you should be able to boot from the new disk aok. I use it here sometimes, works great, but I prefer to use Ignite.

Re: Clone Alternative System disk - will not boot

Victor BERRIDGE — Tue, 29 Aug 2000 10:11:32 GMT

The simplest way would be to use ignite-ux make_recovery tool, if your 2 disks are identical there is nothing stopping you to do a dd of your disk to the new one , it works - I tried... (use block size 1024)

Re: Clone Alternative System disk - will not boot

CHRIS_ANORUO — Tue, 29 Aug 2000 10:23:04 GMT

Hi Craig,

You need to install Ignite UX to clone your system and have a bootable tape.
Follow this link to download the software: http://www.software.hp.com/products/IUX/docs.html

Re: Clone Alternative System disk - will not boot

Alan Riggs — Tue, 29 Aug 2000 13:50:08 GMT

It sounds like what you want is an emergency boot disk, but you do not want/have mirrordisk/UX. In that case, you can create one with the following procedure:

pvcreate -B /dev/rdsk/c0t6d0
mkboot /dev/dsk/c0t6d0
place the disk in a VG, either vg00 or its own
create one or more LVs to hold filesystems.
create and mount filesystems under /newroot (or whatever you wish)
use CPIO to transfer data. (ex: cd /var; find . -xdev -depth| cpio -pdumx /newroot/var)
setboot -a (alternate path)
boot off of new disk to test.

Re: Clone Alternative System disk - will not boot

Victor BERRIDGE — Tue, 29 Aug 2000 16:28:23 GMT

Craigh,
I think we were all wrong?
You are not using LVM is that so?
So what kind of box is this (9000/7XX or8XX)?
We need more information in order to give you a good solution
Best regards
Victor

Re: Clone Alternative System disk - will not boot

Craig Hargreaves — Wed, 30 Aug 2000 07:59:25 GMT

As Victor spotted I am not using LVM and have no requirment for it. The 'box' in question is a Single Board 744 workstaion mounted in a VME rack.
Using the method I posted originaly to create a clone disk and then repairing the disk from recovery program on the Installation CD fixes the problem but this is hardly a neat solution.

Re: Clone Alternative System disk - will not boot

Stefan Farrelly — Wed, 30 Aug 2000 08:03:39 GMT

Try the dd solution as I mentioned in my earlier reply. It works fine and its only a single command.

Re: Clone Alternative System disk - will not boot

John Palmer — Wed, 30 Aug 2000 08:06:55 GMT

I've always used LVM personally but man mkboot mentions various flags pertinent to the whole disk layout.

Do you need to specify -H or -W (or maybe some others) to mkboot?

Re: Clone Alternative System disk - will not boot

John Palmer — Wed, 30 Aug 2000 08:11:15 GMT

Or do you have to supply the -B flag to newfs (to reserve the boot area).

Re: Clone Alternative System disk - will not boot

Victor BERRIDGE — Wed, 30 Aug 2000 09:27:07 GMT

And you have no tape device?

Looks like you cannot create a proper boot area.
If I remember right (more than 3 years have past since...) on non LVM HP 9000 workstations, the copy of the boot area on the root disk is /usr/lib/uxbootlf
I remembered making boot tapes with dd
dd if=/usr/lib/uxbootlf of=/dev/rmt/0mn bs=2k
then
dd if=/dev/rdsk/c201d6s0 of=/dev/rmt/0m bs=64k

So would it be for Craigh
mkboot -b /usr/lib/uxbootlf /dev/dsk/c0t6d0
mkboot -a "hpux (56/52.6.0;0)/stand/vmunix" /dev/rdsk/c0t6d0

You will have to adapt HW path...

Re: Clone Alternative System disk - will not boot

Stefan Farrelly — Wed, 30 Aug 2000 09:36:36 GMT

Victors previous reply is on the money. You need to write the uxbootlf.700 or uxbootlf.800 file to the destination disk using bs=2k to make it bootable.

So, to use dd to copy the entire disk use a bs=2k for the whole disk (if=/dev/rdsk of=/dev/rdsk bs=2k) and although it may take a long time to dd, your end result will be a bootable image disk, mach simpler and faster than any other method.

Re: Clone Alternative System disk - will not boot

CHRIS_ANORUO — Wed, 30 Aug 2000 10:05:14 GMT

Craig,

Try mirroring the root files to the new disk then

Re: Clone Alternative System disk - will not boot

Cheryl Griffin — Wed, 30 Aug 2000 11:58:24 GMT

Craig,

I think the problem is with the command:
# newfs -F hfs -R 256 /dev/rdsk/c0t6d0

This does not have the -B option to reserve the boot area.
Try:
# newfs -F hfs -BLv -R 256 /dev/rdsk/c0t6d0

-B = reserve boot area
-L = long filenames (optional)
-v = verbose

Re: Clone Alternative System disk - will not boot

Stefan Schulz — Thu, 31 Aug 2000 13:42:24 GMT

If you have two (nearly) identical disks there is no need to play with newfs and cpio. Just do a dd in single user mode as described before. Its a fast and easy method for cloning disks. No more configuration, cause the new disk is bootable from the beginning.

If you have two totally different disks i would suggest using make_recovery or better make_sys_image. Both commands/programms come with Ignite/UX.