1

I

A hard disk has been placed online.

Rebuild completed. Device was configured. Manual online was done.

None

2

I

A hard disk added as hot spare.

Device was configured. Manual hot spare was done. Automatic hot spare was done. `Raidbld' made it hot spare.

None

3

W

Hard disk error found.

A bad sector was found on the physical media. Mechanical failure on the device. Host SCSI device detected illegal instruction. Target device generated unknown phase sequence.

If problem occurs frequently, replace the device or contact service representative.

4

W

Hard disk PFA condition found, this disk may fail soon.

Physical device predicted some future failure. External RAID logical device may have become critical.

Follow device vendor's defined action.

5

I

An automatic rebuild has started.

A physical device failed and spare was available. A physical device failed and no spare was available. A spare was added.

None

6

I

A rebuild has started.

Client started the rebuild on user's request. User replaced the failed device and `Raidbld' started the rebuild.

None

7

I

Rebuild is over.

Rebuild completed successfully.

None

8

W

Rebuild is cancelled.

User cancelled the rebuild. Higher priority rebuild started.

Restart the rebuild if required.

9

E

Rebuild stopped with error.

Due to some unknown error on the controller, rebuild failed.

Try rebuild again.

10

E

Rebuild stopped with error. New device failed.

New physical device failed. New physical device may not be compatible with MDCA hardware/firmware.

Replace the physical device.

11

E

Rebuild stopped because logical drive failed.

At least one more physical device failed in the array. Bad data table overflow.

It may not be possible to recover from this error. Contact your service representative.

12

S

A hard disk has failed.

A physical device failed. A user action caused the physical device to fail.

Replace the physical device.

13

I

A new hard disk has been found.

A physical device has been powered on. A new physical device has been added. Controller was powered on. Controller was added. System has rebooted.

None

14

I

A hard disk has been removed.

User removed an unconfigured physical device. An unconfigured physical device failed. A controller was removed. A controller powered off.

Replace the device if needed.

15

I

A previously configured disk is now available.

User set the physical device to unconfigured.

None

16

I

Expand Capacity started.

User started the RAID Expansion operation. A suspended RAID Expansion operation was started.

None

17

I

Expand Capacity completed.

RAID Expansion finished.

None

18

E

Expand Capacity stopped with error.

Multiple physical devices failed.

It may not be possible to recover from this error. Contact your service representative.

19

W

SCSI command time out on hard device.

Physical device has been removed. Physical device failed. Command timeout value is not correct.

None

20

C

SCSI command abort on hard disk.

User may have requested to abort the command. Firmware may have aborted the command to recover from error. The device may have aborted the command.

None

21

W

SCSI command retried on hard disk.

The command may have timed out. Bus reset may have occurred. Device reset may have occurred.

None

22

W

Parity error found.

A physical device did not generate proper parity. The controller failed, did not check parity properly. Cable failed. Improper cable length. Another physical device interfered. Some outside environment affected the data on the cable (for example, radio frequency signal). Terminator is not connected. Improper termination.

It may not be possible to recover from this error. Contact your service representative.

23

W

Soft error found.

An error was detected by physical device and data was recovered.

Run consistency check. If problem occurs frequently, replace the physical device.

24

W

Misc error found.

A physical device reported some error, which does not fit in any category. Read/Write command timeout. Data over run. Physical device was busy when host attempted to send command.

If problem occurs frequently, replace the physical device.

25

I

SCSI device reset.

Firmware has done reset to recover from error. User has done a reset.

None

26

I

Active spare found.

Device was configured. Manual active spare was done. Automatic active spare was done.

None

27

I

Warm spare found.

Device was configured. Manual warm spare was done. Automatic warm spare was done.

None

28

E

Request sense data available.

A physical device reported an error. Firmware reported an operational error.

Read the request sense data to understand the root cause.

29

I

Initialization started.

Host started the initialization.

Wait until the initialization is completed. If the system is shutdown prior to this process being completed, the physical device can be made useful only by reinitializing it.

30

I

Initialization completed.

Physical device initialization completed successfully.

None

31

W

Initialization failed.

Physical device could have problems supporting the SCSI format command.

Try to initialize again. Contact your service representative.

32

S

Initialization cancelled.

User cancelled the operation.

Hard disk must be initialized again or the hard disk cannot be used.

33

S

A hard disk failed because write recovery failed.

Write recovery process failed.

Replace hard disk and rebuild it.

34

S

A hard disk failed because SCSI bus reset failed.

SCSI bus reset failed.

Replace hard disk and rebuild it.

35

S

A hard disk failed because double check condition occurred.

Double check condition occurred.

Replace hard disk and rebuild it.

36

S

A hard disk failed because device is missing.

Access to the hard disk failed.

Replace hard disk and rebuild it.

37

S

A hard disk failed because of gross error on SCSI processor.

Gross error occurred to the on-board SCSI processor.

Replace hard disk and rebuild it.

38

S

A hard disk failed because of bad tag from the device.

The device responded with an invalid tag.

Replace hard disk and rebuild it.

39

S

A hard disk failed because command to the device timed out.

SCSI command timed out on the device.

Replace hard disk and rebuild it.

40

S

A hard disk failed because of the system reset.

System reset occurred.

Replace hard disk and rebuild it.

41

S

A hard disk failed because of busy status or parity error.

The device returned busy status. The SCSI transaction with the device met with parity error.

Replace hard disk and rebuild it.

42

S

A hard disk set to failed state by host.

Command from host set the hard disk to failed state.

Replace hard disk and rebuild it.

43

S

A hard disk failed because access to the device met with a selection time out.

Device disconnected or powered off. Bad device.

Replace hard disk and rebuild it. Check power and cabling.

44

S

A hard disk failed because of a sequence error in the SCSI bus phase handling.

Bad hard disk.

Replace hard disk and rebuild it.

45

S

A hard disk failed because returned an unknown status.

Bad hard disk or incompatible device.

Replace hard disk or the device and rebuild it.

46

S

A hard disk failed because device is not ready.

Device not spinning, just turned bad. Power to the device failed.

Replace hard disk and rebuild it. Check power and rebuild device.

47

S

A hard disk failed because device was not found on startup.

Device not connected. Device not responding. Clear configuration suspend mode command was invoked.

Check setup. Check the startup option parameters on the system.

48

S

A hard disk failed because write operation of the `Configuration On Disk' failed.

Bad hard disk. Device write protected.

Replace hard disk and rebuild it. Check the startup option parameters on the system.

49

S

A hard disk failed because write operation of `Bad Data Table' failed.

Bad hard disk. Device write protected.

Replace hard disk and rebuild it. Check the startup option parameters on the system.

50

W

Physical device status changed to offline.

None

51

I

Physical device status changed to Hot Spare.

None

52

W

Physical device status changed to rebuild.

None

53

W

Physical device ID did not match.

None

54

E

Physical device failed to start.

Reset the physical disk. Replace the disk.

55

W

Physical device negotiated different offset than configuration.

None

56

W

Physical device negotiated different bus width than configuration.

None

57

S

Physical drive missing on startup.

Physical drive missing.

Replace the physical drive or power on all enclosures.

58

E

Rebuild startup failed due to lower disk capacity.

Device capacity not sufficient for doing rebuild.

Replace with a disk having sufficient capacity.

59

W

Physical drive is switching from a channel to the other channel.

Physical drive removed or channel failed.

None

60

E

Temporary-Dead physical drive is automatically made online.

Temporary-Dead state caused because of transient errors.

Analyze event log to find out why the drive was marked DEAD.

61

I

A standby rebuild was started.

A physical device failed and spare was available.

None

62

I

Hot spare replaced with a smaller capacity physical disk.

The new hot spare may have a smaller physical capacity than the physical disk it replaced. The controller coercion setting may have reduced the configurable size of the new hot spare.

None

67

E

Physical disk found on only one disk channel.

Physical disk is connected on only one channel.

Inspect disk channel cables and related hardware for proper operation.

69

E

Physical disk has acquired an inappropriate loop ID. Enclosure disk-slot operations are disabled while this condition persists.

Enclosure selector switch conflict. Physical disk hardware failure. Enclosure disk slot hardware failure.

Ensure that each disk enclosure selector switch is set to a unique number per enclosure manufacturer specification. Inspect physical disk connector. Power-cycle entire system. Replace physical disk. Replace disk enclosure.

70

E

Physical disk port has failed or cannot operate at the configured channel speed.

Physical disk hardware failure. Physical disk is not compatible with system. Enclosure disk slot hardware failure.

Replace physical disk. Replace disk enclosure.

71

E

Mirror race recovery failed for logical drive.

A read or write operation to a physical disk failed while restoring redundancy.

Run consistency check and restore consistency.

72

E

Controller parameters checksum verification failed; restored default.

NVRAM battery low. NVRAM hardware failure. Improper shutdown of the controller during controller parameter update.

Restore correct controller parameter settings. If problem persists, replace controller.

73

I

Online controller firmware upgrade has started.

User has initiated an online firmware upgrade.

None

74

I

Online controller firmware upgrade has completed successfully.

Online controller firmware upgrade has completed without error. The partner controller will now be auto flashed.

None

75

E

Online controller firmware upgrade has failed.

Online controller firmware upgrade has failed. The original firmware will be reloaded.

Use the offline method to load the new firmware.

76

I

A COD with unsupported features has been detected.

Firmware does not support certain features in that COD. COD import is to wrong system COD data is sequestered.

Obtain compatible firmware then reimport the COD or import the COD to a different system

77

I

A new battery was found.

Battery present in the controller could be a new or a replaced unit.

None

78

S

Battery backup unit charger error.

Battery backup unit failure. Hardware problems in battery backup unit.

Replace the battery, or replace the battery backup unit hardware, or if the problem persists contact your service representative.

79

S

Battery will not hold a charge.

Battery failure.

Have your supplier replace the battery.

80

S

Firmware entered unexpected state at run-time.

Memory corruption. Hardware returned unexpected value.

If the controller stops responding reboot and try again. If problem persists contact your service representative.

81

I

Rebuild stopped on controller failure.

Rebuild moved to the surviving controller because the partner, which was running the rebuild, failed.

None

82

E

Check Consistency stopped on controller failure.

Check Consistency failed because the partner, which was running the Check Consistency, failed.

Restart the consistency check.

83

E

Foreground initialization stopped on controller failure.

Foreground initialization failed because the partner, which was running the foreground initialization, failed.

Restart the foreground initialization.

84

I

Background initialization stopped on controller failure.

Background initialization restarted on the surviving controller because the partner, which was running the background initialization, failed.

None

85

I

Configuration group not installed due to physical disk conflict.

Physical disk already configured in another group. Unable to map a physical device in this group.

Move to another controller. Remove one or more existing configuration groups and reboot with this group.

86

I

Configuration group not installed due to logical drive conflict.

Logical drive already configured in another group. Unable to install all the logical drives in the group.

Move to another controller. Remove one or more existing configuration groups and reboot with this group.

87

I

Configuration group not installed due to SAN Map conflict.

SAN Map conflicted with that of another installed group.

Move to another controller. Remove one or more existing configuration groups and reboot with this group.

88

I

Foreign configuration group not installed.

Foreign COD Group found but not installed.

Move to another controller. Remove native configuration group and reboot with foreign group.

89

I

No configuration group installed.

All configuration groups are foreign and clash. Controllers may have changed.

Move to another controller. Re-insert original controllers or remove some groups and reboot with one group.

96

S

Device loop ID conflict (soft addressing) detected.

Device loop ID conflict detected on disk channel resulting in soft addressing; potential data corruption.

Change index selector to enable hard addressing per enclosure manufacturer's specification.

97

I

One or more transport Fibre channel CRC errors occurred during data transfer to/from the physical device in the last hour.

Physical devices were installed or removed causing momentary fibre channel loop disruption. Cabling or associated fibre channel hardware is faulty.

Unless the problem occurs frequently, action is not required.

98

I

The host fibre channel is down.

Host fibre channel device (cable, server, switch, hub, host adapter) has failed. Host fibre channel interface on the controller has failed.

Inspect host fibre channel cables and associated hardware.

99

I

The host fibre channel is up.

The host fibre channel loop initialized successfully.

None

100

I

Redundant access restored on physical disk.

Physical disk is now accessible on both disk channels.

Check I/O modules and back-end connections if disk frequently loses redundant accessibility.

101

I

Started to loop through each drive for predicted failure analysis.

Controller started a predicted failure analysis on disk drives.

None

102

I

Finished predicted failure analysis on each drive.

Controller finished predicted failure analysis.

None

103

I

Background patrol was started or resumed.

Background patrol started.

None

104

I

Background patrol has found no more drives or was commanded to stop.

Background patrol finished or stopped.

None

128

N

Consistency check is started.

User started a consistency check. `Raidbld' started consistency check.

None

129

I

Consistency check is finished.

Consistency check completed successfully without detecting any errors.

None

130

E

Consistency check is cancelled.

User cancelled the consistency check.

Restart consistency check, if required.

131

E

Consistency check on logical drive error.

Inconsistent data was found. Bad sectors were found. A physical device reliability problem.

See bad block and request sense table for more information.

132

E

Consistency check on logical drive failed.

A logical device became critical. A logical device failed.

See request sense data for more information.

133

S

Consistency check failed due to physical device failure.

A physical device failed.

See request sense data for more information.

134

S

Logical drive has been made offline.

One/multiple physical device(s) failed.

It may not be possible to recover from this error. Contact your service representative.

135

E

Logical device is critical.

One physical device failed.

Replace the physical device. Start the rebuild, if required.

136

I

Logical drive has been placed online.

Rebuild completed. User set the physical device online. New configuration was added.

None

137

I

An automatic rebuild has started on logical drive.

A physical device failed and a spare device was available. A spare physical device was found and replaced the failed device.

None

138

I

A manual rebuild has started on logical drive.

Client started the rebuild on user's request. User replaced the failed device and `Raidbld' started the rebuild.

None

139

I

Rebuild on logical drive is over.

Rebuild completed successfully only for this logical drive.

None

140

W

Rebuild on logical drive is cancelled.

User cancelled rebuild. Higher priority rebuild started.

Restart the rebuild if required.

141

E

Rebuild stopped with error.

Due to an unknown error on the controller rebuild failed.

Try rebuild again.

142

E

Rebuild stopped with error. New device failed.

New physical device failed. New physical device is not compatible with MDAC hardware/firmware.

Replace the new device.

143

E

Rebuild stopped because logical drive failed.

At least one more physical device failed in the array.

It may not be possible to recover from this error. Contact your service representative.

144

I

Logical drive initialization started.

User started the initialization.

Any previous data is lost.

145

I

Logical drive initialization done.

Initialize operation completed successfully.

None

146

W

Logical drive initialization cancelled.

User cancelled the initialization.

Restart initialization if required.

147

E

Logical drive initialization failed.

One/multiple physical device(s) failed. Controller has been removed. Controller has been powered off.

Refer to the device failure event.

148

I

A logical drive has been found.

A new configuration has been added. MORE completed. A new controller has been plugged in. Controller has been powered on. System has rebooted.

None

149

I

A logical drive has been deleted.

A new configuration has been added. A new logical device has been deleted. Controller has been removed. Controller has been powered off.

None

150

I

Expand Capacity started.

User started the Online RAID Expansion operation.

None

151

I

Expand Capacity completed.

Online RAID Expansion completed.

None

152

E

Expand Capacity stopped with error.

Multiple physical devices failed.

It may not be possible to recover from this error. Contact your service representative.

153

C

Bad blocks found.

Bad sector was found on a physical device during consistency check/rebuild/RAID expansion operation.

Run a Consistency Check with the Restore option. Restore data from a backup.

154

I

System drive (LUN) size changed.

A new configuration has been added. RAID Expansion has added extra capacity.

None

155

I

System drive type changed.

A new configuration has been added. RAID Expansion completed on RAID 1.

None

156

S

Bad data blocks found. Possible data loss.

Bad blocks were found on multiple physical devices in same zone.

Restore data from a backup.

157

W

System drive LUN mapping has been written to config.

None

158

S

Attempt to read data from block that is marked in Bad Data Table.

Potential data loss.

Restore data from a backup.

159

E

Data for Disk Block has been lost due to Logical Drive problem.

Data retained in RAID Cache for a Write-back Logical Drive cannot be stored to the physical medium because of Logical Drive problem. The Logical Drive problem could be because of multiple physical devices offline or other reasons.

Insure that all the Physical Drives related to the Logical Drive, disk channel, enclosure, or cabling are functional and accessible. Repair or replace them if necessary.

160

E

Temporary-Offline RAID5/RAID3 array is available to the user again with the possibility of data loss in the array.

Temporary-Offline state caused because of transient errors in physical drives.

Verify data from backup.

161

E

Temporary-Offline RAID0+1/RAID1/RAID 0/JBOD array is available to the user again.

Temporary-Offline state caused because of transient errors in physical drives.

None

162

I

A standby rebuild has started on logical drive.

A physical drive failed and a spare device was available.

None

176

I

Logical drive background initialization started.

User may have started background initialization. Firmware may have automatically started background initialization.

None

177

I

Logical drive background initialization stopped.

User may have stopped background initialization. Firmware may have automatically stopped background initialization.

None

178

I

Logical drive background initialization paused.

Background initialization paused due to a higher priority operation.

None

179

I

Logical drive background initialization restarted.

Background initialization started after being paused.

None

180

I

Logical drive background initialization failed.

Background initialization failed.

None

181

I

Logical drive background initialization completed.

Background initialization completed successfully.

None

182

E

Low battery charge level. Logical drive may have lost data.

Controller was powered off for duration longer than battery capacity. User connected a new controller. User connected a new BBU battery.

Run consistency check to verify logical drive consistency. If needed, restore data from backup.

256

S

Fan failure.

Cable connection broken. Bad fan.

Replace fan.

257

I

Fan has been restored.

Faulty fan has been replaced. Cable is connected properly.

None

258

S

Fan failure.

Cable connection broken. Bad fan.

Replace fan.

259

I

Storage cabinet fan is not present.

Enclosure Management Connection is broken. Management hardware is bad. Fan is not present.

Follow enclosure management vendor's diagnostics and repair procedures.

272

S

Power supply failure.

Cable connection is broken. Bad power supply.

Reconnect cable or replace the power supply as required.

273

I

Power supply has been restored.

Faulty power supply has been replaced.

None

274

S

Power supply failure.

Cable connection is broken. Bad power supply.

Replace power supply.

275

I

Storage cabinet power supply is not present.

Management connection is broken. Management hardware is bad. Power supply is not present.

Follow enclosure management vendor's diagnostics and repair procedures.

288

S

Over temperature. Temperature is above 70 degrees Celsius.

Room temperature is too high. Bad fan. Bad sensor.

Turn off the system and allow it to cool down. Adjust the room temperature.

289

W

Temperature is above 50 degrees Celsius.

Room temperature is high. Bad fan.

Replace fan. Turn off the system. Adjust the room temperature.

290

I

Normal temperature has been restored.

Faulty fan has been replaced. Room temperature was reduced.

None

291

S

Over temperature.

Room temperature is too high. Bad fan.

Turn off the system and allow it to cool down. Adjust the room temperature.

292

I

Storage cabinet temperature sensor is not present.

Enclosure management connection is broken. Management hardware is bad. Sensor is not present.

Follow enclosure management vendor's diagnostics and repair procedures.

304

S

Enclosure reported failure state.

Power supply failed. Fan failed. Cabinet is too hot.

Follow enclosure management vendor's diagnostics and repair procedures.

305

W

Enclosure reported critical state.

Not available.

Not available.

306

I

Storage Works enclosure reported normal state.

Problem has been rectified.

None

307

I

Uninterruptible power supply disabled.

None

308

I

Uninterruptible power supply AC failed.

None

309

W

Uninterruptible power supply battery low.

None

310

S

Uninterruptible power supply failed.

None

311

I

Uninterruptible power supply normal.

None

320

S

Fan failure.

Cable connection broken. Bad fan.

Replace fan.

321

I

Fan has been restored.

Faulty fan has been replaced. Cable is connected properly.

None

322

I

Fan is not present.

Enclosure Management Connection is broken. Management hardware is bad. Fan is not present.

Follow enclosure management vendor's diagnostics and repair procedures.

323

S

Power supply failure.

Cable connection is broken. Bad power supply.

Replace the power supply.

324

I

Power supply has been restored.

Faulty power supply has been replaced.

None

325

I

Power supply is not present.

Management connection is broken. Management hardware is bad. Power supply is not present.

Follow enclosure management vendor's diagnostics and repair procedures.

326

S

Temperature is over safe limit. Failure imminent.

Room temperature is too high. Bad fan. Bad sensor.

Turn off the system and allow it to cool down. Adjust the room temperature.

327

W

Temperature is above working limit.

Room temperature is high. Bad fan.

Replace fan. Turn off the system. Adjust the room temperature.

328

I

Normal temperature has been restored.

Faulty fan has been replaced. Room temperature was reduced.

None

329

I

Temperature sensor is not present.

Enclosure management connection is broken. Management hardware is bad. Sensor is not present.

Follow enclosure management vendor's diagnostics and repair procedures.

330

W

Enclosure access critical.

Enclosure management connection is broken. Management hardware is bad.

Follow enclosure management vendor's diagnostics and repair procedures.

331

I

Enclosure access has been restored.

Enclosure has been fixed or replaced.

None

332

S

Enclosure access is offline.

Enclosure management connection is broken. Management hardware is bad.

Follow enclosure management vendor's diagnostics and repair procedures.

333

S

Enclosure Soft Addressing Detected.

Enclosure has duplicate loop ids (Soft Addressing). Potential data corruption.

Change index selector to enable hard addressing as per enclosure manufacturer's specification.

334

I

Enclosure services ready.

None

335

I

Access to temperature sensor has been lost.

Switch card or temperature sensor has been removed.

None

336

I

Access to power supply status information has been lost.

Switch card or connectivity has been removed.

None

337

I

Access to fan status information has been lost. Switch card or connectivity has been removed.

None

384

I

Array management server software started successfully.

The server system (or array management utility server) started.

If you did not expect a system reboot, investigate.

385

E

Write back error.

Data cache write failed.

The data may have been lost. Restore the data from a backup.

386

W

Internal log structures getting full; PLEASE SHUTDOWN AND RESET THE SYSTEM IN THE NEAR FUTURE.

Too many configuration changes occurred since the last boot.

Reboot the system by power cycling whenever convenient.

388

C

Controller is dead. System is disconnecting from this controller.

Contact your service representative.

389

W

Controller has been reset.

Controller failed. Controller was removed from the system. Controller has been powered off.

None

390

I

Controller is found.

Driver has reset the controller to recover from an error. Driver has reset the controller to activate new firmware.

None

391

C

Controller is gone. System is disconnecting from this controller.

New controller has been installed. Controller has been powered on. System has rebooted.

None

392

I

BBU Present.

Controller is dead. Controller has been removed. Controller has been powered off.

None

393

W

BBU Power Low.

A BBU unit was found on the controller.

If this message occurs without power failure, replace the BBU.

394

I

BBU Power OK.

BBU does not have enough power to enable the write data cache.

None

395

C

Controller is gone. System is disconnecting from this controller.

BBU has enough power to enable the write data cache.

None

396

I

Controller powered on.

Controller was removed from the system. Controller has been powered off.

None

397

I

Controller is online.

New controller has been installed.

None

398

C

Controller is gone. System is disconnecting from this controller.

Controller was set online.

None

399

W

Controller's partner is gone, controller is in failover mode now.

Controller was set offline.

If you did not expect this, investigate.

400

I

BBU reconditioning is started.

User started a BBU reconditioning.

None

401

I

BBU reconditioning is finished.

BBU reconditioning completed successfully.

None

402

I

BBU reconditioning is cancelled.

User cancelled the BBU reconditioning.

Restart the BBU reconditioning, if required.

403

S

Installation aborted.

Installation aborted.

404

S

Controller firmware mismatch.

Replacement controller with downlevel firmware installed.

Reload controller firmware.

405

W

BBU removed.

BBU physically removed.

Reinstall BBU.

406

S

WARM BOOT failed.

Memory error detected during WARM boot scan. Possible data loss.

Restore data from a backup.

407

I

BBU calibration cycle started.

New battery detected.

None

408

I

BBU calibration cycle finished.

BBU calibration completed successfully.

None

409

I

BBU calibration cycle is cancelled.

User cancelled the BBU calibration cycle.

None

410

I

BBU battery not present.

A BBU is present, but the battery is not detected.

Install or connect the battery.

411

W

Controller entered Conservative Cache Mode.

None

412

W

Controller entered normal cache mode.

None

413

W

Controller device start complete.

None

414

W

Soft ECC error corrected.

Faulty memory module.

Replace memory module.

415

W

Hard ECC error corrected.

Faulty memory module.

Replace memory module.

416

S

BBU recondition needed.

None

417

W

Controller's partner has been removed.

None

418

E

BBU out of service.

BBU will not be able to power the cache if AC power fails. Firmware will switch WriteBack logical drives to WriteThrough.

Replace BBU.

419

W

Updated partner's status.

None

420

W

Relinquished partner.

None

421

W

Inserted partner.

None

422

W

Dual controllers enabled.

None

423

W

Killed partner.

None

424

W

Dual controllers entered nexus.

None

425

S

Controller boot ROM image needs to be reloaded.

Wrong firmware image file downloaded. MAC address changed.

Contact your service representative to reload the boot ROM image.

426

C

Controller is using default non-unique world-wide name.

MAC address lost or not set.

Contact your service representative to set the controller MAC address.

427

E

Mirror Race recovery failed.

Some physical devices could have failed.

Run consistency check and restore consistency.

428

C

Mirror Race on critical drive.

Logical device is critical.

Replace dead drive and rebuild.

512

I

System started.

The server system (or array management utility server) started.

If you did not expect a system reboot, investigate.

513

I

Size table full.

Too much physical device size information is defined.

Remove unused device information for this system.

514

I

User logged in.

An array management utility user logged in on the server system.

Not available.

515

I

User logged out.

An array management utility user logged out of the server system.

Not available.

516

I

Server alive.

Reconnected to server. Server rebooted.

None

517

S

Lost connection to server, or server is down.

Lost network connection to server. Server shutdown.

None

518

I

Automatic reboot count has changed.

Controller has rebooted. Automatic reboot has rearmed itself or was reconfigured.

None

640

W

Channel failed.

Cable disconnected.

Plug in cable.

641

W

Channel online.

Cable reconnected.

None

642

S

Back end SCSI bus dead.

Lost access to data on SCSI bus.

LRC module may need replacing.

643

I

Back end SCSI bus alive.

Regained access to data on SCSI bus.

None

644

S

Back end fibre dead.

Lost access to data on fibre channel.

LRC module may need replacing.

645

I

Back end fibre alive.

Regained access to data on fibre channel.

None

700

W

Event log empty.

Tried to read past last entry.

None

701

W

Event log entries lost.

Tried to read an entry that does not exist in the event log.

None

702

W

Request sense.

A physical drive has generated an error.

Interpret the Key/ASC/ASCQ and take appropriate action.

703

W

Set real time clock.

Real time clock was set.

None

800

W

New configuration received.

A new configuration was downloaded to controller.

None

801

W

Configuration cleared.

Controller was told to clear the configuration.

None

802

W

Configuration invalid.

The controller found an invalid configuration.

None

803

W

Configuration on disk access error.

The controller could not read the configuration off of the disk.

None

804

W

Configuration on disk converted.

The controller converted a down level configuration on disk.

None

805

W

Configuration on disk import failed.

The controller could not import the configuration.

None

806

I

A debug dump exists on this system.

The controller aborted and created debug dump information.

Contact field support for assistance in retrieving the data.

807

I

A debug dump exists on this system.

The partner controller aborted and created debug dump information.

Contact field support for assistance in retrieving the data.

896

S

Internal controller is in the hung state.

Power controller off and on.

897

S

Introller controller has encountered a firmware breakpoint.

Power controller off and on.

912

S

Internal controller has encountered i960 processor specific error.

Power controller off and on.

928

S

Internal controller has encountered Strong-ARM processor specific error.

Power controller off and on.

929

S

Internal controller back end hardware error.

Timeout waiting for interrupt. Timeout waiting for command completion.

Power controller off and on.