**Version:** TrueNAS 27.0.0-RC.1 (ZFS 2.4.4-1, kernel 6.18.52-production+truenas)
**Hardware:** i7-10700, 48 GB non-ECC DDR4, LSI 9300-16i (IT mode), 7× 1 TB SATA SSD pool + 1 TB SATA SSD target, WD SN530 NVMe boot
**What I was doing:** Migrating an encrypted pool (RAIDZ1 → RAIDZ2) via a temporary single-disk pool.
- Source pool `Primary`: pool-level native encryption (AES-256-GCM, key), ~117 GiB, ~45 datasets. The apps dataset (`Primary/ix-apps`) is unencrypted; everything else inherits encryption from the root.
- Target: new single-disk pool `Temp` (unencrypted).
**Command:**
`zfs snapshot -r Primary@migrate && zfs send -Rw Primary@migrate | zfs recv -u Temp/Primary`
(second attempt also used `-x mountpoint`, run via nohup in the background)
**Result:** The system hard-reset ~30 seconds in, **both times at the same point**: the unencrypted `ix-apps` tree (~33 GB) finished receiving, and the reset happened as the stream moved on to the first encrypted dataset. Nothing was written to the journal before the reset (the last entries are routine), and no panic was captured.
**Things I ruled out:**
- The first attempt was with RAM overclocked (3200 MT/s on 2400/2666 sticks). That attempt also logged 4 checksum errors on one pool disk (repaired from parity), and a permanent error appeared in `libgallium` on the boot pool (written during the RC.1 upgrade). I reverted the RAM to 2666 and ran MemTest86 for 4 passes, 0 errors.
- The second attempt, with stable RAM, failed at the **same spot**.
- Scrubs of the source and target pools were clean afterwards.
**Workaround that worked:** Per-dataset **non-raw** send/recv (`zfs send ds@snap | zfs recv -u -o Temp/…`), which completed all 45 datasets in ~7 min without issue, and the same method back into a new encrypted RAIDZ2 pool. Data verified (logicalreferenced matched on 44/44 datasets, clean scrubs). RAIDZ expansion to 8 disks afterwards also completed fine.
**Suspicion:** raw (`-w`) send/recv of encrypted datasets on 27 RC.1 / ZFS 2.4.4. Happy to try reproducing with a console attached to capture a panic trace, or to provide a debug file, if that’s useful.