FINAL
TRIM
SIZE
:
7.5
in
x
9.0
in
7
If
after
a
few
min
utes,
nothing
app ears
to
happ en,
y
our
system
probably
can't
nd
a
k
ernel
to
b o ot.
If
y
ou're
certain
that
a
v
alid
k
ernel
resides
on
one
of
y
our
devices,
re-c
hec
k
the
status
of
the
device
(see
the
following
list
\P
ossible
Problem
Areas").
If
y
ou
are
attempting
to
b o ot
from
a
lo
cal
device
suc
h
as
a
disk
driv
e,
and
if
the
device
is
turned
on
and
congured
prop erly
,
y
our
k
ernel
le
may
b e
missing
or
corrupted.
If
y
ou
ha
v
e
another
system
to
whic
h
y
ou
can
attach
the
disk
driv
e,
y
ou
can
moun
t
the
le
system
to
that
system
and
c
hec
k
for
the
presence
of
a
v
alid
k
ernel.
If
y
ou
cannot
nd
one
or
if
y
ou
do
not
ha
v
e
another
system
to
moun
t
y
our
disk
on,
y
ou
can
re-install
HP-UX
follo wing
the
original
installation
pro cedures.
Boot
Device
Problems
The
follo
wing
are
p ossible
b o ot
device
problems
whic
h
could
cause
b o ot
failure:
The
device
is
not
p o
w
ered
on
and
in
a
ready
state.
The
device
is
not
congured
for
the
correct
address
(suc
h
as
an
HP-IB
address).
The
cable
connecting
the
device
to
the
con
troller
is
incorrect
or
not
tightly
connected
to
the
correct
lo
cation.
If
y
ou
are
attempting
to
b o ot
an
HP-UX
clien
t
o
v
er
a
LAN,
c
hec
k
the
following:
The
cluster
serv
er
is
running.
The
rbootd
daemon
is
running
on
the
serv
er.
The
cluster
serv
er
has
y
our
con
troller
congured
in
its
/etc/clusterconf
le.
The
LANIC
i.d.
eld
in
/etc/clusterconf
matches
the
LAN
i.d.
found
b
y
the
Bo ot
R
OM.
The
le
/hp-ux
is
a
Con
text
Dep enden
t
File
(CDF).
Also,
b e
sure
there
is
an
elemen
t
in
the
CDF
that
corresp onds
to
the
clien
t
y
ou're
trying
to
b o ot.
7-12
Dealing
with
Problems