Taddeusz

Holy necropost Batman! I actually ended up getting another SAS card, this time a Dell H310. Works really well though I’m sure the expander would have been fine too. More than enough bandwidth for my drives.

Specs say there are 4 USB 2.0 ports on headers. You could ether have an internal pigtail or get a slot mounted USB thing.

Do any drives work on the card? It could be that you got the wrong kind of 8087 breakout cable. There two kinds of cables that have different wiring. Forward breakout cables are meant to connect, in your case, from an adapter card to the drives. A reverse breakout cable is designed to connect from a motherboard's SATA ports to a SAS backplane. You need to make sure your cable is a SAS 8087 forward breakout cable. You can see a deeper explanation here:

For a while I've been having a couple problems with my oauth2proxy. I have cookie expiration set to 24 hours and refresh set to 1 hour. However, it seems after about an hour it's forcing me to login again. I can see the cookie is set to expire after an hour but it's still making me login again within the 24 hour period. The other problem I've been having is that periodically after I choose my Google account I get an error page rather than a success and forwarding to the requested page. If I then go back and attempt to login again it's successful. These two problems are rather annoying. Any ideas?

They support it just fine. I've used QSV with the Plex Docker with both an older Ivy Bridge i5 3470 and my current Coffee Lake i5 8400. It works great!

The Intel data sheet on the J4105 is weird. It doesn’t show list QuickSync support but I’ve seen other people that seem to be using it on that CPU. So it’s possible it doesn’t actually have QuickSync. Sent from my iPhone using Tapatalk

I’m certainly happy you got it working again but it could be the updater failed because it’s on a USB 3.0 port. While, yes, USB 3.0 SHOULD work. Things are never that simple. If you peruse the forums you’ll see lots of people who have USB dismount issues on 3.0 which is usually solved by moving to a 2.0 port. I can’t say for certain that it had a hand in your problem but to discount it out of hand is a bit arrogant and unscientific.

It was worth a try. The kernel doesn’t deal well with XHCI for whatever reason and often times gets unmounted on boot. So it’s always best to use a 2.0 port.

Make sure your USB stick is going into a USB 2.0 port and NOT a USB 3.0 port.

With Unraid 6.7.0 you shouldn't need i915.alpha_support=1 in your syslinux.cfg file. The i915 driver has for a while directly supported up to 8th generation Coffee Lake. It doesn't yet support 9th generation Coffee Lake though. Beyond that I'm not sure what would prevent it from working?

The first thing you cat try is to go into your Disk Setting and change "Tunable (md_write_method)" to "reconstruct write". My personal experience and observation is that the array file system drivers are not very well threaded or maybe not that advanced in their caching abilities. They seem to synchronously alternate reads and writes in order to fill and empty the cache. I've not ever observed this type of behavior in other operating systems where a parity of reads/writes is achieved to balance asynchronous read/write performance. Again, this is strictly my personal observation. I don't have any technical knowledge with how the array cache actually functions.

Well, after all that I see that the type of compression is selectable in the GUI. And in the end I decided to just disable compression. Especially after reading that having it enabled is not currently secure due to the VORACLE attack vector.

Well, this is a revolting development. I changed the "comp-lzo yes" lines and all "compress" types break my connection using the official OpenVPN iOS app. Tunnelblick works fine though.

It would be nice to see an option to select compression type and/or syntax. By that I mean being able to select whether to use 'comp-lzo' or the 'compress' command. Then also if you choose to select the 'compress' command being able to select between 'lzo', 'lz4', or 'lz4-v2'. Understanding that 'comp-lzo' is deprecated I believe 'compress lzo' should be the default syntax. Having a GUI like this means putting in enough functionality so that someone doesn't need to make manual edits like this unless it's something obscure.

Recently I've been getting this message from Tunnelblick about the comp-lzo option being deprecated. I know I can click the checkbox so that the warning doesn't appear again but is there a better fix for this? A way to use a better supported compression option?