Dell Server Internal Physical Disk Unit Health

Summary

Physical Disk Unit Monitor

Causes

• If PhysicalDisk is in warning state, causes/resolutions for this condition:

  Cause	Resolutions
  A predictive failure detected on drive <number> in disk drive bay <bay>.	The drive will need replacement at the next service window.
  A predictive failure detected on drive <number>.	The drive will need replacement at the next service window.
  Insufficient space available on <physical disk> to perform a copyback operation.	Replace the physical disk with a larger physical disk, and then restart the copyback operation.
  <PD Name> is removed.	If a physical disk was removed from the disk group, either replace the disk or restore the original disk. Identify the disk that was removed by locating the disk that has a red "X" for its status. Perform a rescan after replacing or restoring the disk. If a disk was not removed from the disk group, then check for cable problems. Refer to product documentation for more information on checking the cables. Make sure that the enclosure is powered on. If the problem persists, check the enclosure documentation for further diagnostic information.
  <physical disk> is offline.	Force the physical disk online or assign a hotspare to the virtual disk.
  Predictive failure reported for <physical disk>.	Replace the physical disk. Even though the disk may not have failed yet, it is strongly recommended that the disk be replaced. Review other messages for additional information.
  The <physical device> is not supported.	If the physical device is supported, then update the firmware to a supported version. If the physical device is not supported, then replace the physical device with one that is supported.
  The dedicated hot spare <PD Name> is too small.	Assign a larger disk as the dedicated hot spare.
  Insufficient space on the global hot spare <PD Name>.	Assign a larger disk as the global hot spare.
  A redundant path is broken.	Make sure the cables are attached securely. See the Cables Attached Correctly section for more information on checking the cables. Make sure both Enclosure Management Modules (EMMs) are healthy.
  Insufficient space available on the <physical disk> to perform a rebuild.	Replace the physical disk with one of correct protocol (SAS, SATA) with at least the required size. Force rebuild if it does not start automatically.
  Bad block table on <physical disk> is 80% full.	Replace the disk generating this message.
  Rebuild not possible on physical disk <PD Name>.	Remove drive, insert correct protocol type, and force a rebuild as imposed for controller and system.
  Bad block table on <physical disk> is full.	Replace the disk.
  Command timeout occurred on <physical disk>.<args>.	Check the disk is present or replace the disk.
  Component is under a software RAID controller for which health computation is not supported.	Ignore the WARNING state.

• If PhysicalDisk is in critical state, causes/resolutions for this condition:

  Cause	Resolutions
  Fault detected on drive <number> in disk drive bay <bay>.	Remove and reseat the failed drive. If the problem persists, contact technical support. Refer to the product documentation to choose a convenient contact method.
  Drive <number> is removed from disk drive bay <bay>.	Verify drive installation. Remove and reseat the failed drive. If the problem persists, contact technical support. Refer to the product documentation to choose a convenient contact method.
  Drive mismatch detected for drive <number> in disk drive bay <bay>.	Verify the disk meets the array requirements.
  Fault detected on drive <number>.	Remove and reseat the failed disk. If the problem persists, contact technical support. Refer to the product documentation to choose a convenient contact method.
  Drive <number> is removed.	If unintended, verify drive installation. Remove and reseat the indicated disk. If the problem persists, contact technical support. Refer to the product documentation to choose a convenient contact method.
  Patrol Read found an uncorrectable media error on <physical disk>.	Backup your data from the disk. Start disk initialization and wait for it to complete, then restore the data from the backup to the disk.
  A block on <physical disk> was punctured by the controller.	Back up the data from the disk. Start disk initialization and wait for it to complete, and then restore the data from a backup copy.
  Hot spare <physical disk> SMART polling has failed.<args>	Verify the health of the disk assigned as a hot spare. Replace the disk and reassign the hot spare. Make sure the cables are attached securely. See the storage hardware documentation for more information on checking the cables.
  Bad block table on <physical disk> is full. Unable to log block <logical block address >.	Replace the disk generating this message and restore from a backup copy. You may have lost data.
  The rebuild of <physical disk> failed due to errors on the source physical disk.	Replace the source disk and restore data from backup.
  The rebuild failed due to errors on the target <physical disk>.	Replace the target disk. If a rebuild does not automatically start after replacing the disk, then initiate the Rebuild task. You may need to assign the new disk as a hot spare to initiate the rebuild.
  A bad disk block on <physical disk> cannot be reassigned during a write operation.	Replace the disk.
  An unrecoverable disk media error occurred on <physical disk>.	Replace the disk.
  Copyback failed from <physical disk> to <physical disk>.	Replace the disk and retry the operation.
  Security subsystem errors detected for <physical disk>.	Verify the disk is a Secure Encrypted Disk and is not locked. If it is not, replace the disk with a Secure Encrypted Disk. See the storage hardware documentation for more information.
  Power state change failed on <PD Name>. (from <state> to <state>)	Replace the physical disk and try again. Contact technical support if the issue persists.
  Component is under a software RAID controller for which health computation is not supported.	Ignore the CRITICAL state.

Resolutions

Additional information on this issue may be available. Launch the iDRAC Console to debug further.