IBM Storwize V7000 Troubleshooting And Maintenance Manual page 87

Table of Contents

Advertisement

Table 19. Event IDs and codes (continued)
Notification
Event ID
type
010062
E
010063
W
4
4 4 4
010066
W
4
010067
W
010068
E
010069
E
010070
W
010071
W
010072
E
010073
E
010080
E
010081
E
010082
E
010083
E
010084
E
010085
W
010086
W
010087
W
010088
E
010089
E
010090
E
010091
E
010092
E
010093
E
020001
E
020002
E
020003
W
029001
W
029002
E
029003
E
030000
W
030010
W
030020
W
045001
E
045002
E
045003
E
Condition
A drive exceeded the warning temperature threshold.
Drive medium error.
Controller indicates that it does not support descriptor sense for LUNs
that are greater than 2 TBs.
Too many enclosures were presented to a cluster.
The solid-state drive (SSD) format was corrupted.
The block size for the solid-state drive (SSD) was incorrect.
Too many controller target ports were presented to the cluster.
Too many target ports were presented to the cluster from a single
controller.
The drive is offline as a result of a drive hardware error.
The drive is reporting predictive failure analysis (PFA) errors.
The drive is reporting too many errors.
The drive format is corrupted.
The block size for the drive was incorrect.
The drive is offline due to excessive errors.
The error counts for the SAS drive exceeded the warning thresholds.
The SAS device was not recognized.
The SAS enclosure was not recognized.
The SAS device was not able to be identified.
There were excessive medium errors on the drive.
There were excessive overall timeout errors on the drive.
There were excessive times when the drive stopped.
A drive failed validation testing.
There were excessive medium errors on the solid-state drive (SSD).
There were excessive overall timeout errors on the solid-state drive (SSD). 1204
There are too many medium errors on the managed disk.
A managed disk group is offline.
There are insufficient virtual extents.
The managed disk has bad blocks.
The system failed to create a bad block because MDisk already has the
maximum number of allowed bad blocks.
The system failed to create a bad block because cluster already has the
maximum number of allowed bad blocks.
The trigger prepare command has failed because of a cache flush failure.
The mapping is stopped because of the error that is indicated in the data. 1910
The mapping is stopped because of a cluster or complete I/O group
failure, and the current state of the relationship could not be recovered.
One or more power supply unit fans have failed.
A fan is operating outside the expected range.
There was a fan status communications failure.
Error
code
1217
1321
1625
1200
1204
1204
1200
1200
1680
1680
1206
1206
1666
1666
1666
1680
1680
1680
1680
1215
1610
1620
2030
1840
1226
1225
1900
1895
1124
1126
1126
Chapter 7. Event reporting
71

Advertisement

Table of Contents
loading

Table of Contents