I'm running into an issue where my boot drive with TrueNAS installed won't be recognized without CSM enabled. This is a little bit of an issue for me because my ASUS motherboard doesn't allow you to enable CSM if you're using the iGPU. I downloaded the TrueNAS Scale 25.10.3.1 iso, flashed it to a USB using balena, and then went to install it on my system. The USB wasn't recognized without CSM enabled so I threw in a GPU real quick and started the installation. I installed TrueNAS to an NVME SSD and made sure to hit yes when it asks about EFI support. After the installation I rebooted and removed the installation media and the GPU because I thought I wouldn't need it anymore but for some reason I was wrong. Without the GPU CSM automatically disables itself and then the drive isn't recognized as having an OS on it. The drive shows up in BIOS as a storage option but not in the boot options menu. Does anyone know if I did something wrong during installation or if there's a workaround for this or do I just need to have a GPU installed? The GPU I used during installation is one that I borrowed from another system so I can't just leave it in and I don't want to have to buy another one. Any help is appreciated. Thanks in advance!

Edit: Looks like when I used Balena it wrote the ISO in MBR and that's why it wasn't being recognized without CSM enabled. Used Rufus and specified GPT/UEFI mode and it's working fine now!

Absolute noob here. Pretty much the title. I managed to turn my old PC into a Truenas server and have created a pool from new WD Red Plus disks. I have an old WD Blue drive from my old PC with all my files on it and I want to get those files into the pool I've made.

I have seen people suggest importing or mounting the WD Blue drive, however, in Truenas OS version 25.10.3 I cannot find options to mount or import the drive anywhere in the Truenas interface. In the Storage tab I can select 'Import Pool', 'Disks', or 'Create Pool'. From my limited knowledge, Import Pool and Create Pool are not what I am looking for as the files on the drive are not in a pool yet, and creating one on that drive would wipe it. When I click on 'Disks' I can select my WD Blue HDD but the only options are 'Wipe' and 'Edit'. Edit presents me with no options to mount or import the disk.

Once I get past this step I have gathered I should use Rsync. How? Any help is greatly appreciated.

(Also, I was notified I should use 'flair' to denote the OS version of Truenas but I am also a huge reddit noob and do not know how to add flair. Hopefully posting the OS version in the title and body of the post is sufficient.)

Anyone else having issues with Filebrowser after the last update?

I run App Version v2.61.1 - Version: 1.4.5

Truenas has an update available App Version: v2.63.4 - Version 1.4.16

But after the update, the login interface will not show and is stuck on the in initialize screen. Anyone else having this issue?

I'm considering building a TrueNas or a similar system on older windows server hardware.

I've read a lot about data recovery from failed drives, but I can't find anything about taking healthy drives from a failed system/ motherboard or whatever and pluging those drives into another system to get the data back.
I've read that ZFS is/can be used as an open standard so I would guess another system could see the data?

I've had a consumer NAS hardware fail before. At that time I didn't understand the drive file format details and couldn't get the drives to mount on another system.

What can I expect with ZFS?

so i got my hands on old RN42800, 8 bay NAS, i want to install truenas on there, it seems fine but i wanted to ask about the m.2 can i just plot disk there and is ti 2242 or 2260? and boot usb connect via serial console and just install truenas? or how does it work? is it possible ?

is it worth upgrading ram too? for zfs cache ? , did somebody try this ?

I just installed TrueNas 25.10.3.1 on a minisforum ms-01. I'm getting expired session messages after very short durations, as little as 45 seconds; Barely enough time to click around and explore dashboard options. I ran the gauntlet and was able to set a static IP address, but I usually get my admin session terminated before I'm able to configure anything at all. Using latest Chrome. Help?

So can someone please answer me like the "moron" that I am.

When I first set up truenas several years ago I had 6 4tb drives that I set up as 1 pool. My storage is now filling up and it's time to expand my storage.

I have backed up everything externally so I am willing to start over from scratch if it's better.

I have 8x 4tb drives and 2x 8tb to use for my storage pool.

I would like for these to all be one drive when I look at it via my network share.

Tha ks in advance

Hi, I’m trying to deploy Traefik via Docker Compose on TrueNAS SCALE, but I’ve hit the usual problem: TrueNAS reserves ports 80 and 443 for its built‑in nginx, so Traefik cannot bind to them.

I’ve spent hours reading threads about alias IPs, port redirection, and nginx overrides, but I still can’t find a clean, supported solution.

My requirements:

I do not want to modify TrueNAS’s nginx config.

I do not want to create custom nginx reverse‑proxy rules.

I want Traefik reachable from my LAN (192.168.x.x).

I also want Traefik reachable from Tailscale (MagicDNS + HTTPS).

I’m unsure whether the alias IP method on the TrueNAS NIC is the correct or safe approach.

I’m deploying Traefik via custom docker‑compose, not Apps.

I use about 15 custom apps including some that needs TLS and tailscale and traffic (immich, vaulwarden...).

My questions:

Is adding a second alias IP to the TrueNAS NIC the correct way to let Traefik bind to 80/443 without conflicting with TrueNAS nginx?

If yes, should Traefik bind to only the alias IP, or both alias + Tailscale IP?

What are the implications of using an alias on overall deployment of security?

Also that alias is a lan ip, should I use a dhcp ip reservation in my lan routeur?

Is there a better method to expose Traefik on LAN + Tailscale without touching TrueNAS nginx?

What about the "network" tag in the docker compose file?

I have excluded tailscale from my dynamic.yaml traefik config, was I right?

How do others run Traefik on TrueNAS SCALE cleanly without hacks?

Any guidance from people who solved this would help a lot...

Community Edition

I’m relatively new to the TrueNas and NAS world in general - so I’m looking for a community sanity check and/or wisdom. The basic question - I’m not sure if I need to be worried about my drive temps, or if they’re honestly just acceptable and will not decrease the lifespan of my drives much.

The setup - Silverstone CS382 case (drives are pretty tight and stacked, only 3 fans - two small Noctura at the back of the drive cage and one at the back of the case for exhaust. All fans running at 100% speed 24/7)

8 12TB drives in RAIDz2. 4 are IronWolf Pro, 4 are WD Red Pro

Normal operating temps for the drives are between 33-41 degrees. Most wind up in high 30’s but two sit at 40 or 41 and one usually is much cooler around 33. These temps stay pretty stable and are the best I’ve been able to achieve given the thermals of the case. I’ve made peace with this.

My concern - the scrub. Last nights scrub (came back fine) ran for 5 hr 40 minutes and it was a pretty huge increase. One drive hit 50 and one hit 51 the others stayed in the high 40’s - 46, 47, 48, etc.

For a monthly scrub setup - would you file this under acceptable and fine enough (even if not truly ideal), or does this mean I’ve got a bigger problem that really isn’t easy to solve given the case is already cooling as much as it can.

So - chill out or be legit concerned?

Hey everyone,

I wanted to share a major breakthrough I just had after months of hair-pulling, troubleshooting, and testing. If you are running TrueNAS SCALE on lower-power Intel Alder Lake-N95 (or N100) processors—specifically pre-built setups like the Terramaster F4-424—and experiencing random hourly/daily hard freezes or overnight lock-ups, this is highly likely your issue and your fix.

The Setup:

• NAS: Terramaster F4-424
• CPU: Intel N95 (4 Cores)
• OS: TrueNAS SCALE (v25.04.2.6)
• RAM: 16GB (Single stick—waiting out the current RAM pricing insanity before buying a second!)
• Storage: 2x NVMe drives (Boot + App-Data), 4x HDDs (Data Pool)

The Symptom:

The server would completely freeze up. Not just a web UI drop—total networking dead, SSH completely unresponsive, and a frozen screen if a monitor was plugged into it directly. There were absolutely zero error logs, core dumps, or kernel panics written to journalctl because the host processor was stalling silently, usually during low-utilization windows or overnight when the system sat completely idle.

The Problem:

The Intel N95 has a known hardware/firmware interaction bug on modern Linux kernels when transitioning into deep power-saving idle sleep states (specifically C6/C8/C10). When the CPU tries to drop its power consumption down or wake back up from these deep states, the internal voltage drops past a stable threshold, instantly locking the processor state machine.

A common workaround online suggests forcing the CPU scaling governor to Performance, but this forces the CPU clock cycles to stay pinned higher than necessary, wasting power and causing unnecessary heat when the NAS is sitting idle.

The Real Fix (C-State Limiting):

The true, precise engineering fix is to leave your system scaling governor on its optimized powersave profile, but explicitly tell the Linux kernel to limit how deep the CPU can sleep. Capping the idle states to C1E preserves perfect system stability while still allowing the CPU to scale its active clock frequencies all the way down during zero-load periods.

Because TrueNAS SCALE is an appliance, manual edits to /etc/default/grub can be wiped during standard system updates. The correct and safe way to apply this parameter permanently is using TrueNAS's built-in middlewared configuration utility via the shell.

How to apply it:

1. SSH into your TrueNAS box (or open the Web Shell) as admin and elevate to root (sudo -i).
2. Run this command to natively append the parameter to the TrueNAS kernel options database: Bashmidclt call system.advanced.update '{"kernel_extra_options": "intel_idle.max_cstate=1"}'
3. Regenerate your active GRUB boot configuration with the newly embedded setting: Bash/usr/local/bin/truenas-grub.py
4. Reboot your NAS.

How to verify it's working:

Once the system comes back up, you can run this loop in the shell to check your core idle stats:

Bash

for dir in /sys/devices/system/cpu/cpu0/cpuidle/state*/; do echo -n "$(basename $dir): $(cat ${dir}name) -> Usage: "; cat ${dir}usage; done

You should notice that your usage counts are concentrated entirely in state0 (POLL) and state1 (C1E), and the deeper, unstable states (state2/C6, etc.) will completely vanish from the loop.

Meanwhile, if you check your scaling governor, it will still report a safe and efficient powersave.

Since switching to this specific C-state limit, my server uptime has been absolutely pristine, and the overnight crashes have completely vanished without sacrificing the power efficiency of the Terramaster hardware. Hopefully, this saves someone else months of debugging! Let me know if you’ve run into this on your low-power boxes.

Good morning,

we have a full nvme storage on our truenas core. The system has 256 GB of Memory (RAM). The ARC hits are very low (80%) but the zfs Cache only uses 25 GiB and there are still 195 GiB free Ram.

Yesterday i set the sysctl vfs.zfs.arc_max and sysctl vfs.zfs.arc_min to 200 GiB and 150 GiB. Over the night the zfs Cache only took 5 GiB and not more. Now its stuck again and the hit rate is at 85%. The NVME Storage is used as a VM datastore.

Is FreeBSD limiting something?

Thank you.

SOLUTION: The solution came from @Aggravating_Work_848 - the primary cache was set to metadata only. Now after i changed it to ALL the ZFS Cache fills up quiet fast and the ARC hit rate is at 96-99% :)

Issue - After every reboot, docker ps is empty. Running systemctl restart docker immediately brings everything back.

Stuff I tried -- Changing boot order of services, waiting.. Nothing seem to work.

I have no idea whats supposed to be the right way... I have now disabled apps entirerly, and modifyed the docker systemd to pass everything via command args itself.

Whats the workaround I have now

Workaround (what I'm running now):

Put all Docker config in systemd override (since TrueNAS wipes daemon.json):

/etc/systemd/system/docker.service.d/override.conf: 
[Unit] 
StartLimitBurst=1  
StartLimitIntervalSec=910
After=ix-netif.service network-online.target local-fs.target ix-zfs.service 
Wants=network-online.target 
Requires=ix-netif.service

[Service] 
ExecStart=
ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock  
--data-root=/mnt/ssd_mirror/docker_apps --exec-opt native.cgroupdriver=cgroupfs --iptables=true --ipv6=true  
--fixed-cidr-v6=fdd0::/64 --default-address-pool base=172.17.0.0/12,size=24 --default-address-pool  
base=fdd0::/48,size=64
ExecStartPost=/bin/sh -c "iptables -P FORWARD ACCEPT && ip6tables -P FORWARD ACCEPT" 
Restart=always
RestartSec=10
TimeoutStartSec=900
TimeoutStartFailureMode=terminate 

I've been running TrueNAS SCALE virtualized on Proxmox with 4x Seagate IronWolf 4TB (ST4000VN006-3CW104) in a RAIDZ1 pool. I was passing through the motherboard's SATA controller as a PCI device to the TrueNAS VM. Recently Scrutiny flagged all three drives with SMART failures and I went down a rabbit hole trying to figure out what was actually wrong.

My setup:

• Proxmox 9.1.9, single node
• TrueNAS SCALE virtualized
• 4x Seagate IronWolf 4TB in RAIDZ1
• Motherboard SATA controller passed through as PCI device to TrueNAS VM

What Scrutiny reported on all 3 drives:

• SMART attribute 188 (Command Timeout) — FAILED
• Attribute 199 (UltraDMA CRC Error Count) — WARN on one drive
• Attribute 183 (Runtime_Bad_Block) — extremely high on one drive (8,653)

The worst drive (WW66E7T3):

• Command Timeout raw value: 17,180,262,774
• Runtime_Bad_Block: 8,653
• Power Cycle Count: 849 (other drives were at ~153-154)
• UltraDMA CRC: 12

The insane power cycle count compared to the others (bought all at the same time, same usage period) was the first red flag — the drive was clearly losing and re-establishing connection constantly.

What I tried:

1. Realized motherboard SATA controller passthrough is fundamentally problematic — it's not a discrete PCIe device, causes shared interrupt/DMA issues with the host, leading to command timeouts across all drives. Switched to disk-by-id passthrough instead (qm set <vmid> -scsi1 /dev/disk/by-id/ata-...).
2. The worst drive (WW66E7T3) started causing pool crashes immediately after VM start — kernel log flooded with critical target error, dev sda and ZIO errors with error=121.
3. Removed the drive from VM passthrough, ran smartctl -t long from Proxmox host — completed without error, PASSED. No reallocated sectors, no pending sectors, SMART error log clean.
4. Changed SATA cable and port for that drive, re-ran extended SMART — still PASSED, Command Timeout and CRC values didn't increase at all.
5. Re-added drive to pool via zpool replace, but drive keeps causing I/O errors under load (during scrub especially) and crashing the VM. Currently sitting UNAVAIL in the pool.

Current state:

• Pool is DEGRADED with WW66E7T3 UNAVAIL
• Other 3 drives ONLINE, no data errors
• Scrub completed: repaired 0B, 0 errors
• Drive is within warranty (Seagate IronWolf, expires June 2028)

My questions:

1. SMART extended test passes perfectly but the drive fails under real ZFS load — is this a known failure mode? Can a drive pass long SMART but still be genuinely failing?
2. Could this still be a cable/port/controller issue despite the cable swap? The Runtime_Bad_Block of 8,653 and the power cycle anomaly point strongly to physical connection instability.
3. Anyone else running TrueNAS virtualized on Proxmox with motherboard SATA passthrough experiencing similar timeout issues? Switching to disk-by-id helped the other drives significantly.
4. Should I just RMA the drive given it's under warranty, or is there more diagnostics worth running first?

Thanks in advance.

Hi,

I have a promox server and HA and want to integrate a NAS to back up my personal data,.mainly photos and stuff.

, redundant if possible, which NAS would you recommend?

Jellyfin is also a future possibility, how would I integrate this in my system as well ?

Thanks in advance for your input

What is the best practice on how to manage the cert that is used with the web interface for the TrueNAS community edition?

Right now, I have a wildcard cert issued by my DNS provider (Porkbun) that I load into TrueNAS via the /credentials/certificates page. This works great, but when the cert expires, I have to manually upload the new one, point the UI to the new cert, and delete the old one.

I have a different server running Traefik that gets its own wildcard cert, but I don't think running the TrueNAS ui through the reverse proxy makes sense since I need the domain to work for all of the other services running on TrueNAS (smb shares, iSCSI, etc).

I could set up the ACME configuration, but that would require an external script since PorkBun isn't one of the providers they have listed.

I could also set up a script to copy the cert from my Traefik server to TrueNAS.

Is there an easier way to get this to work? What does everyone else do?

I'm virtualizing PBS on a TrueNAS 25.10.2.1 server and it seems to be working fine other than a worrying console message in the PBS VM:

"clocksource: timekeeping watchdog on CPU3: Marking clocksource 'tsc' as unstable because the skew is too large:"

After doing a bit of investigating, it appears this is likely due to using a QEMU VM without the guest agent installed. I installed it without any errors but when I tried to enable it using systemctl, it threw a new error which is well outside my domain knowledge. Any ideas?

root@pbs4b:~# systemctl enable qemu-guest-agent

Synchronizing state of qemu-guest-agent.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.

Executing: /usr/lib/systemd/systemd-sysv-install enable qemu-guest-agent

The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,

Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl.

 Possible reasons for having these kinds of units are:

• A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory.

• A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it.

• A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...).

• In case of template units, the unit is meant to be enabled with some instance name specified.

At what €/Tb and where do you buy Hdds? I have heard some say that for refurbished ones ~10€/Tb is good, but it’s nearly impossible to find them at these prices. I’ve looked at eBay and a local seller and the best I get is ~15€/Tb with many being up to 20€/Tb.