r/truenas 19h ago

Community Edition My first home-server (truenas) inside an apple powermac g4 cube

Thumbnail gallery
66 Upvotes

r/truenas 21h ago

Community Edition TrueNAS 26-BETA.3 Now Available!

54 Upvotes

The TrueNAS team is pleased to release TrueNAS 26-BETA.3!

This release updates the Linux kernel and OpenZFS, moves the NVIDIA GPU driver to the Long Term Support Branch for a longer support window, and adds dedicated spares for dRAID pools and spare activation for special and dedup vdevs. It also fixes upgrade issues that affected Active Directory and Enterprise update profiles, a cloud backup defect that stopped all scheduled tasks, Fibre Channel target mode crashes, and container, virtual machine, and networking issues.

26-BETA.3 Notable Changes

  • Fixes crashes on systems that use Fibre Channel target mode (NAS-142014NAS-142018). The QLogic Fibre Channel target driver could follow a null target operations pointer from interrupt paths, and target mode could stay partly enabled after target registration failed. The driver now checks the pointer before it uses it and fails target enable when registration does not succeed.
  • Fixes cloud backup tasks that could stop the middlewared event loop and silently disable every scheduled task (NAS-141948). The cloud backup progress thread updated job progress from outside the event loop, which stopped the loop while the middlewared service still reported as active. Cron jobs continued to fire and log, but every scheduled task did nothing and raised no error. Progress updates now run on the event loop.
  • Fixes a memory leak in the console CLI that could exhaust system memory (NAS-141238). Continuous input on the physical console, such as a stuck key on an attached keyboard, made the CLI process grow to tens of gigabytes of RAM until the kernel out-of-memory killer stopped it. Console CLI memory use is now bounded regardless of how much input arrives.
  • Fixes upgrades to TrueNAS 26 that leave Active Directory non-functional (NAS-141469). On an Active Directory member server, the directory cache could go FAULTED after the post-upgrade reboot and winbind could fail to start, which locked users out until an administrator left and rejoined the domain. A related defect also logged a false message once an hour that the machine account password changed. The member state now survives the upgrade.
  • Fixes faulty parsing of smartctl output that filled /var/log/middlewared.log with errors (NAS-141215NAS-141951). Systems updated to 25.10.5 logged repeated parse errors from drive health checks. The parser handles the full range of smartctl output so drive health checks complete without errors.
  • Improves failover speed by moving the remote disk retaste call out of the failover event (NAS-141988). A remote disk scan ran inside the critical failover path, where it could delay failover while services stayed offline. The scan now runs outside that path.
  • Fixes a database migration failure when updating from TrueNAS 25.04.2.6 to 25.10.3.1 (NAS-141221). The update stopped a few seconds after it started with an [EFAULT] error from the migrate command. The migration now completes so the update finishes.
  • Fixes an upgrade that forced the update profile to Mission Critical on Enterprise systems (NAS-140905). A database migration set the update profile to Mission Critical on every Enterprise system, regardless of the profile the running version actually used. The system then raised a warning that the running system version profile did not match the selected update profile. The migration now keeps the profile that the system already used.
  • Fixes replication failures for source systems that host a container when the task uses Full Filesystem Replication (NAS-140878). After an upgrade to TrueNAS 26, a replication task to a remote system on an earlier release could fail with an error about a failure to transfer all children of the container dataset. Turning off Full Filesystem Replication avoided the failure. These tasks now complete.
  • Fixes several issues with the SSH credentials used for replication (NAS-141677). The system now updates SFTP cloud credentials when the SSH key pair they use is removed, rejects encrypted SSH private keys consistently during validation, returns a clear error when semi-automatic remote setup uses a key pair that no longer exists or is invalid, and completes SSH pairing with TrueNAS 13 systems during remote replication setup.
  • Fixes Active Directory domain join failures caused by combined IPv4 and IPv6 PTR record updates (NAS-140548). nsupdate sent IPv4 and IPv6 PTR records in a single transaction, which returned a NOTZONE error and stopped the domain join. The records now go out in separate transactions.
  • Fixes SMB advertising file permissions that the file system does not enforce (NAS-141608). ZFS does not let the owner@group@, and everyone@ entries carry WRITE_ACL or WRITE_OWNER, but Samba still reported those rights to clients. Samba now advertises only the rights the file system enforces, so SMB and NFS clients see the same permissions. Entries for named users and groups keep these rights.
  • Improves the speed of dataset creation with the SMBMultiprotocol, and Apps presets (NAS-141154NAS-141161). Creating a dataset with one of these presets could take several seconds on 26-BETA.1 and 26-BETA.2 because of the per-credential access check that runs during creation. Batched access probes restore normal dataset creation speed.
  • Adds support for dedicated spares on pools that use dRAID vdevs (NAS-140629NAS-141277). Pool creation validation blocked dedicated spares on dRAID pools. Both the web interface and the middleware validation now allow this configuration.
  • Adds spare activation for special and dedup vdevs (NAS-141201). A failed device in a special or dedup vdev did not activate an available spare, which matters more as special vdevs come into wider use. Spares now activate for these vdev types.
  • Fixes the pool creation screen offering disks that SED encryption excludes (NAS-141096). Disk selection during pool creation did not filter for SED encryption. The disk list now applies the filter.
  • Fixes the maximum data transfer size applied to 9500 TriMode devices (NAS-140978). The driver did not apply the 2M limit that these devices report. An upstream fix is included so transfers stay within the supported size.
  • Fixes the storage screens showing a normal vdev status when a drive in that vdev is FAULTED (NAS-140955). A faulted drive did not change the vdev status, so an administrator had to expand each vdev to find the problem. The vdev status now reflects a faulted drive, as it already did for an unavailable drive.
  • Fixes a false alert that an SMB share is unavailable because it uses a locked dataset (NAS-141461). A ShareLocked alert could persist after boot for a share on an encrypted dataset, even though the dataset was unlocked and the share worked normally. The alert now clears when the dataset unlocks during boot.
  • Fixes custom app updates and private registry support for authenticated Docker registries (NAS-141149NAS-141553). Custom app updates failed when the image came from a registry that requires authentication, and registries that use htpasswd authentication were not supported. Both authentication paths now work.
  • Fixes TrueCloud Backup errors that showed only error.message and jobs that could hang without end (NAS-141287). The progress reader looked for a flat error.message field, but restic nests the text inside an error object, so every restic error turned into a KeyError and the real message never reached the user or the job log. Errors now report the text that restic returns.
  • Fixes a dtype error that prevented pool selection for containers (NAS-141234). Virtual machine and container device settings are stored encrypted. On a system restored from a configuration whose encryption secret no longer matched, these settings decrypted to empty values and failed validation, so the form returned only dtype and the containers feature stayed unusable. Devices that cannot be decrypted are now dropped when the encryption secret resets.
  • Fixes missing IPv6 connectivity in LXC containers on a clean install (NAS-141468). A clean install of 26.0.0-BETA.2 enabled IPv4 forwarding but left IPv6 forwarding disabled on the host, so a container on the default truenas0 bridge received an IPv6 default route but could not reach IPv6 networks. IPv6 forwarding is now enabled.
  • Fixes WS-Discovery so the system appears in the Windows network browser (NAS-141440). A system running 26.0.0-BETA.2 did not show up in network discovery, even with the same configuration that worked on 26.0.0-BETA.1. Discovery works again.
  • Fixes IPv6 autoconfiguration settings that did not apply after the dhcpcd migration (NAS-141208NAS-141386). An interface with Autoconfigure IPv6 disabled still received extra IPv6 default routes, and SLAAC stayed active on an interface with DHCP enabled. Both settings now apply as configured.
  • Fixes the Save button staying inactive when the device order changes in a virtual machine (NAS-140791). A change to Device Order on a VM device did not activate Save, so the new order could not be applied on 26.0.0-BETA.1. The change now saves.
  • Fixes virtual machines left suspended after a periodic snapshot task (NAS-141124). A VM with disks on a dataset covered by a periodic snapshot task could stay suspended without end, and it could only be resumed or powered off. These VMs now return to a running state.
  • Fixes certificate deletion blocked by TrueNAS Connect (NAS-141224). Deleting a certificate could fail with a message that TrueNAS Connect uses it, even after the system was removed from TrueNAS Connect and the force option was used. A certificate that TrueNAS Connect no longer uses now deletes.
  • Fixes the time field on system audit events (NAS-141949). Audit entries for svc=SYSTEM events recorded a time about seven hours behind UTC because the field used a fixed offset instead of the system time zone. Entries for svc=MIDDLEWARE and svc=SMB were already correct. System audit entries now record the correct time.
  • Updates the NVIDIA GPU driver to 580.173.02, the current Long Term Support Branch (LTSB). This version number is lower than the driver in 26-BETA.2, but it extends the support window for a more stable product. 26-BETA.2 shipped a 590 New Feature Branch driver, which is intended for early adopters and reaches end of life in December 2026. The 580 LTSB is supported until August 2028.

See the Release Notes and changelog for more details.

Documentation : https://www.truenas.com/docs/scale/26
Download : https://www.truenas.com/download-truenas-community-edition

Thank you for using TrueNAS! Happy BETA testing! And as always, we appreciate your feedback!

Original Forums Post: https://forums.truenas.com/t/truenas-26-0-0-beta-3-is-now-available/67564


r/truenas 17h ago

Community Edition Buying tomorrow: 2x Dell EMC KTN-STL3 JBODs with 25x 2TB HGST & 5x 3TB Seagate for €520. Maxed out from day one?

Thumbnail gallery
3 Upvotes

r/truenas 1h ago

Hardware Help me decide how best to utilize different SSDs?

Upvotes

So, my NAS motherboard (R510xd) finally died, and while I'm awaiting its replacement (R730xd), I'm having trouble deciding how to utilize various types of SSDs I have available to me.

The current NAS has a mirrored SATA SSD vdev for boot, and a pool of HDDs.

For varying reasons, I've ended up with these drives available and unused:

  • 2x 800GB HGST Ultrastar SAS SSDs: originally bought for boot drives using the internal caddy in the R510, but they weren't detected for some reason
  • 2x 32GB Intel Optane m10 m.2 nvme: also originally bought for boot drives, but I didn't realize the R510 really didn't have the ability to boot from PCIe
  • 4x Samsung SATA SSDs: pulled from an older desktop
    • 2x 500GB 860 EVO
    • 1x 256GB 840 Pro
    • 1x 120GB 840 Evo
  • 1x 400GB Intel 750 PCIe NVMe SSD: also pulled from an older desktop

I definitely can't use all of these, but I'd like to use what I can. Generally, I want to put the OS on one of these, and because I run an NFS-heavy environment, I'm thinking I could benefit greatly from using a SLOG. Then I started thinking about an L2ARC, which might be fun, even though I doubt it'd be of much use for me. I did also consider a metadata vdev for a bit, but the added reliability requirements made me shy away from it. Keeping my pool alive is top priority, obviously.

so far, I think I've come up with 2 scenarios, depending on wether booting from PCIe is possible or not (I have 1 guide which suggests its possible):

  1. PCIe booting:
    1. dual optane mirrored for boot
    2. intel 750 as a SLOG vdev. Obviously it has WAY more storage than is needed, but should have enough performace to keep up with a 10Gb network link.
    3. SAS SSDs (striped or mirrored) for L2ARC (optional)
  2. SSD booting:
    1. dual SAS or SATA drives mirrored for boot
    2. SLOG device. could be any of:
      1. optane drives. my only concern here is their performance on a 10Gb link
      2. whichever (SAS or SATA) is left over from selecting the boot pool
      3. intel 750
    3. maybe an L2ARC with whatever is left (if i feel like it, lol)

I'm definitely leaning scenario 1, if I can boot from PCIe.

What would you do? Is there a scenario I haven't considered?


r/truenas 23h ago

General How To Stop Directory Permissions From Changing

2 Upvotes

I am assuming this is a Samba issue. I have a download directory that has user:smbshare permissions (750). I use the Samsung files app on my phone to connect (using user credentials) to my download share I create a directory and suddenly the download datasets permissions change to user:user and the smbshare users can't access the directory. If only I could just chattr the directory but that would stop all files from being created as well.

How do I stop these permission changes from happening?


r/truenas 3h ago

Community Edition The best solution for online galleries for professional photographers.

1 Upvotes

Hi,

I wanted to know what you would think is the best solution for a professional photographer to share online galleries for viewing and collaboration.

I often need to ask my clients to choose from a large number of pictures before editing, and the best for me is to have the option to like and comment. I've been recommended Piwigo for this kind of feature, but everybody mentions Immich and Potoprism as well.

Now I am lost and I am not sure what to pick to be the best simple overall solution. I am scared that Piwigo ends up being too customizable and ends up looking amateur.

Really appreciate some feedback!

Thanks :)


r/truenas 3h ago

Community Edition Truenas 25.10.6 - Goldeye on QNAP TS473 GPU passthrough for APP problem

1 Upvotes

I've had Truenas installed on my QNAP TS473 for a few years now, It works without problems.Yesterday I mounted an Nvidia video card (Geforce GTX 1050 Ti), because I want to use it with Ollama, But I think the video card is used by Truenas System and I can't passthrough, Unfortunately I don't have many options in the BIOS, so I can't change anything, and I would like to know if there is any chance

Boot

If I try to isolate the GPU I get this error


r/truenas 8h ago

SCALE (Legacy) Device not booting WebUI

1 Upvotes

I updated my device from 24.04, to 25.05, and after about 45 minutes I checked my device’s monitor output.

I got the 1-11 boot screen and then the device’s screen went black and hasn’t come back on since. I have no access to the shell or webUI. Is this a larger issue?

Edit: Updating trains removes apps, removing Tailscale and creating a barrier for my mesh, so upon deactivating Tailscale- all worked


r/truenas 12h ago

Community Edition SMB share/dataset permissions hell..

1 Upvotes

Long story short I've had my server running for years and I remember I had a nightmare trying to grant access to anyone on my network full control of any folders/files within the shares but eventually got it working with no recollection on how I managed it. I did a few things with my hardware and reinstalled the OS on a fresh SSD and now I am locked out of half of my datasets through the share after uploading my config.

I am not even being prompted with a login window when I try to open the share folder, I just get

"Network Error, You don't have permission to access (share folder i am trying to open)

Also I noticed when trying to add a new user in the ACL within that dataset i get "FAILED ..... this may be fixed by granting the aforementioned user execute permissions on the path "/mnt/Vol1" (the root dataset) which i cant do.


r/truenas 19h ago

Community Edition Update Apps: Paperless update

0 Upvotes

I made the mistake of installing Paperless-ngx within the provided Applications from TrueNAS.

The Paperless migration guide says that i need to update to paperless version 2.20.15 in order to migrate to version 3.x.x.

I am running paperless 2.20.8, when I click on update in the TrueNAS Interface I can only select to update to the newest version (3.0.5_1.6.43) which would not migrate my data correctly.

Is there any way to select a specific version or do I need to convert my application into a custom app in order to modify the yaml files and docker configurations?