BOOT PHASE 2

Boot phase 2

In boot phase 2, the rc.boot script is passed to the parameter 2.

During this phase, the following steps are taken.

The rootvg volume group is varied on with the special version of the varyonvgcommand named the ipl_varyon command. If this command is successful,the system displays 517
; otherwise, one of the following LED codes willappear: 552, 554, or 556, and the boot process is halted.

Root file system hd4 is checked using the fsck -f command. This will verifywhether the file system was unmounted cleanly before the last shutdown.

If this command fails, the system will display code 555.

The root file system (/dev/hd4) is mounted on a temporary mount point (/mnt)in RAMFS.

If this fails, 557 will appear in the LED display.
IBM Eserver p5 and pSeries Administration and Support for AIX 5L V5.3
The /usr file system is verified using the fsck -f command and thenmounted. If this operation fails, the LED 518 appears.

The /var file system is verified using the fsck -f command and thenmounted. The copycore command checks if a dump occurred. If it did, it iscopied from default dump devices, /dev/hd6, to the default copy directory,/var/adm/ras.

Afterwards, /var is unmounted. The primary paging space from rootvg, /dev/hd6, will be activated. The mergedev process is called and all /dev files from the RAM file systemare copied onto disk. All customized ODM files from the RAM file system are copied to disk.

Both ODM versions from hd4 and hd5 are now synchronized. Finally, the root file system from rootvg (disk) is mounted over the root filesystem from the RAMFS. The mount points for the rootvg file systemsbecome available.

Now, the /var and /usr file systems from the rootvg aremounted again on their ordinary mount points.There is no console available at this stage, so all boot messages will be copied to alog. The alog command maintains and manages logs.