8100 Updating Product Software Guide (XCS 6.250) (5697-1716, February 2012)

4 Troubleshooting

This chapter provides information to help you solve problems you may encounter with different

parts of your storage system after completing your upgrade.

To determine if there are problems with HP P6000 Command View, answer the following questions:

• Has an HBA failed?

• Has a controller failed?

• Have you set or reset the storage system password?

The following website provides access to information for troubleshooting problems with HP P6000

Continuous Access:

http://h20000.www2.hp.com/bizsupport/TechSupport/SupportTaskIndex.jsp?lang=en&cc=us&

taskId=110&prodClassId=-1&prodTypeId=18964&prodSeriesId=5061985

Downloading the controller software file

If you cannot download the controller software file from Software Depot, right-click the link and

save it to your desktop. Then, double click the saved file, which opens a window with the link to

the file. Click the link and save it to a directory. Create your own CD from the downloaded file.

NOTE: The XCS firmware image file name has an extension of .sss. The file name contains the

controller model (200 for EVA4x00, and EVA6x00 or 210 for EVA8x00) and the XCS version.

For example, 210_6250.SSS is the name of the XCS 6.250 file for the HSV210 controller. See

Table 6 (page 46) for details.

Bad image header (Status code 65)

HP P6000 Command View transfers the XCS controller software to the controller in segments. As

each segment is received, it is validated by the controller. HP P6000 Command View monitors

each segment transfer and displays the transfer status information.

If a problem occurs, the process stops and HP P6000 Command View displays the unsuccessful

segment transfer. This can be caused by a problem in the XCS controller software image file or

by selecting the wrong image file (see Figure 25 (page 58)). If this occurs, do the following:

1. Click OK to return to the Initialized Storage System Properties window.

2. Click Code load to restart the controller software upgrade.

3. Select the correct image file and continue the process.

If the process fails again with the same message, download the firmware image file again and

repeat the process.

Verify that the correct name was selected. For a list of current image files, see Table 6 (page 46).

Figure 25 Bad image header (Status code 65)

58 Troubleshooting