Below are the download and install/uninstall instructions. You would have to check the rc.boot script, but i think 554 comes from the return code from ipl_varyon -v ... (return code 7 or 8) I would check you have If the file system check fails, you may need to perform other steps. I am working with a 9111-510 server. navigate here
The following is information about an ifix that was made available by IBM. Select the root volume group by number. Un-tar it: # tar xf openssl-18.104.22.1681.tar That will give you folder openssl-22.214.171.1241 within your current folder. does the 630 have the latest ML on before making the mksysb ? http://www-01.ibm.com/support/docview.wss?uid=isg3T1000132
Causes of an LED 552, 554, or 556 The known causes of an LED 552, 554, or 556 during IPL on a RISC System/6000 are: A corrupted file system. Run the following commands, which remove much of the system's configuration and save it to a backup directory. Are you aComputer / IT professional?Join Tek-Tips Forums! If the file system checks were successful, skip to step 8.
Now skip to step 7. 5) A corruption of the JFS log logical volume has been detected. mount /dev/hd4 /mnt mount /dev/hd2 /usr mkdir /mnt/etc/objrepos/bak cp /mnt/etc/objrepos/Cu* /mnt/etc/objrepos/bak cp /etc/objrepos/Cu* /mnt/etc/objrepos /etc/umount all exit Determine which disk is the boot disk with the lslv command. I have solved this problem finally with the help of IBM support. If you are running the Andrew File System (AFS), use the following commands to find out whether you have more than one version of the v3fshelper file.
In most cases, step 4 will be successful. http://www.justskins.com/forums/mksysb-restore-problem-led-179439.html Moreover, performing the scripts on a 3.1 system with 3.2 boot media may actually remove some files and prevent your system from booting successfully in normal mode until missing files (/etc/mount Aix Led Codes The new environment contains the TERM, PATH, HOME, MAIL, SHELL, LOGNAME, USER, USERNAME and SUDO_* variables in addition to variables from the invoking process permitted by the env_check and env_keep options. You can find OpenSSL in the IBM Web Download Pack at: http://www-03.ibm.com/systems/power/software/aix/expansionpack/ Click on Downloads (on the right), log in with your IBM user ID (or register for one, if you
If booting from diskettes, when you see LED c07, insert the next diskette. Note that hd2 and hd3 can be recreated but hd4 cannot be recreated. Do not follow the rest of the steps in this procedure. We've put all those tricks together in one simple script, that can fix a user account, and we called it fixuser.ksh.
With bootable media of the same version and level as the system, boot the system into Service mode. The next screen displays prompts for the Maintenance menu. I have been trying for two days to move the rootvg with no luck. This can be the cause of: A damaged file system A damaged journaled file system (JFS) log device A bad IPL-device record or bad IPL-device magic number (the magic number indicates
You may have to fail over the Etherchannel to a backup adapter, to determine the switch information for the backup adapter in the Etherchannel configuration. Click on the "fromibm" folder, and then click on the "aix" folder. We currently recommend downloading OpenSSL 126.96.36.1991.
A corrupted file system ? For more information, see http://heartblead.com. Resources Join | Indeed Jobs | Advertise Copyright © 1998-2016 ENGINEERING.com, Inc. If you receive errors from the preceding option, do not continue with the rest of this procedure.
When finished, run logform -dev/hd8 and reply yes. For reasons of time, and the for integrity of your AIX operating system, the best alternative at this point may be to reinstall AIX. Join this group Popular White Paper On This Topic ERP Overview Comparison Guide 1Reply Best Answer 0 Mark this reply as the best answer?(Choose carefully, this can't be changed) Yes | A corrupted Journaled File System (JFS) log device ?
It's a shared library update, so any daemons that use it will need to be restarted such as sshd. Then, figure out how the current swap spaces are configured now: # cat /proc/swaps Filename Type Size Used Priority /dev/dm-1 partition 8388604 8262740 -1 /dev/dm-8 partition 8388604 0 -2 This shows Follow the prompts to the installation/maintenance menu. The logical volumes in rootvg will be displayed with two options below.
If the file-system check fails, you may need to perform other steps. The command you can use to disable the password history for a user is: # chuser histsize=0 username Actually, this command does not the password history in /etc/security/pwdhist.dir and /etc/security/pwdhist.pag, but When this file when executed (if it's a program and not just a shell script), it will run with the permissions of the owner or the group of the file. Correct the problem causing the error.
Log In E-mail or User ID Password Keep me signed in Recover Password Create an Account Blogs Discussions CHOOSE A TOPIC Business Intelligence C Languages Cloud Computing Communications Technology CRM Top This thread has been closed due to inactivity. Try it again with new BOSboot diskettes or tape.