Dell EMC ME4084 Owner's Manual page 107

Number Severity Description/Recommended actions
Recommended actions:
•
•
•
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:
•
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:
•
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.
If the last global spare has been deleted or used for reconstruction, ALL disk groups that do not have at least
one dedicated or global spare are at increased risk. Note that even though there may be global spares still
available, they cannot be used for reconstruction of a disk group if that disk group uses larger-capacity disks
or a different type of disk. Therefore, this event may be logged even when there are unused global spares. If
the dynamic spares feature is enabled, this event will be logged even if there is an available disk that may be
used for reconstruction.
Recommended actions:
•
485 Warning The indicated disk group was quarantined to prevent writing invalid data that may exist in the controller that
logged this event.
This event is logged to report that the indicated disk group has been put in the quarantined offline state
(status of QTOF) to prevent loss of data. The controller that logged this event has detected (using
information saved in the disk group metadata) that it may contain outdated data that should not be written to
the disk group. Data may be lost if you do not follow the recommended actions carefully. This situation is
typically caused by removal of a controller module without shutting it down first, then inserting a different
controller module in its place. To avoid having this problem occur in the future, always shut down the Storage
Controller in a controller module before removing it. This situation may also be caused by failure of the
CompactFlash card, as indicated by event 204.
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.
Replace the controller module that logged this event.
Visually trace the cabling between enclosures and correct the cabling.
Configure disks as dedicated spares or global spares.
• For a dedicated spare, the disk must be of the same type as the other disks in the linear disk group
and at least as large as the smallest-capacity disk in the linear disk group, and it should have the same
or better performance.
• For a global spare, it is best to choose a disk that is as big as or bigger than the largest disk of its type
in the system and of equal or greater performance. If the system contains a mix of disk types (SSD,
enterprise SAS, or midline SAS), there should be at least one global spare of each type (unless
dedicated spares are used to protect every disk group of a given type, which will only apply to a linear
storage configuration).
If event 204 is logged, follow the recommended actions for event 204.
If event 204 is NOT logged, perform the following recommended actions:
• If event 486 is not logged at approximately the same time as event 485, reinsert the removed
controller module, shut it down, then remove it again.
Events and event messages 107