chapter 7 ppt.ppt

7/25/2019 Chapter 7 ppt.ppt

1/47

Chapter 7

Installation and Boot Process Overview

7.1 Preparing for the Installation

7.2 The Installation Process

7.3 Boot Process7.4 Troubleshooting NOS Installation


2/47

Preparing for the Installation


3/47

Installing a NOS

Netor! operating s"ste# $NOS%installation is the process of creatingan& cop"ing NOS s"ste# files to a har&&is!.

B" purchasing a P' or ser(er ith apreinstalle& OS) a custo#er a(oi&s theco#ple* process of installation an&

configuration. The &rabac! is that a custo#er #a"

not be able to control the e*actfeatures) pac!ages) an& configurationof the OS or NOS.

NOS ainistrators usuall" prefer to

ha(e &irect control of softare (ersions)up&ates) an& patches installe& on thes"ste#.


4/47

Planning the System

The NOS installation shoul& be carefull" prepare&. There is no one NOS that or!s ith all co#puter

har&are) so &eter#ine hether the currentl" a(ailablehar&are ill or! ith the NOS.

+eter#ine if the NOS supports all application softare that

ill be loa&e& on the s"ste#. Beco#e fa#iliar ith the NOS itself. ,s part of the

installation process) i#portant configuration &ecisions illha(e to be #a&e.


5/47

Planning Hardware Installation

-erif" that e(er"thing specifie&in the installation plan is rea&"an& a(ailable before beginningthe installation.

,cti(ities inclu&e

/ -erif"ing the Installation Site/ -erif"ing the Poer Source

/ -erif"ing the 0PS Sie

/ ,&euate Te#perature in aSer(er oo#

/ -erif"ing the Netor!'onnection


6/47

Server Hardware Components

'hec! the co#ponents that ill beuse& to asse#ble the netor!ser(er.

So#e (en&ors &o not asse#ble allthe har&are for a netor! ser(erhen the" are or&ere&.

-erif" that the ser(er chassis is thecorrect #o&el that as or&ere&an& the correct for# factor.

ost ser(er chassis are either of atoer configuration) a i&e5 or

6fat5 toer configuration) or a rac!5#ount configuration.


7/47


, rac!5#ount ser(erchassis #ust be #ounte&

in an euip#ent rac!

&esigne& for rac!5

#ounte& har&are. The rac!s generall" co#e

in se(eral sies $heights%.

The rac! sie is #easure&

in rac! units $0% an& astan&ar& rac! unit is 1.78

inches.


8/47


-erif" that the folloing pro&ucts are or&ere&/ , #onitor that supports -9, resolution of at least 1:24 b"

7;< &ots per inch $&pi%

/ 0PS is a(ailable for the netor! ser(er

/ ,n a&euate bac!up s"ste#

/ The correct cables ha(e been &eli(ere& to connect the S'SIchannel controller to the &is! &ri(es

/ The correct nu#ber an& t"pe of processors are a(ailableith #e#or" for the# to a&euatel" perfor# their function

/ The correct S'SI a&apter an& ,I+ controller

/ The correct =ibre 'hannel host bus a&apter $>B,%

/ The netor! interface car& $NI'%

/ Other har&are that #ight be reuire& for the netor! ser(er


9/47

Hardware Requirements

The #ost current (ersions of popular NOSs) such as ?in&os @P an&e& >at 7) can onl" run on certain har&are configurations.

?hen choosing an NOS (ersion to install) (erif" that the !e" ele#entsof the s"ste# har&are #eet the #ini#u# reuire#ents of the NOS./ 'P0 t"pe $architecture%

/ 'P0 spee&

/ ,#ount of ,/ ,#ount of a(ailable har& &is! space


10/47

Creating a Hardware Inventory

The har&are in(entor" shoul& be create& before an"installation progra#s are run or before an" atte#pt toprepare the har& &is! for installation.

The har&are in(entor" shoul& inclu&e the folloingfor each &e(ice

/ +e(ice t"pe

/ anufacturer

/ o&el nu#ber

/ +e(ice &ri(er (ersion

/ BIOS re(ision nu#ber/ A*pansion car&s an& peripheral &e(ices attache& to

the s"ste#


11/47

Creating a Hardware Inventory

So#e installations #a" reuire #ore &etailsabout the har&are) such as the slot herean e*pansion car& is locate&) or e(en the

u#per settings on a particular car&.

ost of this infor#ation can be obtaine& b"using a utilit" such as +e(ice anager.


12/47

Identifying Hardware

Using Device Manager

In ?in&os 2::: the &e(iceappears ith a "ello uestion#ar! ne*t to the &e(ice na#ein +e(ice anager.

The easiest a" to i&entif" if

the har&are &ri(er has notbeen installe& is to loo! at the&e(ice an& if it has a uestion#ar! in a "ello circle ne*t toit.

This icon #eans ?in&os2::: recognie& the &e(icebut coul& not fin& a suitable&ri(er for it.


13/47

Checking Hardware

Compatibility Lists

'hec! ith the NOS an&har&are #anufacturers to(erif" that the har&are isco#patible ith the NOS.

?hile softare an& har&are#anuals #a" containco#patibilit" infor#ation) the#ost up5to5&ate source ofthis infor#ation is the ?orl&?i&e ?eb.

The e& >at ebsite offers ahar&are co#patibilit" list.


14/47

Verifying the Network

To test network connectivitywhen using the TCP/IP protocol,all network operating systemsuse the pingcommand.

Here are successful pingcommands using a TCP/IPaddress in Windows and Linux

Here are unsuccessful ping

commands in Windows andLinux.


15/47

The Installation Process


16/47

Installation Media

T"picall") a NOS is installe& using a '+5O that containsthe s"ste# files an& an installation progra#.

In so#e cases) a NOS is installe& (ia flopp" &is!s.

If a high5spee& Internet connection is a(ailable) it #a" bepossible to install a (ersion of ?in&os) 0NI@) or Cinu* o(er a

netor!. ?ith a C,N connection) it is possible to install #ost NOSs

using the local netor!.


17/47

BIOS Settings

The Basic InputDOutput S"ste#$BIOS% t"picall" resi&es in Oon the #otherboar& an& is thefirst progra# run hen a s"ste#is poere& on.

It is responsible for testinghar&are &e(ices using aprocess calle& Poer5On SelfTest $POST%.

The BIOS also loa&s theoperating s"ste# fro# (arious

#e&ia) inclu&ing har& &is!s)flopp" &is!s) an& usuall" '+5Os.


18/47

The Installation Program

An installation program controls andsimplifies the installation process.

Depending on the NOS, the installation

program prompts the user for

configuration information. Most installation programs allow

partitioning and formatting of the

hard disk before copying system files.

Partitioning and formatting arediscussed in the next few sections.


19/47


In Windows, the installation

program is called setup.exe.

On a Red Hat Linux system, the

installation program is currentlycalled Anaconda.

These programs guide the user

through the NOS installation

process.


20/47


Installation programs also give theuser the option to install a default

set of components or choose each

component manually.

If installing a NOS for the first time,or installing a NOS on a non-production

server, consider using one of these

defaults. Using a default setting

simplifies the installation process and

ensures that a crippled or non-

functioning system will not be created.


21/47


If the server is going to be putinto production, strongly

consider a custom installation.

Manually choosing the componentsand features will guarantee that

the system is built for the

specific tasks required in a

specific environment.


22/47

Disk partitions

In order to efficiently use the storage spaceon a hard disk, the disk is divided into

sections called partitions or slices.

Each partition, or slice, is a logical division

of the hard disk. A disk can have one or more

partitions. Typically, a network server is configured with

multiple partitions before installing the NOS.


23/47

Disk partitions

A system with multiple disk partitionshas the following advantages:

Multiple operating systems can be installed on the

same disk.

Data can be physically separated from the system files

to provide security, file management, and/or fault

tolerance.

specific partition, called a !s"ap! partition, can be

created in order supplement the system #M and

enhance performance.


24/47

Partitioning a disk

On s"ste#s that use a +OS5t"pe partition table) such as?in&os an& Cinu*) the first sector of the &is! is calle& theaster Boot ecor& $B% or the aster Boot Sector.

If the B or &is! label is corrupte& or otherise lost) the s"ste#ill no longer boot properl". =or this reason) a cop" of theBD&is! label shoul& be !ept as a bac!up on a flopp" &is!.


25/47

Partitioning a disk

ost NOS installation softare inclu&es a progra# calle& =+ISE.=+ISE stan&s for fi*e& &is!. =+ISE progra#s are &esigne& to#anipulate the partition table of a har& &is!. , =+ISE progra#can be use& to create partitions) &elete partitions) an& setpartitions as Facti(e.

Cinu* pro(i&es a (ersion of =+is! as ell) although the (ersionthat Cinu* uses is f&is!) ith all loercase letters. The Cinu*(ersion of f&is! is test5base& as ell but pro(i&es a #ore fle*ible#eans of partitioning a har& &is! than &oes icrosoft (ersion.


26/47

Partitioning a disk

Cinu* pro(i&es its on tools that can be use& hen installing a Cinu*5onl" s"ste#.

These are 90I tools that are #uch #ore easier to use than f&is!. There are so#ethir& part" tools that can be use& to partition a Cinu* s"ste#. The best5!non toolfor &oing this is PoerGuest Partitionagic

FIPS is apartitioning tool is inclu&e& in the installation '+ that co#e ith #ostof the Cinu* &istributions. =irst Non&estructi(e Interacti(e Partitioning Splitting$=IPS% is a large partitioning tool that can be use& to split a =,T partition into to

partitions. =IPS is #ost co##onl" use& on ?in&os s"ste#s that nee& to #a!e aseparate partition to install Cinu* on. =IPS &oes this b" first splitting the e*isting =,Tpartition. Then "ou can &elete that partition an& installing Cinu* on that nepartition.


27/47

$"ap %iles

, sap file is an area of the har& &is! that is

use& for (irtual #e#or". -irtual #e#or" is

har& &is! space that is use& to supple#ent

,.


28/47

$"ap %iles

,lthough ?in&os uses a sap file) it &oesnot ha(e to be configure&. The sap file is

create& as a file in the NOS partition.

0NI@ s"ste#s t"picall" &e&icate an entire

partition to sap space. This partition) or

slice) is calle& the sap partition. The

#ini#u# sie of the sap partition shoul& be

eual to tice the co#puter ,) or 32 B)hiche(er a#ount is larger) but no #ore than

12< B on a e& >at Cinu* s"ste#.


29/47

%ormatting the Disk

When formatting a partition on a Windows NOS,

choose between the following file systems:

NTFS (New Technology File System) Recommendedfor network servers

FAT32

FAT

When formatting a UNIX or Linux partition, choose

between the following file systems:

UFS (UNIX File System)

EXT3


30/47

&reating an Initial dministrative ccount

The ainistrati(e account has unrestricte& access to createan& &elete users an& files.

An administrative account is very powerful and

requires a "strong" password. A password is

considered strong when it contains eight

characters or more and does not use

recognizable names or words found in adictionary. Strong passwords also use a

combination of upper and lowercase letters,

numbers, and other characters.

For example: bUCc@n33r is a stronger password

than buccaneer03!


31/47

&ompleting the Installation

After providing the installation program with

the necessary information, the program will

create the NOS system files on the hard disk.

Other basic applications and components will

also be copied to the hard disk, as determined

by the installation program. Depending on the size of the NOS, the number of

selected components, and the speed of server,

it can take from a few minutes to over an hour

to complete the copying process.


32/47

The 'oot Process


33/47

The $teps of the 'oot Process

The Windows 2000 boot process occurs in fivestages:

Step 1.The pre-boot sequence

Step 2.The boot sequence

Step 3.The kernel load

Step 4.The kernel initialization

Step 5.The logon process


34/47

'asic %iles #e(uired

The following is a list of major filesthat a Windows 2000 system needs in

order to boot properly

NTLDR

Boot.ini

Bootsect.dos (only if dual booting)

Ntdetect.com

Ntbootdd.sys

Ntoskrnl.exe

Hal.dll

SYSTEM registry key

Device drivers


35/47

'I)$ Interaction

BIOS controls all aspects of the boot process.

The instructions an& &ata in the O chip that control the boot

process an& the co#puter har&are are !non as the Basic

InputDOutput S"ste# $BIOS%.

The Poer On Self Test $POST% +uring the POST) a co#puter

ill test its #e#or" an& (erif" that it has all the necessar"

har&are) such as a !e"boar& an& a #ouse. This infor#ation is

use& b" the BIOS to control all aspects of the boot process.


36/47

Detailed $teps of the 'oot Process

Step 1.Pre-boot Sequence The first step of the boot process is the

POST. This is actually something that every

computer will do, regardless of its operating

system.

After the computer completes the POST, it willallow for other adapter cards to run their own

POSTs, such as a SCSI card that is equipped

with its own BIOS, for example.

After the POST routine is complete, the

computer will locate a boot device and load

the Master Boot Record (MBR) into memory,

which in turn locates the active partition and

loads it into memory.


37/47


Step 2.Boot Sequence Once the co#puter loa&s NTC+) the boot seuence begins to

gather infor#ation about har&are an& &ri(ers.

NTC+ uses the Nt&etect.co#) boot.ini) an& bootsect.&os files.The bootsect.&os file ill onl" be use& in the e(ent that the

co#puter is set up to &ual5boot. , #aor function pro(i&e& b" NTC+ is sitching the processorinto 325bit flat #e#or" #o&e.


38/47


Step 3. Kernel Load The !ernel loa& phase begins ith Ntos!rnl.e*e loa&ing along

ith the file. ,t this point NTC+ still pla"s a role in the boot

process.

NTC+ ill also rea& the s"ste# registr" !e" into #e#or") an&

select the har&are configuration that is store& in the registr". Itill loa& the configuration nee&e& for the co#puter to boot.


39/47


Step 4. Kernel Initialization

The initial !ernel loa& phase is no co#plete an& the !ernel ill

begin to initialie.

Four additional steps will now take place:

The har&are !e" is create&

The clone control set is create&

+e(ice &ri(ers are loa&e& an& initialie&

Ser(ices are starte&


40/47


Step 5. *ogon

The *ogon screen begins the final step in the boot+up process.

lthough this is the final step, it is not considered a completed or

successful boot until a user logs on.


41/47

*inu 'oot Process

The boot process beteen ?in&os 2::: an& Cinu* is (er"si#ilar.

One #ain &ifference is the file t"pes that are use&. The na#esof the files t"pes that are use& to boot the to s"ste#s #a" be&ifferent) but the" essentiall" perfor# the sa#e functions.

In the en&) both s"ste#s ill co#e to a logon pro#pt that illas! for a userna#e an& passor& to authenticate into thes"ste#.


42/47


43/47

nable to 'oot from Installation Media

There are several steps to take if the system will notboot from a CD-ROM:

'onsult the s"ste# Basic InputDOutput S"ste# $BIOS% setup #enu. ,hot!e" seuence is generall" reuire& to enter the BIOS #onitor.

a!e sure that the BIOS is capable of supporting an& booting fro# a'+5O) an& that the correct boot seuence is configure& in BIOS.

'onsult the &ocu#entation that ca#e ith the '+. a!e sure the '+contains s"ste# files an& is &esigne& to be bootable.

nable to 'oot


44/47

nable to 'oot

from Installation Media cont.0

'hec! that the '+ is recognie& b" theoperating s"ste# an& proper &e(ice &ri(ersare a(ailable.

'hec! to see if another s"ste# can boot fro#

the '+ or rea& the '+. Inspect the &ata si&e for scratches)

fingerprints) or &ust) if it is suspecte& that theproble# is ith the &isc itself.

+eter#ine if the proble# is ith the '+5O&ri(e.


45/47

Problems During the Installation Process

Partitioning or formatting the hard disk fails.

Check the BIOS settings and hard disk documentation

to troubleshoot this problem.

The system "hangs" during the installation process.A hang is defined, as a period of several minutes

during which there is no discernable activity on the

system.

The installation media cannot be read at some point during the installationprocess. This problem occurs "hen installing "ith a &D that is dirty or

scratched.

When something goes wrong during the installation

process, use the "back" button or key so the

configuration can be reversed. Here are some other

common problems:

i ll i bl


46/47

Post+installation Problems

After installing the Network Operating System(NOS), the system may not load the NOS properly

or will not allow a logon.

If the system fails to load the NOS, consult

the manufacturer website and documentation.

First time load failures are difficult totroubleshoot.

P i ll i P bl


47/47

Post+installation Problems

Very specific information about thesystem and the NOS will need to be

gathered. If the system reports

specific errors, write those down and

search for information about those

errors on the web or in thedocumentation. If necessary, call a

technical support line and ask for

help.

If unable to logon) the proble# is usuall" forgottenainistrator account infor#ation that asconfigure& &uring the installation process.

chapter 7 ppt.ppt

Documents