I have a CSR setup to update my cloudflare cert every 30 days, will that still work?
1 Like
"Failed to start docker for Applications: Docker service could not be started" error on Apps page for me on first boot of beta. reboot a few times and still doesnāt come back up.
Rollback to 25.04.2.1 and apps come back up.
Tried using the happy face feedback button on beta and this error comes up 
1 Like
I canāt help it; I just have to rephrase this:
Dropping all things S.M.A.R.T. on TrueNAS Scale is a consequential move.
That will continueā¦failure alerts and emails are unchanged.
The odds of it being a false alert have been reduced.
2 Likes
All things SMART have not been droppedā¦
Specific WebUI options have been removed
Disk management has been better automated.
I agree its consequential.
We expect it to be much better, but we left all the hooks for users to have their own systems.
Please report a bug and share the ticket number. They will need a full debug.
Known issues are GTX NVidia cards???
Suggest you Reboot. Then report a bug with full debug
Rollback and indicate whether the issue went away.
Please report theNAS-ticket.
Hi @Captain_Morgan,
Thanks for your response.
Best way to get a debug log without access to the built-in report bug feature?
Edit:
Nvm think I found it
Edit #2:
Not only did I find it, but it fixed itself. I think it mustāve been that not all my apps were updated. I updated them all since lastnightās issues, and after trying just now, it appears fixed. 
Edit #3:
But is this used disk space happening for others?
Edit #4:
It fixed itself againš¤Ŗ
Edit #5:
It broke itself again. Jira ticket made w debug logš¤Ŗ
1 Like
Should we wait for it to fix itself again?
Iād suggest starting a thread in General and sharing details and a NAS-ticket. Process, hardware and setup are interesting to understand. Add the link to your previous comment.
Not sure if I shared my debug the right way in the ticket, so I asked for it to be private. Iām sure itāll get fixed eventually 
Yes. I saw that as well. It then fixed itself overnight and is now reporting disk space correctly.
1 Like
This is consistent with the way the Web shell was āfixedā in CORE 13.3 and what happened with virtualisation in Fangtoothā¦
3 Likes
Itās Mark Nudelman style ā¦
less > more
Removing the SMART UI is madness. TrueNAS and ZFS are all about protecting the data. Making scheduled SMART tests easily accessible by being an inherent part of the product is essential to that. Donāt dump the feature and suggest that some 3rd party app developer will pick it up.
Whatās next? Dumping the scrub UI because itās too hard to maintain? Cloud sync?
How does the team arrive at these decisions? We get Incus that no one wanted asked for and now the SMART UI is taken away, also which no one asked for.
Whatās even more baffling is that Incus is not something that the paying customers would ever request because enterprise customers will have their own virtualisation infrastructure, yet it seems likely that the SMART UI is something they would rather retain.
The prime directive of software development is to deliver what the users ask for. That clearly is not being practiced. So whatās going on here?
4 Likes
Lots of people asked for it, mainly as a way to run LXCs. iX half-assed its implementation (ripping out the existing VM solution in the process), pissed everyone off, and has now ripped it back out, pissing off even more people.
2 Likes
Thatās an opinionā¦have you tested it?
It would be useful to see reports from users that use the new software.
TrueNAS as a business has managed and supported hundreds of thousands of drives so we didnāt make the decision lightly and do have significant experience with the old method and what worked and did not work.
1 Like
One bug Iāve experienced is the replication task page not loading due to the new Pydantic validation failing on tasks created on previous TN versions (NAS-137351).
A more critical issue Iāve discovered is that the ACL editor always sets the owner/group of files, even if the āApply owner/groupā boxes are not checked.
Unfortunately also reproduced on 25.04, though itās fine on 24.10. JIRA ticket for this is: NAS-137378. Likely commit causing the regression is mentioned in the comments there.
Now in the progress of looking how much more data has had its owner and group re-set, since any ACL change with 25.04 and later caused this. 
This could be worth mentioning as a known issue for both 25.04 and 25.10, as this might not be noticed at first.
But other than those two issues (and some minor reported frontend glitches: NAS-137369), the beta seems fine.
3 Likes
Oh, and the āRebuild Directory Services Cacheā button seems to be missing from the new AD UI. At least that can still be called from CLI.
Iāve also experienced more AD issues with randomly getting "Stored machine account secret is invalid. [ā¦] " errors every few hours or days. They usually resolve themselves 10 minutes later, but itās still an issue in TN.
During those errors (faulted AD state), users/groups cache are unexpectedly cleared. Some ongoing discussion for that in: Unclear error message - #4 by TheJulianJES. The users/groups being cleared did not happen in 25.04 IIRC.
JIRA issue for this: NAS-137379
2 Likes
Thanks for the deatiled testing and review.
Great catchesā¦ and yes this is very important.
Weāll get into known issues asap @ABain
Edit: Appears to be in 25.04 and 25.10
2 Likes
Can you confirm that this a a new issue in 25.10 and not lingering from 25.04??