Fatal Error During Loading Disk Drive Firmware (ReturnCode 249: One or more drives in a drive list had an exception)

Asset ID:	1-72-1609354.1
Update Date:	2017-10-05
Keywords:

Solution Type Problem Resolution Sure

Solution 1609354.1 : Fatal Error During Loading Disk Drive Firmware (ReturnCode 249: One or more drives in a drive list had an exception)

Applies to:

Sun Storage 2510 Array - Version Not Applicable to Not Applicable [Release N/A]
Sun Storage 2530-M2 Array - Version Not Applicable to Not Applicable [Release N/A]
Sun Storage 6180 Array - Version All Versions to All Versions [Release All Releases]
Sun Storage 6130 Array - Version All Versions to All Versions [Release All Releases]
Sun Storage 2540-M2 Array - Version Not Applicable to Not Applicable [Release N/A]
Information in this document applies to any platform.

Symptoms

A disk drive firmware upgrade fails with "ReturnCode 249: One or more drives in a drive list had an exception."

Below is an example using the Sun Storage Common Array Manager CLI:

# /opt/SUNWstkcam/bin/sscs modify -a MyArrayName -c Tray.85.Drive.01 -o firmware
WARNING: This command will load new firmware if needed and may impact array management and data availability.
Do you wish to continue? [y,n] : y
Analyzing Firmware
Servicing request to update Disk Drives ST373455FSUN72G
... Loading ST373455FSUN72G firmware
Error from updating Disk Drives - Fatal error during loading disk drive firmware (ReturnCode 249: One or more drives in a drive list had an exception)
Firmware install failed.

Cause

At least one of the disk devices in the list could not be upgraded. This could be because:

One (or more) of the disks to be upgraded is defective.
One (or more) of the disks to be upgraded is in a configuration status which does not allow it to be upgraded.
For example, a failed disk which has been replaced but not yet built back into its volume group is detected by the upgrade process as 2 devices: the "placeholder" for the removed disk in the volume group and the new unassigned disk. Since the upgrade process is unable to communicate with at least one of these devices (the removed disk), it aborts the upgrade altogether.

A firmware upgrade should only be carried out when the array and its data structures are in an optimal state.
In the first scenario above, the array is not optimal because a disk is defective.
In the second scenario, the array data structures are not optimal because a volume group is degraded or is running with a hot spare.

Solution

Take the necessary steps to bring the array to an optimal status, then carry out the firmware upgrade.

If you are attempting to upgrade several drives and are unable to determine which drive is causing the upgrade to fail, try upgrading them one by one using the CAM command line interface:

# sscs modify -a <ArrayName> -c <Tray.xx.Drive.yy> -o firmware

Path to "sscs":

Solaris: /opt/SUNWstkcam/bin/sscs
Linux: /opt/sun/cam/bin/sscs
Windows: c:\Program Files\Sun\Common Array Manager\bin\sscs.bat

Note: As documented in the Sun Storage Common Array Manager Array Administration Guide, all I/O to the array must be stopped as a prerequisite to upgrading disk drive firmware. This applies even if the drive(s) to be upgraded do(es) not contain any data. Refer to the manuals for your version of CAM on the Disk Device Software Documentation page of the Oracle Technology Network.

Do you still have questions? You can use My Oracle Support Communities. Communities put you in touch with industry professionals like yourself. They are monitored by Oracle support engineers, so you can expect reliable and correct answers. Ask questions and see what others are asking about in the Disk Storage 2000, 3000, 6000 RAID Arrays & JBODs Community.

Attachments

This solution has no attachment