IBM QS21 User Guide - Page 79

Recovering, system, firmware, Checking, image, Booting, System, startup, messages

Get IBM QS21 - BladeCenter - 0792 PDF manuals and user guides
UPC - 883436016940
View all IBM QS21 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 79 highlights

Recovering the system firmware code The system firmware is contained in two separate images in the flash memory of the blade server: temporary and permanent. These images are referred to as TEMP and PERM, respectively. The system normally starts from the TEMP image, and the PERM image serves as a backup. If the TEMP image becomes damaged, such as from a power failure during a firmware update, the system automatically starts from the PERM image. If the TEMP image is damaged, you can recover the TEMP image from the PERM image. See "Recovering the TEMP image from the PERM image" for further information. Checking the boot image To check whether the system has started from the PERM image, enter: cat /proc/device-tree/openprom/ibm,fw-bank A P is returned if the system has started from the PERM image. Booting from the TEMP image To initiate a boot from the TEMP image after the system has booted from the PERM side, complete the following steps: 1. Turn off the blade server. 2. Restart the blade system management processor from the Advanced Management Module. 3. Turn on the blade server. Note: If the temp side is corrupted the boot times out, and an automatic reboot occurs after switching to the PERM side. If the blade server does not restart, you must replace the system board assembly. Contact a service support representative for assistance. Recovering the TEMP image from the PERM image To recover the TEMP image from the PERM image, you must copy the PERM image into the TEMP image. To perform the copy, complete the following steps: 1. Copy the perm image to the temp image. Using the Linux operating system, type the following command: update_flash -r 2. Shut down the blade server using the operating system. 3. Restart the blade system management processor from the management module. 4. Turn on the blade server. You might need to update the firmware code to the latest version. See "Updating the system and BMC firmware" on page 41 for more information on updating the firmware code. System firmware startup messages The system firmware displays the progress of the startup process on the serial console from the time that ac power is connected to the system until the operating system login prompt is displayed following a successful operating system startup. Chapter 7. Solving problems 63

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
Recovering
the
system
firmware
code
The
system
firmware
is
contained
in
two
separate
images
in
the
flash
memory
of
the
blade
server:
temporary
and
permanent.
These
images
are
referred
to
as
TEMP
and
PERM,
respectively.
The
system
normally
starts
from
the
TEMP
image,
and
the
PERM
image
serves
as
a
backup.
If
the
TEMP
image
becomes
damaged,
such
as
from
a
power
failure
during
a
firmware
update,
the
system
automatically
starts
from
the
PERM
image.
If
the
TEMP
image
is
damaged,
you
can
recover
the
TEMP
image
from
the
PERM
image.
See
“Recovering
the
TEMP
image
from
the
PERM
image”
for
further
information.
Checking
the
boot
image
To
check
whether
the
system
has
started
from
the
PERM
image,
enter:
cat
/proc/device-tree/openprom/ibm,fw-bank
A
P
is
returned
if
the
system
has
started
from
the
PERM
image.
Booting
from
the
TEMP
image
To
initiate
a
boot
from
the
TEMP
image
after
the
system
has
booted
from
the
PERM
side,
complete
the
following
steps:
1.
Turn
off
the
blade
server.
2.
Restart
the
blade
system
management
processor
from
the
Advanced
Management
Module.
3.
Turn
on
the
blade
server.
Note:
If
the
temp
side
is
corrupted
the
boot
times
out,
and
an
automatic
reboot
occurs
after
switching
to
the
PERM
side.
If
the
blade
server
does
not
restart,
you
must
replace
the
system
board
assembly.
Contact
a
service
support
representative
for
assistance.
Recovering
the
TEMP
image
from
the
PERM
image
To
recover
the
TEMP
image
from
the
PERM
image,
you
must
copy
the
PERM
image
into
the
TEMP
image.
To
perform
the
copy,
complete
the
following
steps:
1.
Copy
the
perm
image
to
the
temp
image.
Using
the
Linux
operating
system,
type
the
following
command:
update_flash
-r
2.
Shut
down
the
blade
server
using
the
operating
system.
3.
Restart
the
blade
system
management
processor
from
the
management
module.
4.
Turn
on
the
blade
server.
You
might
need
to
update
the
firmware
code
to
the
latest
version.
See
“Updating
the
system
and
BMC
firmware”
on
page
41
for
more
information
on
updating
the
firmware
code.
System
firmware
startup
messages
The
system
firmware
displays
the
progress
of
the
startup
process
on
the
serial
console
from
the
time
that
ac
power
is
connected
to
the
system
until
the
operating
system
login
prompt
is
displayed
following
a
successful
operating
system
startup.
Chapter
7.
Solving
problems
63