If you need assistance correcting the problem causing the error, contact one of the following: local branch office your point of sale your AIX support center Run the following commands to Cesar Delgado replied Mar 12, 2005 Hi i have the following document for IBM site: Recovery from LED 552, 554, or 556 in AIX Versions 4 and 5 This document discusses A corrupted file system ? The time now is 04:26 AM.

Any ideas ??? The majority of instances of LED 552, 554, and 556 will be resolved at this point. Bureau of the CensusVollansicht - 1992Money Income of Households, Families, and Persons in the United States, Band 3Vollansicht - 1990Alle anzeigen »Häufige Begriffe und Wortgruppen__ 9 __________________ __ dollars__ __dollars $29,999 Make sure that the disk drive that you have chosen as your bootable device has a yes next to it: ipl_varyon -i Example: PVNAME BOOT DEVICE PVID VOLUME GROUP ID hdisk1

This tool uses JavaScript and much of it will not work correctly without it enabled. Repeat step 4 for all file systems that did not successfully complete fsck the first time. If the file system checks were successful, skip to step 8. Repeat step 1 through step 3.

If hd4 and/or hd2 is unrecoverable, AIX must be reinstalled or restored from system backup. No spaces please The Profile Name is already in use Password Notify me of new activity in this group: Real Time Daily Never Keep me informed of the latest: White Papers Join your peers on the Internet's largest technical computer professional community.It's easy to join and it's free. Submit feedback to IBM Support 1-800-IBM-7378 (USA) Directory of worldwide contacts Contact Privacy Terms of use Accessibility Home Services Forums Advertise Contact or Login Login to Your Account Remember Me?

By joining you are opting in to receive e-mail. Series P-23, Ausgabe 181Vollansicht - 1992Current Population Reports: Population characteristics. The next screen displays prompts for the Maintenance menu. Attempt to repair the file system with this command: # fsck -p /dev/hd# Replace hd# with the appropriate file system logical volume name.

This document was originally written for AIX Versions 4 and 5 but applies to all versions. Thanks. In reviewing the devinst.log file today, we determined that the install process was unable to find the /usr/share directory. Now skip to step 7. 5) A corruption of the JFS log logical volume has been detected.

A corrupted Journaled File System (JFS) log device ? 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 6. Please enter a title. If fsck indicates that block 8 could not be read, the file system is probably unrecoverable.

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. I have tried it three different ways: 1) Build a Generic mksysb DVD backup from the p630 and then boot from it on the p615 2) Build a personal mksysb DVD Hopefully this helps someone else who may encounter this. If any of the following conditions occur, proceed accordingly.

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 If step 4 is successful, continue to step 8. 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. The easiest way to fix an unrecoverable file system is to recreate it.

The easiest way to fix an unrecoverable file system is to recreate it. I have then tried the steps covered in the Problem Solving guide to recover from the 0554 LED error. lppchk -v --> ok df -k --> fs ok ? So i am trying to connect directly, or do we need to configure RMAN? * C:\Users\praveen kumar gogula>RMAN target / Recovery Manager: Release 11.2.0.1.0 - Production on Thu Sep 22 17:11:52

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:... If you get errors from the preceding option, such as missing hard disk messages, do not continue with the rest of this procedure. Nonetheless, the solution was to correct the p630 first. Bureau of the CensusVerlagU.S.

I have solved this problem finally with the help of IBM support. 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 Thus, on the source machine I did a backup on the /usr3/share directory, expanded the /usr filesystem with more space, restored the backup to the /usr/share directory, recreated a "Generic DVD Please type your message and try again.

It is NOT recommended to use the following procedure in lieu of restoring from a system backup. cd /sbin/helpers ls -l v3fshelper* If you have only one version of the v3fshelper file (for example, v3fshelper), proceed to step 12. As for why it was done, the only thing that comes up is someone needing space and decinding to do this trick rather than expanding the filesystem - not an issue 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