BOOT PHASE 3

Boot phase 3

After phase 2 is completed, rootvg is activated and the following steps are taken:

/etc/init process is started. It reads the /etc/inittab file and calls rc.boot with argument 3.

The /tmp file system is mounted.The rootvg is synchronized by calling the syncvg command and launching itas a background process. As a result, all stale partitions from rootvg areupdated.

At this stage, the LED code 553 is shown.

At this stage, the cfgmgr command is called; if the system is booted in normalmode,

the cfgmgr command is called with option -p2; if the system is bootedin service mode, the cfgmgr command is called with option -p3. The cfgmgrcommand reads the Config_rules file from ODM and calls all methodscorresponding to either phase=2 or phase=3.

All other devices that are notbase devices are configured at this time.

Next, the console is configured by calling the cfgcon command. After theconfiguration of the console, boot messages are sent to the console if noSTDOUT redirection is made.

However, all missed messages can be found in/var/adm/ras/conslog. LED codes that can be displayed at this time are:

-c31: Console not yet configured. Provides instructions to select console.– c32: Console is an LFT terminal.

– c33: Console is a TTY.

-c34: Console is a file on the disk._ Finally, the synchronization of the ODM in the BLV with the ODM from the /(root) file system is done by the savebase command.

_ The syncd daemon and errdemon are started.

_ The LED display is turned off.

_ If the file /etc/nologin exists, it will be removed.

_ If there are devices marked as missing in CuDv, a message is displayed on