Upload data

The following support data is uploaded when the IBM Storage Scale System disks in enclosures display a drive replace notification on an IBM Storage Scale System 3000, 3200, 3500, 5000, or .

  • The output of mmlspdisk command for the pdisk that is in replace state.
  • Additional support data is provided only when the event is initiated as a response to a callback. The following information is supplied in a .tgz file as additional support data:
    • Last 10000 lines of mmfs.log.latest from the node which generates the event.
    • Last 24 hours of the kernel messages (from journal) from the node which generates the event.
    • For IBM Flash Core Module (FCM) drives, a diagnostic report (drive debug log) per drive. This report only contains internal counters or debug statistics for failure analysis; it does not contain any data stored on the drive. Drive debug logs are in plain text format, they can be reviewed, and they are stored on the I/O node at /var/log/ess/hal/drivedumps.
The following support data is uploaded when the system displays any hardware issue in an IBM Storage Scale System 5000 system.
  • The output of the opal_elog_parse command for the serviceable event that caused failure.
  • Additional support data is provided only when the event is initiated as a response to a callback. The following information is supplied in a .tgz file as additional support data:
    • Last 10000 lines of mmfs.log.latest from the node which generates the event.
    • Last 24 hours of the kernel messages (from journal) from the node which generates the event.
The following support data is uploaded when the system displays any hardware issue in an IBM Storage Scale System 3000 or an IBM Storage Scale System 3200 system.
  • The output of the mmhealth command and the actual component that caused failure.
  • Additional support data is provided only when the event is initiated as a response to a callback. The following information is supplied in a .tgz file as additional support data:
    • Last 10000 lines of mmfs.log.latest from the node which generates the event.
    • Last 24 hours of the kernel messages (from journal) from the node which generates the event.