Other than some Instance issues, overall looks great!
It shows the following in Update:
- Current Train: TrueNAS-SCALE-Fangtooth
- Upgrade TrueNAS-25.04-RC.1 ā TrueNAS-25.04.0
- Selected train does not have production releases, and should only be used for testing.
I would suggest deleting the 25.04.0 boot environment if it already exists.
Check you have the correct manual update file, this is the correct link after the changes yesterday:
https://update.sys.truenas.net/scale/TrueNAS-SCALE-Fangtooth/TrueNAS-SCALE-25.04.0.update
I tried the method that you suggested deleting the 25.04.0 boot environment and using the link you provided. Same result, still on RC.
Is there a limit to how many boot environments GRUB can show? It does not show 25.04.0 in the GRUB list on boot but it does show it in boot environments list inside TRUENAS gui. Shows it as āRestartā but will not activate it after reboot. I have 14 boot environments.
Update went fine, except that my SMB shares didnāt work anymore (coming from EEL). I had to re-enter the passwords in the TrueNAS User Credentials again.
I guess it is related to: NAS-135357 / 25.10 / Fix validation of NT hashes by anodos325 Ā· Pull Request #16271 Ā· truenas/middleware Ā· GitHub
1 Like
Yes. There was a validation escape in the UI / API that allowed users to disable password authentication by entering an empty string for the password rather than checking the box to disable password authentication. I thought I had fixed it for 25.04.0 (so that alert would be raised regarding this misconfiguration) but it looks like the fix was incomplete and so I just pushed a proper fix with CI tests. The underlying API issue is being addressed for 25.10.
TL;DR, make sure that your accounts without passwords are properly set with password disabled in the UI, and donāt enable SMB for accounts that should not have password auth.
2 Likes
You should post your issues in a separate thread. The release thread isnāt a great place to get support on specific issues since it makes it hard to follow.
1 Like
My upgrade from RC1 to 25.04.0 worked fine in the 3 places I have done it so far.
1 Like
The āStorageā UI doesnāt show me the drive temps anymore. Hasnāt worked with beta, rc, or release of Fangtooth. Yes Iāve refreshed the cache. Does this work for anyone?
Reporting does show the temperatures, but seems to have that lunid issue like in the screenshot. Not sure thatās related to the root issue at all, but yeah all my disks in reporting look like:
Disk Temperature SSD | TOSHIBA_THNSN81Q92CSE Model | {serial_lunid}96US106UTB4V_500080d91082af09
Yep disk temp is working for me, but it also did work on the rc
1 Like
Thanks, does your Reporting page also show {serial_lunid}asfasdadsf ?
I have 120 disks. I wonder if itās not properly enumerating things? Scrolling through reporting is a bit tedious. Found other methods to check, but I like when the UI shows everything properlyā¦
Yep its showing
Disk Temperature HDD | ST4000VN008-2DR166 Model | {serial_lunid}ZGY7LDJL_5000c500c6c82b32
2 Likes
Is that in every case this error pops out? Because if so, I would like to maybe create a PR to make that error a bit more descriptive.
Bug report submitted (NAS-135396).
I wonder if some basic support for snapshots will be added in point release. Impossible backup/restore of VMs is blocker for migration.
Otherwise:
3 Likes
Storage Dashboard is still not showing drive temps.
2 Likes
Yes. As mentioned in UI, the feature is experimental. We are going to keep adding in functionality as the dot releases progress.
Thats nice to hear. I understand that its experimental. I just didnt know if point releases are just for bugfixes or if they can also introduce new features like snapshots for Incus VMs.
Experimental among other things implies that APIs and functionality are subject to change.
2 Likes