Physicaldisk events

The following table lists the events that are created for the Physicaldisk component.

Table 1. Events for the Physicaldisk component
Event	Event Type	Severity	Call Home	Details
gnr_nvram_disarmed	STATE_CHANGE FAILED	ERROR	no	Message: The NVDIMM of the pdisk {0} is disarmed.
				Description: NVDIMM is unable to preserve future content.
				Cause: The 'tslsnvramstatus' command reports disarmed failure condition for the NVRAM drive of the disk.
				User Action: Identify the NVDIMM cards or BPM, which has encountered the errors from FSP log or call home data. Replace the faulty NVDIMM cards, BPM or both as soon as possible.
gnr_nvram_erased	STATE_CHANGE FAILED	ERROR	no	Message: The NVDIMM of the pdisk {0} reports an erased image.
				Description: Image is erased. The NVDIMM contents is not persisted.
				Cause: The 'tslsnvramstatus' command reports the erased-failure condition for the NVRAM drive of the disk.
				User Action: Verify that any NVDIMM cards, BPM encountered any errors from FSP log or call home data. If any errors are found then replace the faulty NVDIMM cards, BPM or both as soon as possible. If no errors are found then try to add the drive back to RG.
gnr_nvram_ok	STATE_CHANGE HEALTHY	INFO	no	Message: The NVDIMM of the pdisk {0} is normal.
				Description: NVDIMM is in good condition.
				Cause: N/A
				User Action: N/A
gnr_nvram_persist_error	STATE_CHANGE FAILED	ERROR	no	Message: The NVDIMM of the pdisk {0} cannot persist.
				Description: NVDIMM failed to save or restore memory contents.
				Cause: The 'tslsnvramstatus' command reports the fail-to-persist failure condition for the NVRAM drive of the disk.
				User Action: Identify the NVDIMM cards or BPM, which encountered the errors from FSP log or call home data. Replace the faulty NVDIMM cards, BPM, or both as soon as possible.
gnr_nvram_unhealthy	STATE_CHANGE DEGRADED	WARNING	no	Message: The NVDIMM of the pdisk {0} is unhealthy.
				Description: Error is detected but save or restore might still work for the NVRAM drive of the disk.
				Cause: The 'tslsnvramstatus' command reports unhealthy failure condition for the NVRAM drive of the disk.
				User Action: Identify the NVDIMM cards or BPM, which has encountered the errors from FSP log or call home data. Replace the faulty NVDIMM cards, BPM or both as soon as possible.
gnr_pdisk_bpm_degraded	STATE_CHANGE DEGRADED	WARNING	no	Message: The backup power module (BPM) for NVDIMM {0} of the pdisk {id} is in condition: {1}.
				Description: Short remaining lifetime for a backup power module (BPM) for a NVDIMM.
				Cause: The 'tslsnvramstatus' command reports that the lifetime of a BPM is close to its end.
				User Action: Replace the BPM for this NVDIMM soon.
gnr_pdisk_bpm_failed	STATE_CHANGE FAILED	ERROR	no	Message: The backup power module (BPM) for NVDIMM {0} of the pdisk {id} is in condition: {1}.
				Description: End of life for a backup power module (BPM) for a NVDIMM.
				Cause: The 'tslsnvramstatus' command reports that end of life is reached for a BPM.
				User Action: Replace the BPM for this NVDIMM.
gnr_pdisk_bpm_ok	STATE_CHANGE HEALTHY	INFO	no	Message: The backup power module (BPM) for NVDIMM {0} of the pdisk {id} is in condition: {1}.
				Description: A backup power module (BPM) for a NVDIMM has a good remaining lifetime.
				Cause: N/A
				User Action: N/A
gnr_pdisk_degraded	STATE_CHANGE DEGRADED	WARNING	no	Message: GNR pdisk {0} is degraded.
				Description: The pdisk state is degraded.
				Cause: The mmlspdisk command reports degraded user condition for the disk.
				User Action: The IOA cache battery might have failed. For more information, issue the mmlspdisk command or see the 'Disk diagnosis' subsection under the 'Maintenance procedure' section in the 'IBM Storage Scale: Problem Determination Guide'.
gnr_pdisk_diagnosing	INFO	WARNING	no	Message: Timeouts or I/O errors initiated a diagnosis run on the GNR pdisk {0}.
				Description: The system has started, and pdisk is now in the diagnostic state.
				Cause: A disk error or timeout (read / write) has occurred, as can be seen in the output of the mmvdisk pdisk list --smart-data --recovery-group <recovery- group> -L command.
				User Action: For more information, see the 'Disk diagnosis' subsection under the 'Maintenance Procedure' section in the 'IBM Storage Scale: Problem Determination Guide'.
gnr_pdisk_disks	STATE_CHANGE HEALTHY	INFO	no	Message: Pdisks are detected on this node.
				Description: Pdisks found.
				Cause: N/A
				User Action: N/A
gnr_pdisk_draining	STATE_CHANGE DEGRADED	ERROR	no	Message: GNR pdisk {0} is draining.
				Description: The pdisk state is draining. The data is being drained from the disk and moved to distributed spare space on other disks.
				Cause: The mmlspdisk command shows draining user condition for the disk.
				User Action: Wait for the draining process to finish.
gnr_pdisk_found	ADD_ENTITY	INFO	no	Message: GNR pdisk {0} was found.
				Description: A GNR pdisk, which is listed in the IBM Storage Scale configuration, was detected.
				Cause: N/A
				User Action: N/A
gnr_pdisk_maintenance	STATE_CHANGE DEGRADED	WARNING	no	Message: GNR pdisk {0} is in maintenance.
				Description: The GNR pdisk is in maintenance because the state is suspended, serviceDrain, pathMaintenance, or deleting. This might be caused by some administration commands like the mmdeldisk command.
				Cause: The mmlspdisk command shows maintenance user condition for the disk.
				User Action: Complete the maintenance action. If the issue persists, then contact IBM support.
gnr_pdisk_missing	STATE_CHANGE DEGRADED	WARNING	no	Message: GNR pdisk {0} is missing.
				Description: Native RAID has lost connectivity to the drive and further analysis is needed to find the root cause of the failure. There might be several technical reasons, which cannot be resolved by replacing the disk.
				Cause: The mmlspdisk command reports missing user condition for the disk.
				User Action: Check whether the drive is correctly seated in the socket and is getting power. Also, check whether there are SAS errors in the logs. If other drives are also missing, then check whether there is a common failure domain (such as enclosure powered off or disconnected cables). In rare cases the drive might be dead and must be replaced.
gnr_pdisk_needanalysis	STATE_CHANGE FAILED	ERROR	no	Message: GNR pdisk {0} needs analysis.
				Description: The GNR pdisk has a problem that has to be analysed and solved by an expert.
				Cause: The mmlspdisk command shows attention user condition for the disk.
				User Action: If the issue persists, then contact IBM support.
gnr_pdisk_nodisks	STATE_CHANGE HEALTHY	INFO	no	Message: No pdisks found on this node.
				Description: No pdisks found, but some pdisks are expected on recovery group nodes.
				Cause: N/A
				User Action: N/A
gnr_pdisk_ok	STATE_CHANGE HEALTHY	INFO	no	Message: GNR pdisk {0} is OK.
				Description: The pdisk state is OK.
				Cause: N/A
				User Action: N/A
gnr_pdisk_pathsum_degraded	STATE_CHANGE DEGRADED	WARNING	no	Message: GNR pdisk {id} path state is degraded because of maintenance or failure.
				Description: Not all of the expected paths are active.
				Cause: The mmvdisk pdisk list --recovery-group all -Y command shows that not all expected paths are active.
				User Action: If you do maintenance, finish it. Otherwise, check the SAS cable. If you cannot determine the problem, contact IBM support for a service action.
gnr_pdisk_pathsum_ok	STATE_CHANGE HEALTHY	INFO	no	Message: GNR pdisk {id} has the expected paths active.
				Description: All expected paths are active.
				Cause: N/A
				User Action: N/A
gnr_pdisk_replaceable	STATE_CHANGE FAILED	ERROR	no	Message: GNR pdisk {0} is replaceable.
				Description: The pdisk is ready to be replaced, which means that all the data is drained out of the disk.
				Cause: The mmlspdisk command shows replaceable user condition for the disk.
				User Action: Replace the pdisk.
gnr_pdisk_sedlocked	STATE_CHANGE FAILED	ERROR	no	Message: GNR pdisk {0}, which is a self-encrypting drive, is locked.
				Description: A self-encrypting drive, which has encryption enabled, is locked. GNR does not have access to any data on the drive.
				Cause: The mmlspdisk command shows that the pdisk state contains sedLocked.
				User Action: The drive must be unlocked to be used by GNR. For more information, see the section 'Maintenance Procedures' in the 'ESS Knowledge Center'.
gnr_pdisk_server_down	STATE_CHANGE FAILED	ERROR	no	Message: GNR server {0}, responsible for pdisk {1}, is unresponsive and hence causing the pdisk to be unavailable.
				Description: The recovery group server node, which is responsible for this pdisk, is reported as unresponsive. This causes this pdisk to be unavailable to the recovery group.
				Cause: The recovery group server node, which is responsible for this pdisk, is down or unresponsive.
				User Action: Determine the health of the recovery group server nodes and resolve any health issues that are found.
gnr_pdisk_server_up	STATE_CHANGE HEALTHY	INFO	no	Message: GNR server {0} responsible for pdisk {1} is active.
				Description: The recovery group server node, which is responsible for this pdisk and previously reported as unresponsive, is now active.
				Cause: N/A
				User Action: N/A
gnr_pdisk_unknown	STATE_CHANGE DEGRADED	WARNING	no	Message: GNR pdisks are in unknown state.
				Description: The pdisk state is unknown.
				Cause: The pdisk state, which was previously known, is now unknown.
				User Action: Check the mmlspdisk command output for errors and verify that the pdisk states are correct.
gnr_pdisk_vanished	DELETE_ENTITY	INFO	no	Message: GNR pdisk {0} has vanished.
				Description: A GNR pdisk, which was previously listed in the IBM Storage Scale configuration, was not detected.
				Cause: N/A
				User Action: N/A
gnr_pdisk_vwce	STATE_CHANGE FAILED	ERROR	no	Message: GNR pdisk {0} has volatile write cache enabled.
				Description: Volatile write cache is enabled on the drive. The writes, that are already committed, can be lost in case of a power loss. GNR only reads from this disk, does not write to it.
				Cause: The mmlspdisk command shows that the pdisk state contains VWCE.
				User Action: Check the reason behind enabling the volatile write cache. For example, a new drive was added with wrong defaults or wrong UDEV rules. Fix the modes by using the 'sg_wr_modes' command.
gnr_pdisk_wcache_disabled	STATE_CHANGE HEALTHY	INFO	no	Message: GNR pdisk {0} has write cache disabled.
				Description: Write cache is disabled for this pdisk, which is the recommended state.
				Cause: N/A
				User Action: N/A
gnr_pdisk_wcache_enabled	STATE_CHANGE DEGRADED	WARNING	no	Message: GNR pdisk {0} has write cache enabled.
				Description: Write cache is enabled for this pdisk, a potential data loss is possible in case of power loss.
				Cause: The mmvdisk pdisk list --smart-data --recovery-group all -L -Y command shows that write cache is enabled for the this disk.
				User Action: Disable the write cache for the pdisk. For example, use the 'sdparm --set WCE=0 -s <devicename>' command.
ssd_endurance_ok	STATE_CHANGE HEALTHY	INFO	no	Message: The ssd-endurance-percentage of GNR pdisk {0} is OK.
				Description: The ssd-endurance-percentage value is OK.
				Cause: N/A
				User Action: N/A
ssd_endurance_warn	STATE_CHANGE DEGRADED	WARNING	no	Message: The ssd-endurance-percentage of GNR pdisk {0} is on a warning value.
				Description: The ssd-endurance-percentage value is a warning value.
				Cause: The ssd-endurance-percentage value of the pdisk is between 95 and 100.
				User Action: SSDs have a finite lifetime based on the number of drive writes per day. The ssd-endurance-percentage values are actually reported as a number between 0 and 255. This value indicates the percentage of life that is used by the drive. The value 0 indicates that full life remains, and 100 indicates that the drive is at or past its end of life. The drive must be replaced when the value exceeds 100.