Generated smartd.conf contains unknown Directive root

Description

Since I replaced a hard drive the smartd config is generated broken. Error from /var/log/messages:

Jan 11 21:28:13 **** 1 2024-01-11T21:28:13.962641+01:00 ****.local smartd 2896 - - File /usr/local/etc/smartd.conf line 3 (drive /dev/ada0): unknown Directive: root
Jan 11 21:28:13 **** 1 2024-01-11T21:28:13.962658+01:00 ****.local smartd 2896 - - Run smartd -D to print a list of valid Directives.
Jan 11 21:28:13 **** 1 2024-01-11T21:28:13.962668+01:00 ****.local smartd 2896 - - Configuration file /usr/local/etc/smartd.conf has fatal syntax errors.

The config /usr/local/etc/smartd.conf:

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

First this “root” only appeared for the entry of the replaced disk after enabling SMART. Then I tried to disable/reenable SMART for all disks. Now “root” will be added to all enabled disks. Now I’ve disabled all and tried to get it for one drive (/dev/ada0) to work. Also strange: It has two entries in the config.

I searched the forum and the bug tracker, but didn’t found anything helpful. I’ve didn’t edited the smatd.conf by hand.

I run TrueNAS Core version: TrueNAS-13.0-U6.1

Problem/Justification

None

Impact

None

Attachments

2

Activity

Show:

Bug Clerk April 4, 2024 at 8:25 AM

This issue has now been closed. Comments made after this point may not be viewed by the TrueNAS Teams. Please open a new issue if you have found a problem or need to re-engage with the TrueNAS Engineering Teams.

Bug Clerk March 20, 2024 at 3:02 PM

Ievgen Stepanovych January 24, 2024 at 12:03 PM

We’ll try to do something to prevent this.

For SED password to take any effect, you need to have a special disk.

If this is not the case for you, setting password will not do anything and you can safely remove it.

Sven Strittmatter January 24, 2024 at 11:45 AM

That’s weird because the HTML does not have a name/id that suggest a username or password:

<input _ngcontent-bij-c441="" matinput="" autocomplete="off" autocapitalize="none" ix-auto="input__S.M.A.R.T. extra options" ix-auto-type="input" class="mat-input-element mat-form-field-autofill-control ng-tns-c130-21 cdk-text-field-autofill-monitored ng-valid ng-dirty ng-touched" type="text" max="undefined" min="undefined" id="mat-input-8" placeholder="S.M.A.R.T. extra options" aria-invalid="false" aria-required="false">

<input _ngcontent-bij-c441="" matinput="" autocomplete="off" autocapitalize="none" ix-auto="input__SED Password" ix-auto-type="input" class="mat-input-element mat-form-field-autofill-control ng-tns-c130-25 password-field cdk-text-field-autofill-monitored ng-valid ng-dirty ng-touched" type="text" max="undefined" min="undefined" value="" id="mat-input-12" placeholder="SED Password" aria-invalid="false" aria-required="false">

Quick search says that autocomplete="off" should prevent that password managers put something in the input. Maybe this is a bug of Bitwarden. I search their issues and xref here, if I find something.

Sven Strittmatter January 23, 2024 at 2:07 PM

Yes, its the Bitwarden Firefox extension 🙈

No idea how to suppress this behavior. I’m using Bitwarden in FF and TrueNAS since years. I’ve wondered some times were this SED Password came from. Do I have now such a SED password configured and does it destroy something, if we get managed to remove this autofill problem?

Complete
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Story Points

Components

Fix versions

Affects versions

Priority

More fields

Katalon Platform

Created January 11, 2024 at 9:25 PM
Updated May 8, 2024 at 5:55 PM
Resolved April 4, 2024 at 8:25 AM