Originally posted by: ppereira

Hi; I'm trying to migrate owr NIM Master from AIX6 to AIX7
The NIM Server is an Lpar running AIX 6.1 TL07 SP03
I mapped a drive to the NIM Master and did an alt_disk_copy to this new disk.
To test the procedure I exported the altinst_rootvg and removed the disk. Mapped this drive to an empty Lpar and booted it.
After I checked that it was the same as the original one, I mapped the AIX7 iso on the vios through VMLibrary (AIX7 TL00 SP01) to the Lpar and booted it.
The partition came alright, selected the migration procedure and it started the migration proccess ok.
After updating 522 filesets it fails just about to reboot because it cannot create the boot image.
It fails with:

0301-154 bosboot: missing proto file: /usr/lib/drivers/pci/sissas64_dd

Started a maintenance shell and in fact this file does not exists. I checked the original system (the one running AIX6) and this file is there.

If I run lslpp -w /usr/lib/drivers/pci/sissas64_dd it turns out that the fileset which owns this file is devices.common.IBM.sissas.rte, which in the source system looks like this:
nimmaster01:/# lslpp -f devices.common.IBM.sissas.rte
Fileset File

---

Path: /usr/lib/objrepos
devices.common.IBM.sissas.rte 6.1.5.1
/usr/lib/methods/cfgsissas_proto
/usr/lib/methods/cfgsissata_proto
/usr/lib/methods/cfgsissasarray
/usr/bin/sissasraidmgr
/usr/lib/methods/sissasraidmgr.cat
/usr/lib/methods/sissas.cat
/usr/lib/drivers/pci/sissas64_dd
/usr/lib/methods/sissas_err.cat
/usr/lib/methods/ucfgsissaspdisk
/usr/lib/methods/cfgsissas
/usr/lib/methods/chgsissasarray
/usr/lib/methods/cfgsissaspdisk
/usr/lib/drivers/pci/sissas_dd
/usr/lib/drivers/pci

Path: /etc/objrepos
devices.common.IBM.sissas.rte 6.1.5.1
NONE

and in the target system (after migration) looks like this:

1. lslpp -f devices.common.IBM.sissas.rte

Fileset File

---

Path: /usr/lib/objrepos
devices.common.IBM.sissas.rte 7.1.0.1
/usr/lib/methods/cfgsissas_proto
/usr/lib/methods/cfgsissata_proto
/usr/lib/methods/cfgsissasarray
/usr/bin/sissasraidmgr
/usr/lib/methods/sissasraidmgr.cat
/usr/lib/methods/sissas.cat
/usr/lib/methods/sissas_err.cat
/usr/lib/drivers/pci
/usr/lib/methods/ucfgsissaspdisk
/usr/lib/methods/cfgsissas
/usr/lib/methods/chgsissasarray
/usr/lib/methods/cfgsissaspdisk
/usr/lib/drivers/pci/sissas_dd

Path: /etc/objrepos
devices.common.IBM.sissas.rte 7.1.0.1
NONE

There is no sissas64_dd file listed for this fileset.
I've got other systems running AIX7 and if I list the files for this filesets (for the same version of the fileset) it shows the file sissas64_dd listed.

So the migrated system is not being able to boot because of the problem when generating the boot image.
I think I could copy this file from a healthy system and go on with the boot proccess but I would like to know what am I doing wrong.

Thanks in advance.
Pablo.

Originally posted by: alethad

Someone had a similar issue and posted a question to this site. See if this helps you.

http://www.ibm.com/developerworks/forums/message.jspa?messageID=14812404
Otherwise if you google your message you will find several references to it. I'm not sure if this is just a warning or fatal error.

Good luck
You've got to continue to grow, or you're just like last night's cornbread -- stale & dry Loretta Lynn alethad

Originally posted by: ppereira

Hi, I had already gone through the links above before posting the question. The thing is that the solution didn't seem to be very "elegant".
Anyway, since I didn't find any official or better solution I tried the following procedure.

• When the migration procedure stops complaining that it couldn't find the file /usr/lib/drivers/pci/sissas64_dd, proceed to maintenance mode.
• In maintenance mode copy the file /usr/lib/drivers/pci/sissas64_dd from other AIX 7 (which was installed from scratch from the media used to migrate and updated with newer service pack. The machine used to copy was at 7100-00-03-1115)
• Execute bosboot -ad hdiskX (This time bosboot completed OK)
• Exit maintenance mode.

This procedure worked and the machine booted without any further problem.

My guess is that because I am using a very early media of AIX7 (7100-00-00) it lacks some files which are needed to migrate from AIX6. In fact, the file mentioned above does not exists on this media or an installed machine using this media, and it appears right after applying service pack 3.
Unfortunately I couldn't find any newer media to try out.
I will stick to this procedure to migrate until I could find a newer media or create an updated lpp_source on our NIM master and test it.

Regards and thanks again.
Pablo.

Originally posted by: uzair_rock

What command did you use in maintenance mode to copy the file from other server. I'm getting the following error:

scp sourceserver:/usr/lib/drivers/pci/sissas64_dd /usr/lib/drivers/pci/
PRNG is not seeded
lost connection

Please help as I am stuck with an installation. Thanks.

Originally posted by: ppereira

I didn't use scp. I created an iso image with the file and mounted via VMLibrary on the cdrom of the partition running in maintenance mode.
Anyway the final outcome wasn't 100% good.
Although the partition booted and the AIX was at 7, when I tryed to update the operating system installing the latest technology level it didn't work complaining about building dates of the filesets.
I tryed a lot of things but none of them worked, so I gave up.

Originally posted by: SystemAdmin

I just ran into this issue. I was upgrading 2 servers, one from 6100-02-03-0909 and the other from 6100-06-09-1228, both going to 7100-00-03-1115 and then updated to 7100-01-05-1228. The older version of AIX 6 upgraded fine, but the newer version failed.

Like ppereira, I created and ISO image containing the file to copy it to the server. This got me out of maintenance mode, but I could not install the TL update. In the end, I use smitty and removed the drivers that were giving me the build date conflict errors. When I went to re-install the drivers from my media, I could not. The response from the attempted install was that the fileset was effectively installed through superseding filesets.

Ken C

Originally posted by: guerilla

Do I need to be in maintenance mode to load these files?

/usr/lib/ras/autoload/sischndd64.kdb

/usr/lib/drivers/pci/sischn_dd

/usr/lib/ras/autoload/sissas64dd64.kdb

/usr/lib/ras/autoload/sissasdd64.kdb

I went into maintenance mode on one machine A and then used FTP to copy the files from a good machine B to my other machine A. I then booted into multi-user mode on machine A. My "bosboot -a" command then worked successfully. Now on to completing the upgrade.

I also have another machine C, that is missing the same files. These missing files is causing my "bosboot -a" command to not work.

[root@machineC]/> bosboot -a

0301-154 bosboot: missing proto file: /usr/lib/drivers/pci/sischn_dd
[root@machineC]/>

So I'm wondering if it would be okay to copy the files while in multi-user mode?

Or do I need to be in single user mode?

Mike

Originally posted by: Wouter Liefting

Instead of spending hours figuring out what's going on, how about this:

- Make a backup of your NIM DB, save it somewhere in your nimvg.

- Make an mksysb (or SAN flash copy, or something like that) of your NIM server rootvg, and a savevg (or SAN flash copy, ...) of your nimvg. Just in case.

- Do a fresh install from AIX, make sure to install SSL, SSH and the NIM master s/w, then upgrade to latest AIX 7.1 level as required.

- Import, varyonvg nimvg, restore backup of NIM DB

It should be possible to do all of this in less than two hours.

I personally love doing fresh installs over migrations. They give you a good chance to clean up your OS, make sure your documentation and procedures are up to date, and clean out the "crud" that may have been accumulating in your OS for years (uncleaned logfiles, files in /tmp or other temporary files that should've been deleted but weren't, and so forth).

Originally posted by: iaca400

Confirming Pablo's procedure above, I've also encountered the missing proto file error during a NIM upgrade. The file missing was sischn_dd.

I found this file in another partition. Entered into maintenance mode and copied it to the /usr/lib/drivers/pci directory of the target system.

bosboot -ad /dev/ipldevice ran successfully after this.