Boot
errors
and
handling
The
following
sections
describe
boot
errors
and
actions
you
can
take
to
resolve
these
errors.
Boot
list
The
following
table
describes
boot
list
errors.
Table
4.
Boot
list
errors
Message:
“It
was
not
possible
to
boot
from
any
device
specified
in
the
VPD”
Reason
The
firmware
found
a
valid
VPD
but
it
could
not
find
bootable
code
on
any
of
the
devices
listed
in
it.
Action
Specify
at
least
one
device
in
the
BladeCenter
Management
Module
that
contains
bootable
code.
You
need
to
access
the
Management
Module
through
its
web
interface
and
direct
your
browser
to
Blade
Tasks
→
Configuration
→
Boot
Sequence
.
Message:
“Boot
list
successfully
read
from
VPD
but
no
useful
information
received”
Reason
The
firmware
found
a
valid
VPD,
but
there
are
no
devices
listed
in
it.
The
VPD
has
never
been
initialized.
Action
Specify
at
least
one
device
in
the
BladeCenter
Management
Module
that
contains
bootable
code.
You
need
to
access
the
Management
Module
via
its
web
interface
and
direct
your
browser
to
Blade
Tasks
→
Configuration
→
Boot
Sequence
.
Message:
“Boot
list
could
not
be
read
from
VPD”
Reason
The
firmware
can
not
access
the
VPD.
It
is
possible
that
a
service
processor
communication
failure
occurred.
Action
Remove
the
Blade
server,
reinsert
and
restart
it.
If
the
problem
persists,
replace
the
system
board
assembly.
Disk
boot
(yaboot)
The
following
table
describes
disk
boot
(yaboot)
errors.
Table
5.
Disk
boot
(yaboot)
errors
Message:
“Unable
to
open
file,
Invalid
device”
Reason
The
boot
loader
was
invoked
with
the
wrong
parameters.
It
could
not
find
a
file
that
contained
bootable
code
at
the
location
specified.
Action
Check
that
the
parameters
that
you
pass
to
yaboot
describe
the
correct
device
name,
partition
number
and
file
system
path.
For
more
information,
refer
to
the
yaboot
documentation
distributed
with
the
yaboot
source
(HOWTO-Booting
with
yaboot
on
PowerPC).
Message:
“Couldn’t
determine
boot
device”
Reason
The
boot
loader
was
invoked
without
specifying
the
location
of
boot
code.
Action
Ensure
that
correct
parameters
are
passed
to
yaboot,
by
either
using
the
firmware
environment
variables
or
passing
them
in
the
yaboot
config
file
yaboot.conf
.
20
BladeCenter
QS20
Type
0200:
Problem
Determination
and
Service
Guide
Содержание BladeCenter QS20
Страница 1: ...BladeCenter QS20 Type 0200 Problem Determination and Service Guide SC33 8297 00...
Страница 2: ......
Страница 3: ...BladeCenter QS20 Type 0200 Problem Determination and Service Guide SC33 8297 00...
Страница 8: ...vi BladeCenter QS20 Type 0200 Problem Determination and Service Guide...
Страница 26: ...8 BladeCenter QS20 Type 0200 Problem Determination and Service Guide...
Страница 49: ...v Operating system control file setup Chapter 2 Diagnostics and troubleshooting 31...
Страница 50: ...32 BladeCenter QS20 Type 0200 Problem Determination and Service Guide...
Страница 56: ...38 BladeCenter QS20 Type 0200 Problem Determination and Service Guide...
Страница 80: ...62 BladeCenter QS20 Type 0200 Problem Determination and Service Guide...
Страница 94: ...76 BladeCenter QS20 Type 0200 Problem Determination and Service Guide...
Страница 98: ...80 BladeCenter QS20 Type 0200 Problem Determination and Service Guide...
Страница 99: ......
Страница 100: ...Part Number 42C4969 Printed in USA SC33 8297 00 1P P N 42C4969...
