• Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

Comments (4)

1 fjw999 commented Permalink

Do you think it would work if you took a mksysb image of your 6.1 system then used nimadm to upgrade it to 7.1 and use that image to restore to your multibos standby image. This way you would keep all your users etc. howerver the -M flag might prevent that. Fraser

2 cggibbo commented Permalink

Fraser, <div>&nbsp;</div> Yes that would be a logical way to use it. <div>&nbsp;</div> Although I can't help but feel like I've just jumped through several hoops to do something I could have done with NIM alone, in a lot less steps. <div>&nbsp;</div> Perhaps this would be useful if you did not have access to a NIM server at a remote site but you had one at your local site. You could do the nimadm mksysb migrate at the local site, then ftp the mksysb image over to the remote site and use multibos to "migrate" the remote LPAR to the higher-level of AIX. <div>&nbsp;</div> I guess one advantage is you don't need a spare disk with the multibos method as opposed to nimadm. <div>&nbsp;</div> Food for thought either way.

3 SomeshChourey commented Permalink

Hi <div>&nbsp;</div> Thanks for the document <div>&nbsp;</div> I tried this way and when i rebooted with multibos boot device its not booting up <div>&nbsp;</div> Can you please how can i boot the server with an old boot device . <br /> Error code :e14d led code <div>&nbsp;</div> Can you please help <div>&nbsp;</div> <div>&nbsp;</div> This is what the error when i tried to boot from raritan console : <div>&nbsp;</div> boot Unable to use memory at load-base <br /> Data stack pointer = c10ff8 <div>&nbsp;</div> 000000c10ff0: 00 00 00 00 00 00 00 10 ff ff ff ff ff ff ff fe :................: <br /> 000000c11000: 00 00 00 00 de ad be ef 00 00 00 00 00 00 00 00 :................: <br /> 000000c11010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 :................: <br /> 000000c11020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 :................: <br /> Call History <br /> ------------ <br /> throw - c3ba04 <br /> $abort - c47c80 <br /> map-load-addr - c8a648 <br /> $load - c8a748 <br /> (poplocals) - c3d040 <br /> (load) - c8ab08 <br /> boot|load - c8ba18 <br /> boot - c8c1f0 <br /> evaluate - c4d1c0 <br /> ^c17100 - c17100 <br /> invalid pointer - 4 <br /> invalid pointer - 4 <br /> quit - c4dadc <br /> quit - c4d698 <div>&nbsp;</div> My Fix Pt Regs: <br /> 00 0000011000000000 9000000000003002 00000000deadbeef 0000000000c47c7c <br /> 04 0000000000000021 0000000000c8a621 0000000000c11f58 0000000000c03008 <br /> 08 0000000100000000 00000000fd677f5f 0000000000c8a744 0000000000000000 <br /> 0c 0000000000009ec8 0000000000000000 0000000000000000 0000000000000000 <br /> 10 0000000000ee5170 0000000000ee5120 0000000000c47c74 0000000000c47c80 <br /> 14 fffffffffffffffe 0000000000004000 0000000000000000 0000000000000000 <br /> 18 0000000000c13000 0000000000c38000 0000000000c14fc0 0000000000c16fc0 <br /> 1c 0000000000c20000 0000000000c43338 0000000000c11f90 0000000000c10ff8 <br /> Special Regs: <br /> %IV: 00000900 %CR: 48808044 %XER: 20000000 %DSISR: 00000000 <br /> %SRR0: 0000000000c43160 %SRR1: 900000000000b002 <br /> %LR: 0000000000c3f73c %CTR: 0000000000000000 <br /> %DAR: 0000000000000000 <div>&nbsp;</div> Note: SRR0, SRR1, R0-R2 may have been altered by a dec-int. <br /> ok <br /> 0 &gt; boot Unable to use memory at load-base <br /> Data stack pointer = c10ff8 <div>&nbsp;</div> 000000c10ff0: 00 00 00 00 00 00 00 10 ff ff ff ff ff ff ff fe :................: <br /> 000000c11000: 00 00 00 00 de ad be ef 00 00 00 00 00 00 00 00 :................: <br /> 000000c11010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 :................: <br /> 000000c11020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 :................: <br /> Call History <br /> ------------ <br /> throw - c3ba04 <br /> $abort - c47c80 <br /> map-load-addr - c8a648 <br /> $load - c8a748 <br /> (poplocals) - c3d040 <br /> (load) - c8ab08 <br /> boot|load - c8ba18 <br /> boot - c8c1f0 <br /> evaluate - c4d1c0 <br /> ^c17100 - c17100 <br /> invalid pointer - 4 <br /> invalid pointer - 4 <br /> quit - c4dadc <br /> quit - c4d698 <div>&nbsp;</div> My Fix Pt Regs: <br /> 00 0000011000000000 9000000000003002 00000000deadbeef 0000000000c47c7c <br /> 04 0000000000000021 0000000000c8a621 0000000000c11f58 0000000000c03008 <br /> 08 0000000100000000 00000000fd677f5f 0000000000c8a744 0000000000000000 <br /> 0c 0000000000009ec8 0000000000000000 0000000000000000 0000000000000000 <br /> 10 0000000000ee51c0 0000000000ee5170 0000000000c47c74 0000000000c47c80 <br /> 14 fffffffffffffffe 0000000000004000 0000000000000000 0000000000000000 <br /> 18 0000000000c13000 0000000000c38000 0000000000c14fc0 0000000000c16fc0 <br /> 1c 0000000000c20000 0000000000c43338 0000000000c11f90 0000000000c10ff8 <br /> Special Regs: <br /> %IV: 00000900 %CR: 48808044 %XER: 20000000 %DSISR: 00000000 <br /> %SRR0: 0000000000c3cf44 %SRR1: 900000000000b002 <br /> %LR: 0000000000c3f73c %CTR: 0000000000000000 <br /> %DAR: 0000000000000000 <div>&nbsp;</div> Note: SRR0, SRR1, R0-R2 may have been altered by a dec-int. <br /> ok <div>&nbsp;</div> Thanks <br /> Somesh Chourey

4 cggibbo commented Permalink

Hi Somesh, <div>&nbsp;</div> If you recorded the bootlist output prior to rebooting then you can use this information to determine which disk to boot from in the openfirmware prompt. <div>&nbsp;</div> For example: <div>&nbsp;</div> # bootlist -m normal -ov <br /> 'ibm,max-boot-devices' = 0x5 <br /> NVRAM variable: (boot-device=/vdevice/v-scsi@30000002/disk@8100000000000000:2 /vdevice/v-scsi@30000003/disk@8100000000000000:2) <br /> Path name: (/vdevice/v-scsi@30000002/disk@8100000000000000:2) <br /> match_specific_info: ut=disk/vscsi/vdisk <br /> hdisk0 blv=hd5 pathid=0 <br /> Path name: (/vdevice/v-scsi@30000003/disk@8100000000000000:2) <br /> match_specific_info: ut=disk/vscsi/vdisk <br /> hdisk0 blv=hd5 pathid=1 <div>&nbsp;</div> At the openfirmware prompt: <div>&nbsp;</div> 0&gt; boot /vdevice/v scsi@30000002/disk@8100000000000000:2 | <div>&nbsp;</div> Where: <div>&nbsp;</div> /vdevice - Virtual I/O Bus <br /> /v-scsi@30000004 - Virtual I/O SCSI Adapter <br /> /disk@8100000000000000:4 - Virtual I/O SCSI Disk Device <div>&nbsp;</div> This is documented in the following article: <div>&nbsp;</div> http://www.ibmsystemsmag.com/aix/trends/aix/AIX-Updates-With-Multibos/ <div>&nbsp;</div> Or you could simply boot into SMS and select the alternate boot disk partition. <div>&nbsp;</div> Good luck! <div>&nbsp;</div> Cheers. <div>&nbsp;</div> Chris

Add a Comment Add a Comment