New replacement drives are not tested for SMART

[lukyjay]

Hi

Freenas 11 release

Drive failed so I replaced it. Went to my SMART schedule and the new drive is not toggled to be checked even though the old was.

If this is intended design does anyone know why? Also can we get a warning on the replace disk screen?

Thanks

 

[danb35]

If this is intended design does anyone know why?

Not sure if it's the intended design, but it's been that way for a long time. Currently slated to be fixed in 11.1, though: https://bugs.freenas.org/issues/19669 (A previous request was erroneously marked resolved a year ago: https://bugs.freenas.org/issues/14296)

 

[BigDave]

If this is intended design does anyone know why?

Not so much intended but the new disk has probably received a new designation from
FreeNAS when it replaced the old one. i.e. the old drive was ada2 and the new drive was
given ada6. It does change and it's up to you to keep tabs on this because it can not be
made an automatic thing due to physical drive changes almost always changing the
numbers that identify them. Make it a point to visit your config for smart testing on
a regular basis when changing out drives or adding hardware that changes how the
drives are "seen" by the OS.

 

[BigDave]

Currently slated to be fixed in 11.1, though

I did not hear about this
That's awesome! It will be interesting to watch how that's going to work out...

 

[danb35]

Not so much intended but the new disk has probably received a new designation from FreeNAS when it replaced the old one.

Nope, not what's going on. The SMART tests are tied to a disk ID in the config database, and that disk ID seems to be mostly based on the disk's serial number. But the GUI then translates that to the disk name (i.e., adan/dan) when scheduling the SMART tests.

Edit: You can confirm this yourself by opening the config database in an SQLite browser and taking a look at the tasks_smarttest and tasks_smarttest_smarttest_disks tables.

 

[danb35]

I did not hear about this

Well, the fact that the bug has a target set for 11.1 doesn't necessarily mean it will be fixed in 11.1--but it's still a positive sign.

 

[Ericloewe]

If 11.1 closes most of its current tickets, it'll probably be the biggest update in FreeNAS history, from an admin's point of view, even without considering the new GUI.

We don't talk about Corral unless we absolutely must.