Dylan

I've a 4 bay NAS and am considering buying a second (almost the same) to serve as a backup device. Both would be wired on home LAN and running HexOS. The backup device would have greater storage capacity and slightly more RAM/CPU capability. What is the most efficient/automated way of copying writes to primary over to backup? My instinct would be to use schedule a cron job via rsync at certain intervals. However, I've also never used TrueNAS, prior to HexOS, and my ZFS administration was on production servers where backups were handled by a different group. So, what it be like?

This is the way. Pool expansion takes time and the greater the capacity, the longer it takes.

Hey folks. Just want to share the the HexOS team is aware of the IntelARC GPU passthrough issue and has a test system being used to try and ID and diag/resolve the issue. Thank you for your patience.

Thanks @jpadgett - We'll take a look at this and see if we can add your content to our Directory Of Guides. Really appreciate your efforts!

Here is a good jumping off point: LINK

Good looking rig - is it loud?

I finally got a chance to do some more digging. Turns out my file manager, Nemo, (Linux Mint) uses GVfs which mounts SMB shares via /run/user/1000/gvfs but not statically nor with appropriate permissions to torrent TO that location. So I made entries in fstab to /mnt but was still having issues before realizing that for permanent shares /media is the correct directory. Once fstab reflected those changes, I appear to be humming along nicely. //bigboy.local/shows /media/shows cifs credentials=/root/.smbcredentials,iocharset=utf8,vers=3.1.1,file_mode=0777,dir_mode=0777 0 0 //bigboy.local/movies /media/movies cifs credentials=/root/.smbcredentials,iocharset=utf8,vers=3.1.1,file_mode=0777,dir_mode=0777 0 0 Permissions and fstab were the right moves - the tthing that threw me off was GVfs and how it handles smb shares upon user login. Weird.

I think this is the most important consideration, even over personal risk tolerance because, with enough redundancy you're good regardless.

Maybe? Depends on your risk tolerance, I guess. THIS Google study showed iffy results at best. And THIS guys logic is kinda why I was asking; to get a sense if others in the community were as proactive as the linked article. I can see the benefit, but it also comes with a PITA factor of time which, if measured against failed drives, potential lost data and stupid RMA's might make sense.

The point of a HDD burn-in is exactly that, to catch manufacturer defects (usually bad physical sectors) before you write your data to it, especially if you choose to use refurbished drives. It's not witchcraft it's just an extra step one can take to try and be proactive to HDD health instead of reactive to bad HDD health.

Nice link!

Basically title (not ssd/nvme drives) Does anyone burn-in HDD's prior to deployment? I can see the potential value especially when (in my case) I use a few select sized disks very targeted for my specific use-case. My cost per disk is ~$175-$250 (eventually) totaling >8 drives, less spares. Given "bad batch failures" it kind of makes sense - again for my use-case. However, I've lived in data-center's and managed thousands and 10 to 100's of thousands disks where this wasn't performed. Likely due to a cost/time benefit. Meaning, for a production environment generating $millions it just wasn't worth the time. Scale that down to me, and maybe it does. What about you?

Full disclosure - I just watch this dude's channel and enjoy his work on storage performance analysis. While THIS specific video is about MAC's, it still seems apropos to what we often encounter when attempting to evaluate the never ending cost/performance/capacity Jenga dance.

@Taylor G. To echo what the others have said, I agree - especially while HexOS is still in beta. Even if TrueNAS supports it, it invites problems. I'd at least wait for a v1 release before using any important data.

I won;t say never because you never know. However, if I were to guess, the price will likely increase once ver 1.0 is released, so the current $199 price point is probably the cheapest it will be unless some sort of special is introduced.

Hi @g3rar2! Unfortunately, no. That price point expired a little over a month ago. I do hope you'll still join us, though!

Not to nit-pick but clarity matters. HexOS IS TrueNAS. HexOS is a wrapper that is intended to simplify the deployment, configuration and management of the same utilities supported by TrueNAS. It will just take some time to build out the app support specific to HexOS.

@steakboy Use Rsync between local hosts, wget fur URL downloads and curl if you need more advanced protocol or API support. https://www.geeksforgeeks.org/difference-between-wget-vs-curl/ https://www.geeksforgeeks.org/rsync-command-in-linux-with-examples/?ref=header_outind

My man is doing it again!!

Thank you for sharing such a detailed experience - really! This type of feedback really does help new users get a sense of expectation and context. I hope you continue to have fun and look forward to seeing what you're able to accomplish in the future!🤓

This might be worth adding to our directory of guides, so looking forward to it!

What did you use to reset the sector count?

I love these kinds of posts - even if it is theoretical it may be just the thing that sparks anothers curiosity and ingenuity. That's innovation.

You can already do that via cron jobs. In the TrueNA UI, go to System -> Advanced Settings and scroll until you see "Cron Jobs"

I'd riot in the streets over that one.