ZFS snapshots and boot environments are great, even on my non-ECC systems!

Would you consider making an audio version of the podcast available via RSS feed? Also, thank you for the great work; I enjoy the podcast.

You keep mentioning the podcast, but I don't find it when searching in my podcast app [PocketCast]. Is the podcast restricted to some platform? It would be great to be able to access the content without having to deal with KZbin.

Nice work again guys, really loving this series (also, first post).

C.R.E.A.M, get the money!

i run truenas as a vm on proxmox but pass through my hba and have never had any issues i think my main reason for doing so is that truenas takes over the whole boot device so i cant store other things on it

Thanks for the info on midclt api. I've now updated my shutdown script to do it properly. Also checks for any running VMs and shuts them down cleanly, too. (This is on a once-a-week second backup target and test box that only runs for a few hours a week, before I get slated for not running it 24/7)

Does the zfs thing apply to HexOS as well?

Me 3 weeks ago: Why is my TN scale interface not running? idrac in... system crashed, reboot was halted and the specific ram module in error is indicated. Stick swapped, restarted and back in business in like 5 mins. That is a huge time savings as mentioned. Older ECC systems sure are not the fastest, but cheap and massive amounts of even DDR3 are pretty great + cheap enough to keep extra dimms on hand. Great convo on ECC and you are better with ZFS without a doubt, with or without ECC.

Great discussion! I'd love if someone would make the TrueNAS permissions/ACL pages make sense for me.

When was the last time you had a memory error?

There is no reason (other than cost and compatibility) not to use ECC. ZFS only solves the data integrity of the storage system. It will happily commit bad data from the program writing to disk. ECC only solves the basic error though. A catastrophic error will simply cause the system to panic and shutdown.

Slowly transitioning all my PCs to Linux at the moment, sick of Microsoft noseyness.

Given that there’s no benefit to this being video, it’s a shame that this isn’t available as a podcast instead. I’d subscribe to that there, if I could.

Question: How important is doing scrubs on my pool? Is it worth the stress inflicted on the drives? What is the danger to my data if I bypass scrubs? Thanks guys.

Not just Intel that doesn't need Nvidia driver, AMD chips have internal graphics

I would definitely pick used ECC over new non-ECC.

Aren't you afraid of Scrub runs without ECC as they read data from the drives, do some checksum calculations and "corrections" RAM and might write those "corrections" back to the drives? Isn't there a chance of ZFS corrupting a lot of data on the drives if those "corrections" are wrong because of a statically bit-flipped RAM cell, for example?

I've only been using TrueNAS for about 2 years, and I don't use it professionally (being a software engineer); I only use it for my home server. Over the years, my home servers have always been comprised of my older desktop PC hardware as I upgrade which is not ECC. This was the case even before I used ZFS, and even then I didn't have data issues. With checksums, I feel even more secure and I have not had a single identifiable issue with my non-ECC memory. That said, I also don't have a lot of heavy memory workloads. Most of my memory is just used for ZFS cache.

Is it possible to tell TrueNAS SCALE to send an Alert on ECC errors?

I *_love_* how you guys tackled this topic. While I understand why it's a controversial topic, it has always been needlessly controversial when discussed in the community in the past! Thanks for answering the question so well and emphasizing that the ECC vs. Non-ECC RAM decision ultimately boils down to a risk/reward decision.

Possibly the most sensible and sane discussion of ECC vs. non-ECC that I have listened to. By comparison there was a reddit r/ZFS question today about someone wanting to know just how long they could keep using a drive that was getting failing sectors and could they wait until the drive failed completely before replacing it, relying on all the ZFS error correction capabilities to fix smaller errors. I genuinely couldn't get my head around that sort of parsimonious mentality that valued their data so little to take those kinds of risks.

I got hexOS and immediately went out and cobbled together a system very similar to what LTT tested, and I can’t get the OS to complete an install. Hoping they can figure that out soon.

I can't wait for the ECC vs Non-ECC episode! 😎

Hey guys! Thank you so much for your help and encouragement. iX has been an amazing partner and we couldn't be happier with this relationship. You guys have been phenomenal in embracing this idea and giving us the support we needed to get this thing off the ground. You understand our mission and intended audience. And we're so excited with what's to come in 2025 and beyond. Thanks again!

It was great to hear more about the history of TrueNAS and especially how Kris has been contributing to freebsd and ZFS for so many years.

could you do a video on all specialty vdevs and their use cases

Makemkv app for the wishlist is what I wish for.

Thanks. Question. My TrueNAS core setup is as follows. Purely storage, general docs, I have my media (movies, tv shows, music), central log collection and a few databases (Influxdb and mariadb). My main system has 164GB of RAM and 40+ TB of storage. Would I benefit from either L2 Arc or SLOG cache? Don't want to spend money on it unless there will be a worth it.

Staying on Core, until SMB & NFS performance comes to par. RaidZ expansion, a long time coming. Only home use, but performance and stability is important.

Wow, this is the first I have heard of the `midclt call system.shutdown`; I I must have accidentally done hard shutdowns many times before! :) I'll have to pay attention to that. Might I suggest, this should be considered a bug, if you have total design control over the appliance, it should respond gracefully to every way a normal user might expect to shut it down, whether through `shutdown` or `poweroff` or the ACPI signal from pressing the power button. If the middleware is a service, I imagine the kernel has to politely request that it shut down, I'm not doing a `kill -9` here. Thanks for doing this podcast; what an exciting look at the future of my favorite storage product!

Will we get a backup/restore facility for LXC and VMs in a future release of True NAS? The lack of this is why I run Proxmox and True NAS inside of that as VM alongside my other VMs/LXCs.

My view of SLOG is: 1. Unless you absolutely need synchronous writes (e.g. database transactions, VM or iSCSI zVolumes), make sure that you configure your dataset or NFS mount or SMB from e.g. Mac for asynchronous writes - synchronous writes do c. 2x-10x as much disk I/O as asynchronous writes. SMB writes from Windows are always asynchronous. 2. If you can, put your synchronous write data on a fast Optane/NVMe/SATA SSD device rather than use an SLOG. 3. If you still need to do synch writes to a slow HDD, then a good datacentre quality Optane/NVMe/SATA SSD for an SLOG (which offloads the majority of writes - the ZIL writes to a separate device) can be beneficial.

My own view of L2ARC is: 1. Put your hot data on Optane/NVMe/SATA SSD if it is small enough for this to make sense. 2. Check your reports to see what your ARC hit rate is; if below 99% then add more RAM if you are not already maxed out. 3) If your ARC hit rate is still below 99% AND you have maxed out your memory AND providing that you have at least 64GB of memory then consider adding L2ARC if your L2ARC storage is much much faster than the data storage i.e. SSD vs HDD or Optane vs SATA SSD.

thank you for these podcasts. love them!!! could you chat a bit more in detail of whats planned some wish lists for the next two major releases? Thank you guys

Thanks for reading out my question guys, appreciate it! Interesting approach re the SATA DOM, would be good to know if in-place is doable without that step (and how). For anyone else watching/for reference, mine is a 4 bay, plus SSD DOM, and a SSD log in there too.

I see the new Community / Enterprise branding hasn't yet reached @kris' T-shirt!!! 🙂

Really great 1st episode. Keep this up! I think it's super useful.

Hi guys, is Clustering dead, or is that in the roadmap?

LOL it's been years since Kris was on BSD Now, but but I recognised his face as soon as I saw the thumbnail.

If it wasn't for my foray into the early TrueNAS SCALE betas, I would've been a contiguous FreeNAS/TrueNAS user for over 12 years on the same installation--but definitely not on the same media. Along the way I swapped out my mirrored USB drives with SATA SSDs for the boot media.

I've got a TrueNAS Mini still chugging along soundly since 2017. Just updated to Electric Eel last week. 2nd place, perhaps? 🙂

Feature request: partner with proxmox and xcp-ng for hyperconverged infrastructure and SAN.

Kris & Chris!

To anyone thinking of upgrading to Electric Eel, make sure that you read AND act on the instructions in the Release Notes.

iX rarely say it, but they were a big part of OpenZFS RaidZ Expansion - they don't just produce TrueNAS, they have also been instrumental in a lot of OpenZFS enhancements.

According to official TrueNAS' Software Status web pages, Electric Eel is only suitable for testing and not yet suitable for production use even by Early Adopters.

Been using FreeNAS and Now TrueNAS since version 9 or so.. Wouldn't trust my important data to anything else. iX is genuinely doing the lord's work, in a sector full of empty promises and buzzwords... Keep it up Team!

It's good to hear about some exponential growth of folks' adoption of major versions of TrueNAS!

Hi Kris, I was at asiaBSDcon 2014 and 2016, still running the same homelab (free)truenas install since 2013 quite an awesone and undestructible tech ! Nice to see this new podcast !