Project

General

Profile

Bug #14296

Upon disk replacement, automated SMART tests need re-configuring

Added by disk diddler over 4 years ago. Updated almost 3 years ago.

Status:
Resolved
Priority:
Nice to have
Assignee:
Dru Lavigne
Category:
Documentation
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:

HP Microserver N54L, 8GB memory, 6x HDD, FN 9.3.1 stable train, latest from USB bootable.

ChangeLog Required:
No

Description

I am pretty sure I've brought this up on the forums before, sorry don't recall where.

I have 7 jobs configured.
12'th of month ADA0 full SMART
13'th of month ADA1 full SMART
14'th of month ADA2 full SMART
(etc)

Also another job, every 2 days, short SMART test, all disks.

When you replace a faulty disk, the SMART test 'unticks' the disks it needs to test in the job, thereby missing future tests.
This may be due to how the backend is coded, perhaps the test doesn't REALLY talk to ADA0 or ADA1 but the GPT id or other such low level identifier?

Regardless, I propose this either be fixed so that the tests then re-point to the new disk in the same 'slot' or alternatively a very clear and obvious notice is displayed "please re-configure automated SMART tests for the new drive"

Associated revisions

Revision 7aec96ca (diff)
Added by Dru Lavigne over 4 years ago

Add 4th step to drive replacement process. Fixes #14296.

History

#1 Updated by Jordan Hubbard over 4 years ago

  • Status changed from Unscreened to Closed: Not To Be Fixed

This has been debated many times, and there is also a contingent who feels that copying a SMART test to another device behind the user's back is "too magical" and shouldn't be done. Since the user has replaced the drive, the logic goes, they should also know to add the SMART test.

#2 Updated by disk diddler over 4 years ago

Jordan Hubbard wrote:

This has been debated many times, and there is also a contingent who feels that copying a SMART test to another device behind the user's back is "too magical" and shouldn't be done. Since the user has replaced the drive, the logic goes, they should also know to add the SMART test.

This is the kind of atrocious 'we're always right' response I'd expect of Cyberjock. In the very least it's not hard to have a screen pop up or text adjustment warning the user to do it themselves - that surely isn't difficult?
Every simple UI suggestion I make for this gets shot down, then you guys wonder why the forums is full of inane questions. 2 sentences could alleviate this problem in a dialogue box.

#3 Updated by disk diddler over 4 years ago

Jordan Hubbard wrote:

This has been debated many times, and there is also a contingent who feels that copying a SMART test to another device behind the user's back is "too magical" and shouldn't be done. Since the user has replaced the drive, the logic goes, they should also know to add the SMART test.

This is the kind of atrocious 'we're always right' response I'd expect of Cyberjock. In the very least it's not hard to have a screen pop up or text adjustment warning the user to do it themselves - that surely isn't difficult?
Every simple UI suggestion I make for this gets shot down, then you guys wonder why the forums is full of inane questions. 2 sentences could alleviate this problem in a dialogue box.

EDIT: and people wonder why I'm skeptical about FN10 when it's gone back to the drawing board for UI, what small positive changes have been snuck through for usability will be reset back to the dark ages again.
Very frustrating.

#4 Updated by Jordan Hubbard over 4 years ago

I don't understand the response. No one said anything about being "right" - the observation was simply made that copying SMART tests was controversial and there's not a single "right" answer here, just subjective opinions about what should be done.

If you want to send us a github pull request that implements the change in behavior you're asking for, it will absolutely be given a fair and unbiased evaluation.

#5 Updated by disk diddler over 4 years ago

Sorry I'm frustrated, I've made at least 3 suggestions now which have been shot down.

All I'm suggesting in the least, is that the "replace disk" dialogue box, be re-worded or improved with a banner or something indicating to the user

*"Warning, XYZ tasks/jobs WILL need to be re-configured replacing disk, please be sure to check your existing tasks/jobs which utilise this device in their corresponding menus" *
That simple sentence is the difference between things like this bug report or people finding out their smart monthly checks haven't run on disk X in an array for 9 months, because they didn't fix it, and again - avoids posts on the forums.

I totally understand not copying the existing SMART job, I imagine it's not simple, but a simple text warning surely couldn't be a huge amount of work.

#6 Updated by Dru Lavigne over 4 years ago

  • Status changed from Closed: Not To Be Fixed to Resolved
  • Priority changed from No priority to Nice to have

Added as the 4th step to the drive replacement process in 9.10 Guide: https://github.com/freenas/freenas/commit/7aec96ca39d4dfca1ff2043208ee090bab73d701.

#7 Updated by Dru Lavigne almost 3 years ago

  • Category changed from 2 to Documentation
  • Assignee set to Dru Lavigne
  • Target version set to Master - FreeNAS Nightlies

Also available in: Atom PDF