Smart tests are stuck on 10%. I just wiped the drives and did a new install and issue persists

I am running HexOS, which reports SMART errors, so headed to TrueNAS to get more information. It reports healthy system but unable to do any SMART tests.

I plugged drives into my windows pc and checked them on crystalmark and that also reported them as healthy.

Is there a way I can force a full, standalone tests on these drives?

They are 8TB Toshiba NAS N300 drives

I’m having a very similar issue. Also HexOS and with 2 x 14Tb Toshiba N300 discs. I ran a scrub that finished with 0 errors. Now I tried running SMART test, both long and short. Every time I run a SMART test it gets to 10% and then seemingly abruptly aborts, returning unknown failure. The TrueNAS ui however shows the progress still stuck at 10%, only in CLI does it show that the test was aborted when running smartctl -a.

After searching around a bit all I can find is that it may be a Toshiba firmware issue causing it to immediately abort on any background activity, power-state transition, or SMART polling. However I have no apps running and nothing except system services should be using the drives.

Did you manage to solve this? Or is there anyone here who recognizes the issue and knows of any solution?

I bought some new used drives to replace them. Turns out that I probably damaged them while moving as felt the gyroscopic effect, which apparently means is a death sentence for them.

I’ve seen SMART tests sit at 10% for hours and still be working in the background. On TrueNAS it often looks stuck even though the disk is busy. Checking the job from the shell or SMART logs usually shows progress. If it never moves, I’d suspect a controller or cable issue rather than the OS, especially after a clean install.

SMART tests always have the lowest priority when it comes to reading the drive data. If your NAS is reading or writing, the SMART test is placed on hold. This is internal to the drive. If you tried to run a SMART test during a Scrub or Resilver, that test will barely move until those operations are completed.

All you can do is run smartctl -a /dev/??? to see how much had been accomplished or remains.

Also, never trust the SMART Results unless it says “FAILED”. The drive can still be faulty even when a “PASSED” is displayed. This is the result of a power on self-test (POST), it is quick and dirty check and a drive failure, lets say you have Reallocated Sectors incrementing, well that will still be a “PASSED” indication, even though the drive is experiencing failures.

This is why it is important to read and understand the SMART data.