Number
Severity
Description/Recommended actions
•
Check that there is a module or blank plate in every module slot in the enclosure.
•
If none of the above explanations apply, replace the controller module that logged the error.
When the problem is resolved, event 478 is logged.
478
Info.
A problem reported by event 476 or 477 is resolved.
Recommended actions:
•
No action is required.
479
Error
The controller reporting this event was unable to flush data to or restore data from non-volatile memory.
This mostly likely indicates a CompactFlash failure, but it could be caused by some other problem with the
controller module. The Storage Controller that logged this event will be killed by its partner controller, which
will use its own copy of the data to perform the flush or restore operation.
Recommended actions:
•
If this is the first time this event has been logged, restart the killed Storage Controller.
•
If this event is then logged again, replace the CompactFlash.
•
If this event is then logged again, shut down the Storage Controller and replace the controller module.
480
Error
An IP address conflict was detected for the indicated iSCSI port of the storage system. The indicated IP
address is already in use.
Recommended actions:
•
Contact your data-network administrator to help resolve the IP address conflict.
481
Error
The periodic monitor of CompactFlash hardware detected an error. The controller was put in write-through
mode, which reduces I/O performance.
Recommended actions:
•
Restart the Storage Controller that logged this event.
•
If this event is logged again, shut down the Storage Controller and replace the CompactFlash.
•
If this event is logged again, shut down the Storage Controller and replace the controller module.
482
Warning
One of the PCIe buses is running with fewer lanes than it should.
This event is the result of a hardware problem that has caused the controller to use fewer lanes. The system
works with fewer lanes, but I/O performance is degraded.
Recommended actions:
•
Replace the controller module that logged this event.
483
Error
An invalid expansion-module connection was detected for the indicated disk channel. An egress port is
connected to an egress port, or an ingress port is connected to an incorrect egress port.
Recommended actions:
•
Visually trace the cabling between enclosures and correct the cabling.
484
Warning
No compatible spares are available to reconstruct this disk group if it experiences a disk failure. Only disk
groups that have dedicated or suitable global spares will start reconstruction automatically.
This situation puts data at increased risk because it will require user action to configure a disk as a dedicated or
global spare before reconstruction can begin on the indicated disk group if a disk in that disk group fails in the
future.
Events and event messages
117
