rix

This requires you to remove your custom ripper.sh Or just add these lines to the file: https://github.com/rix1337/docker-ripper/commit/92cf8f62bb6d430ca07358ea21743b98022d8e68

Thanks for investigating. I have updated the included ripper.sh which will now delete all .tmp files located at /tmp minutely. Docker Image should update within the next hour.

Has anyone else had issues with Intel Quicksync hardware transcoding running the 6.8 rc series? Streams have stopped working for my users and if they start at all, they are extremely blocky and unwatchable.

Not currently, The script always looks for the latest release on github. This probably could be solved - but not actively by me. I will however integrate a Pull Request that does this, if one appears.

Hi, this has nothing to do with the latest docker build, but rather the Version string suddenly containing a dash followed by letters. (-beta1) I have fixed the script that detects the latest version of DNScrypt https://github.com/rix1337/docker-dnscrypt/commit/93475503fa0e9e32b91244b164684af6ca1f75a0 Pull the latest docker image, once it is built an test if it now works.

Happy to help - you just need patience, if I am not available for a couple of weeks.

This looks wrong - the parameter needs to be passed as follows: You need to enter it in the advanced container settings And on changing what ripper does please refer to: https://github.com/rix1337/docker-ripper#how-do-i-set-ripper-to-do-something-else Just edit this line in your local ripper.sh https://github.com/rix1337/docker-ripper/blob/master/root/ripper/ripper.sh#L122 so it does not have a 2 after -c 0,2 This will only output mp3: /usr/bin/ripit -d "$DRIVE" -c 0 -W -o "$STORAGE_CD" -b 320 --comment cddbid --playlist 0 -D '"$suffix/$artist/$album"' --infolog "/log/autorip_"$LOGFILE"" -Z 2 -O y --uppercasefirst --nointeraction >> $LOGFILE 2>&1 For more info take a look at http://manpages.ubuntu.com/manpages/cosmic/man1/ripit.1.html

This could be due to the verbose logging of the container. Try and add --log-opt max-size=50m as Extra parameters in the container's advanced settings. This should drastically limit the container size due to docker logs.

Just ping me on github, this happens every other month.

Please refer to https://github.com/rix1337/docker-ripper#makemkv-needs-an-update I have triggered said update, which should be built in ~3hours

Sold mine and went with a 1080 Ti

Glad you got this sorted.

Not that I am aware of. Passing through /dev/sr0 is all thats required.

Yes of course, please refer to https://github.com/rix1337/docker-ripper/blob/master/README.md#how-do-i-set-ripper-to-do-something-else The BluRay quality by default should be equal to the content on disk, as no reencoding is done.

Before we go stable: Please take a look at the SACK exploit. https://access.redhat.com/security/vulnerabilities/tcpsack A kernel update may be advisable..

Working fine in my intel soc. Uptime 1+ day

The error in question being: Temporary failure in name resolution The script could not grab github.com. Ill try to fix the template.. Thanks for the report!

Thank you @peteknot for informing me. I have fixed the regex. The next container build should work again.

I returned my RTX 2080 and might try another brand in the future.

Have you tried a) not stubbing the gpu (not using vfio-pci.ids in the flash config) b) not plugging in anything to the gpu c) not booting gui mode? Is power draw still high when you run unraid then? for me it is even with a, b and c If so, the issue could lie somewhere in the kernel... 😫

I have now installed UNRAID NVIDIA which installs driver version 410.78. To use this as well as disable stubbing I have booted in shell mode (not the UNRAID GUI mode). I also checked for BIOS updates - the card is up to date. The RTX 2080 is now seen by Unraid and nvidia-smi. With that I can achieve 100 W at idle, still 35 W more than previously. Also the vm works as previously. Required: Non-GUI boot Disabled Stubbing No booted VM Spun down array Before returning the GPU I would appreciate input from other RTX 2080 owners! Is your idle power consumption as high as mine? If not, I am very interested in the model you are using. My card is a "Gigabyte RTX 2080 Windforce".

For sure sounds like the same issue. I will test just booting bare-metal windows to lock this issue down to unraid itself.

True, though in IDLE both cards should consume less than 20 W: For the 1070 it was around 7-10 W My issue lies with the 2080 consuming more than 50 W in idle.

Thanks for your reply. top/htop shows my cpu in deep sleep / less than 3% usage the GPU fans spin merrily - the thing is, when stubbing the GPU it becomes invisible to UNRAID - there is no process that should use the gpu as long as the VM is not running. What google tells me, the GPUs GDDR6 might not clock down in idle, without a relatively new driver. Sadly the unraid nvidia plugin is not up to date and as long as the GPU is stubbed it will not use the driver anyway...

I have replaced my server + dedicated Gaming system setup in January and couldn't be happier. I have pinned 12 of the 16 threads in my Ryzen 2700X that are passed solely to a Windows 10 VM. Up until yesterday the system was drawing ~65 W in IDLE, which is high, but acceptable for the hardware inside my UNRAID server. That is until I replaced the GTX 1070 I was previously using with a new RTX 2080. Idle power draw has doubled to 125 W. Please be aware, that I have stubbed the entire GPU (4 specific devices: GPU, Sound, USB-C, Some additional Controller) and Gaming performance inside the Windows 10 VM is satisfactory with the 2080. Power draw is as high when I boot the server without stubbing. There is also no noticable difference between booting GUI and normal Shell mode. What I have noticed however, is that once I boot the Windows 10 VM and log out there (stopping costly background processes in Windows) the power draw goes down. I cant really measure the difference, because booting up the VM itself draws a few dozen extra W but these figures are the best I got: Running a single plex stream in a docker on my UNRAID server increases power draw from 125 W to about 150 W. Booting the VM to the Desktop increases the Draw to roughly 170 W, but logging off in Windows (still running the VM) drops power draw (still streaming Plex) to 100 W. This looks like a kernel/driver issue to me. From various reviews I can see the 20-series from NVIDIA drawing 3-5 W more than the 1070 in IDLE. Any help is appreciated, because running 24/7 this doubles my power bill. I have zero clue where the extra 60 W would be going... EDIT: To clarify: idle means only Unraid and docker containers running - array spun down.