Same recommendation here. I went through two QNAP units before being fed up and building my own 12 Bay for about 1200. My first QNAP died shortly after the 3 year warranty expired and the second died shortly before. I was able to RMA the second and sell it to recoup some money towards building my own TrueNAS system that I can now fix myself and not rely on proprietary anything.

Buy your candy at the end of August like I do and they are half price or even lower. This is what happens when you wait until what you would think the opportune time to buy your Halloween candy is.

My thoughts exactly when reading the headline.

I’m still confused on the sentence “re-imagining is exactly the right term”, because to me imagination is fluid and ever changing, but they said this term means the story has not changed.

I would expect remaster to be the proper term here, but I’ve not played the original or seen this iteration so I’m not sure what to think.

Holy shit, I love you wind taking abilities. I too had no idea who he was but thankfully don’t have to deal with confronting propogandized family members.

Why stop there? Pretty sure BL3 was free at some point recently.

Again, your ISP does DSCP markings. They will only benefit you if you are facing congestion issues inside your local network. When that external FaceTime call packet is received by your router, if you receive it at all because your ISP doesn’t care about markings, and you are having Internet issues, it’s going to reach your end point crazy fast inside your LAN, but I bet the call will drop regardless because the UDP steam is either too jittered, or completely frozen anyway because of the upstream ISP issue.

It’s great to configure this to understand the principle, but I’ve been in the industry long enough to know when QoS is required over a 10MB MPLS pipe, and not required over a 1GB+ pipe. The pipes are so big today that flow control has little use case any longer and can cause more issues and hand holding configuration than necessary.

I guess what I’m trying to say is if you’re having issues with your home Internet, you will see it regardless of how much mitigation you try to configure inside your own LAN.

Flow control is really a thing of the past. In production, we mark priority based on source port and destination host at the WAN edge. SMB\NFS replication across the WAN is an example of this. As another commented mentioned, voice should be tagged at the switch later and carried over the network. Tagging at your router is a moot point in residential because your ISP is discarding any DSCP you hand them.

Yeah, now think of how many 1x1 pieces there are in here that adds to piece count. As I’ve built a few more sets recently, the amount of 1x1 is rediculous given they could use 2x1 or 3x1 in many situations I’ve seen their usage in. And it’s in almost every single set.

I was a little unfair in my post towards Proxmox. It really is a great solution and I can’t really complain, but it sucks in comparison to ESX where many “custom” items are still hidden in the cli or custom configuration items,. Many of these things are available in the GUI in ESX which is a pretty rough translation for some that have worked in ESX for many years like myself. ESX isn’t without it’s CLI moments but they are rarely ever needed, and if needed only for drastic measures.

The UI is not very intuitive and really looks quite dated too. ESX, Nutanix and XCP-NG have much better interfaces imo, and if Proxmox could throw some of that extra money they’ve earned from the VMware exodus in their UI it would be worthwhile.

Again, I shouldn’t complain but as I get older there’s not much “tinkering” time anymore, and the less time I have to sift through forum posts or official documentation on why something isn’t working as intended, the more easily frustrated I get.

Don’t go Podman. When I started years ago I installed Fedora with the “containerization” option. This installs podman, not docker as I’m sure most know. I did not.

Podman works great for the most part, but it’s slight differences from docker will have you fighting tooth and nail for certain services to work correctly. And not many (if any at all) have any documentation on getting their containers working with Podman of they don’t start. If you make a GitHub issue asking why or how to get things running in Podman because their docker stack doesn’t work flawlessly like it will in docker, good luck getting help (Mailcow comes to mind specifically here).

Looking back, this decision really shoehorned some very fundamental ideals about containers in my mind, but it was a long fought road I would not choose again. The knowledge I gained about containers with docker would have come soon enough on the easy road.

And yes, you can install Docker on Fedora, but I was much too far down the Podman track before finding out. My environment has changed drastically as of late and most things have been migrated to docker apps in Truenas now, living directly next to their storage as intended (the arr stacks really take a performance hit running their databases over NFS once you have a lot of media for example).

Quick note about Proxmox after coming from ESX myself - it sucks compared to ESX. I’ve tried to move away from it and Nutanix was the closest I could find to ESX, but after my server started complaining it’s drives were not compatible I jumped ship to avoid any write damage to them. I’m downsizing my lab now, I have proxmox running in 3 small NUCs with CEPH storage share and it’s working pretty good. Would love to run ESX or Nutanix instead, but they require a loaf of bread in resource requirements where proxmox only needs a slice of bread in comparison.