Did your procedure fix your problem? If so, could you please mark this thread as answered - that way when someone else has a similar problem, they will be able to search and use your procedure as it is "answered".
perhaps this has nothing to do with other hardware or os. Last weekend I had a similar problem with blv after migrating on existing systems to a higher TL level of AIX (from AIX 5.3 TL9 to 12)
A long while ago I used this script to remove all disks in my environment:
Then reboot and use the following EMC procedure: emc92878
em: After upgrading AIX 5.2 to ML03 (Maintenance Level 3), the bootlist command shows - (dash) in the device list for an available hdisk# a below: Before upgrade to ML03 : #bootlist -m normal -o hdisk17 hdisk6 # After upgrade to ML03 : #bootlist -m normal -o - <--- (error) hdisk17 # Change: Upgrade AIX 5.2 from ML02 to ML03 Root Cause: This issue has been seen if the hdiskpower entry is located before hdisk entry in the ODM CuDv table. AIX code checks the first device th the wwpm and LUN and assumes that all devices are of subclass "fcp". The first device matched in this case is hdiskpower0 because it has the same wwpn and lun#. However, the subclass is "pseudo" which i recognised by AIX code. Fix: In this fix description , we are assuming that rootvg is on hdiskpower0 #powermt display dev=0 Pseudo name=hdiskpower0 Symmetrix ID=000287460464 Logical device ID=027F state=alive; policy=SymmOpt; priority=0; queued-IOs=0 ============================================================================== ---------------- Host --------------- - Stor - -- I/O Path - -- Stats --- ### HW Path I/O Paths Interf. Mode State Q-IOs Errors ============================================================================== 1 fscsi1 hdisk17 FA 13cA active alive 0 0 0 fscsi0 hdisk6 FA 4cA active alive 0 0 #bootlist -m normal -o hdisk17 - <<<<<<< hdisk6 is missing # Procedure : 1. save hdiskpower0 entry in a file : odmget -q"name=hdiskpower0" CuDv > /tmp/hdiskpower0.add 2. save hdisk6 (hdisk with - in bootlist) entry in a file : odmget -q"name=hdisk6" CuDv > /tmp/hdisk6.add 3. delete hdiskpower0 entry fron CuDv : odmdelete -o CuDv -q"name=hdiskpower0" 4. delete hdisk6 entry fron CuDv : odmdelete -o CuDv -q"name=hdisk6" 5. adds hdisk6 back : odmadd /tmp/hdisk6.add 6. check if bootlist is ok : bootlist -m normal -o 7. adds hdiskpower0 back : odmadd /tmp/hdiskpower0.add 8. check if bootlist is ok : bootlist -m normal -o 9. if all the above is ok , you can save the changes to boot image : savebase -v 10. reboot the host 11. check if bootlist is ok : bootlist -m normal -o or for more details : bootlist -m normal -v -r
In my case I removedall hdiskpowerX entries before the hdisk with blv on it. Try it out!
kelleg
6 Operator
•
4537 Posts
1220
0
Posted November 29th, 2010 10:00
Mariano,
Did your procedure fix your problem? If so, could you please mark this thread as answered - that way when someone else has a similar problem, they will be able to search and use your procedure as it is "answered".
Thanks,
glen