Disk events
The following table lists the events that are created for the Disk component.
Event | Event Type |
Severity | Call Home | Details |
---|---|---|---|---|
disc_recovering | STATE_CHANGE | WARNING | no | Message: Disk {0} is reported as recovering. |
Description: A disk is in a recovering state. | ||||
Cause: A disk is in recovering state. | ||||
User Action: If the recovering state is unexpected, then refer to the Disk issues section in the IBM Storage Scale: Problem Determination Guide. | ||||
disc_unrecovered | STATE_CHANGE | WARNING | no | Message: Disk {0} is reported as unrecovered. |
Description: A disk is in unrecovered state. | ||||
Cause: A disk is in unrecovered state. The metadata scan might have failed. | ||||
User Action: If the unrecovered state is unexpected, then refer to the Disk issues section in the IBM Storage Scale: Problem Determination Guide. | ||||
disk_down | STATE_CHANGE | WARNING | no | Message: Disk {0} is reported as not up. |
Description: A disk is reported as down. | ||||
Cause: This can indicate a hardware issue. | ||||
User Action: If the down state is unexpected, then refer to the Disk issues section in the IBM Storage Scale: Problem Determination Guide. The failed disk might be a descriptor disk. | ||||
disk_down_change | STATE_CHANGE | INFO | no | Message: Disk {0} is reported as down because the configuration changed. FS={1}, reason code={2}. |
Description: A disk is reported as down because the configuration changed by using the mmchdisk command. | ||||
Cause: N/A | ||||
User Action: N/A | ||||
disk_down_del | STATE_CHANGE | INFO | no | Message: Disk {0} is reported as down because it was deleted. FS={1}, reason code={2}. |
Description: A disk is reported as down because it was deleted by using the mmdeldisk command. | ||||
Cause: N/A | ||||
User Action: N/A | ||||
disk_down_io | STATE_CHANGE | ERROR | no | Message: Disk {0} is reported as down because of an I/O issue. FS={1}, reason code={2}. |
Description: A disk is reported as down because of an I/O issue. | ||||
Cause: An IBM Storage Scale callback event reported that a disk is in the down state because of an I/O issue. | ||||
User Action: If the down state is unexpected, then see the Disk issues section in the IBM Storage Scale: Problem Determination Guide. | ||||
disk_down_rpl | STATE_CHANGE | INFO | no | Message: Disk {0} is reported as down because it was replaced. FS={1}, reason code={2}. |
Description: A disk is reported as down because it was replaced by using the
mmrpldisk command.![]() ![]() |
||||
Cause: N/A | ||||
User Action: N/A | ||||
disk_down_unexpected | STATE_CHANGE | ERROR | no | Message: Disk {0} is reported as unexpected down. FS={1}, reasoncode={2}. |
Description: A disk is reported as unexpected down. | ||||
Cause: An IBM Storage Scale callback event reported a disk in down state of unexpected reason. | ||||
User Action: If the down state is unexpected, then refer to the Disk issues section in the IBM Storage Scale: Problem Determination Guide. | ||||
disk_down_unknown | STATE_CHANGE | WARNING | no | Message: Disk {0} is reported as down for unknown reason. FS={1}, reasoncode={2}. |
Description: A disk is reported as down for unknown reason. The disk was probably stopped. | ||||
Cause: An IBM Storage Scale callback event reported a disk in down state of unknown reason. Probably the disk was stopped or suspended. | ||||
User Action: If the down state is unexpected, then refer to the 'Disk issues section in the IBM Storage Scale: Problem Determination Guide. | ||||
disk_failed_cb | INFO_EXTERNAL | INFO | no | Message: Disk {0} is reported as failed. FS={1}. Affected NSD servers are notified about the disk_down state. |
Description: A disk is reported as failed. | ||||
Cause: An IBM Storage Scale callback event reported a disk failure. | ||||
User Action: If the failure state is unexpected, then see the Disk issues section in the IBM Storage Scale: Problem Determination Guide. | ||||
disk_found | INFO_ADD_ENTITY | INFO | no | Message: The disk {0} was found. |
Description: A disk was detected. | ||||
Cause: A disk was detected. | ||||
User Action: N/A | ||||
disk_fs_desc_missing | STATE_CHANGE | INFO | no | Message: Device {0} has no desc disks assigned in failure group(s) {1}. |
Description: Failure groups have no assigned descriptor disks as reported by the
mmlsdisk command. This is usually a normal condition.![]() ![]() |
||||
Cause: N/A | ||||
User Action: N/A | ||||
disk_fs_desc_ok | STATE_CHANGE | INFO | no | Message: Device {0} descriptor disks identified for all failure groups. |
Description: GPFS device has descriptor disks identified for all failure groups as reported by the mmlsdisk command. | ||||
Cause: N/A | ||||
User Action: N/A | ||||
disk_io_err_cb | STATE_CHANGE | ERROR | no | Message: Disk {0} is reported as I/O error. node={1}. |
Description: A disk state is reported as I/O error. | ||||
Cause: An IBM Storage Scale callback event reported a disk I/O error. | ||||
User Action: For more information, see the Disk issues section in the IBM Storage Scale: Problem Determination Guide. | ||||
disk_up | STATE_CHANGE | INFO | no | Message: Disk {0} is up. |
Description: Disk is up. | ||||
Cause: N/A | ||||
User Action: N/A | ||||
disk_vanished | INFO_DELETE_ENTITY | INFO | no | Message: The disk {0} has vanished. |
Description: A declared disk was not detected. | ||||
Cause: A disk is not in use for an IBM Storage Scale file system, which can be a valid situation. | ||||
User Action: N/A | ||||
![]() ![]() |
![]() ![]() |
![]() ![]() |
![]() ![]() |
![]() ![]() |
Description: An NSD path to the device is missing. | ||||
Cause: The mmlsnsd -X command does not find a device for the NSD on this node. | ||||
User Action: Check output of the mmlsnsd -Xcommand. If the down state is unexpected, then refer to the Disk issues section in the IBM Storage Scale: Problem Determination Guide. | ||||
![]() ![]() |
![]() ![]() |
![]() ![]() |
![]() ![]() |
![]() ![]() |
Description: An NSD path to the device is visible. | ||||
Cause: N/A | ||||
User Action: N/A |