Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

nimadm alt migration 5.3 to 6.1 phase8 bosboot failed

Status
Not open for further replies.

alexia32

Technical User
Jul 31, 2007
156
NZ
Hello
I am doing some migration 5.3 to 6.1 (alternate migration) it is working on some machines but failed on one machine with the following error
+-----------------------------------------------------------------------------+
Executing nimadm phase 8.
+-----------------------------------------------------------------------------+
Creating client boot image.
mv: 0653-401 Cannot rename /devaix1_alt/alt_inst/dev/hd5 to /devaix1_alt/alt_inst/dev/hd5.save.368792:
A file or directory in the path name does not exist.
0505-158 nimadm: WARNING, unexpected result from the mknod command.
0505-180 nimadm: Error creating client boot image.
Cleaning up alt_disk_migration on the NIM master.

Any idea what I can do to fix it ?

the aix client is running 5.3 TL9: 5300-09-01-0847
NIM server is running: 6100-02-03-0909

all the phase1-phase7 were successfull (migration AIX packages phase6 successfull)

it failed when trying to create the boot disk.
I cleaned the disks and retry (chpv -c hdisk1 ; chpv -C hdisk1 and also clear the pv chdev -a pv=clear -l hdisl1) but still have the same error on phase 8.
I can;t find anything on IBM website about this issue for 5.3.
If you have an idea please help me.. :)

Cheers
Al
 
Hi

Just a few thoughts , if not tried already


have you tried running alt_disk_copy manually and does it work ?

i.e. unmirror root vg take pout hdisk1

then run alt_disk_copy to hdisk1

try booting from alternate disk

if this works , then you can either leave it and migrate to 6.1 or retry the alternate migrate again

Or you can remove hdisk1 from rootvg and retry it

Thanks



 
You need to make sure you only have hd5 as the boot logical volume on your root disk.

For instance if you had previously used multibos and had hd5 and bos_hd5, alt disk would fail on that as it's hard coded to only use hd5 (and cannot rename bos_hd5), cleaning up multibos to leave just hd5 fixes that.

I'm assuming you have hd5.save.368792 on there as well?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top