TrueNAS 25.10.0 is Now Available!

Hi,

Just upgraded Truenas from 25.04.2.4 to 25.10.0.

The problem described below occurs also on a fresh 25.10.0 installation.

Setup: Truenas is running as VM in Proxmox, /dev/sda is the boot drive, storage device defined in Proxmox.

Problem: in /var/log/netdata/error.log some Python scripts are logging multiple errors/second.

File “/usr/lib/python3/dist-packages/middlewared/utils/disks_/disk_io.py”, line 86, in read_gpt
dev_fd = os.open(devobj, os.O_RDONLY)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
PermissionError: [Errno 13] Permission denied: ‘/dev/sda’
Unexpected error reading partitions for device: ‘/dev/sda’
Traceback (most recent call last):
File “/usr/lib/python3/dist-packages/middlewared/utils/disks_/disk_class.py”, line 397, in partitions
return read_gpt(dev_fd or self.devpath, self.lbs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Partial output of lsblk:

root@tnas[/home/truenas_admin]# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 64G 0 disk
├─sda1 8:1 0 1M 0 part
├─sda2 8:2 0 512M 0 part
└─sda3 8:3 0 63.5G 0 part
sdb 8:16 0 1.7T 0 disk
└─sdb1 8:17 0 1.7T 0 part
sdc 8:32 0 1.7T 0 disk
└─sdc1 8:33 0 1.7T 0 part
sdd 8:48 0 1.7T 0 disk
└─sdd1 8:49 0 1.7T 0 part

File /var/log/netdata/error.log size reached already 19MB in less than 24h.

root@tnas[/home/truenas_admin]# ls -l /var/log/netdata
total 642
-rw-r–r-- 1 netdata netdata 0 Nov 3 23:11 debug.log
-rw-r–r-- 1 netdata netdata 19497609 Nov 4 16:30 error.log
-rw-r–r-- 1 netdata netdata 0 Nov 3 23:11 health.log
root@tnas[/home/truenas_admin]#

In Reporting, Disks I am not able to see any stats for boot drive /dev/sda. Stats are available for all the other drives.

Any idea on how I can limit this logging or fix the issue?

Thank you, Sorin

This type of detailed user issue belongs in the General TrueNAS channel.

You can provide a link from here to there.

Info comparing 25.04.2 would be useful. Perhaps we can see if anyone else has the issue…

Thanks for the 20,000 systems that have updated to Goldeye in its 1st week..

This effort and any bug reports are critical to software quality. We expect 25.10.1 to be available in December before everyone takes a needed holiday.

3 Likes

Bummer, a SMB fix would have been nice before then,

1 Like

Posted a dedicated message in Truenas General, name “Truenas 25.10.0: multiple repeated error messages in /var/log/netdata/error.log”. Due to the forum rules and my current limitations I can’t include the link, please added if you can.

For me, the only system completely unaffected by the SMB bug is the one reverted to 25.04.2.5.

Even with the smb3 directory leases = Yes mitigation suggested on another thread, the ones on 25.10 are a bit flaky.

2 Likes

No issues on 25.10.0 release TrueNAS-SCALE-25.10.0-MASTER-20251002-234253. SMB works, all is well. Container VM’s require manual start and works. Reverted from 25.10.1 since Windows 10/11 workstations would not display folder structures of SMB shares unless refreshed.

System:

AMD EPYC 7401P 24-Core Processor, 256 GB ECC RAM, 10GbE, 40GbE, 6x14tb hdd, nvme boot drive.

But you’re not on the 25.10.0 release.
You’re on the nightly, i.e. experimental build.

Was that intentional?
25.10.1 is also a nightly version atm.

1 Like

You’re referring to 25RC1? Yeah, I’ll give the nightlys a run and stay with them if they seem stable enough each month.

Not sure what you are asking here. You were the one who brought up 25.10.1, which is still in development.

No one has mentioned 25RC1 except you.

If you are aware you run the experimental nightly branch I have nothing more to add.

2 Likes

Hello,
I’ve read here and there that there might be some issues with SMB on version 25.0.0.
Personally, I’m having a problem with the properties of SMB shares in Windows 11 File Manager:

Otherwise, I haven’t found any other SMB problems. Everything seems to be working correctly. Are you experiencing any issues with SMB sharing?

A painful yes.

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

2 Likes

I have downgraded to 25.4 because he can’t sleep, wakes up frequently, and there are still many problems. I will never use 25.10 forever. Maybe I will consider 26. It depends on the situation.

3 Likes

An update on TrueNAS 25.10 (Goldeye) status.

First, uptake has been very good. 25.10.0 is #3 of most popular versions.

Fangtooth (25.04) is still the dominant version and the one recommended for General use. The adoption of Community Edition has been very strong.

This week (Nov 18-21), there is a 25.10.0.1 hotfix release planned. It resolves about 10 of the more critical Goldeye bugs: SMB, Apps and general. It includes NAS-138259.

The Goldeye 25.10.1 update is still scheduled in December before Xmas. It will have the normal hundred improvements, some related to our Enterprise rollout, and be a major step toward “General” use quality. I expect the nightly version to be available at the end of November.

Many thanks for all the bug reports. With over 30,000 systems using 25.10 we have enough test coverage to get Goldeye to the same quality as Fangtooth in Q1 2026.

7 Likes

Hmm, but NAS-138529 was closed without change, wasn’t it ? :wink: Ahh i see you mean 138259 np :slight_smile:

grafik

2 Likes

What will be the best practice when this is finally released? Should we revert the

midclt call smb.update ‘{“smb_options”: “smb3 directory leases = Yes”}’

workaround we’ve been using to mitigate the issue? If so, before or after the upgrade?

It’s probably a good idea to switch back to defaults. If you do this, then your configuration will be automatically updated as we grow confidence in new feature / performance characteristics.

1 Like

I understand your perspective. From my viewpoint, once the option becomes available, I’m going to switch my profile to “General (default)” on my “production” machine, and them probably set up a mimi PC for testing purposes. I just have to ensure that the miniPC has two NVMe slots.

Because you like bugs.

1 Like

What an odd thing to say.

I understood @MarkHoltz’s plan to set it to General instead of Early Adopter specifically in order to avoid the most untested (and thus buggy) releases.

1 Like