If any of the following conditions occur, proceed accordingly. This is effectively a whitelist for environment variables. 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. fsck: Not a recognized file system type. navigate here
The logical volumes in rootvg will be displayed with two options below. Recovery from LED 552, 554, or 556 in AIX 3.1 or 3.2 Warning: Please do not use this document if the system is a /usr client, diskless client, or dataless client. If your /etc/inittab file was corrupt and you recreated it, the following steps may not be necessary. The time now is 04:07 AM.
to the following: PATH=/bin:/usr/bin/:/etc:/usr/ucb:. If the inittab file is corrupt, set your terminal type in preparation for editing the file. (xxx stands for a terminal type, such as lft, ibm3151, or vt100.) TERM=xxx export TERM df /dev/hd3 df /dev/hd4 If the output from the df command shows that either file system is out of space, erase some files from that file system. By aaa in forum AIX Replies: 3 Last Post: July 18th, 07:47 AM mksysb restore fails: Could not copy volume group information to the disk By Theo Welters in forum AIX
If step 4 is successful, continue to step 8. have been observed to cause a hang at LED 553. It may be empty or missing, or it may have an incorrect entry. Topics AIX (224)Backup & restore (35)DB2 (6)EMC (13)EMC Networker (3)Fun (3)GPFS (10)Hardware (9)HMC (14)HP Output Server (17)IBM Content Manager (20)Installation (30)Logical Partitioning (6)LVM (14)Monitoring (13)Networking (17)NIM (12)ODM (4)Oracle (3)Performance (12)PowerHA /
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. Hope this helps Mark -- Posted via http://dbforums.com Mark Guest October 31st,10:47 PM #3 Re: mksysb Restore Problem - LED Error Code 0554 netcom.com (Chris Peek) wrote in message news:
I have been trying for two days to move the rootvg with no luck. Top This thread has been closed due to inactivity. In reviewing the devinst.log file today, we determined that the install process was unable to find the /usr/share directory. For systems of 5.1 and above, make sure that hd5 is greater than 12 MB: lslv hd5 (Check to see what the PP Size: is equal to) lslv -m hd5 LP
Okay, so what if you need to run a command through sudo that requires a certain environment variable? If the file system checks were successful, skip to step 8. Aix Led Codes The next screen contains prompts for the Maintenance menu. It may look something like this: An easy fix for this issue is to cahnge the character set translation within PuTTY.
If step 4 is successful, continue to step 8. 7) With the key in the Normal position, run the following commands to reboot the system: # exit # sync;sync;sync # shutdown http://bsnux.com/aix-error/aix-error-code-20ee000b.html Instead, run the command on the VIOS instead. This involves deleting it from the system and restoring it from a very current system backup. Watson Product Search Search None of the above, continue with my search Recovery from LED 552, 554, or 556 in AIX ProblemDeterminationDocument Technote (FAQ) Question Recovery from LED 552, 554, or
But for production systems, that may not always be possible. Number of results found: 381.Displaying results: 21 - 30.← Previous EntriesNext Entries → Order No time to lose? IBM's supported way is to use a mksysb to move the rootvg and then do exportvg and importvg on the data/user volume groups. http://bsnux.com/aix-error/aix-error-code-e14d.html If the file system checks were successful, skip to step 8.
Cancel Red Flag SubmittedThank you for helping keep Tek-Tips Forums free from inappropriate posts.The Tek-Tips staff will check this out and take appropriate action. The bootable media can be any one of the following: – A bootable CD-ROM – mksysb – A bootable install tape Follow the prompts to the Welcome to Base OS menu. All these settings and regulations more than often result in people getting locked out from their accounts on AIX systems, and also getting frustrated at the same time.
For AIX 3.2 only, run the following commands, which will remove much of the system's configuration, saving it to a backup directory. If fsck indicates that block 8 could not be read, the file system is probably unrecoverable. To aid the user, it could be useful to clear the password history for his or her account, so he or she can re-use a certain password that has been used Otherwise, go to step 16.
Recovery procedure Boot your system into a limited function maintenance shell (Service or Maintenance mode) from AIX bootable media. lslv -m hd5 Save the clean ODM database to the boot logical volume. ('#' is the number of the fixed disk, determined with the previous command.) savebase -d /dev/hdisk# If you Does anyone have ideas? http://bsnux.com/aix-error/aix-error-code-0c46.html The -y option gives the fsck command permission to repair file systems when necessary. # fsck -y /dev/hd1 # fsck -y /dev/hd2 # fsck -y /dev/hd3 # fsck -y /dev/hd4 #
Home | Invite Peers | More UNIX Groups Your account is ready. Register Forum Archives Operating Systems Linux and UNIX AIX mksysb Restore Problem - LED Error Code 0554 mksysb Restore Problem - LED Error Code 0554 - AIX I am in the To recover follow below procedure: 1) Start the Service mode boot from CD-ROM or mksysb. 2) Using bootable media at the same version and level as the system, boot the system. The easiest way to fix an unrecoverable file system is to recreate it.
By joining you are opting in to receive e-mail. ln -s /usr/bin /bin ln -s /usr/lib/boot/unix /unix ln -s /usr/lib /lib ln -s /home /u Use the following command to make sure that rc.boot is not missing or corrupt. Do not follow the rest of the steps in this fax. With BOSboot diskettes or tape of the same version and level as the operating system, boot the system.
Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework. This flag can be used to avoid having to manually answer multiple confirmation prompts, however, use of this flag can cause permanent data loss in some situations. If you have only one disk, then hdisk0 is the proper hdisk# to use. The use of this information is the sole responsibility of the customer and depends on the customer's ability to evaluate and integrate this information into the customer's operational environment.
Also, you can just configure an IP address on it, and see if it will work. SUID/GUID examples No SUID/GUID: Just the bits rwxr-xr-x are set: # ls -lt test.pl -rwxr-xr-x 1 root root 179 Jan 9 01:01 test.pl SUID and user's executable bit enabled (lowercase s): To get information from Red Hat on recommended swap space sizes, take a look here: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/5/html/Deployment_Guide/ch-swapspace.html. Some known causes of an LED 552, 554, or 556 are: a corrupted file system a corrupted Journaled File System (JFS) log device a bad IPL-device record or bad IPL-device magic