Software ROS then locates, loads, and turns control over to AIX 5L Boot Logical Volume (BLV). However, the imfs method is preferred since it uses information stored in the logical volume control block to re-populate the /etc/filesystems file. syncd daemon started. Recovery procedure 1. http://bsnux.com/error-code/aix-557-error-code.html
From your nim server, do : 1) smit nim_mac_op 2) choose the client to diagnose, 3) choose operation you want to do. The rootvg is synchronized by calling the synchvg command and launching it as background process. NIM master server not booting (LED 0517) abhi_bajaj_cse01 asked Mar 13, 2009 | Replies (5) Hello Everyone , I have a Big issue with my nim master server .i restated my Please refer to your system user's or installation and service guide for specific IPL procedures related to your type and model of hardware. this contact form
Lamar Saxon replied May 19, 2010 517 - Mounting client remote file system during network IPL. Base devices are all devices that are necessary to access rootvg. If the run level field is empty, this is interpreted as 0123456789. Choose Access this volume group and start a shell before mounting file systems (Option 2).
If the /etc/inittab file does not exist, the init command places the system in the maintenance run level by default. 5. Bootstrap code locates the Boot Logical Volume (BLV = hd5) from the harddisk BLV contains AIX kernel, rc.boot Script, Reduced ODM and Boot commands. The stdin, stdout, and stderr file descriptors may not be available while the init command is processing inittab entries. 557 Error Code Aix NOTE: The -y option gives fsck permission to repair file system corruption when necessary.
I brought the system up in maintenance mode , and 'fsck' says the root filesystems are clean. If the process is not running, ignore this entry. Companies Vision Solutions Toolbox for IT My Home Topics People Companies Jobs White Paper Library Collaboration Tools Discussion Groups Blogs Follow Toolbox.com Toolbox for IT on Twitter Toolbox.com on Twitter Toolbox.com http://www.tek-tips.com/viewthread.cfm?qid=1290352 rc.boot 2 in detail rc.boot 2 (LED 551) ipl_varyon to activate rootvg ( success LED= 517, error LED=552,554,556).
Display the processes: # ps -ef | grep find root 20378 13964 0 11:07:20 pts/0 0:00 grep find root 28970 1 4 11:05:46 - 0:03 find / -type f 3. 0555 Error In Aix If you get errors from the preceding option, do not continue with the rest of this procedure. It will locate and load bootstrap code. System ROS contains generic boot information and is operating system independent.
Thread Tools Show Printable Version Email this Page… Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode September 28th,04:50 PM #1 Boot error message - If CDE mentioned in /etc/inittab we will get graphical console. Ibm Reference Code 0517 You're now being signed in. 518 Error Code Aix 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
Any entries writing to stdout or stderr may not work predictably unless they redirect their output to a file or to /dev/console. http://bsnux.com/error-code/aix-517-error-code.html Register now while it's still free! Since NFS requires TCP/IP daemons to run correctly, TCP/IP daemons are started ahead of the NFS daemons. David Kirkby. ---------------------------------- Email address can be found at: [url]http://homepage.ntlworld.com/drkirkby/home-email.jpg[/url] Dr. 517 Error Code Aix
Resources Join | Indeed Jobs | Advertise Copyright © 1998-2016 ENGINEERING.com, Inc. so configuration data has been written to ODM of RAMFS. Select the root volume group by number. 7. weblink It is during this step that you can press a function key to choose a different boot list.
system initialization During system startup, after the root file system has been mounted in the pre-initialization process, the following sequence of events occurs: 1. Aix Boot Code 557 lsitab Lists records in the /etc/inittab file. Any ideas/experience with this ?
rc.boot 1 in detail init process from RAMFS executes rc.boot 1 (if any error LED=c06) restbase command copies ODM from BLV to RAMFS.(success LED=510, error LED=548) cfgmgr -f calls Config_rules ( I must admit as to not > knowing my way around the AIX log files yet, so that is one I will > have to investigate. "man errpt" for some options You may want to boot into maintenance mode or single user and edit /etc/filesystem to remove any remote mounts. 0552 Aix Error Code The alog command maintains and manages logs. 3.Boot Phase 3 After phase 2 is completed rootvg is activated and the following steps are taken, a. /etc/init process is started.
The bootable media can be any ONE of the following: Bootable CD-ROM NON_AUTOINSTALL mksysb Bootable Install Tape Follow the screen prompts to the following menu: Welcome to Base Operating System Installation To temporarily replace the disk-based /etc/filesystems file, run the following commands: mount /dev/hd4 /mnt mv /mnt/etc/filesystems /mnt/etc/filesystems.[MMDDYY] cp /etc/filesystems /mnt/etc/filesystems umount /mnt MMDDYY represents the current two-digit representation of the Month, Init with rc.boot 1 configures base devices. http://bsnux.com/error-code/aix-518-error-code.html Thanks and Regards Anupam Chauhan Top Best Answer 0 Mark this reply as the best answer?(Choose carefully, this can't be changed) Yes | No Saving...
They differ from run levels in that the init command can never enter run level a, b, c or h. After the configuration of the console , boot messages are send to the console if no STDOUT redirection is made. Boot your system into a limited function maintenance shell (Service, or Maintenance mode) from AIX bootable media to perform file system checks on your root file systems. The most important components are the following: - The AIX 5L kernel - Boot commands called during the boot process such as bootinfo, cfgmgr - A reduced version of the ODM.
Now the condition is /dev/hd4 is mounted on / in the RAMFS; cfgmgr -f configured all base devices . At this stage, the restbase command is called to copy a partial image of ODM from the BLV into the RAMFS. The procedure described is useful when file system corruption in the primary root file systems is suspected or, in many cases, to correct an IPL hang at LED value 517, 518, The error message on > > the display of my IBM RS/6000 7025 F50 is: > > 0517 > > SYNCVG ROOTVG > > > > not as I said previosly.
This document applies to AIX versions 4 and 5. Recovery procedure Boot your system into a limited function maintenance shell (Service, or Maintenance mode) from AIX bootable media to perform file system checks on your root file systems. init from BLV replaced by init from hard disk in rc.boot 3, init process /etc/inittab file and remaining devices are configured. 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.
once When the init command enters a run level that matches the entry's run level, start the process, and do not wait for termination. developerWorks Maintenance Updates Connect with IBM developerWorksdeveloperWorks on FacebookdeveloperWorks on TwitterdeveloperWorks on LinkedIndeveloperWorks on YouTubedeveloperWorks on Google+ Login with LinkedIN Or Log In Locally Add a record named xcmd on the /etc/inittab using the mkitab command: # mkitab "xcmd:2:respawn:find / -type f > /dev/null 2>&1" 3. There is no console available at this stage; so all boot messages will be copied to alog.
Restart the process when it dies.