No issue updating from 25.04.2.5.
I had a bug with RC with special character “&” in a cloud sync mount point that crippled all the cloud tasks. Issue revolved with this update. Thanks!
Blockquote
I cool my drives in dry ice, so -13C is my actual threshold…will the fix affect me? 
Looking forward to updating later today.
4 Likes
Same error. 
Any suggestions on what else I could try?
Upgraded from 25.04.2.5 now none of my users can access their windows home drive. Some of the other shares also seem to be playing up
Edit:
- i had to change the share type from Private Dataset Share to Default Share and now i can’t change it back to Private Dataset Share. When I select Save after changing the purpose, the Save button becomes greyed out and the options have not been saved i.e. if i close the window it says I have unsaved changes
in my autofs i originally had ://nas/${USER} and it mapped correctly the directory has root. this was very many many years (truenas) versions.
I have now had to change the mapping as ://nas/home/${USER}
Session Timeout is complete BS as well. My keeps timing out in less than 1 min. Ridiculous. I switch windows to write this comment, and it has already timed out.
1 Like
These are errors reported in SMART. sudo smartctl -x /dev/sdf to view detailed information. Keep in mind that restarts may change the sd-name assigned to the problematic drive.
That’s a list of ZFS errors, of which you have none currently.
Gotcha. Thanks. I will keep an eye on that drive which is a part of a mirror pool while I order a replacement.
any chance of a guide for what we need to do with certs now? my domain is with cloudflare and I am already using the acme DNS authenticator, do I need to change anything?
Nothing was changed, unless you were using TrueNAS as a certificate authority for some reason.
ah, excellent, thanks for clarifying.
should we change our SMB shares to use a profile before updating, or it doesn’t matter?
The upgrade from Fang was uneventful.
My 5060TI finally appears for GPU isolation.
Oracle Linux 10 won’t boot with the GPU added.
Error Name: EFAULT
Error Code: 14
Reason: [EFAULT] internal error: Non-endpoint PCI devices cannot be assigned to guests
Error Class: CallError
Trace: Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/middlewared/plugins/vm/supervisor/supervisor.py", line 191, in start
if self.domain.create() < 0:
^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/libvirt.py", line 1373, in create
raise libvirtError('virDomainCreate() failed')
libvirt.libvirtError: internal error: Non-endpoint PCI devices cannot be assigned to guests
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/middlewared/api/base/server/ws_handler/rpc.py", line 360, in process_method_call
result = await method.call(app, id_, params)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/middlewared/api/base/server/method.py", line 57, in call
result = await self.middleware.call_with_audit(self.name, self.serviceobj, methodobj, params, app,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/middlewared/main.py", line 954, in call_with_audit
result = await self._call(method, serviceobj, methodobj, params, app=app,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/middlewared/main.py", line 771, in _call
return await methodobj(*prepared_call.args)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/middlewared/api/base/decorator.py", line 108, in wrapped
result = await func(*args)
^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/middlewared/plugins/vm/vm_lifecycle.py", line 57, in start
await self.middleware.run_in_thread(self._start, vm['name'])
File "/usr/lib/python3/dist-packages/middlewared/main.py", line 668, in run_in_thread
return await self.run_in_executor(io_thread_pool_executor, method, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/middlewared/main.py", line 665, in run_in_executor
return await loop.run_in_executor(pool, functools.partial(method, *args, **kwargs))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/middlewared/plugins/vm/vm_supervisor.py", line 68, in _start
self.vms[vm_name].start(vm_data=self._vm_from_name(vm_name))
File "/usr/lib/python3/dist-packages/middlewared/plugins/vm/supervisor/supervisor.py", line 201, in start
raise CallError('\n'.join(errors))
middlewared.service_exception.CallError: [EFAULT] internal error: Non-endpoint PCI devices cannot be assigned to guests
It is fixed in 25.10.1 and should be in a Goldeye nightly.
The real issue is bad drive smart data with negative temperatures.
I tried restarting several times, but this error always appears.
First screen:
Second screen:
I tried removing the 25.10.0 boot environment from System → Boot, I tried updating again… same error.
I also tried manually applying the update, but no success.
Only the 25.10-RC.1 boot environment works.
1 Like
Just for reference… I’m not sure if this is related to the problem or not: https://forums.truenas.com/t/after-upgrading-from-24-10-2-to-25-04-rc-1-my-truenas-server-keeps-hanging-every-morning/36927/4
But since version 25.04-RC.1, I had to add this command as a startup script to prevent the server from randomly freezing: ethtool -K eno1 tso off gso off.
update went without a hitch!
Great timing! The SATA drives I have on order are due to be delivered tomorrow and I can get started installing TrueNAS and configuring my new NAS machine.
1 Like
I’m experiencing severe random reboot issues, which occur approximately every 2-3 hours. Due to these frequent reboots, OpenWrt in the VM crashes, and it might take days before I can upload the error logs.
Everything is working great! This is an outstanding release. Excellent features and stability. Amazing!
I was on RC1, when I did the update. On initial boot the vdevs were gone. I just had to reboot, and they all came back. Not big deal, but I just wanted to mention it. It seems obvious to reboot, but I did panic for a second.
I as able to repeat this by dropping back to the RC1 and upgrading again.
1 Like
Can you start a detailed thread in General… post the link here.
Unless others are seeing it, it may be something very specific to your system.
1 Like
Oooof!! I use Jailmaker. For reasons I won’t go into, I need to rebuild my NAS. On a TrueNAS Tech Talk it was said that 25.10 will replace Incus containers with libvirt-based ones, so I’ve suffered with my current build just waiting patiently for 25.10, so my backup software can use the promised new container setup from the get-go.
Now finally 25.10 lands and it’s like… “Fooled you! Have some more Incus “experimental” containers sucka!” This hurts, and I do feel cheated, but I should know better than to make decisions based on a YouTube video months out from software release date. My bad.
ZFS and containers is all I care about. Like the Metallica song… nothing else matters. Yes I know it’s not all about me… but there’s plenty of people using enterprise Linux backup software who too only care about ZFS management and containers from TrueNAS, so like the Sam Smith song… I know I’m not the only one.
I guess I’ll just rebuild now and not wait any longer (for all I know libvirt-based containers might miss 26.04 too… fool me once…). I’ll put Jailmaker back on since it’s working fine for my use case, and because Incus is deemed “experimental” and going away - I’d rather use the experimental tool I know works already. Without Jailmaker (take a bow Jailmaker), I’d have ditched TrueNAS for Proxmox (or even Ubuntu), a long time ago. But TrueNAS has WAY better disk handling, so if it can finally get good container management, then chef’s kiss
2 Likes