Project

General

Profile

Bug #8953

/dev/hptrr alert message

Added by Dan Ove Brest over 5 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Nice to have
Assignee:
William Grzybowski
Category:
Middleware
Target version:
Seen in:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

The freenas is not showing eny errors in Alert panel or in the volume status when smart error on a drive.

i get an email:

This message was generated by the smartd daemon running on:

host name:  xxx
DNS domain: xxx

The following warning/error was logged by the smartd daemon:

Device: /dev/hptrr [hpt_disk_1/9/1], 1 Offline uncorrectable sectors

Device info:
WDC WD1003FBYX-01Y7B0, S/N:WD-WCAW31003025, WWN:5-0014ee-20583ec40, FW:01.01V01, 1.00 TB

For details see host's SYSLOG.

You can also use the smartctl utility for further investigation.
No additional messages about this problem will be sent.

and an CLI status:

Mar 30 21:46:25 Goliat smartd3845: Device: /dev/hptrr [hpt_disk_1/9/1], 1 Currently unreadable (pending) sectors
Mar 30 21:46:25 Goliat smartd3845: Device: /dev/hptrr [hpt_disk_1/9/1], 1 Offline uncorrectable sectors
Mar 30 21:46:25 Goliat kernel: <118>Mar 30 21:46:25 Goliat smartd3845: Device: /dev/hptrr [hpt_disk_1/9/1], 1 Currently unreadable (pending) sectors
Mar 30 21:46:25 Goliat kernel: <118>Mar 30 21:46:25 Goliat smartd3845: Device: /dev/hptrr [hpt_disk_1/9/1], 1 Offline uncorrectable sectors

is it possible to get this in the Alert button?

Associated revisions

Revision d488357d (diff)
Added by William Grzybowski over 5 years ago

Add tool to capture smartd alerts Ticket: #8953 Merge-FN93: yes Merge-TN93: yes

Revision 6999e083 (diff)
Added by William Grzybowski over 5 years ago

Add tool to capture smartd alerts Ticket: #8953 Merge-FN93: yes Merge-TN93: yes (cherry picked from commit d488357d466dcd2d59827fcc1221fa38dd513aa3)

Revision 1dde2d2d (diff)
Added by William Grzybowski over 5 years ago

Add tool to capture smartd alerts Ticket: #8953 Merge-FN93: yes Merge-TN93: yes (cherry picked from commit d488357d466dcd2d59827fcc1221fa38dd513aa3)

Revision be1fa524 (diff)
Added by William Grzybowski over 5 years ago

Call smart alert tool from smartd.conf Ticket: #8953 Merge-FN93: yes Merge-TN93: yes

Revision 49fc4d81 (diff)
Added by William Grzybowski over 5 years ago

Call smart alert tool from smartd.conf Ticket: #8953 Merge-FN93: yes Merge-TN93: yes (cherry picked from commit be1fa5244d80459a0c6f7b5077db1683052d1d1f)

Revision 4be75878 (diff)
Added by William Grzybowski over 5 years ago

Call smart alert tool from smartd.conf Ticket: #8953 Merge-FN93: yes Merge-TN93: yes (cherry picked from commit be1fa5244d80459a0c6f7b5077db1683052d1d1f)

Revision bbfe5562 (diff)
Added by William Grzybowski over 5 years ago

Add smart module to the alert system Ticket: #8953 Merge-FN93: yes Merge-TN93: yes

Revision 96eebb95 (diff)
Added by William Grzybowski over 5 years ago

Add smart module to the alert system Ticket: #8953 Merge-FN93: yes Merge-TN93: yes (cherry picked from commit bbfe5562738f1f4d52da2190e70a159f1c543ddc)

Revision aff3609a (diff)
Added by William Grzybowski over 5 years ago

Add smart module to the alert system Ticket: #8953 Merge-FN93: yes Merge-TN93: yes (cherry picked from commit bbfe5562738f1f4d52da2190e70a159f1c543ddc)

History

#1 Updated by Dan Ove Brest over 5 years ago

  • File ixdiagnose.tgz added

#2 Updated by William Grzybowski over 5 years ago

  • Assignee deleted (William Grzybowski)

Well, smartd is supposed to email you these problems. I don't see any real gain using the alert system along with the email that smartd sends.

Maybe a goal for 10?

#3 Updated by Jordan Hubbard over 5 years ago

  • Assignee set to Xin Li
  • Target version set to Unspecified

#4 Updated by Jordan Hubbard over 5 years ago

  • Status changed from Unscreened to Screened
  • Assignee changed from Xin Li to William Grzybowski

BRB: I have to agree with the submitter - a smartd failure is definitely worthy of sending an alert, since the user may not even have email notifications set up, and the failure of a drive is at least as big a deal as any other "red alert" indications we have. Recommend having an alert module which checks smart status.

#5 Updated by William Grzybowski over 5 years ago

Calling smartctl en everydisk everytime seems overkill. Do you think /var/log/messages|grep smartd would work?

#6 Updated by Jordan Hubbard over 5 years ago

Yes, we talked about "grepping the log" as a reasonable approach to feeding the alert system. I'd say so.

#7 Updated by William Grzybowski over 5 years ago

Well, grepping wont work very well since we may get historical logs.

I'll investigate about using a script for alert in smartd.conf.

#8 Updated by William Grzybowski over 5 years ago

  • Status changed from Screened to Ready For Release

I've added smart alerts to the alert system using smartd.conf -M exec directive.

I appreciate some testing in Nightlies train.

#9 Updated by Jordan Hubbard over 5 years ago

  • ChangeLog Entry updated (diff)

#10 Updated by Jordan Hubbard over 5 years ago

  • Status changed from Ready For Release to Resolved

#11 Avatar?id=14398&size=24x24 Updated by Kris Moore about 4 years ago

  • Target version changed from Unspecified to N/A

#12 Updated by Dru Lavigne almost 3 years ago

  • File deleted (ixdiagnose.tgz)

Also available in: Atom PDF