Sun Storage 2500-M2 Array Running Firmware 07.84.xx.xx Recovery Script Fails with "Internal Target Error" while "Alarm Database Recovery mode is active." Reported in Sun Storage Common Array Manager (CAM) Alarms.

Asset ID:	1-72-2379891.1
Update Date:	2018-04-30
Keywords:

Solution Type Problem Resolution Sure

Solution 2379891.1 : Sun Storage 2500-M2 Array Running Firmware 07.84.xx.xx Recovery Script Fails with "Internal Target Error" while "Alarm Database Recovery mode is active." Reported in Sun Storage Common Array Manager (CAM) Alarms.

Applies to:

Sun Storage 2540-M2 Array - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

Recovery script fails with "Internal target error"

/opt/SUNWsefms/bin/service -d 2540_1 -c recover label=2540 vol=a vdiskID=0 raidLevel=1 capacity=236223201280 segmentSize=32768 offset=0 readAhead=0 drives=t99d06,t99d04,t99d02,t99d05,t99d03,t99d01 vdiskLabel=1 volumeWWN=6000000-0000042B523F44CE volumeSSID=0

Fails in recovery script as follows:

SLEEPSEC_VAL1=60
+ export SLEEPSEC_VAL1
+ /opt/SUNWsefms/bin/service -d 2540_1 -c recover label=2540 vol=a vdiskID=0 raidLevel=1 capacity=236223201280 segmentSize=32768 offset=0 readAhead=0 drives=t99d06,t99d04,t99d02,t99d05,t99d03,t99d01 vdiskLabel=1 volumeWWN=6000000-0000042B523F44CE volumeSSID=0
Executing the recover command on 6540_1
Completion Status: Internal target error

Alarm generated in CAM "Database Recovery mode is active."

Alarm ID : alarm52
Description: Database Recovery mode is active.
Severity : Critical
Element : SUN.222222.SX22222222
GridCode : 93.66.1434
Date : 2018-01-10 20:16:43

Error reading the master record: Dbm database error ( StorageArrayProfile)

Changes

The conditions to encounter this situation are:

The Sun Storage 2500-M2 has the firmware 07.84.
You reset the array configuration using either the CAM CLI or BUI.

Cause

The controller is booting up in database recovery mode, with no configuration. The backup database images are locked in read-only mode. The storage administrator is expected to recreate the configuration, using the database backup images.

Solution

To resolve this issue you need to cancel the recovery mode on the controllers.

1. Execute the following command to clear the recovery mode:

# /opt/SUNWsefms/bin/service -d <arrayname> -c cancelDatabaseRecoveryMode

Wait 5 min. The alarm in CAM will auto clear. If the alarm does not clear please contact Oracle support.

Note: This is the procedure to follow if the above solution does not resolve the issue.

2. Either use Webex or dispatch a field engineer onsite (if webex is not an option for the customer) in order to execute the following commands through both controllers A and B:

-> loadDebug
-> cancelDatabaseRecoveryMode_MT

Note: Executing the "cancelDatabaseRecoveryMode_MT" command does not change or affect the running array configuration.

Example:

-> loadDebug
value = 1 = 0x1
->
-> cancelDatabaseRecoveryMode_MT
SYMbol process complete, retCode: RETCODE_OK
value = 0 = 0x0
->

The alarm will be cleared in CAM after the polling interval which is 5 minutes.

If recovery mode is still active please continue to step 3.

3. You will need to clear the configuration using 'sysWipeAllConfigData'.

Refer to Document : 1576782.1 - How to Reset Array Configuration via Shell on Sun Storage 6180, 6580, 6780 and 2500-M2 Arrays Running Firmware 07.84.xx.xx or Higher

Example:
-> sysWipeAllConfigData
Executing configuration reset. Boards will reboot on completion.

Once the controllers reboot and the recovery mode is cleared you can run the recovery script created from makesscs.

References

<NOTE:1576782.1> - How to Reset Array Configuration via Shell on Sun Storage 6180, 6580, 6780 and 2500-M2 Arrays Running Firmware 07.84.xx.xx or Higher

Attachments

This solution has no attachment