Important Notice: In fixing the one SMB issue, we may have exposed another. If you are a heavy SMB user please do not update until we’ve had time to diagnose. We are investigating and expect to have a resolution in the near future. Thanks!
We are pleased to release TrueNAS SCALE 24.10.0.1 and 24.04.2.4!
These releases address a small number of issues discovered in the 24.10.0 and 24.04.2.3 releases.
Notable Changes in 24.10.0.1:
Fix memory consumption related to SMB AIO reads (NAS-132166).
Just to restate from my “pre-heating” thread, while we had expected and planned for 24.04.2.3 to be the final Dragonfish release, the fixes here are being published for both branches to ensure the stability of our Conservative and Mission Critical SCALE users.
Electric Eel has had an incredible uptake speed with over 25,000 installs in just under ten days - new TrueNAS users should start with 24.10 to take advantage of the general system improvements. Existing Dragonfish users with a need for the improved feature set of RAIDZ expansion, Docker-backed Apps, and other improvements should consider moving to 24.10 after reviewing the upgrade notes to understand the Kubernetes to Docker migration and ensure a smooth upgrade.
just tried installing the update and on reboot im getting a kernel panic error? its strange…might just rollback for now but i also did notice i had a boot-pool error saying it was degraded, dont know how or why, but was hoping it was just a bug as all my drives have run well and never any errors on tests before…
but hopefully its not an issue with the update?
edit: the first error shows as a checksum verification error just for added info…yeah and 24.10.0.0 load perfectly fine for me
I updated this morning and while the update was successful, every time I tried to write data, it would randomly cause the system to panic and reboot. I had to revert back to 24.10.0 to stop it from rebooting during writes.
Can’t see anything in the update that would seem to be related to that issue, it was a relatively small amount of changes. A bug ticket, debug and further details on the type of workload would be super helpful.
While the update was successful, there may be something wrong with SMB with the update from 24.04.2.3 → 24.04.2.4. Linux can see the shares in the file manager and work with them, but the shares have disappeared from the file managers network section from all windows 10 and windows 11 computers. Mapping a drive works and they are accessible from there
I don’t see anything obvious and no obvious errors. Ping by ip or by name works fine as does ssh.
Similiar issue here too after updating. When there are smb reads it goes in kernel panic and restarts. Tried couple times and it happened almost constantly.
System supermicro x12 STL
Cpu intel xeon E 2314
64gb ecc
2 pools
Pool 1 ----2 ssd’s in mirror Samsung 990pro 1 tb
Pool 2 — 2 vedvs 6x16tb z2 wd ultrastar ---- and 4x4 tb z2 hgst nas drives
Didn’t realize this update had some out today, finally went to update from 24.04 to 24.04.2.3 and had all sorts of problems with SMB/CIFS shares, rolled back to 24.04 and all is working again. Started to search and saw this release today, and checked the boot environment and sure enough, it had updated to 24.04.2.4. SMB reads and writes were failing, TrueNAS would panic and reboot.
Updated from 24.04.2.3 to 24.04.2.4.
Luckily no kernel panic or network error with SMB transfer here, but catastrophic transfer performance (maximum transfer of around 1MB/sec with drops to a few bytes/s).
Rollback solved the problem. There is clearly a problem around SMB.
If TrueNAS didn’t panic and reboot anything utilizing the SMB/CIFS share would essentially lock. I only use TrueNAS to host an SMB share with all of my media on it, everything else I use a separate machine for. Plex would start to play an item and within 10 seconds it would just sit buffering because it couldn’t read anymore. SabNZBd would start a download and then lock up and become unresponsive and I would be forced to reboot the host running the Sab container. If it did manage to remain responsive the downloads would fail as “corrupt”.
I have fix candidate for 24.10.0.1 SMB reboot issue, but need someone who can reliably reproduce it. If you can reproduce and are willing to test the fix, please send me a private message and I’ll provide files and instructions on how to install.
Can I just say that the release notes link from the webapi is not helpful. It points to a long document for 24.10 with no indication about what changed in 24.10.0.1.
I updated from ElectricEel-24.10.0 to ElectricEel-24.10.1 and after reboot, all my Dockers apps were not shown.
There was a notification that nvidia.github.io was not reachable or something, I didn’t bother to investigate much, I just used the ElectricEel-24.10.0 boot and restarted. So now I’m back on ElectricEel-24.10.0.
Sorry that I didn’t gather much info while having issues, but I didn’t have time to have my stuff offline.
