Dylan

After loading about 1TB of data onto a Plex server, give Plex a break to process all of that data. After my copies were complete I couldn't understand why Plex responsiveness was almost zero. Until I logged onto the dashboard with the activity button constantly spinning. It is trying to pull a TON of meta-data to associate with all of the movies. So yeah...don't expect to play all of your favorite films and shows just after a huge copy.

Which is exactly why I try to preach for consistent backups - it enables you to experiment with reduced risk.

Can you tell us a little more of what's going on as well as what hardware and network you are using?

Thank you for your feedback @PsychoWards and @Sonic. I saw your other post about running HexOS as Proxmox VM and specifically your comment about how much of the HW is under utilized. Since the larger device may only be for backups and perhaps one other use case, this presents opportunity. I'll keep the forum(s) updated as I get closed to actual deployment but this was a good first round of insight.

Nice looking device....just hella expensive.

Hi Jon - have you had a chance to see if post edit restrictions can be eased up yet?

Heya @Zeldatrek - Dual channel is supported; can you log into your BIOS and confirm all is reported? If so, what about booting to a live linux ISO and see what is reported there. Please report back and let us know!

I'd be happy to work with any/all commenters to help create a guide we can add to our DIRECTORY OF GUIDES - @Tamaluko Is your first post sufficient or would any additions or edits be helpful?

Picked THIS up for my primary streaming/storage device about four months ago. I've been super pleased with its performance so I went ahead and bought a second SIMILAR unit primarily for backups and potentially other edge/IOT (read home surveillance) usage. The difference being the primary uses an Intel N100 and, near as I an tell, is a little better supported when it comes to transcoding and streaming. The backup is slightly more equipped with CPU and RAM. Primary has 4x8TB raidz1 and the backup unit (eventually) will have 4x18TB in a raidz2. The only issue I see is if I use the back up unit for home surveillance, the high read/write IO could impact overall disk life. Am I wrong here? Tagging @Sonic as I would like to hear your experience on the AMD version of the Aoostar, so far. Thanks!

To the best of my knowledge there has not been a published version as we are still pre 1.0 (beta) - even the HexOS ISO download link refers to the TrueNAS version. That will (should?) be changing once version 1.0 is release.

@Tamaluko Great write-up and thank you for sharing. I went through a similar situation today that I posted about HERE. However in my case it was Plex playing funny with changing a .tmp file and associated permissions that when removed, fixed the issue.

I like my Firefox with all of my privacy extensions - add free YT is a must. Brave serves as my alternate from time to time.

Nice!

I've only been following this guy for about a year and despite his dry delivery find his content easily digestible, thorough and informative. Enjoy!

Tagging @jonp for visibility.

Great question! Because I have limited needs, just a storage device with basic streaming capabilities, I use HexOS on the daily - mainly Plex. However, this is just part of my larger effort to build out a home solution that will eventually replace paid-for services that have increasingly risen is price and are more inclusive of advertisements (I LOATH ads with a perfect hatred). I am attempting to time my efforts with HexOS maturation. Which is to say as HexOS gains in features, I look to increase my DIY replacement of paid-for services. I know not everyone has the same timeline, level of effort, risk tolerance etc.. as I do, but that's why I jumped in early. I keep backups, try to contribute to this community and help where I can to see where this is going.

It looks like REPLICATION will likely be my preferred method as I DO wish to automate this. @Mobius Buddy backup is a GREAT approach for offisite backups and one I will use and ask others the same, I just want to automate my writes from primary to secondary in keeping with the 3-2-1 rule - the "1" being when buddy backups are implemented. I'm still at "2" 😆

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 @Theo4, @ehrie & @Iliyria - The HexOS team is ware of the IntelARC GPU issue. They have a test system built and are working to ID the cause/resolution. Thank you for your patience.

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.

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.