Migration 5.2 to 5.3 issues

[visvid]

Hi

We are trying are trying to migrate our CSM server from 5.2 RML05 to AIX 5.3

We have carried out all the prelimes, ie tarring certain dirs and running csmbackup and ./pre_migration

We have broken the mirror on rootvg and done a alt_clone

We also have loads of disk space and mem , how ever when we boot off the first cd to install we get the following error:

0516-1122

0516-842 Unable to make logical partition copies for logical volume

As mentioned above we do have the space , however when we tried to increase /usr either via chfs or extendlv they both failed


Any ideas , I cant seem to find any info on migration from 5.2 to 5.3 , there is loads of info about 4.3 or 5.1 to 5.3 but not 5.2


Regards


visvid

 

[p5wizard]

error message for chfs or extendlv?

HTH,

p5wizard

 

[visvid]

error meesages is incl in first part of the message :

0516-1122

0516-842 Unable to make logical partition copies for logical volume

interesting thing is I manage to migrate a client from 5.2 to 5.3 on both Power 4 and 5,upto 5.3 RML 02 so I am not sure why the CSM fails , anyone got any ideas ?

On the 7th day God created Super Moto

 

[p5wizard]

As mentioned above we do have the space , however when we tried to increase /usr either via chfs or extendlv they both failed

failed how? message? If there is a problem with rootvg setup, this might be also the cause of your upgrade issue...




HTH,

p5wizard

 

[visvid]

it failed with the CD install saying there was not enough space in /usr /home etc , and when the system tried to increase this it failed , the error codes incl above. We then tried to manually increase these and again it failed with the 2 error codes on the chfs -a cmd

0516-1122

0516-842 Unable to make logical partition copies for logical volume

It has worked on both a P4 and P5 client servers, we are going to try the other datacentre CSM next week and see if that too fails.

Will keep you updated

On the 7th day God created Super Moto

 

[p5wizard]

lsvg rootvg
lsvg -p rootvg
lsvg -l rootvg
lsvg altinst_rootvg
lsvg -p altinst_rootvg
lsvg -l altinst_rootvg
lsdev -Ccdisk

please?

You said you broke the mirror and ran a alt_clone: You cloned the rootvg to another disk and are "alt_disk_install" - upgrading that cloned rootvg? Is there enough disk space in that cloned rootvg?

Also: why would you be booting from CD in the first place... Or is the clone for fallback purpose only (sort of instant mksysb) and are you upgrading the original rootvg?

I don't understand completely... I must admit I am not in familiar terrain here. Please explain.


HTH,

p5wizard

 

[fjw999]

I had something similar when upgrading from 4.3.3 to 5.3 where i couldn't mirror the rootvg after the upgrade and was seeing the same error you are. I found there was a bug in Aix 5.3 where it couldn't mirror a volume group that had a 16 character VG IDENTIFIER. Not sure whether this is the same problem you are having but if your 5.2 system was an upgrade from 4.3 then your rootvg might only have a 16 character identifier. You can see this from `lsvg rootvg`

Fjw

 

[visvid]

Our VG Indentifier is 32 characters , as mentioned it has worked on out P4 and P5 clients but not our Server, we are going to look at the pre_migration script and see if there are any bugs there

keep you posted

On the 7th day God created Super Moto

 

[plamb]

it this a stripped lv ??

 

[visvid]

no not stripped

VOLUME GROUP: rootvg VG IDENTIFIER: 0050353a00004c00000001045249128b
VG STATE: active PP SIZE: 128 megabyte(s)
VG PERMISSION: read/write TOTAL PPs: 1092 (139776 megabytes)
MAX LVs: 256 FREE PPs: 332 (42496 megabytes)
LVs: 27 USED PPs: 760 (97280 megabytes)
OPEN LVs: 26 QUORUM: 1
TOTAL PVs: 2 VG DESCRIPTORS: 3
STALE PVs: 0 STALE PPs: 0
ACTIVE PVs: 2 AUTO ON: no
MAX PPs per PV: 1016 MAX PVs: 32
LTG size: 128 kilobyte(s) AUTO SYNC: no
HOT SPARE: no BB POLICY: relocatable


On the 7th day God created Super Moto

 

[p5wizard]

lsvg -l rootvg
lslv hd2 output
lslv hd1 output

please?

HTH,

p5wizard

 

[visvid]

rootvg:
LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT
hd5 boot 1 2 2 closed/syncd N/A
hd6 paging 16 32 2 open/syncd N/A
hd8 jfslog 1 2 2 open/syncd N/A
hd4 jfs 5 10 2 open/syncd /
hd2 jfs 24 48 2 open/syncd /usr
hd9var jfs 3 6 2 open/syncd /var
hd3 jfs 41 82 2 open/syncd /tmp
hd1 jfs 2 4 2 open/syncd /home
hd10opt jfs 1 2 2 open/syncd /opt
tftpbootlv jfs 1 2 2 open/syncd /tftpboot
nimsrclv jfs 104 208 2 open/syncd /nimsrc
csminstall jfs 8 16 2 open/syncd /csminstall
hd7 sysdump 6 6 1 open/syncd N/A
loglv00 jfs2log 1 2 2 open/syncd N/A
local jfs 1 2 2 open/syncd /usr/local
jr00 jfs 8 16 2 open/syncd /jr
tsm jfs2 2 4 2 open/syncd /tsm
loglv01 jfs2log 1 2 2 open/syncd N/A
epdm jfs2 2 4 2 open/syncd /var/epdm
logs jfs2 1 2 2 open/syncd /logs
aix51_06lv jfs 20 40 2 open/syncd /nimsrc/AIX51_06
aix52_03lv jfs2 21 42 2 open/syncd /nimsrc/AIX52_03
config jfs2 8 16 2 open/syncd /config
aix52_05lv jfs2 30 60 2 open/syncd /nimsrc/AIX52_05
aix53_02 jfs2 32 64 2 open/syncd /nimsrc/AIX53_02
ora_920 jfs2 40 80 2 open/syncd /nimsrc/packages/oracle/9.2.0
nsr jfs2 3 6 2 open/syncd /nsr

lslv hd2
LOGICAL VOLUME: hd2 VOLUME GROUP: rootvg
LV IDENTIFIER: 0050353a00004c00000001045249128b.5 PERMISSION: read/write
VG STATE: active/complete LV STATE: opened/syncd
TYPE: jfs WRITE VERIFY: off
MAX LPs: 32512 PP SIZE: 128 megabyte(s)
COPIES: 2 SCHED POLICY: parallel
LPs: 24 PPs: 48
STALE PPs: 0 BB POLICY: relocatable
INTER-POLICY: minimum RELOCATABLE: yes
INTRA-POLICY: center UPPER BOUND: 32
MOUNT POINT: /usr LABEL: /usr
MIRROR WRITE CONSISTENCY: on/ACTIVE
EACH LP COPY ON A SEPARATE PV ?: yes
Serialize IO ?: NO
lslv hd1
LOGICAL VOLUME: hd1 VOLUME GROUP: rootvg
LV IDENTIFIER: 0050353a00004c00000001045249128b.8 PERMISSION: read/write
VG STATE: active/complete LV STATE: opened/syncd
TYPE: jfs WRITE VERIFY: off
MAX LPs: 512 PP SIZE: 128 megabyte(s)
COPIES: 2 SCHED POLICY: parallel
LPs: 2 PPs: 4
STALE PPs: 0 BB POLICY: relocatable
INTER-POLICY: minimum RELOCATABLE: yes
INTRA-POLICY: center UPPER BOUND: 32
MOUNT POINT: /home LABEL: /home
MIRROR WRITE CONSISTENCY: on/ACTIVE
EACH LP COPY ON A SEPARATE PV ?: yes
Serialize IO ?: NO
cr01csm:/home/pre_migration.050606153810#


On the 7th day God created Super Moto

 

[p5wizard]

So rootvg is still mirrored - I read you have to unmirror rootvg before attempting to upgrade? (Did you re-mirror it after the failed upgrade?)

what does lsvg -p show?

Is there still free space on both disks - i.e. are all your mirrors nicely placed over the two disks? If not, then it should be obvious why you can't extendlv/chfs...

[red]EACH LP COPY ON A SEPARATE PV ?: yes[/red]

There's a script somewhere in another thread to review mirror placement. I'll look it up.



HTH,

p5wizard

 

[visvid]

ok reason rootvg is mirrored , is because the migrate failed and we have returned rootvg to a mirrored VG

On the 7th day God created Super Moto

 

[p5wizard]

mirror check script is in

Disk mirroring question
thread52-1067044


HTH,

p5wizard

 

[CrystalWizard]

do not set it up to mirror while upgrading, if you have. That's always a bad idea. Very bad.

do your migration, reboot, check that things are ok then make a mksysb. THEN do a new mirror.