Can anyone explain me the detailed booting procedure on Solaris 2.8
Regards,
Max29583
Can anyone explain me the detailed booting procedure on Solaris 2.8
Regards,
Max29583
HI ........
I was just putting this together for my group. I think this will guide you well.
Remi
______________________________________________________________
Solaris Installation Guide
Solaris
All servers are installed with the Solaris 8 Operating Systems.
OS was manually installed on each server. No custom jumpstart was initiated due to the incompatibility of software between Sun & Eclipsys.
The following guides you through a quick installation.
Installation could be through command line if you're using a laptop as a connection or GUI interface, either way, the prompts are still the same.
Before you begin: You will need the following information: IP address, netmask and hostname of the system.
1) Installation starts at the OK> prompt, which you can get to by doing any of these methods:
2) Starting the Installation: Insert either the �Installation� or �Operating Environment�
CD and type boot cdrom at the OK> prompt.
** Either CD will take you through the installation **
The first phase starts with system identification & information about the system. It asks you about the language and locales you want to use
Next, you are to identify: A) The Hostname for the system
B) Whether the system is networked or non-networked
If networked, then provide the IP address & netmask for this machine.
3) Next you will be asked to select the name services
Name services
[ ] NIS+
[ ] NIS
[ ] DNS
[X ] None
Select the service if you have complete details like domain names etc or select none to configure after installation.
4) OS distribution & Disk configuration
After identification is complete the installation process proceeds on to the OS and disk configuration and need your input for these settings. Selection depends on role of your machine
Typical space requirement for Solaris is given here.
[X] Entire Distribution plus OEM support 64-bit 1242.00 MB (F4 to Customize
[ ] Entire Distribution 64-bit ...............1215.00 MB
[ ] Developer System Support 64-bit.... 1154.00 MB
[ ] End User System Support 64-bit ...... 765.00 MB
[ ] Core System Support .............. .334.00 MB
� Entire distribution with OEM has all software with some third party software
� Entire distribution has all software without third party software .
� Developer system has run time libraries for C software etc.
� End user has X windows and CDE environment .
� Core system is without X windows softwares etc.
5) You will be presented with choice to select the boot disk among the disks present in the
system ,unless you have reasons select the c0t0d0 at boot disk.
[ X ] c0t0d0 \(17269 MB\) boot disk 17269 MB
[ ] c0t1d0 \(17269 MB\) 17269 MB
overlap partition represents entire disk and is slice s2 of the disk partition .
Next the current layout is given \( if existing \) and you are asked to select between
Automatic and Custom layout of disk partitions.
� Automatic layout make a single partition of entire boot disk.
� Customize option gives and option to create the partitions and select the sizes.
Things to keep in mind while doing interactive or custom installation
� Additional space is required in /var & /home if server is to handle mail and printing as mail and print files are formed in /var & if the user home directories are to be located on /home partition
A sample partition table may look like following.
File system/Mount point Disk/Slice Size
---------------------------------------
/ c0t0d0s0 300 MB
swap c0t0d0s1 2000 MB
overlap c0t0d0s2 17269 MB
/usr c0t0d0s3 2000 MB
/opt c0t0d0s4 1000 MB
/var c0t0d0s5 1000 MB
*** The swap partition size depends on the size of RAM in the system if you are not sure of its size keep it double the RAM or more than RAM in the system.
If you are not sure of individual partition sizes of /, /usr /opt & /var make one partition as / and keep its size sufficiently higher than the distribution size you have selected in earlier steps . Always keep in mind the future software that you might have to install like compilers applications etc and log files that will be generated and accumulate in /var directory or partition.
After you have specified the partition sizes it gives summary and error if any
Installation Option: Initial
Boot Device: c0t0d0s0
Client Services: None
Software: Solaris 2.7, Entire Distribution
File System and Disk Layout:
/ c0t0d0s0 300 MB
swap c0t0d0s1 2000 MB
/usr c0t0d0s3 2000 MB
/opt c0t0d0s4 1000 MB
/var c0t0d0s5 1000 MB
One more question is asked about rebooting
[X] Auto Reboot
[ ] Manual Reboot
Afterwards it starts configuring disk making partitions and installing software indicating the progress in a table.
MBytes Installed: 700.66
MBytes Remaining: 0.00
Installing:
| | | | | |
0 20 40 60 80 100
After the installation is complete it customizes system files , devices ,logs , installs patches which are there in OS CD for that release. You should install recommended latest patches later
System then reboots or ask you to reboot depending upon the choice selected earlier .
6) After Installation
After rebooting it asks for new root passed and comes to console prompt where you can login as root.
Install patches, add additional softwares , create users, etc. etc.
This is an installation guide - I believe the OP was asking for the boot procedure for Solaris - which any good Solaris book, or the information at docs.sun.com, will detail.
Cheers
ZB
Here you go, It might save you some time searching...
BOOT PROCESS BREAKDOWN
1) The boot command reads and loads the bootblock into memory.
2) The bootblock locates and loads the secondary boot program, ufsboot, into memory and passes control to it.
NOTE: A network boot uses a different secondary boot program: inetboot instead of ufsboot.
3) ufsboot locates and loads the core kernel images and the required kernel runtime linker (krtld) into memory and
passes control to the loaded kernel.
4) The core kernel locates and loads mandatory kernel modules from the root disk directory tree and executes
the main startup code.
5) The kernel startup code executes, creating and initializing kernel structures, resources, and software components.
6) The system executes shell scripts from system directories, bringing the system up to the init state specified in
the /etc/inittab file.
Common Errors Normal Output Phase
-one of keyboard LED blinks Resetting... ok boot
-doesn't occur LEDs remain on -console goes black || (POST phase)
-keyboard LEDs blink ||
-monitor stays blank -OBP banner appears \/
never see banner Initializing Memory Execute primary
-see spinning baton boot prgm - OBP
Unable to find boot device Rebooting with command (Ref. "boot-device"
Timeout waiting arp rarp Boot device : File & Args or "diag-device")
||
||
\/
File does not appear to be FCode UFS Reader Load the bootblk prgm
executable (Enterprise Servers only) (sectors 1 - 15 on boot disk)
Not a valid ELF file ||
(Executable and Linking Format) ||
Can not find secondary boot \/
program loading:/platform/../ufsboot Load and start the secondary
File does not appear to be (Enterprise Servers only) boot prgm (platform/`uname -m`/
Fast Data Access MMU miss ufsboot) *tells prom load kernel modules
||
||
\/ ("boot -a")
Unable to load kernel module.. SunOS Release 5.7... Load and start the static kernel modules (kstat)
Data Access Exception Copyright..... /platform/`uname -m`/kernel/unix (genunix)
||
||
\/
moddir, rootdev, forceload... Kernel reads the /etc/system file
For each entry in /etc/system a sysparam
entry is created in /usr/include/sys/sysconf.h
||
\/
Kernel initializes
(can start processes on its own)
||
\/
Kernel starts the sched process (PID 0)
and then the init process (PID 1)
||
\/
init process reads files /etc/default/init
and /etc/inittab
(single user) ||
\/
Errors (depending on which script Configuring network sysinit entries executed
causes error): interfaces: -builds run level S using
-network plumbing & config /sbin/rcS
-mount /usr (if separate) Hostname: ||
-mount /proc and /dev/fd ||
-configure /devices (reconfig) ||
-configure /dev (reconfig) ||
-mount /var (if separate) ||
\/
-mount all other file systems (run level 2) Uses initdefault entry to determine
-additional network config The system is coming up. run-level to boot to (default=3)
such as defaultrouter checks Please wait. ||
and dynamic routing tests ||
-start NIS or NIS+(if applicable) \/
-name service network config /dev/rdsk/c0t0d0s3:is clean Builds:
-NFS client configuration /dev/vx/rdsk/dskgrp/vol:clean -run level 2 via /sbin/rc2
-/etc/rc2.d/S*
-automount config(if applicable) -run level 3 via /sbin/rc3
-syslog configuration syslog service starting. -/etc/rc3.d/S*
-save panic dump(if applicable) volume management starting. ||
-CDE login screen enabled ||
-NFS server config(if applicable) (run level 3) \/
LOGIN
The system is ready.