how to change 4G boot disk to 9G boot disk ???

[paullu]

hi: all
now i have a machine with a 4G boot disk,i want to use a new 9G disk and replace the 4G disk.so the OS can boot from this 9G disk,how can i do to finish it??




paullu
Dec 06 2002

[Tom Geudens]

Hi,
1. Take an Ignite tapebackup of your bootdisk
2. Take another (!) Ignite tapebackup of your bootdisk.
3. Shut the machine
4. Replace 4Gb disk (with the new 9Gb disk)
5. Boot the machine from the Ignite tape and Igniterestore to the new disk.

Regards,
Tom

[Heinz Gaertner]

Hi,

another way is to use mirror disk (if installed). The disk must be built in first, of course.
pvcreate -B /dev/rdsk/cXtYdZ (the device of your new disk)
mkboot /dev/dsk/cXtYdZ
vgextend vg00 /dev/dsk/cXtYdZ
lvextend -m 1 /dev/vg00/lvol1 vg00
(do this for all lvols, the first three ones boot, root and primary swap must be the first ones on the disk and contiguous)
check if all is ok:
lvlnboot -v
Then you can try to boot from the other disk. If this works then reduce the mirrors from your original disk:
lvreduce -m 0 /dev/vg00/lvol1 /dev/dsk/OLDDISK
vgreduce vg00 /dev/dsk/OLDDISK
Don't forget to set the primary boot path to the new disk.

Bye

[Jean-Louis Phelix]

Sorry heinz, but it has few chances to work except if you want to loose 2 or more Go on the new disk. When a vg is created, if defaults max_pe to requirement of the biggest disk. In this case you won't have enough PE to address 9Go, except if you've created your initial vg with -e max_pe option. So ignite solution is the good one ...

Regards.

[Donald Kok]

Hi Paullu,

I recommend Tom's Solution too. In his step 5, you have the chance to change the sizes of your filesystems. So this is the moment to increase /var /usr etc...

After all, I expect this to be the reason you want a bigger disk ;-)

Goodluck
Donald

[Heinz Gaertner]

Hi,

sorry, you folks are right. The default size goes to 4 MB PE-size with 2000 PE's leaving you with a 8 GB disk and not 9 GB. And you are right ignite is the easiest way to go and has indeed some advantages like changing filesystems (var and usr are not so critical, can be done in single user mode, more interesting is the root-filesystem for example).

Sorry again for the bad hint

Heinz

[Michael Tully]

The procedure listed by Tom is definitely the way to go. However, if I can I would like to expand on it.

Run an ioscan and make note of the hardware address your DAT tape or whatever your using, and the new 9Gb drive for later.
Create the two ignite tapes as required.
# make_tape_recovery -x inc_entire=vg00 -I -v -a /dev/rmt/0mn (note the use of the rewind command)

Reboot your system, and halt where you have the 10 second opportunity to do so.
do an SEA and look for the tape drive hardware address.
Select this "P?" so that the tape can boot. Use the interactive menu to create a system on your drive.

This procedure gives you the benefit of a full backout.

[Tom Jackson]

Been there. Ignite is an easy way to do it.

Tom

[Cheryl Griffin]

ITRC Knowledge Base document shows another way to do this with Ignite:
UIUXKBRC00010068 Max PE per PV limits replacing disks in VG00 with larger disks

Cheryl

[paullu]

hi: all
At first thanks for all your suggests,i had thought to use the way of tom,now his suggests inspire me.thant you very much.i like this forums.



paullu

[KapilRaj]

hi,

Take an ignite backup (You are sure u can boot through that & recover). Try the following interesting way of achiving it.

4 GB ---- /dev/rdsk/c0t6d0
9 GB ---- /dev/rdsk/c0t5d0 (Newly added )

1. Boot through the 4 GB at ISL type

hpux -lm

you get the root login

Exicute the following commands

vgchange -a y /dev/vg00
pvcreate -B -f /dev/rdsk/c0t5d0
mkdir /dev/vgboot
mknod /dev/vgboot/group c 64 0x??010000 where ?? = a unique minor number for vg.
vgcreate /dev/vgboot /dev/dsk/c0t5d0
vgchange -a y /dev/vgboot
lvcreate -C y -r n -L "SIZE in MB of /stand" /dev/vgboot
lvcreate -C y -r n -L "SIZE in MB of primary swap" /dev/vgboot
lvcreate -C y -r n -L "SIZE of root filesystem" /dev/vgboot

create all the other Logical volumes with lvcreate command on the newly created vg
newfs -F hfs /dev/vgboot/rlvol1
newfs -F vxfs /dev/vgboot/rlvol3

exicute newfs for all the other filesystems respect.....

lvlnboot -b /dev/vgboot/lvol1
lvlnboot -r /dev/vgboot/lvol3
lvlnboot -s /dev/vgboot/lvol2
lvlnboot -d /dev/vgboot/lvol2
lvlnboot -R

mkdir /newboot
mkdir /newroot
mount /dev/vgboot/lvol1 /newboot
mount /dev/vgboot/lvol3 /newroot
cd /stand
find . -xdev -depth |cpio -pxdm /newboot
cd /
find . -xdev -depth |cpio -pxdm /newroot

cat /newroot/etc/fstab |sed s/vg00/vgboot/g > /newroot/etc/fstab.new
cp /newroot/etc/fstab /newroot/etc/fstab.old
cp /newroot/etc/fstab.new /newroot/etc/fstab
>/newroot/etc/mnttab
>/etc/mnttab

reboot -r

interrupt the boot sequence & try to boot through the new disk. It will work

Nice ???

Another way (make sure data is backed up)

Boot through the 4 GB disk

hpux -lm

lvrmboot -r /dev/vg00(RISK starts from here !!)
pvcreate -B -f /dev/rdsk/c0t5d0
vgextend /dev/vgboot /dev/dsk/c0t5d0
lvchange -C n /dev/vg00/lvol1
lvchange -C n /dev/vg00/lvol2
lvchange -C n /dev/vg00/lvol3

pvmove /dev/vg00/lvol1 /dev/dsk/c0t6d0 /dev/dsk/c0t5d0
pvmove /dev/vg00/lvol2 /dev/dsk/c0t6d0 /dev/dsk/c0t5d0
pvmove /dev/vg00/lvol3 /dev/dsk/c0t6d0 /dev/dsk/c0t5d0

Like this do movbe all the PES to the newly added disk


for i in lvol1 lvol2 lvol3
do
lvchange -C y /dev/vg00/lvol1
lvchange -C y /dev/vg00/lvol2
lvchange -C y /dev/vg00/lvol3
done

vgreduce /dev/vg00 /dev/dsk/c0t6d0
lvlnboot -b /dev/vg00/lvol1
lvlnboot -r /dev/vg00/lvol3
lvlnboot -s /dev/vg00/lvol2
lvlnboot -d /dev/vg00/lvol2
lvlnboot -R

reboot -r

Guys can correct me if i am wrong / some thing is missing.

kaps.

[Russell Gould]

Download the latest version of Ignite and use that. Especially if you are replacing the 4Gb with a 9Gb. Once taken, you can shutdown the server - replace the 4Gb (and keep that as your rollback) and insert the 9Gb, interrupt the bootup, boot from Ignite tape and it will be very straight forward. Also been there - problems using Ignite are generally MUCh easier to fix than nasty LIF lvlnboot issues. Provides a user friendly interface.

Good luck

Russ