Project

General

Profile

Bug #50819

Fix smart config not being regenerated when reloading smartd

Added by Bug Clerk almost 2 years ago. Updated almost 2 years ago.

Status:
Done
Priority:
No priority
Assignee:
Vladimir Vinogradenko
Category:
Middleware
Target version:
Seen in:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
No
Needs Doc:
No
Needs Merging:
No
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

Seen on the QA x-10 running TrueNAS-11.1-U6-INTERNAL7
I set the Services ->smart -> configuration -> critical to 40 on Friday to test a reported issue.
I went back and zeroed it out after I was done yesterday (8/27/18)
Support got a ticket today Kayako (FGP-949-13975), I am getting an email alert, and there is a critical alert in the GUI
(Screenshots provided)


Related issues

Related to FreeNAS - Bug #56025: Rework SMART alertClosed
Related to FreeNAS - Bug #56034: Rework SMART alerts and add one-shot alertsDone
Has duplicate FreeNAS - Bug #53037: S.M.A.R.T. will not startClosed
Copied from FreeNAS - Bug #43196: Fix SMART config not being regenerated when reloading smartdDone
Copied to FreeNAS - Bug #51006: Fix smart config not being regenerated when reloading smartdDone

History

#1 Updated by Bug Clerk almost 2 years ago

  • Copied from Bug #43196: Fix SMART config not being regenerated when reloading smartd added

#2 Updated by Bug Clerk almost 2 years ago

  • Status changed from Unscreened to In Progress

#3 Updated by Dru Lavigne almost 2 years ago

  • Target version changed from Master - FreeNAS Nightlies to 11.2-RC2

#4 Updated by Dru Lavigne almost 2 years ago

#5 Updated by Bug Clerk almost 2 years ago

  • Copied to Bug #51006: Fix smart config not being regenerated when reloading smartd added

#6 Updated by Bug Clerk almost 2 years ago

  • Status changed from In Progress to Ready for Testing

#7 Updated by Dru Lavigne almost 2 years ago

  • Subject changed from Changes made in the Smart Service Configuration are not being updated to Fix smart config not being regenerated when reloading smartd
  • Needs Doc changed from Yes to No
  • Needs Merging changed from Yes to No

#8 Updated by Dru Lavigne almost 2 years ago

  • Has duplicate Bug #53037: S.M.A.R.T. will not start added

#9 Updated by Bonnie Follweiler almost 2 years ago

  • Status changed from Ready for Testing to Failed Testing

Test Failed in FreeNAS-11.2-INTERNAL29

#10 Updated by Bug Clerk almost 2 years ago

  • Status changed from Failed Testing to In Progress

#11 Updated by Bug Clerk almost 2 years ago

  • Status changed from In Progress to Ready for Testing

#12 Updated by Bonnie Follweiler almost 2 years ago

38580
38589
38598
38601

Test Failed in FreeNAS-11.2-INTERNAL33
After almost 2 hours there is no alert
Screenshots provided

#13 Updated by Dru Lavigne almost 2 years ago

  • Status changed from Failed Testing to In Progress
  • Needs Merging changed from No to Yes

#14 Updated by Vladimir Vinogradenko almost 2 years ago

Acceptance Criteria

Boot machine with SMART critical temperature set to large value (e.g. 100 C). Clear alerts if any are present.

Set SMART critical temperature to temperature lower than HDD temperature (e.g. 20 C). Alerts should appear in a few seconds (I don't know how often UI refreshes alerts so it's better to reload the page).

#15 Updated by Vladimir Vinogradenko almost 2 years ago

#16 Updated by Vladimir Vinogradenko almost 2 years ago

  • Related to Bug #56034: Rework SMART alerts and add one-shot alerts added

#17 Updated by Vladimir Vinogradenko almost 2 years ago

  • Status changed from In Progress to Ready for Testing

#18 Updated by Vladimir Vinogradenko almost 2 years ago

  • Status changed from Ready for Testing to In Progress

#19 Updated by Dru Lavigne almost 2 years ago

  • Status changed from In Progress to Done
  • Needs QA changed from Yes to No
  • Needs Merging changed from Yes to No

#21 Updated by Shawn Anderson almost 2 years ago

  • Seen in changed from TrueNAS-11.1-U6.1 to 11.2-RC2

I am seeing this same issue in RC2

#22 Updated by Dru Lavigne almost 2 years ago

The work on the related tickets (the ones that are Ready for Testing) should resolve the issue. However, they are targetted for U1, due out a few weeks after RELEASE.

Also available in: Atom PDF