Home > Error Code > Aix 557 Error Code

Aix 557 Error Code


The /etc/inittab file is composed of entries that are position-dependent and have the following format, /etc/inittab format = Identifier:RunLevel:Action:Command Each entry is delimited by a newline character. Top Best Answer 0 Mark this reply as the best answer?(Choose carefully, this can't be changed) Yes | No Saving... if the file is not removed, then login is not possible. The easiest way to fix an unrecoverable file system is to recreate it. navigate here

Choose 0 continue. Do not continue with the rest of the steps in this document. Also outlined is a recovery procedure. mount /dev/hd2 in RAMFS. https://www-304.ibm.com/support/docview.wss?uid=isg3T1000217

0554 Error Code In Aix

run syncvg in background and report stale PPs. off If the process associated with this entry is currently running, send the warning signal (SIGTERM), and wait 20 seconds before terminating the process with the kill signal (SIGKILL). lslv -m hd5 WARNING: Do not proceed further if the system is a /usr client, diskless client, or dataless client. After entering SMS, choosing maintenance mode and accessing a root volume group without mounting file systems, I get the following: 0516-510 physical volume not found 0516-548 partially successful with updating root

the message system initialization completed is send to the console. If you have user-created file systems in the rootvg volume group, run fsck on them now. The next screen has the Maintenance Menu. 0517 Aix 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

A complete list of files that are part of the BLV can be obtained from directory /usr/lib/boot. The next screen displays information about all volume groups on the system. Correct the problem causing the error. http://www-01.ibm.com/support/docview.wss?uid=isg3T1000131 Display the processes: # ps -ef | grep find root 28972 13964 0 11:07:33 pts/0 0:00 grep find # To delete this record from the /etc/inittab file, you use the rmitab

If this doesn't appear to be working, type the following at the command line:     sync; sync; halt 13) If the problem still persists, consult your local SE before you attempt init executes rc.boot script from the BLV in the RAM. Note that hd9var and hd3 can be recreated, but hd4 and hd2 cannot be recreated. I suspect the second hard drive may be dead - when I bring up the configuration menu it shows up in the config with ????.

0552 Aix Error Code

Isolating the cause of the hang could be excessively time-consuming and may not be cost-effective in your operating environment. More Bonuses Boot your system into a limited function maintenance shell (Service or Maintenance mode) from bootable AIX media to use this recovery procedure. 0554 Error Code In Aix Either boot the system from boot diskettes or boot tape 2) Select option to perform system maintenance functions from the INSTALL and MAINTENANCE menu. 3) Enter the following command:/usr/sbin/getrootfs hdisk0 from 0518 Error Code Aix Action It tells the init command how to treat the process specified in the process field.

You don't want to get ‘paging space low' messages when creating a new boot image on /dev/hd5. http://bsnux.com/error-code/aix-517-error-code.html Submit feedback to IBM Support 1-800-IBM-7378 (USA) Directory of worldwide contacts Contact Privacy Terms of use Accessibility Recovery from LED 551, 555, or 557 in AIX V4 Contents About This Document If fsck indicates that a file system has an unknown log record type, or if fsck fails in the logredo process, then go to step 5. If they are full, erase files that aren't needed. Aix Led Codes

Enter the command/etc/continue hdisk0 from maintenance mode. To correct this situtation, perform the following steps: Boot system in service mode. Watson Product Search Search None of the above, continue with my search Recovery from LED 551, 555, or 557 in AIX V5 KnowledgeCollection Technote (FAQ) Question Recovery from LED 551, 555, his comment is here The entire command field is prefixed with exec and passed to a forked sh as sh -c exec command.

Another possibility is that a NEW SCSI device has been added to the system and there are two or more devices with the same SCSI ID. rm /etc/nologin i.e. The /tmp filesystem is mounted.

With bootable media of the same version and level as the system, boot the system.

alain replied Aug 19, 2008 hi hope this help LED 551, 555, and 557 - Corrupted File System, Corrupted JFS log, and so on. i. The cfgmgr command reads the Config_rules files from ODM and calls all methods corresponding to either phase 2 or 3. The bootable media can be any ONE of the following: Bootable CD-ROM mksysb Bootable Install Tape Follow the screen prompts to the Welcome to Base OS menu.

HMC, FSM, etc), select the VIOS partition and look at the Reference Code. 551 indicates VIOS rootvg activation (varyon) 555 means fsck error, fsck failure of / (root) filesystem, /dev/hd4 557 activate primary paging space. unmount /var swapon /dev/hd6 i.e. http://bsnux.com/error-code/aeg-c2-error-code.html Any legal sh command syntax can appear in this field.

Correct the problem causing the error. For example, if the LED count is 17 (minus the two for the native ports), then the second concentrator box is the problem. starts errdaemon for error logging. This flag can be used to avoid having to manually answer multiple confirmation prompts, however, use of this flag can cause permanent, unnecessary data loss in some situations.

Choose 0 continue. The following actions are recognized by the init command: respawn If the process does not exist, start the process. The rootvg has not yet been activated. LED display turned OFF.

LED codes displayed during this stage will be generic AIX 5L codes. g) All customized ODM files from the RAMFS are copied to disk.Both ODM versions from hd4 and hd5 are synchronized. I do not have a diagnostic CD but do have the original 4.3.2 installation disks. Base devices are all devices that are necessary to access rootvg.

d) The /usr file system is verified using fsck -f command and then mounted. If you receive errors from the preceding option, do not continue with the rest of this procedure. if the /etc/nologin exists, it will be removed. The next screen displays a warning that indicates you will not be able to return to the Base OS menu without rebooting.

Posted by anAND at 7:25 AM Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest No comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Blog Archive The init command is run as the last step of the startup process. 2. However all missed messages can be found in /var/adm/ras/conslog. Converter - Free Space White Papers & Webcasts Using Virtualization to Balance Work with TCO Deploy a dynamic, services-oriented cloud for your business Business VoIP Comparison Guide Simplified Enterprise Phone Systems