Topic
  • 10 replies
  • Latest Post - ‏2012-09-04T08:22:50Z by space9
rkbca
rkbca
4 Posts

Pinned topic NIMADM fails

‏2012-04-12T11:40:26Z |
Getting below mentioned error while trying upgraded from 5.3 to 7.1. Please assist me what needs to be done.

Creating client boot image.
0301-154 bosboot: missing proto file: /usr/lib/drivers/pci/sissas64_dd
0505-180 nimadm: Error creating client boot image.
Cleaning up alt_disk_migration on the NIM master.
Unmounting client mounts on the NIM master.
forced unmount of /libk071_alt/alt_inst/var
forced unmount of /libk071_alt/alt_inst/usr
forced unmount of /libk071_alt/alt_inst/tmp
forced unmount of /libk071_alt/alt_inst/opt
forced unmount of /libk071_alt/alt_inst/home
forced unmount of /libk071_alt/alt_inst/admin
forced unmount of /libk071_alt/alt_inst
Cleaning up alt_disk_migration on client libk071.
Unexporting alt_inst filesystems on client libk071:
Client alt_disk_install command: alt_disk_install -M 7.1 -X
forced unmount of /alt_inst/var
forced unmount of /alt_inst/usr
forced unmount of /alt_inst/tmp
forced unmount of /alt_inst/opt
forced unmount of /alt_inst/home
forced unmount of /alt_inst/admin
forced unmount of /alt_inst
Bootlist is set to the boot disk: hdisk0 blv=hd5
A file or directory in the path name does not exist.
/usr/sbin/nimadm1147: /libk071_alt/alt_inst/etc/firstboot: 0403-005 Cannot create the specified file.
Updated on 2012-09-04T08:22:50Z at 2012-09-04T08:22:50Z by space9
  • sajjadhashimi
    sajjadhashimi
    35 Posts

    Re: NIMADM fails

    ‏2012-04-12T13:23:54Z  
    What TL you have at 5.3? I believe there is a minimum requirement of TL required for AIX 6/7 migration. I can't remember if its TL7 or TL9. Maybe this is why its failing, if you aren't at the minimum required level.
  • alethad
    alethad
    286 Posts

    Re: NIMADM fails

    ‏2012-04-12T16:09:03Z  
    Did you check this message out? It's in your output you sent.

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

    As the previous reply says you need to verify your oslevel if it's high enough and high enough to contain the file above.

    Did you run the pre_migration script? Did you see any errors or warnings?

    One thing I ran into with a 5.3 to 6.1 was the names of the LV's being too long. can't have rootvg LV's longer than 11 or non-rootvg LV's longer than 15. Not sure if this has changed for 7.1 or not but worth checking into if your naming convention for your LV's are long.
    Good luck.

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

    Re: NIMADM fails

    ‏2012-04-13T07:08:31Z  
    • alethad
    • ‏2012-04-12T16:09:03Z
    Did you check this message out? It's in your output you sent.

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

    As the previous reply says you need to verify your oslevel if it's high enough and high enough to contain the file above.

    Did you run the pre_migration script? Did you see any errors or warnings?

    One thing I ran into with a 5.3 to 6.1 was the names of the LV's being too long. can't have rootvg LV's longer than 11 or non-rootvg LV's longer than 15. Not sure if this has changed for 7.1 or not but worth checking into if your naming convention for your LV's are long.
    Good luck.

    You've got to continue to grow, or you're just like last night's cornbread -- stale & dry Loretta Lynn alethad
    I also faced the same issue while upgrading the server from AIX 5.3 TL12 to AIX 6.1 TL6.

    Executing nimadm phase 8.
    -----------------------------------------------------------------------------
    Creating client boot image.
    0301-154 bosboot: missing proto file: /usr/lib/drivers/pci/sissas64_dd
    0505-180 nimadm: Error creating client boot image.
    Cleaning up alt_disk_migration on the NIM master.

    lv count and all below 11 only.
  • rkbca
    rkbca
    4 Posts

    Re: NIMADM fails

    ‏2012-04-13T09:49:48Z  
    Hi All,

    Thanks for your reply. Client TL is 5300-12-05-1140 and NIM master upgraded TL1-SP3. Still facing the same issue.

    I have assigned VNX array lun for alternate disk migration with powerpath installed. this could be lead to any issue.. suggest me.

    Regards,

    Karthik R.
  • sajjadhashimi
    sajjadhashimi
    35 Posts

    Re: NIMADM fails

    ‏2012-04-13T13:18:41Z  
    • rkbca
    • ‏2012-04-13T09:49:48Z
    Hi All,

    Thanks for your reply. Client TL is 5300-12-05-1140 and NIM master upgraded TL1-SP3. Still facing the same issue.

    I have assigned VNX array lun for alternate disk migration with powerpath installed. this could be lead to any issue.. suggest me.

    Regards,

    Karthik R.
    quick googling reveals one solution, worth looking into; (at the very bottom of the link)

    http://translate.google.com/translate?hl=en&sl=ru&tl=en&u=http%3A%2F%2Fwww.aixportal.ru%2Fforum%2F10-aixhardware%2F13666----aix-53--61.html

    If for some reason it doesn't work for you, google on

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

    and translate the link you see in russian :)

    Good Luck.
  • alethad
    alethad
    286 Posts

    Re: NIMADM fails

    ‏2012-04-13T15:36:33Z  
    • rkbca
    • ‏2012-04-13T09:49:48Z
    Hi All,

    Thanks for your reply. Client TL is 5300-12-05-1140 and NIM master upgraded TL1-SP3. Still facing the same issue.

    I have assigned VNX array lun for alternate disk migration with powerpath installed. this could be lead to any issue.. suggest me.

    Regards,

    Karthik R.
    What model SAN are you using? IBM or EMC or what?
    I found a little something similar to this for EMC but you didn't indicate what you're using.

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

    Re: NIMADM fails

    ‏2012-04-14T04:09:08Z  
    • alethad
    • ‏2012-04-13T15:36:33Z
    What model SAN are you using? IBM or EMC or what?
    I found a little something similar to this for EMC but you didn't indicate what you're using.

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

    I have assigned LUN from EMC VNX 7500. is there any setting needs to be done ? or is nimadm possible for emc array ?

    Regards,

    Karthik R
  • alethad
    alethad
    286 Posts

    Re: NIMADM fails

    ‏2012-04-16T19:53:01Z  
    • rkbca
    • ‏2012-04-14T04:09:08Z
    Hi,

    I have assigned LUN from EMC VNX 7500. is there any setting needs to be done ? or is nimadm possible for emc array ?

    Regards,

    Karthik R
    Here's a link to what I found online. Not sure it it's related to yours but thought it might be worth checking out.
    http://unix.ittoolbox.com/groups/technical-functional/ibm-aix-l/missing-proto-file-1120977

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

    Re: NIMADM fails

    ‏2012-04-16T19:58:14Z  
    • rkbca
    • ‏2012-04-14T04:09:08Z
    Hi,

    I have assigned LUN from EMC VNX 7500. is there any setting needs to be done ? or is nimadm possible for emc array ?

    Regards,

    Karthik R
    Here's another link. I sent the other and forgot to include this one.

    http://www.ibm.com/developerworks/forums/thread.jspa?threadID=351716

    Hope it helps.
    Good luck.

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

    Re: NIMADM fails

    ‏2012-09-04T08:22:50Z  
    I met the same problem

    First, make sure that /usr/lib/drivers/pci/sissas64_dd exists
    If not, copy sissas64_dd in the /usr/lib/drivers/pci on source server, then retry, I solved it

    but I faced the same problem in other server migration
    in this case, there is the sisas64_dd file.
    you need to recreate bos boot image.
    remove a /dev/ipldevice, /dev/IPL_rootvg and recreate that
    1. rm /dev/IPL_rootvg
    2. rm dev/ipldevice
    3. mknod /dev/IPL_rootvg c 10 0
    4. ln /dev/rhdiskx /dev/ipldevice
    5. bosboot -ad /dev/hdiskx
    6. bosboot -ad /dev/ipldevice
    7. shutdown -Fr