5.2.8 to 5.3.5 upgrade (migration) strangeness 1

[sbrews]

I was wondering if anyone has run across this situation when trying to upgrade/migrate from 5.2.9 to 5.3.5. The steps I took are/were:

1.) unmirror the rootvg
2.) update the boot records to reflect just the one disk.
3.) Put the 5.3.5 cd #1 in the cdrom (lpar set to have cdrom)
4.) Rebooted.
5.) Hit 5 when "keyboard" appeared on the screen.
6.) System proceeded to boot from cdrom - no errors.
7.) When the menu came up, the only options I had were:
- Complete/New install
- Preservation install

There was no option for migration and the preservation install would not let me use any disk other than hdisk2. The OS/rootvg is on hdisk0.

Has anyone ever run into this? If so, what did you do to resolve it?

On a side note (and adding to the weirdness), I called IBM for support. IBM is insisting that the system serial # I gave them says its a system that belongs to the Dept. of Commerce (which it doesnt and its sitting in my data center/I can go touch it if I need to).



Add a little color to your PUTTY terminal: faq52-6627

 

[khalidaaa]

Well when i upgraded my 5200-08-00 machine to 5300-04-00 and then 5300-04-03 with no problems! i used my NIM master for that! and i managed to choose the migration option!

I know this might not be helpful but did you try to go for 5300-04-00 at first instead of 5300-05-00?

Regards,
Khalid

 

[DukeSSD]

Lots of SSA? unplug them.
Lots and lots of fibre disks? unplug them.
Did you use the pre-migration script on the first CD to checkout the upgrade?
Did you search before posting?....thread52-1329375
Pad string?
Ghost disks?

 

[sbrews]

Nope - no SSA
Yes - lots and lots and lots of fibre

I dont recall the pre-migration script complaining about anything - but I will go run it again.

I did search around - but I dont recall what I used as search terms so I didnt find the thread you referenced. I will go read up on it and see if anything else - besides the tons of fibre disks - jumps out. Thanks for the tip.



Add a little color to your PUTTY terminal: faq52-6627

 

[MoreFeo]

We had a similar problem while migrating to 5.3, and it was what DukeSSD has said, too much SSA disks (I think the limit is 64), so if you've got too much fiber disks it might be the problem. Unplugging the SSA disks worked for us.

 

[sbrews]

Well, I've checked for ghost disks, pad string, etc. All is good. The only thing left is the # of fibre disks. When another maintenance window comes up I will unplug the fibre and see what turns out.

Thanks again for the tips.

Add a little color to your PUTTY terminal: faq52-6627

 

[hfaix]

Similar to MoreFeo, I had this problem at 64 SSA disks.