jesta

Just wanting to add a report to this topic since I mainly bought the 5700G to run a VM off the iGPU: For me it's NOT working. I can get the VM to POST. In Ubuntu I can navigate the first install menu but if I select install Ubuntu the screen goes black and nothing comes up. Using safe graphics I can install the OS but after reboot the screen stays black (rebooted server also) In PopOS I can see the boot messages scrolling and when the UI loads the screen goes black and doesn't come back. Looks like loading the driver makes the iGPU crap the bed. This feels so close yet so far away. Specs: 5700G MSI B450m Mortar (Non-Max), BIOS 7B89v1I (AGESA ComboAm4v2PI 1.2.0.7) 3070 as second GPU VBIOS extracted with UBU (1638) BIOS Settings: Re-Size BAR Support --enable Above 4G memory/Crypto --enable Initiate Graphic Adapter --IGD Integrated Graphics --Force UMA Frame Buffer Size --4G IOMMU --enable DMA Protection --auto DMAr Support --auto SVM Mode --enable NX Mode --enable Boot mode --UEFI Unraid config: video=efifb:off No ACS override needed, GPU and Audio are in their own IOMMU groups added modprobe blacklist amdgpu VM OS: Ubuntu 22.10 or PopOS 22.04 Machine: tried both Q35-6.2 and i440fx-4.1 BIOS: SeaBIOS VM XML: <kvm> <hidden state='on'/> </kvm> <hostdev> ... edited the addresses, multifunction etc ... </hostdev> <qemu:commandline> <qemu:arg value='-set'/> <qemu:arg value='device.hostdev0.x-vga=on'/> </qemu:commandline>

Got another tip that works quite well for me! Switching my CPU (Ryzen 7 5700g) to the "powersave" governor saves me about 10W under normal load because all cores will run at 1.4GHz. I only need higher clocks when gaming on my Win 10 VM so I automated governor switching depending on whether I'm logged in to Windows: install Putty and set up ssh key authentication to the UnRAID host, save a Putty profile for the server that utilises ssh key authentication open Group Policy Editor by hitting Win+R, entering gpedit.msc and hitting enter in Computer Configuration > Windows Settings > Scripts for Shutdown and User Configuration > Windows Settings > Scripts for logout create new entries for Start/Login and Shutdown/Logout: for script name input path to plink.exe (C:\Program Files\PuTTY\plink.exe) for script parameters input -batch <Putty profile> /etc/rc.d/rc.cpufreq powersave/ondemand So you get a total of 4 entries (one each for start/shutdown/login/logout) that set the governor to powersave or ondemand (or whatever you prefer).

Thanks for this docker! One question: It says I need to set up cron jobs for recurring transactions... How do I do this since crontab isn't available in the container? [Edit] Created a User Script with docker exec --user www-data Firefly-III /usr/local/bin/php /var/www/html/artisan firefly-iii:cron Does the job.

Hey first of all thanks for the great plugins! Quick bug report: I just updated to the latest version of System Statistics and the System Stats graphs don't work anymore. They do in "Real-time" but not for "Last day" etc. What do you need to help fix this issue? Tried changing some settings and reinstalled. Edit: Was on 6.9.3. Updating to 6.10.3 fixed it.

I have a WIndows 10 VM that I'd like to be able to start by pressing a key on a keyboard directly connected to my server. To make this work I can issue bind '"\C-w":"virsh start Windows10\n"' in any terminal session and CTRL-W starts the VM. But this won't work on the keyboard connected to the server. I have tried adding the above command to the go file but that didn*t work. Any ideas?

I set up FileRun using @BamaJ13's docker template and ran into the issue that files created/uploaded through FileRun's webUI are readonly to other users and thus can't be modified over for example SMB. I first tried very long to launch the docker with different user:group settings and messing with ACLs but couldn't get it to work. Then I dug long and deep and found an undocumented solution. Here are the two steps needed: add two environment variables in template: "APACHE_RUN_GROUP = users" and "APACHE_RUN_GROUP_ID = 100" after first run, modify or create file /mnt/user/appdata/filerun/customizable/config.php with following content: <?php umask(012); Then all files/dirs created by FileRun will belong to group "users" and have read and write access for other users of UnRAID. Have fun!

Hey guys, I need some help. I recently lost my cache drive and had to restore docker.img and appdata from a backup (tried the two backups I have). Since then nextcloud won't work anymore. The container loads fine: But when accessing nextcloud all I get is Error 504: Gateway timed out. /log/nginx/error.log says this: Any pointers how to fix this?

Setup: Ryzen 5 2600x MSI B450m Mortar RX 5700XT in first PCIE slot (3.0x16, for gaming VM) GT 710 1Gb in third PCIE slot (2.0x1 via chipset, for UnRAID) I can enable GOP to get the system to POST on the GT 710 by switching to UEFI mode. When booting UnRAID in GUI mode the server comes up fine and prints the boot process on screen but when the GUI should start all I get is a blank screen with the cursor blinking in the upper left corner. emhttp is running per '$ ps aux | grep emhttp' and I can reach the GUI from a different machine. I have tried with 'nomodeset' in the syslinux config which didnt change anything. I have booted Unraid 6.9 RC2 from a different thumb drive and it has the same result. Am I just out of luck with yet ANOTHER incompatible hardware setup (NVME drive can't be passed through, GPU has the AMD reset bug) or is there anything left to try? tower-diagnostics-20210110-0900.zip

The "Logs" page is partly empty for me. Only the "$ ip route show" window is populated with information, the openvpn log and status doesn't show up. I guess status is empty if I'm running in client mode? Where does the plugin expect the log file to be?

Since we got your attention on this issue, here's two recent reddit threads discussing the issue: Unraid is unusable for me because of the docker excessive writes bug destroying my cache ssd. Is nobody bothered by this? Btrfs and cache writes...a question for those who switched. It appears most people have fixed the issue by switching from btrfs to xfs for the cache drive. Using iotop I can still (after switching to xfs recently) see about 1mb/min writes to cache on an idle server. Thats close to 1.5Gb per day without doing anything.

This broke UnRAID for me. Setup: Ryzen 5 2600X MSI B450m Mortar 2x16Gb RAM 3 Drives via onboard SATA 4 Drives via Dell H310 IT-mode 1 NVME drive Tried to pass through one of the two onboard USB controllers that has a USB hub with Keyboard and mouse connected. It is in it's own IOMMU group and can be passed through without a problem using the "vfio-pci-ids=" method. Unraid fails to load with text about the USB controller on the screen, no explicit error messages. (Didn't take a picture, sorry). Fixed by removing /config/vfio-pci.cfg on a Windows machine.

I am running unraid. I know letsencrypt needs to be running to renew. The question is will starting up the container that previously ran fine and got me certificates issued renew those certificates if they are about to expire? And how long before they expire?

Maybe, but I got it set up like this, the VPN tunnel was available for other reasons and I'd rather not run another docker on my VPS. It is only a single core with 2Gb RAM... Any comments on wether my script will do what I want it to?

I have nextcloud docker up and running and have used this container to get certificates which worked absolutely painless. Thanks! Since nextcloud is using ports 80 and 443 I can not have this container running all the time to renew certificates before they expire. I wrote a little script that will be executed weekly to hopefully renew the certificates automatically: #!/bin/bash # Stop nextcloud container to free up ports 80 and 443 docker stop --time=30 nextcloud # Start letsencrypt container docker start letsencrypt sleep 1m docker stop --time=30 letsencrypt # Remove old backup certs rm /mnt/user/appdata/nextcloud/keys/cert.crt_old rm /mnt/user/appdata/nextcloud/keys/cert.key_old # Backup current certs mv /mnt/user/appdata/nextcloud/keys/cert.crt /mnt/user/appdata/nextcloud/keys/cert.crt_old mv /mnt/user/appdata/nextcloud/keys/cert.key /mnt/user/appdata/nextcloud/keys/cert.key_old # Copy new certs cp /mnt/user/appdata/letsencrypt/keys/letsencrypt/cert.pem /mnt/user/appdata/nextcloud/keys/cert.crt cp /mnt/user/appdata/letsencrypt/keys/letsencrypt/privkey.pem /mnt/user/appdata/nextcloud/keys/cert.key # Start nextcloud container docker start nextcloud Will this make the letsencrypt container recognise the certificates and renew them if they are about to expire? How long before they expire will they be renewed? Thanks again!