Table 28. Event descriptions and recommended actions (continued)
Number Severity Description/Recommended actions
● Replace the disk with one of the same type (SSD, enterprise SAS, or midline SAS) and the
same or greater capacity.
● Configure the disk as a spare.
266 Info. A volume-copy operation for the indicated master volume has been aborted by a user.
Recommended actions:
● No action is required.
267 Error A volume-copy operation completed with a failure.
This event has two variants:
1. If the source volume is a master volume, you can remount it. If the source volume is a
snapshot, do not remount it until the copy is complete (as indicated by event 268).
2. Possible causes are the pool running out of available space and crossing the high threshold,
volumes being unavailable, or general I/O errors.
Recommended actions:
● For variant 1: No action is required.
● For variant 2: Look for other events logged at approximately the same time that indicate a
pool space or volume failure. Follow the recommended actions for those events.
268 Info. A volume-copy operation for the indicated volume has completed.
Recommended actions:
● No action is required.
269 Error A partner firmware update operation could not be performed.
This event has these variants:
1. System health is insufficient to support firmware partner update.
2. System has unwritable cache data present.
3. Unable to determine if unwritable cache data is present.
4. Incompatible firmware versions in the controller modules.
5. Incompatible firmware is present in the system.
Recommended actions:
● For variant 1, 2, or 3: You must resolve this condition before the firmware update
will proceed. Log into the system and run the show system command to identify
unhealthy components and find recommendations for restoring system health. The check
firmware-upgrade-health command can be used to verify that the system is ready
for firmware upgrade. For unwritten cache data, use the CLI show unwritable-cache
command.
● For variant 4: This feature can be manually re-enabled after both controller modules are
running compatible firmware.
● For variant 5: The controller modules should be updated to the latest version of firmware.
Info. A partner firmware update operation has started. This operation is used to copy firmware from
one controller to the other to bring both controllers up to the same version of firmware.
Recommended actions:
● No action is required.
270 Warning Either there was a problem reading or writing the persistent IP data from the FRU ID SEEPROM,
or invalid data were read from the FRU ID SEEPROM.
Recommended actions:
● Check the IP settings (including iSCSI host-port IP settings for an iSCSI system), and update
them if they are incorrect.
271 Info. The storage system could not get a valid serial number from the FRU ID SEEPROM on the
controller, either because it could not read the FRU ID data, or because the data in it is not valid
Events and event messages 97
To Next Page
Loading...
