Possible bug: Replaced drives become removed from SMART testing.

[diskdiddler]

Since deploying my FreeNAS Machine in July last year, I've had 2 disk failures (7200rpm disks are a joke, don't ask, sigh)

I was just fiddling and looking around my system when I noticed the same 2 disks are actually missing from my routine SMART tests that are performed.
This is applicable to both my long and short pre-configured monthly tests.

Screenshot:

Perhaps this is just a known thing by the developers / advanced users and my own issue. If so, I recommend the replace disk screen have some wording / updates, making it clear "NOTE, you may need to reconfigure automated tests, such as X,Y,Z"

More information at your request, thanks

EDIT: Note, I did the disk replacements under 9.2.1.6 - I'm now on 9.3, perhaps this has been addressed, if so, apologies.

 

[Ericloewe]

Right, this is a known issue that is still outstanding.

The short-term solution is a reminder in the documentation to set up SMART tests for the new drives. Long-term, a fix is being investigated for FreeNAS 10.

 

[diskdiddler]

Right, this is a known issue that is still outstanding.

The short-term solution is a reminder in the documentation to set up SMART tests for the new drives. Long-term, a fix is being investigated for FreeNAS 10.

I don't think the reminder should be in the documentation, the reminder should be in the replace disk wizard / tool, prompting the user on the spot (and THEN the documentation)

 

[Rilo Ravestein]

I have to disagree. Changing the docs is much faster, and i would think that anyone doing something like this would check the documentation for changes, known issues etc. first.

 

[diskdiddler]

You're welcome to disagree, I'm living proof people don't need to check the documentation to do it. I can't fathom a world where you outright expect people to not only check the documentation each time but furthermore seem to believe that adding the message to the software, would be a negative thing.
How on earth is both a bad thing?

 

[Rilo Ravestein]

You are actually the living proof that people do need to check the documentation. You are also the living proof that people don't do that. ;) Which is not the the developers fault.

Besides that, nobody here said that adding the message to the software would be a bad thing, i'm really curious where you got that from. I only said that it would be logical to do the documentation first, as it is quicker, because the software/fix has some dev/test/release process.

 

[diskdiddler]

People do NOT need to check the documentation, because I was able to rebuild my pool successfully and have the replacement disk work. There was no indication of any fault, my storage array returned back to working as intended functionality, my faulty disk messages were gone.
By definition, I managed to complete the replacement successfully, without the documentation. This bug which is clearly admitted as a bug by eric in the second post is a side effect which is not visible to the user.
Adding a note to the documentation is fine of couse. You'll capture 20/30/50/60% of people replacing disks with adding it to the doco.
AND / OR you can capture 100% of people, reduce threads like this one, by having a notice upon disk replacement

"Please note, replacing disks will require adjustment to the folowing scripts / jobs"

 

[Rilo Ravestein]

If you don't want to read the manual, that's your choice. You are the living proof of what can happen then. And again: Nobody said the notification should not be in the gui. I only said that putting it in the doc would be faster and, like you said, that could help some people that actually RTFM until the notification is in the gui or the bug is fixed.

 

[diskdiddler]

Agree there's no harm adding to the doc.

 

[diskdiddler]

Should I be posting some kind of request or bug notification or documentation amendment suggestion somewhere or is this thread enough? The issue no longer impacts me but it would be nice for new users to not have to deal with this.

 

[joeschmuck]

Thought I'd stir this pot just a little...

My two cents are to add it to both the docs and the application. Lets face it, application updates are being done daily and it's easy to slide in an alert to flash up when you change the drive and have it toss you a note that if you had a SMART test scheduled (as you should) that you will need to fix it up.

My issue with the user manual is I hate to read it all the time "just in case" it changes. At least with the previous way FreeNAS was released, the manual changed with the release and you could read all about the differences when you upgrade your software and you didn't need to refer back to the manual because you knew nothing changed. Do you see my point?

Also, FreeNAS has matured to more than a simple NAS appliance, it's a full featured application that does more than any NAS I've seen. Look at all those plugins and jails and well, just too much going on these days. Not complaining, just it's more than I think anyone ever expected it to become.

Anyway, pot stirred a little.

 

[diskdiddler]

Not really stirring the pot, just reinforcing that it would be good to have it in both places :)