Okay, I’ll try and extract a debug file, if that should fail for some reason I’ll get that log at least.
Right. These sorts of issues can often be hard to detect through CI / CD. Details of individual user configurations / hardware often contribute heavily to bugs, and so it’s hard to make a fix without something to work with (unless other people hit the same issue and upload debugs).
1 Like
Completely understandable. Debug file generated and uploaded.
By the way: the error I described in Ticket 135701 and, after getting redirected here, in TrueNAS console uses wrong VGA still persists. I cannot use my BMC for remote control because of this and I don’t think my configuration is very unusual - if you could maybe repoen that ticket it would be great.
You were redirected because trueNAS doesn’t control this behaviour.
My guess is its BIOS and PCie settings. But its worth another forum post on the specific issue… does anyone else have (and resolved) a similar issue.
I’m pretty sure if my board had a nicer BIOS i could specify some kind of default behaviour but the OS could override it.
That’s exactly what the user in the Reddit post you linked did - he changed the NVIDIA X server settings.
Same thing on any normal PC - you can choose which monitor(s) attached to which GPU(s) you want to use.
I don’t know how far this comparison goes as we don’t have a GUI on TrueNAS but I am sure the OS could override the BIOS’s default output.
I am also facing the same issue, thinkning to go back to EE
Perhaps its possible, but its not a current capability or one that has been advertized.
So, it would be a feature request… not a bug report. If hundreds of people wanted the new feature and there was a known solution, it would then get traction.
Thanks for the report.
For benefit of others. The issue is due a reporting bug which over-reports CPU utilization. There is no TrueNAS performance issue, just a reporting issue in all 25.04 versions.
https://ixsystems.atlassian.net/browse/NAS-135633
It will get addressed in a later version when that part of reporting gets an overhaul. For some reason, its not an easy fix.
2 Likes
Is the OPs unexpectedly slow VM (and htop) related so a different issue then?
No idea… do we have NAS-tickets for them?
That is definitely not the same issue.
My NAS didn’t just report usage. It was barely usable as described above - especially the VM but, as I wrote, that was only a symptom, not the cause.
Please reopen my original bug ticket.
It also wasn’t just these two. Boot times and overall web UI snappiness were both very bad.
Sorry to hear… I jumped then gun.
Can you collect the metrics like boot time … post them here.
I’ll try to get the jira ticket re-opened.
If not it will be a new ticket.
That is an entirely different issue then. And its always been this way on any 25.04 version? Could be with the newer LTS kernel we shipped then still. Are you willing to smell-test a nightly of 25.10 to see if the updated kernel there helps any?
I calculated boot times from syslog (from the first “Linux version 6.x…” to “Reached target truenas.target”).
24.10.2.3 (with my init tasks that might slow things down a bit): 1min23s
24.05.2 (without any customizations): 5min16s.
Which over metrics do you need?
I am, if I can just boot back to 24.10 without anything broken/migrated by the nightly 
If i have to reinstall and restore a config from before the update that’s fine too.
The only thing that would be a no-go would be something that changes my application data or VM zvol or something like that.
Yes, you can update and then roll back. Just need the datapoint to confirm if the kernel is the thing in play here, or if something else is going on…
Okay, can I just use any current 25.10 nightly?
Go ahead and grab the latest: