TrueNAS 25.10-RC.1 is Now Available!

Looks like we found a similar issue internally… hope it is a duplicate.

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

I think the tickt might be prive, but here for future reference.

1 Like

Ah, interesting! Thanks for reporting that. Did you try BETA.1 before that and had the same issue there?

I already had the issue with not being able to upgrade custom apps since BETA.1, but also on RC.1. Reported the issue a month ago here: NAS-137429
Hopefully, this is the same issue I’m seeing.

Thank you TrueNas for doing such a great job. I was listening to the podcast to see what’s new. I think the changes will be a good improvement. I guess it a on going learning process which will help us get better at using TrueNas

1 Like

Yeah, I’m unfortunately still seeing the same issue on 25.10-RC.1.
It seems like the health check is badly broken. The issue is that it sometimes doesn’t find the credentials file, which middleware should create in the health check just before that. Underlying exception is: “Credentials cache does not exist”.

I needed to add custom code to print the underlying exceptions, since they’re never even logged anywhere and replaced with a generic “Stored machine account secret is invalid” message, which is only half-true…

Since a failing health check now also causes the AD user/group cache to clear (or at least not show) in the frontend, I’ve had custom code on BETA.1 to basically just disable the health check. Everything seemed to work fine then.
I’ll likely just implement the same on RC.1 again, since AD is spammy and unusable without that when editing permissions in the TN UI.

There are more details on the underlying exceptions (that are not logged without custom code) in my comment on JIRA here. (might need to scroll down manually and open all answers to A. Walker)

Has anyone gotten Secure Boot working without any hacks? :slight_smile:

In a test VM I made it does not. Checking with virsh I find:

  1. Enrolled keys not enabled: <feature enabled='no' name='enrolled-keys'/>
  2. Correct loader is used: <loader readonly='yes' secure='yes' type='pflash' format='raw'>/usr/share/OVMF/OVMF_CODE_4M.secboot.fd</loader>
  3. Wrong VARS file is used: <nvram template='/usr/share/OVMF/OVMF_VARS_4M.fd' templateFormat='raw' format='raw'>/var/db/system/vm/nvram/68_Test_VARS.fd</nvram>

/usr/share/OVMF/OVMF_VARS_4M.fd has no Secure Boot keys but /usr/share/OVMF/OVMF_VARS_4M.ms.fd does:

root@truenas[~]# strings /usr/share/OVMF/OVMF_VARS_4M.fd | grep -i microsoft
root@truenas[~]# strings /usr/share/OVMF/OVMF_VARS_4M.ms.fd | grep -i microsoft
Microsoft Corporation1200
)Microsoft Root Certificate Authority 20100
Microsoft Corporation1.0,
%Microsoft Windows Production PCA 20110
Ehttp://crl.microsoft.com/pki/crl/products/MicRooCerAut_2010-06-23.crl0Z
>http://www.microsoft.com/pki/certs/MicRooCerAut_2010-06-23.crt0
Microsoft Corporation1;09
2Microsoft Corporation Third Party Marketplace Root0
Microsoft Corporation1+0)
"Microsoft Corporation UEFI CA 20110
Khttp://crl.microsoft.com/pki/crl/products/MicCorThiParMarRoo_2010-10-05.crl0
Dhttp://www.microsoft.com/pki/certs/MicCorThiParMarRoo_2010-10-05.crt0
Microsoft Corporation1;09
2Microsoft Corporation Third Party Marketplace Root0
Microsoft Corporation1*0(
!Microsoft Corporation KEK CA 20110
Khttp://crl.microsoft.com/pki/crl/products/MicCorThiParMarRoo_2010-10-05.crl0
Dhttp://www.microsoft.com/pki/certs/MicCorThiParMarRoo_2010-10-05.crt0

I don’t see any known issues… can you start a new thread with full details of process and setup? Post link here.

Sure, here you go: Secure Boot toggle in 25.10-RC.1 virtual machines doesn't enable enrolled keys VARS

But why remove smart UI from truenas? It was there & it was beautiful.

It was removed because it was creating more problems than it was solving… not because of aesthetics. Customers were experiencing higher disk failure rates due to false positives. SSD tests were very restricted and weak.

The SMART data is still being used. The plumbing was retained so that users can (edit) monitor SMART data from an app — Scrutiny.

Maybe I’m being dense, but how does scrutiny control smart tests? I can’t find any levers to choose when and which tests take place.

1 Like

A cron schedule can be set using COLLECTOR_CRON_SCHEDULE. I think scrutiny only reads the SMART information and never schedules any tests.

1 Like

So an interface to schedule SMART tests was replaced by the official freedom to install an application which reads the results of the tests that users who install Goldeye anew now have to schedule through manual cron jobs. (BlindEye?)
:roll_eyes:

Just install Multi-Report

3 Likes

But is that not, de facto, the same process as just setting up a cron job in the cli and hence Scrutiny is just a dashboard? It’s not even a GUI because there is not actual interface.

Edit: if Scrutiny enabled the scheduling of smart tests via the GUI I would basically accept this as a design change but this feels like (another) cop out.

I don’t think scrutiny even displays test results. As far as I know it doesn’t read error logs or test logs. It only looks at metrics. There is a feature request for error/test logs:

Scrutiny does track metrics in a time-series database. So if you like historical data you can now track metrics over time. Not sure if that is any useful when it comes to S.M.A.R.T. metrics.

I do agree that the user-interface part is a dashboard - you don’t get to control or configure anything. There is a collector which periodically puts metrics from S.M.A.R.T. into a database (influxdb). The UI displays the metrics from the database.

I can’t believe a professional NAS system requires installing a third-party app just to view S.M.A.R.T. data.

6 Likes

Technically speaking you can via smartctl xd
but yes it’s a bit s

Also: you couldn’t view SMART data in the GUI before 25.10. You could schedule SMART tests and view their results (success or failure).

Yet another example of “we couldn’t figure out how to do it right, so we won’t do it at all.”

3 Likes

I will try new things if instructions are given and I don’t have to guess what to do.

If the inbuilt smart was causing false positives, would it not be better to fix that.

Smart detection should be built into TN and not dependant on a 3rd party app lots of people might not even know they need to install.

I am just an end user, not admin level

4 Likes

Hahaha, it really is inexplicable.

1 Like

Is anyone else seeing a large number of worker threads with their VMs? I’m seeing like nearly 20-60 worker threads on my VMs, it seems weird.