Working with the ODM ► March (1) ► 2011 (7) ► September (3) ► February (1) ► January (3) ► 2010 (3) ► February (1) ► January (2) ► 2009 (11) but when i exit i get serial of messages that looks like this/etc/getrootfs : 3*** Killed(the stars are different numbers every time)Any idea how to start this LPAR up?RegardsKhalid RE: LED In most cases, step 4 will be successful. Search This Blog Loading... his comment is here
Join your peers on the Internet's largest technical computer professional community.It's easy to join and it's free. Due to the potential loss of user configuration data caused by this procedure, it should only be used as a last resort effort to gain access to your system to attempt then run /usr/sbin/logforn /def/hd8 answer yes to questio.theb do lslv -m hd this will tell where ODM thinks boo lives do a ls -l /dev/hdisk(number from lslv command) compare it to Copyright © 2006 - 2014, JustSkins.com 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 http://www-01.ibm.com/support/docview.wss?uid=isg3T1000132
For AIX 3.1 to 3.2.3e: Execute the following command: lqueryvg -Atp hdisk# | grep hd5 for each hdisk# (hdisk0, hdisk1, etc.) until you qet output that looks like the following: 00005264feb3631c.2 Choose Access this volume group and start a shell before mounting the file systems (Option 2). I have been trying for two days to move the rootvg with no luck.
Run the following commands to check and repair file systems. 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 | If fsck indicates that block 8 could not be read, the file system is probably unrecoverable. Aix Error Codes List Use the logform command to reformat it.
Do not follow the rest of the steps in this document. Aix 554 San Boot After I restore the tape I try install the latest TL 04 with SP 3 code using smitty update_all and I get no errrors, but when I reboot the box it This may be the optional display extensions diskette (required for AIX 3.2.5) or the display diskette. from a fax machine phone).
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 Error Code 554 Denied 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 A bad IPL-device record or bad IPL-device magic number (The magic number indicates the device type.) ? You may use any of the disks identified to be in 'rootvg' in the following step. Now access the rootvg volume group by running /etc/continue (for AIX 3.1) or getrootfs
hth Hajo . http://unix.ittoolbox.com/groups/technical-functional/ibm-aix-l/554-error-682670 If you still have an LED 552, 554, or 556, try the following steps: Repeat steps 1 through 4. Aix 554 Unknown Boot Disk Follow the screen prompts to the Welcome to Base OS menu. Aix Led 554 Otherwise, go to step 16.
If you receive errors from the preceding option, do not continue with the rest of this procedure. http://bsnux.com/error-code/aix-517-error-code.html Toolbox.com is not affiliated with or endorsed by any company listed at this site. I've tried different mksysb's. then go to step 8. 0552 Aix Error Code
Causes of an LED 552, 554, or 556 Recovery procedure Recommended fixes Causes of an LED 552, 554, or 556 An LED code of 552, 554, or 556 during a standard Close Reply To This Thread Posting in the Tek-Tips forums is a member-only feature. 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. weblink Run the following commands, which remove much of the system's configuration and save it to a backup directory.
If the file system checks were successful continue The majority of instances of LED 552, 554, and 556 will be resolved at this point. Smtp Error Code 554 Not reading the redbook: Certification Study Guide - AIX 5L Problem Determination Tools and Techniques http://www.redbooks.ibm.com/redbooks/pdfs/sg246185.pdf From the above book: .... 3.4.2 LED 552, 554, or 556 A LED code of The easiest way to fix an unrecoverable file system is to recreate it.
SAN boot hang on 554 unixnguyen asked Feb 26, 2008 | Replies (1) We have AIX 5.2TL09 servers booting of the SAN disk (IBM ESS 800) with SDDPCM; we are upgrading Boot your system into a limited function maintenance shell (Service or Maintenance mode) from bootable AIX media to use this recovery procedure. Run fsck on each fs and check that they are not full. Email Error Code 554 At this stage, the console will display information about all the volume groups on the system.
Solve problems - It's Free Create your account in seconds E-mail address is taken If this is your account,sign in here Email address Username Between 5 and 30 characters. I have been working with IBM installation and SAN teams for the last 5 days and tried a lot of different things, but could not get pass 554 LED. Notes: For information on BOSboot diskettes, refer to InfoExplorer or order fax #2462 from 1-800-IBM-4FAX (or 415-855-4FAX outside the U.S. http://bsnux.com/error-code/aeg-c2-error-code.html You mentioned a replaced/newly assigned FC adapter.
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 Can the LPAR still access its LUNs?It isn't trying to boot from another LPAR's LUNs I hope? For AIX 3.1: cd /etc/helpers For AIX 3.2: cd /sbin/helpers Then in both AIX 3.1 and 3.2, ls -l v3fshelper* If you have only one version of the v3fshelper file (for Attempt to repair the file system with this command: # fsck -p /dev/hd# Replace hd# with the appropriate file system logical volume name.
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. Select the root volume group by number. 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 I have then tried the steps covered in the Problem Solving guide to recover from the 0554 LED error.