Closed killmasta93 closed 4 years ago
Is it a new installation?
Triggers that contain delta(5d)>0 and last()>0 will fire on any change unless last value is zero. E.g. when disk is replaced with zero values the trigger will not fire, but if value is less or more - it will. Therefore, replacing a faulty drive with faulty one will still trigger a problem that stays for 5 days (default).
Thanks for the reply, what happened was that the server rebooted today, but no disk were changed
Please show me the history of one of the disks (Latest data, Non-medium error count).
Thanks for the reply, here is the picture
You can see the increase right here, but to be sure click on Graph
and select values
.
Thanks for the quick reply, im attaching the picture, so does that mean all the disks are about to die out??
Could not be told straight away. Considering it was already 178 and only jumped by one - recent change is not fatal. Just keep the disk in check and make backups. Given that it's not a single disk error, the reason could be: power supply, data cable or controller.
Thanks for the reply, will keep in mind
Describe the problem Hi, So today i got alert saying errors of non-medium the only thing that is odd is that i got an alert for all the disk which i find it odd
sdm: Number of Non-Medium errors has changed within past 5 days on prometheus3hagroup 1h 59m 39s No 1 action
To Reproduce
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
Provide all outputs described in Testing step Serial numbers should be replaced with X_SERIAL_X.
Please complete the following information: