Misconfigured SMART test schedule leads to buggy WebUI which i cant fix anymore

Hi there,
i was configuring SMART test schedules as I closed the Browsertab or just pressed save in the ui. The next thing I now is seeing, that i cant edit the smart test task anymore as you can see in the schreenshot. I noticed on my other Truenas machine, that if I change smart schedules, it changes the settings in etc/smartd.conf. So I tried deleting the faulty settings in this file as root with no difference. Everytime I reboot or restart Smart service, it clears this file and populates it with the faulty config again from somewhere else.
The result of this bug is, that i cannot change any settings on the Data Protection Site, since this one setting is faulty and therefore no other buttons work either.

Any help is much appreciated.

Thank you in advance for your time and effort!

Greetings
BillyElliot

My nano etc/smartd.conf look like this:

  GNU nano 7.2                                                                                                                                                         /etc/smartd.conf *                                                                                                                                                                
/dev/nvme0n1 -d nvme -a -d removable -n standby -W 0,0,0 -m root -M exec /usr/local/libexec/smart_alert.py\
-s L/../(01)/./(00)\

/dev/sdd -a -d removable -n standby -W 0,0,0 -m root -M exec /usr/local/libexec/smart_alert.py\
-s S/../../(7)/(09)\

/dev/sdd -a -d removable -n standby -W 0,0,0 -m root -M exec /usr/local/libexec/smart_alert.py\
-s L/../(01)/./(00)\

/dev/sdb -a -d removable -n standby -W 0,0,0 -m root -M exec /usr/local/libexec/smart_alert.py\
-s S/../../(7)/(09)\

/dev/sdb -a -d removable -n standby -W 0,0,0 -m root -M exec /usr/local/libexec/smart_alert.py\
-s L/../(01)/./(00)\

/dev/sdc -a -d removable -n standby -W 0,0,0 -m root -M exec /usr/local/libexec/smart_alert.py\
-s S/../()/./(18)\

/dev/sdc -a -d removable -n standby -W 0,0,0 -m root -M exec /usr/local/libexec/smart_alert.py\
-s L/../(01)/./(00)\

/dev/sda -a -d removable -n standby -W 0,0,0 -m root -M exec /usr/local/libexec/smart_alert.py\
-s S/../()/./(18)\

/dev/sda -a -d removable -n standby -W 0,0,0 -m root -M exec /usr/local/libexec/smart_alert.py\
-s L/../(01)/./(00)\

This can risk borking your system. It’s best to avoiding modifying the system files before addressing the underlying problem.


Have you tried clearing the browser cache or using a private window/tab or using a different browser?

1 Like

Yea i know. I did not know what else to do. I made a backup before i tried.
I tested in private tab and on different device. both the same result. Cant edit Scheduling.
Thank you for your help though!

What if you upload a screenshot to imgur or a site that allows it? Then link it in here?

the screenshot is now up. It was a permission thing. Since I was new to the forum. I edited my post anyway and got another trust level.

Looks like another GUI bug.

A couple things you can try:

  1. Hold CTRL and zoom in and out with your mouse wheel.
  2. Delete the first SMART task, and then see if the second one allows you to edit/delete it. (Then you can create your tasks again.)

If neither works, I would submit a bug report.

I created a Bug Report, since nothing helps.

https://ixsystems.atlassian.net/browse/NAS-134403

1 Like

@BillyElliot Had you performed an upgrade at all recently before the issue?

Have you resolved the issue?

If you still have the problem, do you have a copy of your TrueNAS configuration file from before the incident?

If you do have a copy then I would suggest the following:

  1. Create a new backup of your TrueNAS configuration file, save it somewhere safe.
  2. Upload the older TrueNAS configuration file and the system may reboot. If it does not reboot, make it happen.
  3. Do you still have the problem?
    I suspect your configuration file is messed up, I don’t see any other reason for this type of error to occur on a TrueNAS version that has been used by a Lot of people without issue, but all kinds of strange things happen.

If you feel like it, you could just reset to the factory configuration and maybe that will fix it. Unfortunately that would mean you have to reconfigure the entire NAS, and most people do not enjoy that.

Hi all,
the issue is fixed by a command to delete the faulty smart task via Cli. The command can be found via the link above.
Thanks everybody for helping!

1 Like