Grass Valley PRS 250 RAID Storage System User Manual
Page 59
Updating Licensed Internal Code
RAID Instructions
3-13
When an operation listed in the status screen starts,
PROCESSING
appears on the
screen beside the operation. As the operation proceeds, the bar graph in the other
screen indicates the percentage of the operation that is completed. When the
operation is completed, its status changes from
PROCESSING
to
SUCCESSFUL
.
If the operation cannot be completed, its status changes from
PROCESSING
to
FAILED
. In such a case, you should restart the installation procedure. If the file
you are loading does not contain SP PROM code, the status for the SP PROM
operations is
NOT AVAILABLE
.
It takes about 25 minutes to down load microcode.
Meaning of error message from an SP PROM update
Bad PROM database
No valid PROM image exists on any database disk module. No change was made to
the existing PROMs. Make sure you loaded the new code as explained in this
section.
Buffer reservation failed
A microcode error occurred. No change was made to the existing PROM. Retry. If the
error recurs, consult your service provider.
PROM Database Load
Failed
A microcode error occurred. No change was made to the existing PROM. Retry. If the
error recurs, consult your service provider.
PROM Erase Failure:
PROM
n
PROM
n failed the erase procedure. The SP will not function properly until all the
PROMs have been replaced. Consult your service provider.
PROM Program Failure:
PROM
n
PROM
n failed the program procedure. The SP will not function properly until all the
PROMs have been replaced. Consult your service provider.
Update Licensed Internal Code
Microcode Filename (.\00079400.BIN): FLARE638.BIN
0
20
40
60
80
100
92%
Checksum Validity
- SUCCESSFUL
Initializing SP
- SUCCESSFUL
Downloading Microcode
- SUCCESSFUL
Installing Microcode
- SUCCESSFUL
Restarting SP with new microcode
- SUCCESSFUL
Downloading PROM image
- SUCCESSFUL
Installing PROM image
- SUCCESSFUL
Restarting SP with new PROM image - PROCESSING
. . . . . . . .
. . . . .
. . . . . .
. . . . . .
. . . . .
. . . . . .