xaositek

Nothing like a Monday surprise! 6.12.0-beta17!!

I'm pretty sure the unRAID staff takes a break around December 25 because they are giving gifts like Santa! 6.12.0-beta16!

You know it's a good day when you see a beta drop! 6.12.0-beta15!

It's our lucky day!! 6.12.0-beta14!

All my existing Dockers are functional and update as necessary in beta 13. I did test installing a new Docker and did not have any issues. My Pools are XFS Cache Drive (single disk) and XFS Pool (One Drive + Parity)

Dang y'all getting twisted when there is nothing here but harmless fun. Let's see if we can get this thread back on the fun side before we lose it all together. Who is ready for beta 14?! As someone who has been on the beta train with 6.12 for awhile now, I haven't had to submit a bug report for anything in beta 13 so things are looking bright! Just remember guys, while we all know unRAID is a business and we all want to be keyboard warriors, for some people this is the only place they get to relax and have a good time; let's not try to sour the experience for everyone if you personally don't like the content, it's easy enough to just click away or start your own thread for more organized thoughts in a manner structured in your own way.

Fast X trailer was released today but unRAID is over here with 6.12.0-beta12 now!! For the fans:

Betas are faster than Vin Diesel! 6.12.0-beta11!!

@starbetrayer I think @SpencerJ forgot about you.... 6.12.0-beta10!!! No morse code today - just facts!

@starbetrayer - I think @SpencerJ's bird is slow today.... -.... .-.-.- .---- ..--- .-.-.- ----- -....- -... . - .- ----.

-.. --- -. .----. - / -... . / ... .- -.. --..-- / -... . / --. .-.. .- -.. .-.-.- / .. - .----. .-.. .-.. / --. . - / - .... . .-. . -.-.--

There is another branch beyond Stable and Next called Test.

It is released "VmVyc2lvbiA2LjEyLjAtYmV0YTY="

Anyone else notice that when you view a single drive from the "Main" tab, none of the "Self-Test", "Attributes", "Capabilities", etc are shown? I am running beta 5 on two different servers and notice this on both.

Any updates on Multiple GPU support? https://github.com/b3rs3rk/gpustat-unraid/issues/38

Ran into an odd issue where websites would get a 502 Gateway error after today's rebase to Alpine 3.17. The following error will fill the logs: nginx: [emerg] "stream" directive is not allowed here in /etc/nginx/conf.d/stream.conf:3 Ending up figuring out you can do the following, then restart your Container and it'll fix it. ls -al /etc/nginx/conf.d/ /etc/nginx/stream.d/ mv -v /etc/nginx/conf.d/stream.conf /etc/nginx/stream.d/ I did open https://github.com/linuxserver/docker-nginx/issues/87

I'll give you my two pennies after building with a 13900K. Ultimately when the cores are at idle, they are sipping power so I feel like disabling them to squeeze out maybe 0.25watts is a bit of a stretch, even disabling HT seems like a bit of an extreme measure. You'd be better off limiting the turbo boost which looks puts a power draw ceiling at 180watts. unRAID will run time at the stock 1.6/2.1 of your E and P cores. unRAID will have no issues running at those frequencies with the 8 P cores and 4 E cores. For reference other unRAID box which ran Dockers for Plex, *arr services, Transmission, nGinx, MariaDB, and PiHole did so on an Intel i5-9400F (https://www.intel.com/content/www/us/en/products/sku/190883/intel-core-i59400f-processor-9m-cache-up-to-4-10-ghz/specifications.html) which had six cores and no hyper thread. Base clock of 2.9ghz, turbo boost to 4.1ghz; ultimately this box never broke a sweat, even if running an additional Windows 11 VM. TL;DR - just let it run, I had a server with far less and you're not going to gain enough in such minor tinkering only to realize you may want it back; just limit turbo boosts and you'll be fine.

So I kept all the nVidia configuration in place which I knew was working and then added the /dev/dri as a new device. Once I did that, the iGPU was the first targeted GPU to do the work. Unfortunately I'm a bit out of time to try and max out the iGPU and see if it'll roll over to the nVidia card. Accord to this page (https://forums.serverbuilds.net/t/guide-hardware-transcoding-the-jdm-way-quicksync-and-nvenc/1408/2) it should work like this - "Plex will use QuickSync first in case of both a iGPU and Nvidia GPU installed."

Thank you! Got that that fixed up!

I just built out an Intel 13900K which also has an nVidia 1660 card on it. The graphics card is not used by any VMs; it would be nice to somehow load share / balance between the two cards. Unsure how OP got both the nVidia and i905 drivers to show up in /dev/dri, but here is my outputs.

Looks like we migrated to PHP 8 today.

Okay that was it for me - my local DNS name is "wiki" so my APP_URL to be https://wiki (I use bridged mode so port 443 for my install) and now the most recent version is working great!

Blast you aren't alone there - I blindly applied the update some time ago and just noticed it was broken - I don't rely on Bookstack every day but confirmed that ls25 did patch it up (thanks for that!)

Any idea where I can do this? Sorry first time I've ran into this scenario, most route through my NginX server but in case this I don't want public accessibility to it.