HP MSA 1040 HP MSA Events Description Reference Guide (762785-001, March 2014) - Page 47

con the replacement as a dedicated or global spare for future use.

Get HP MSA 1040 PDF manuals and user guides View all HP MSA 1040 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 47 highlights

401 Warning The indicated log has filled to a level at which diagnostic data will be lost if not transferred to a log-collection system. Recommended actions • Transfer the log file to the log-collection system. 402 Error The indicated log has wrapped and has started to overwrite its oldest diagnostic data. Recommended actions • Investigate why the log-collection system is not transferring the logs before they are overwritten. For example, you might have enabled managed logs without configuring a destination to send logs to. 412 Warning One disk in the indicated RAID-6 vdisk failed. The vdisk is on line but has a status of FTDN (fault tolerant with a down disk). If a dedicated spare or global spare of the proper type and size is present, that spare is used to automatically reconstruct the vdisk; events 9 and 37 are logged to indicate this. If no usable spare disk is present, but an available disk of the proper type and size is present and the dynamic spares feature is enabled, that disk is used to automatically reconstruct the vdisk; event 37 is logged. Recommended actions • If no spare was present and the dynamic spares feature is disabled (that is, event 37 was NOT logged), configure an available disk as a dedicated spare for the vdisk or replace the failed disk and configure the new disk as a dedicated spare for the vdisk. That spare will be used to automatically reconstruct the vdisk; confirm this by checking that events 9 and 37 are logged. • Otherwise, reconstruction automatically started and event 37 was logged. Replace the failed disk and configure the replacement as a dedicated or global spare for future use. • Confirm that all failed disks have been replaced and that there are sufficient spare disks configured for future use. 413 Info. Created a replication set with the indicated primary volume. Recommended actions • No action is required. 414 Error Failed to create the indicated replication set for the indicated volume. This operation is not permitted if the specified volume is already in a replication set or is not a master volume. Recommended actions • If the volume is a master volume and is not in a replication set, retry the operation. 415 Info. Deleted the indicated replication set. Recommended actions • No action is required. Event descriptions 47

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
Event descriptions
47
401
Warning
The indicated log has filled to a level at which diagnostic data will be lost if not transferred to a
log-collection system.
Recommended actions
•
Transfer the log file to the log-collection system.
402
Error
The indicated log has wrapped and has started to overwrite its oldest diagnostic data.
Recommended actions
•
Investigate why the log-collection system is not transferring the logs before they are overwritten. For
example, you might have enabled managed logs without configuring a destination to send logs to.
412
Warning
One disk in the indicated RAID-6 vdisk failed. The vdisk is on line but has a status of FTDN (fault tolerant
with a down disk).
If a dedicated spare or global spare of the proper type and size is present, that spare is used to
automatically reconstruct the vdisk; events 9 and 37 are logged to indicate this. If no usable spare disk is
present, but an available disk of the proper type and size is present and the dynamic spares feature is
enabled, that disk is used to automatically reconstruct the vdisk; event 37 is logged.
Recommended actions
•
If no spare was present and the dynamic spares feature is disabled (that is, event 37 was NOT
logged), configure an available disk as a dedicated spare for the vdisk or replace the failed disk and
configure the new disk as a dedicated spare for the vdisk. That spare will be used to automatically
reconstruct the vdisk; confirm this by checking that events 9 and 37 are logged.
•
Otherwise, reconstruction automatically started and event 37 was logged. Replace the failed disk and
configure the replacement as a dedicated or global spare for future use.
•
Confirm that all failed disks have been replaced and that there are sufficient spare disks configured for
future use.
413
Info.
Created a replication set with the indicated primary volume.
Recommended actions
•
No action is required.
414
Error
Failed to create the indicated replication set for the indicated volume.
This operation is not permitted if the specified volume is already in a replication set or is not a master
volume.
Recommended actions
•
If the volume is a master volume and is not in a replication set, retry the operation.
415
Info.
Deleted the indicated replication set.
Recommended actions
•
No action is required.