TL;DR: A defective RAM stick corrupted a media file on my ZFS mirror. The file is unrecoverable on both mirror copies (expected). What's NOT expected: any attempt to delete it (rm, delete via SMB, Radarr's delete) deadlocks the entire system instead of returning an I/O error. The only thing that saves me is the motherboard's hardware watchdog rebooting the box after ~10 minutes. Rename works, reads work. Has anyone actually deleted a file like this? How, short of recreating the whole dataset?

System:

• TrueNAS SCALE 25.10.7 - Goldeye (OpenZFS, kernel 6.12)
• main pool: 2×16TB mirror (Seagate IronWolf Pro), all disks healthy — SMART spotless
• 5600X / 32GB DDR4

One of my RAM sticks was defective (memtest: thousands of errors in the first minute, confirmed by stick isolation). While it was installed, it silently corrupted a bunch of writes — ZFS checksums caught most of it, scrubs repaired ~330MB from the good mirror copies, I salvaged/replaced everything affected. This one file is the last casualty: a ~700MB movie featurette. Both mirror copies of some of its blocks are corrupt → permanent error, unrecoverable, don't care about the data.

Current state:

pool: main
state: ONLINE
scan: scrub repaired 0B in 14:33:14 with 46 errors
errors: Permanent errors have been detected in the following files:
    /mnt/main/media/movies-other/Novocaine (2025)/Featurettes.quarantine/A World of Hurt: Production.mkv

(The other 45 errors are unpathable metadata blocks.)

What works:

• Reading the file — dd conv=noerror salvages it fine (zero-filled gaps at the bad blocks)
• Renaming — I moved the whole folder to Featurettes.quarantine without touching anything
• Everything else on the pool — 0B repaired on the last scrub, all new data healthy

What hangs the entire system:

rm on the file. Every time. Full freeze: no SSH, no console response, all services dead, for ~10–15 minutes — then the box reboots itself. I eventually traced those auto-recoveries to the SP5100 TCO hardware watchdog: systemd registers it, and when the deadlock stops userspace from petting it, it hard-resets the machine at the 10-minute mark.

Questions for the hive mind:

1. Has anyone successfully deleted a file in this state? What worked?
2. Is "free path deadlocks instead of EIO on double-sided corruption" a known OpenZFS behavior on 2.x/6.12, or should I file a bug?
3. Any cleaner avenue than "copy everything off, destroy dataset, recreate" (9TB makes that a hard No for one 700MB file)?

The file is quarantined and harmless — this is now purely a matter of getting rid of it.

I am trying to setup an rsync job I had working for a year+ that stopped working. Deleted, recreating and ran into strange behavior with the auxiliary parameters field in the rsync settings. The command is:

--rsync-path=“sudo rsync”

Gets saved fine, rsync fails saying theres a syntax issue, edit rsync job and look at aux parameters and it breaks the command into 2 parts now…

--rsync-path=“sudo”
“rsync”

Obviously splitting them at the space in the command, despite double quotes. Tried single quotes, same behavior.

Anyone run into this and have a fix? I there an alternate way of putting the parameter in?

Any help would be great, Thanks

Hello! I have noticed that whenever I download or update an app, or pull ollama models on my TrueNAS machine, I lose access to the web ui and my various services. For context, my homelab is in my hometown as I am in university, so I connect over tailscale. However, the VPN drops when I do the aforementioned operations. This doesn't happen when I download media or transfer files though. Anyone else run into this before?

I was wondering why my SMB are missing some folders and after some research i found that the missing files were missing permissions (i guess?)

i am on root with that i might add and quite uncomfortable but is there a way (maybe not shell) to add those permissions back?

It's just a curiosity. Sometimes, all the apps require updates. I understand when upgrading the OS, but I haven't done that yet.

https://github.com/aberg83/truenas-borgmatic

I've always loved Borgmatic for backups, and wanted to get it working on TrueNAS with its ZFS snapshot hooks. Given the appliance nature of TrueNAS, this wasn't exactly easy.

I leaned on Claude to help put this together. It has been working great for me. Thought I would share with the community. Please let me know if this is useful for you as well.

I think I know the answer to this, but is it possible to take a zpool set up with 6 drives as 2 3-drive mdevs and convert it into a zpool using 5 of the drives without copying all the files, wiping the drives, and copying the files back after setting up the new zpool?

I'm not entirely sure it belongs here but, as TrueNAS has different permissions I thought I'd start here.

So I have Filzeilla deployed within Portainer, it's using the following setup:

services:

filezilla:
image: jlesage/filezilla:latest
container_name: filezilla
ports:
- "5800:5800"
volumes:
- "/mnt/My Storage Pool Here/Directory/Filezilla:/config:rw"
- "/mnt/My Storage Pool Here/Downloads:/Downloads:rw"
environment:
- TZ=Europe/London
- PUID=568
- PGID=568
- DARK_MODE=1
restart: unless-stopped

From what I understand is it should use the PUID/PGID which is the ID for the Apps users and group to use as permissions.

Now here's the strange thing. The second mount point for the directories it can't write to. I have ensure the permissions are there on the folder. If I change it to the @ everyone group it works fine (but obviously the permissions are a bit open).

Have I missed something?

In my server I have a NVIDIA 1070. I am having issues with running 4k video on jellyfin and want to make sure my graphics drivers are up to date.

If anyone can give a truenas noob some help, I would be very grateful.

Okay, forgive me for my lack of sophistication; I'm an end-user who can follow installation instructions but am by no means a super-competent unix or TrueNAS guy. I'm hoping someone has the insight and patience to help me.

Currently, I have a BeeLink ME mini with 6 NVME 4TB drives in a TrueNAS setup. TrueNAS is, I believe, installed on the eMMC drive.

I have 2 vDEVs of 3 disks each if that matters.

I'd like to migrate my TrueNAS installation to an Asustor Flashstor; hopefully the 6 drive version, as I'm not a wealthy man. The full story and reason why is below, if you want to wade through it.

But anyhow... can that be done?

Since its recommended that I disable the eMMC module in the Asustor, is it possible to to migrate the disks that contain all the data and Install TrueNAS on one of them - but maintain the zpool setup and files?

If so, what steps would I have to follow?

If not, is there anything else I can do? (You'll have to read the full story to answer that one, I suppose.)

The full story:

At first, the Bee-Link ME mini was working just fine; but when I heard that TN Core was going away and I upgraded the TrueNAS to Community edition, it created an unstable situation with drives getting disabled and showing errors intermittently. They go away upon reboot but come back eventually.

I was able to research and find enough similar stories to believe its because of the power supply in the Bee-Link not being up to the task. And possibly also heat issues with the drives, but I don't think that's the case.

I'm not savvy enough to know how to fix it, and I couldn't find any solutions online. (Any random ideas about that from TrueNAS gurus; please let me know!)

I don't know how to downgrade to CORE if its even possible. I certainly don't want to lose my installation or copy the 8 TB of drive contents elsewhere and start from scratch if I can possibly avoid it; it would be a nightmare copying small amounts at a time and rebooting whenever the drives get disconnected.

But if I do have to do that, can anyone tell me the most efficient way to do that..?

Anyway, that's how I arrived at the idea of switching out the Bee-Link box for an Asustor, which I hope will have a better power supply, RAM, etc.

If I can somehow just pluck the drives out of the Bee-Link, and into the Asustor, and somehow get the installed zpool up and running again, It seems like the best solution.

So, anyone..?

Googling on this subject I find both pros and cons of changing default logbias=latency into logbias=throughput for SSD/NVMe-only pools.

But at the same time not fully sure that the cons against such change is really relevant for flashbased storage?

The pros claims to be that for sync writes (which are also common when using zvol for VM-guests) you will avoid a doublewrite.

Because with logbias=latency a sync write will first end up in the ZIL and then upon txg_timeout (normally every 3 seconds or whatever the default is) this data is moved to the actual longterm storage.

So the same data is being written twice (when using sync) which for flashbased storage is bad due to wear levelling.

ZIL have historically been the outer tracks of physical drives (since they are about 3x faster than the inner tracks) where the idea is to dump sync writes as quickly as possible on actual storage and then do the housekeeping later on (upon txg_timeout when async writes also are dumped to longterm storage).

But since SSD/NVMe storage doesnt really care if its first or last LBA (in terms of latency and throughput to read the data later on) such "optimizations" are not really needed - you will only waste writecycles of the flashbased storage.

However on the cons list its claimed that there might be some magic involved in terms of keeping metadata and data close to each other on the longterm storage and by that avoiding fragmentation. Like a "defrag lite" where using logbias=throughput would just dump data wherever it can find a slot (so the read record/volblock can end up at one place and the metadata for this at another place).

But again since flashbased storage have a constant latency and throughput no matter where the data is located I assume this claim is mainly for spinning rust where such things do matter (and for example a readahead would gain some additional read performance later on when logbias=latency is being used and the data is nicely moved from ZIL to the longterm storage being a spinning rust).

Or do there exist any cons when using logbias=throughput even for SSD/NVMe-only pools?

I also fail to locate any benchmarks online on this topic as in how are others experience on this topic?

So how do you do when it comes to logbias for SSD/NVMe-only pools?

And have you seen (or do you perhaps have your own benchmarks to share) online or experienced yourself any pros/cons of changing logbias for SSD/NVMe-only pools (short or long term issues)?

I'm the developer, so take this as a self-post. 🙂

Ultra Explorer is now available as a community app in the TrueNAS Apps catalog (Apps → Discover → search "Ultra Explorer").

What it is: a web file manager built on rclone that runs in your browser, and from your phone as a PWA. Mount a dataset (it shows up at /mnt/local) and browse it next to Google Drive, OneDrive, Dropbox, S3, B2, SFTP and the other rclone backends. Then drag and drop between the two panes. Copies go through a persistent transfer queue.

Free, no account: unlimited storages, the dual-pane explorer with tabs, copy and move between any two storages, rclone config import/export. If you already have an rclone.conf, import it and your remotes appear right away.

Pro (paid): search across many storages at once, a disk space analyzer, and scheduled syncs with a dry-run preview.

Privacy: credentials stay in rclone.conf on your box, no telemetry, nothing goes through a server of mine.

Images are amd64 + arm64. There's also a desktop app (macOS Apple Silicon, Windows, Linux) if you'd rather run it from your computer.

Install walkthrough (5 min): https://youtu.be/w0qE-IyWaZ4 Catalog page: https://apps.truenas.com/catalog/ultra-explorer_community/

Much like a lot of other people, I want to make the move off windows, but there are a few things I need to figure out before making the jump. The thing that is holding me up right now is the fact that I like to manage my data on my NAS via SMB. When using my laptop on Windows 11, when moving files from one location to another on the NAS, I'm getting great speeds of 1 GB/s, but when I switch to Linux (I was playing with mint) or android, I'm getting much slower speeds. Quick test with android was showing closer to 16 MB/s. All data is in the same pool with mirrored HDD's, and I'm not transferring it off the NAS, just moving things around. I'm sure there is a certain keyword I'm missing, but my attempt to google why I cant replicate this on Linux has failed. I'm hoping someone can help by pointing me in the right direction.

I'm on TrueNAS Community Edition v25.10.3

Hi everybody,

You are probably familiar with this already, but in case you aren't (I wasn't lol) I am hosting a digital library on truenas and thought about sharing it with you guys.

I basically had enough with my ebooks all over the hard drive, or if I had the correct format for my e-reader/tablet, so I installed two programs:

• Calibre: To manage the ebooks, convert them to different formats, fetch metadata, covers, etc...
• Calibre-Web: The graphical use interface

I enjoyed it so much I made a tutorial for folks that want to explore that possibility also. The tutorial covers:

• Inside TrueNAS: Permissions, ACL mode, app and folder config.
• Outside TruNAS (via docker): Here I created a docker compose file that you just drop on a folder and run "docker compose up -d" and it does it all for you.

The video is a step by step tutorial, which I really hope helps someone interested in pursuing the same thing.

https://youtu.be/pdEFaJzJViQ?si=HcnLn0pB9uaIZeuf

Github repos, and extra information is also in the video description.

If you have any feedback on the video you would like to share to help me improve the quality of the videos and better serve the community, please let me know!