Unable to save the base customized information on /dev/ipldevice using cfgmgr command on AIX
Hello,
I am getting the following error when i run cfgmgr commands on aix 6.1, please assist.
# cfgmgr
cfgmgr: 0514-609 Unable to save the base customized information
on /dev/ipldevice.
............
# ls -l /dev/ipldevice
crw------- 2 root system 17, 0 May 10 18:42 /dev/ipldevice
rootvg is not mirrored and there are not stale pv's in rootvg
I am getting the following error when i run cfgmgr commands on aix 6.1, please assist.
# cfgmgr
cfgmgr: 0514-609 Unable to save the base customized information
on /dev/ipldevice.
............
# ls -l /dev/ipldevice
crw------- 2 root system 17, 0 May 10 18:42 /dev/ipldevice
rootvg is not mirrored and there are not stale pv's in rootvg
ASKER
no modification were made to any disks in rootvg.
the cfgmgr error occurred after i mapped a lun from vio to the lpar via a script on nim.
first cfgmgr command worked, whereas the second cfgmgr gave that error, so right now i have only one active path on the new disk.
# ls -il /dev/ipldevice /dev/r$(bootinfo -b)
304 crw------- 2 root system 17, 0 May 10 18:42 /dev/ipldevice
304 crw------- 2 root system 17, 0 May 10 18:42 /dev/rhdisk0
the cfgmgr error occurred after i mapped a lun from vio to the lpar via a script on nim.
first cfgmgr command worked, whereas the second cfgmgr gave that error, so right now i have only one active path on the new disk.
# ls -il /dev/ipldevice /dev/r$(bootinfo -b)
304 crw------- 2 root system 17, 0 May 10 18:42 /dev/ipldevice
304 crw------- 2 root system 17, 0 May 10 18:42 /dev/rhdisk0
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
No, the disk was for non rootvg.
After performing the first two steps
synclvodm rootvg
bosboot -a -d /dev/ipldevice
cfgmgr worked, and resolved the issue, but do i still need to execute the following third command
bosboot -a -d hdisk0
After performing the first two steps
synclvodm rootvg
bosboot -a -d /dev/ipldevice
cfgmgr worked, and resolved the issue, but do i still need to execute the following third command
bosboot -a -d hdisk0
No,
it's fully equivalent to bosboot -a -d /dev/ipldevice
I only suggested using it in case the other command wouldn't work.
Glad to hear that it works now!
wmp
it's fully equivalent to bosboot -a -d /dev/ipldevice
I only suggested using it in case the other command wouldn't work.
Glad to hear that it works now!
wmp
ASKER
ok. do you know if the combination of both commands fixed the issue or was it just one of them, from the following two commands that fixed the issue.
synclvodm rootvg
bosboot -a -d /dev/ipldevice
synclvodm rootvg
bosboot -a -d /dev/ipldevice
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
did you recently replace a disk in your rootvg?
Anyway, we'll have to determine what your actual boot device is and
whether /dev/ipldevice (which is a hard link) points to this disk.
So issue
ls -il /dev/ipldevice /dev/r$(bootinfo -b)
Now compare the major/minor numbers (columns 5 and 6, "17, 0" in your example) and the inode numbers (column 1) of the shown devices.
If they're not identical (which I assume) please post the output of the command I gave you. We will then try to correct this issue by recreating the "ipldevice" hardlink.
wmp