bastl

Members
  • Posts

    1219
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by bastl

  1. First of all big thanks @bonienl for all your usefull plugins and the great work for the cummunity!!! 🥰 As usual on a new Unraid box, the "dynamix system temp" plugin is a must have. I installed it, went to the settings page, pressed Detect and nothing happened. Same after a reboot. No drivers have been detected or loaded. After searching around and a little help from @ich777 I found a solution and thought I post a small How2 in case someone else finds this useful. for reference my initial post: My new system is a MinisForum HM90 mini PC. Specs: Ryzen 9 4900H (Renoir Zen 2) with Radeon RX Vega 8 Graphics 2x 16GB Kingston 3200 DDR4 Kingston 512GB NVME (cache for VMs) 2x Samsung 870 1TB SSD (data-pool for system, appdata and files) random flash stick as dummy array disk Unraid 6.10.3 installed plugins: Dynamix System Temperature GPU statistics Nerd Tools Radeon Top Nuvoton NCT6687 Driver Unassigned Devices and all sorts of other useful stuff + a couple dockers (Nextcloud, Jellyfin ...) sensors gave me the following output: root@mini:~# sensors amdgpu-pci-0600 Adapter: PCI adapter vddgfx: 1.32 V vddnb: 874.00 mV edge: +44.0°C slowPPT: 4.00 mW k10temp-pci-00c3 Adapter: PCI adapter Tctl: +60.2°C nvme-pci-0100 Adapter: PCI adapter Composite: +43.9°C (low = -0.1°C, high = +84.8°C) (crit = +94.8°C) running "sensors-detect" showed: root@mini:~# sensors-detect # sensors-detect version 3.6.0 # System: BESSTAR TECH LIMITED HM90 [Default string] # Kernel: 5.15.46-Unraid x86_64 # Processor: AMD Ryzen 9 4900H with Radeon Graphics (23/96/1) This program will help you determine which kernel modules you need to load to use lm_sensors most effectively. It is generally safe and recommended to accept the default answers to all questions, unless you know what you're doing. Some south bridges, CPUs or memory controllers contain embedded sensors. Do you want to scan for them? This is totally safe. (YES/no): YES Silicon Integrated Systems SIS5595... No VIA VT82C686 Integrated Sensors... No VIA VT8231 Integrated Sensors... No AMD K8 thermal sensors... No AMD Family 10h thermal sensors... No AMD Family 11h thermal sensors... No AMD Family 12h and 14h thermal sensors... No AMD Family 15h thermal sensors... No AMD Family 16h thermal sensors... No AMD Family 17h thermal sensors... No AMD Family 15h power sensors... No AMD Family 16h power sensors... No Hygon Family 18h thermal sensors... No Intel digital thermal sensor... No Intel AMB FB-DIMM thermal sensor... No Intel 5500/5520/X58 thermal sensor... No VIA C7 thermal sensor... No VIA Nano thermal sensor... No Some Super I/O chips contain embedded sensors. We have to write to standard I/O ports to probe them. This is usually safe. Do you want to scan for Super I/O sensors? (YES/no): YES Probing for Super-I/O at 0x2e/0x2f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... Yes Found `ITE IT8613E Super IO Sensors' Success! (address 0xa30, driver `to-be-written') Probing for Super-I/O at 0x4e/0x4f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... No Some systems (mainly servers) implement IPMI, a set of common interfaces through which system health data may be retrieved, amongst other things. We first try to get the information from SMBIOS. If we don't find it there, we have to read from arbitrary I/O ports to probe for such interfaces. This is normally safe. Do you want to scan for IPMI interfaces? (YES/no): YES Probing for `IPMI BMC KCS' at 0xca0... No Probing for `IPMI BMC SMIC' at 0xca8... No Some hardware monitoring chips are accessible through the ISA I/O ports. We have to write to arbitrary I/O ports to probe them. This is usually safe though. Yes, you do have ISA I/O ports even if you do not have any ISA slots! Do you want to scan the ISA I/O ports? (yes/NO): yes Probing for `National Semiconductor LM78' at 0x290... No Probing for `National Semiconductor LM79' at 0x290... No Probing for `Winbond W83781D' at 0x290... No Probing for `Winbond W83782D' at 0x290... No Lastly, we can probe the I2C/SMBus adapters for connected hardware monitoring devices. This is the most risky part, and while it works reasonably well on most systems, it has been reported to cause trouble on some systems. Do you want to probe the I2C/SMBus adapters now? (YES/no): YES Using driver `i2c-piix4' for device 0000:00:14.0: AMD KERNCZ SMBus Module i2c-dev loaded successfully. Next adapter: SMBus PIIX4 adapter port 0 at 0b00 (i2c-0) Do you want to scan it? (yes/NO/selectively): yes Client found at address 0x50 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... Yes (confidence 8, not a hardware monitoring chip) Probing for `EDID EEPROM'... No Client found at address 0x51 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... Yes (confidence 8, not a hardware monitoring chip) Next adapter: SMBus PIIX4 adapter port 2 at 0b00 (i2c-1) Do you want to scan it? (yes/NO/selectively): yes Next adapter: SMBus PIIX4 adapter port 1 at 0b20 (i2c-2) Do you want to scan it? (yes/NO/selectively): yes Next adapter: AMDGPU DM i2c hw bus 0 (i2c-3) Do you want to scan it? (yes/NO/selectively): yes Next adapter: AMDGPU DM i2c hw bus 1 (i2c-4) Do you want to scan it? (yes/NO/selectively): yes Next adapter: AMDGPU DM i2c hw bus 2 (i2c-5) Do you want to scan it? (yes/NO/selectively): yes Next adapter: AMDGPU DM i2c hw bus 3 (i2c-6) Do you want to scan it? (yes/NO/selectively): yes Next adapter: AMDGPU DM aux hw bus 1 (i2c-7) Do you want to scan it? (yes/NO/selectively): yes Next adapter: AMDGPU DM aux hw bus 2 (i2c-8) Do you want to scan it? (yes/NO/selectively): yes Next adapter: AMDGPU DM aux hw bus 3 (i2c-9) Do you want to scan it? (yes/NO/selectively): yes Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `to-be-written': * ISA bus, address 0xa30 Chip `ITE IT8613E Super IO Sensors' (confidence: 9) Note: there is no driver for ITE IT8613E Super IO Sensors yet. Check https://hwmon.wiki.kernel.org/device_support_status for updates. No modules to load, skipping modules configuration. Unloading i2c-dev... OK root@mini:~# "k10temp-pci-00c3" looked like this is the CPU temp sensor for the 4900H. As ich777 pointed out 'ITE IT8613E Super IO Sensors' might also be something to look at. It's actually the chip managing the fan speeds. First thing I did, I compared it with my other AMD build (Threadripper TRX40 plattform) where I also have Dynamix System Temps installed. In the plugin folder on the TRX40 Unraid flash disk I found a couple files that are missing on the new box. /boot/config/plugins/dynamix.system.temp drivers.conf: it87 k10temp sensors.conf: # sensors chip "it8792-isa-0a60" ignore "fan1" chip "it8792-isa-0a60" ignore "fan2" chip "k10temp-pci-00c3" label "temp1" "CPU Temp" chip "it8792-isa-0a60" label "temp1" "MB Temp" chip "it8792-isa-0a60" label "fan3" "Array Fan" Same "k10temp-pci-00c3" as on my new HM90 box. So I manually created the "drivers.conf" on the new system with the same drivers to load (it87+k10temp). After that I went back to the "Dynamix System Temperature" settings page and it87 + k10temp showed up as available drivers. Be careful don't press detect or the entry will be removed again. Pressing save and the sensors should be available to select now but a sensor for the fan speed is still missing. A quick restart of the box and still only the k10temp, gpu and nvme sensors showed up. In another forums thread a user with a Terramaster box had the solution for me. Forcing another id did the trick and the fan speed showed up and a couple other temp sensors. modprobe it87 force_id=0x8620 Unfortunately this will not survive a system reboot. You have to add that line on your go file located in the config folder on your Unraid flash disk. nano /boot/config/go #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & # load driver for System Temp to show fan speeds modprobe it87 force_id=0x8620 If someone knows what these other 3 temp sensors are showing, let me know. @limetech In the release notes for 6.6.0-RC1 you stated: - removed CONFIG_SENSORS_IT87: ITE IT87xx and compatibles - it87: version 20180709 groeck Linux Driver for ITE LPC chips (https://github.com/groeck/it87) Are there any new drivers available which replaced these old it87 ones that I can use instead or which can you implement and auto load in Unraid? And another question: @bonienl is there an easier way for people to load these drivers by clicking "detect" and not doing it by hand?
  2. quick update in case someone stumbles across this. This sensor is the fan sensor. I will do a full writeup and link it here, when all is sorted out. Thanks again EDIT: solution you can find her
  3. save my sunday and give me the driver pleeeeeeeease ... just kidding 😂
  4. You're right. Sry for that. Next post will be in the depending forum. Open the PC is no problem, but without removing the cooler you can't really see the motherboard at all 😂
  5. Thanks for the quick answer. I already searched the forums. 😂 searching for "4900H" brings up nothing. "HM90" only a single guy with boot issues "minisforum" a couple people asking for compatibility, passthrough and setup for unraid, nothing related not sure where to start. "sensors" gives me the following output root@mini:~# sensors amdgpu-pci-0600 Adapter: PCI adapter vddgfx: 699.00 mV vddnb: 874.00 mV edge: +45.0°C slowPPT: 1000.00 uW k10temp-pci-00c3 Adapter: PCI adapter Tctl: +61.0°C nvme-pci-0100 Adapter: PCI adapter Composite: +47.9°C (low = -0.1°C, high = +84.8°C) (crit = +94.8°C) "k10temp-pci-00c3" might be the CPU temp sensor for the 4900H. If i stress the CPU it spikes up. Question is how to load/unload the driver and set it up correctly for the plugin to register and how do I find the fan sensor. questions questions question 🙄 running "sensors-detect" root@mini:~# sensors-detect # sensors-detect version 3.6.0 # System: BESSTAR TECH LIMITED HM90 [Default string] # Kernel: 5.15.46-Unraid x86_64 # Processor: AMD Ryzen 9 4900H with Radeon Graphics (23/96/1) This program will help you determine which kernel modules you need to load to use lm_sensors most effectively. It is generally safe and recommended to accept the default answers to all questions, unless you know what you're doing. Some south bridges, CPUs or memory controllers contain embedded sensors. Do you want to scan for them? This is totally safe. (YES/no): YES Silicon Integrated Systems SIS5595... No VIA VT82C686 Integrated Sensors... No VIA VT8231 Integrated Sensors... No AMD K8 thermal sensors... No AMD Family 10h thermal sensors... No AMD Family 11h thermal sensors... No AMD Family 12h and 14h thermal sensors... No AMD Family 15h thermal sensors... No AMD Family 16h thermal sensors... No AMD Family 17h thermal sensors... No AMD Family 15h power sensors... No AMD Family 16h power sensors... No Hygon Family 18h thermal sensors... No Intel digital thermal sensor... No Intel AMB FB-DIMM thermal sensor... No Intel 5500/5520/X58 thermal sensor... No VIA C7 thermal sensor... No VIA Nano thermal sensor... No Some Super I/O chips contain embedded sensors. We have to write to standard I/O ports to probe them. This is usually safe. Do you want to scan for Super I/O sensors? (YES/no): YES Probing for Super-I/O at 0x2e/0x2f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... Yes Found `ITE IT8613E Super IO Sensors' Success! (address 0xa30, driver `to-be-written') Probing for Super-I/O at 0x4e/0x4f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... No Some systems (mainly servers) implement IPMI, a set of common interfaces through which system health data may be retrieved, amongst other things. We first try to get the information from SMBIOS. If we don't find it there, we have to read from arbitrary I/O ports to probe for such interfaces. This is normally safe. Do you want to scan for IPMI interfaces? (YES/no): YES Probing for `IPMI BMC KCS' at 0xca0... No Probing for `IPMI BMC SMIC' at 0xca8... No Some hardware monitoring chips are accessible through the ISA I/O ports. We have to write to arbitrary I/O ports to probe them. This is usually safe though. Yes, you do have ISA I/O ports even if you do not have any ISA slots! Do you want to scan the ISA I/O ports? (yes/NO): yes Probing for `National Semiconductor LM78' at 0x290... No Probing for `National Semiconductor LM79' at 0x290... No Probing for `Winbond W83781D' at 0x290... No Probing for `Winbond W83782D' at 0x290... No Lastly, we can probe the I2C/SMBus adapters for connected hardware monitoring devices. This is the most risky part, and while it works reasonably well on most systems, it has been reported to cause trouble on some systems. Do you want to probe the I2C/SMBus adapters now? (YES/no): YES Using driver `i2c-piix4' for device 0000:00:14.0: AMD KERNCZ SMBus Module i2c-dev loaded successfully. Next adapter: SMBus PIIX4 adapter port 0 at 0b00 (i2c-0) Do you want to scan it? (yes/NO/selectively): yes Client found at address 0x50 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... Yes (confidence 8, not a hardware monitoring chip) Probing for `EDID EEPROM'... No Client found at address 0x51 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... Yes (confidence 8, not a hardware monitoring chip) Next adapter: SMBus PIIX4 adapter port 2 at 0b00 (i2c-1) Do you want to scan it? (yes/NO/selectively): yes Next adapter: SMBus PIIX4 adapter port 1 at 0b20 (i2c-2) Do you want to scan it? (yes/NO/selectively): yes Next adapter: AMDGPU DM i2c hw bus 0 (i2c-3) Do you want to scan it? (yes/NO/selectively): yes Next adapter: AMDGPU DM i2c hw bus 1 (i2c-4) Do you want to scan it? (yes/NO/selectively): yes Next adapter: AMDGPU DM i2c hw bus 2 (i2c-5) Do you want to scan it? (yes/NO/selectively): yes Next adapter: AMDGPU DM i2c hw bus 3 (i2c-6) Do you want to scan it? (yes/NO/selectively): yes Next adapter: AMDGPU DM aux hw bus 1 (i2c-7) Do you want to scan it? (yes/NO/selectively): yes Next adapter: AMDGPU DM aux hw bus 2 (i2c-8) Do you want to scan it? (yes/NO/selectively): yes Next adapter: AMDGPU DM aux hw bus 3 (i2c-9) Do you want to scan it? (yes/NO/selectively): yes Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `to-be-written': * ISA bus, address 0xa30 Chip `ITE IT8613E Super IO Sensors' (confidence: 9) Note: there is no driver for ITE IT8613E Super IO Sensors yet. Check https://hwmon.wiki.kernel.org/device_support_status for updates. No modules to load, skipping modules configuration. Unloading i2c-dev... OK
  6. Hi @ich777 First of all, big thanks for your version of Jellyfin. I use it on my new small Unraid media server build on an MinisForum HM90 mini PC. It uses an Renoir Zen 2 based Ryzen 9 4900H with Radeon RX Vega 8 Graphics. After some issues with your default port mappings 8096 > 8096 and 8920 > 8920 I now have access to the WebUI. I had to adjust the Ports to 18096 and 18920 for me to have access. Not sure whats wrong with the default mappings and my network config. I tried bridged, br0 and a custom network, same problem on all of them with the default ports. I installed the "Radeon TOP" and "GPU statistics" plugins to check the stats on the dashboard and with "radeontop" via terminal. Jellyfin statistics is showing the transcoding with 65fps. GPU statistics 4k source: radeontop idle: radeontop transcoding 4K source file: It looks like the GPU transcoding is working even without the adjustment of the go file. 👍 Jellyfin statistics is showing the transcoding with 65fps. I have also installed the "Dynamix System Temperature" and your "Nuvoton NCT6687 Driver" plugin. Unfortunately the temperature plugin doesn't find any drivers, so I have no fan or CPU temp monitoring available. Any ideas what I'am missing? If I shoud test some stuff for you, please let me know. Maybe you can add the 4900H to the list of supported hardware. 😉
  7. Perfekt. Gerade getestet mit nem alten Stick. Funzt! Nen neuer Stick fürs OS ist bestellt. Am Wochenende wird dann umgestellt. 👍
  8. Servus zusammen, ich pack mal meine Frage hier rein, vielleicht kann mir jemand den ein oder anderen Tipp geben. Folgendes habe ich vor. Auf meinem Hauptsystem mit Unraid laufen diverse Dienste wie Nextcloud, Unifi, Bitwarden etc. Da ich den Threadripper auf die Dauer nicht ständig laufen haben will, kam mir die Idee, ich könnt die meisten Dienste ja auf einen low-power MiniPC auslagern. Dort sollte dann ebenfalls Unraid drauf, da mir die Verwaltung über die GUI recht gut zusagt. Nun das Problem. Der MiniPC hat eine 500GB NVME und 2x1TB SSD. Weitere Festplatten passen nicht rein bzw. sind alle Anschlüsse belegt, außer natürlich USB Geräte. Jetzt stellt sich mir die Frage, Docker+VMs laufen nur mit gestartetem Array. In das Array sollte man allerdings keine SSDs packen, da TRIM nicht unterstützt wird bzw. die Parität dadurch geschrottet werden kann. Ich würde bei der Kiste auch ohne Array Disks auskommen, das scheint allerdings nicht zu funktionieren. Besteht die Möglichkeit einen einfachen USB Stick (quasi als Dummy) als einziges Array Device zu nutzen, damit das Array überhaupt gestartet wird? Die NVME würde ich für 1-2 VMs nutzen und die 2x1TB als gespiegelten Pool für die Services und paar Daten die anfallen. Shares nur auf den Pools und absolut nix auf dem Array, geht das? Oder macht es Sinn die NVME als Array zu nehmen? Dann dürfte doch Trim nutzbar sein ohne Parität, oder? Gibt es etwas, was ich dabei übersehe? Irgendwelche Tipps?
  9. @Nodiaque As workaround for testing Win11 you can use the following on 6.9.2:
  10. I guess most of you who tried to test the final Windows 11 build might allready noticed, the installer checks for the presence of a TPM module and enabled SecureBoot. If one of them is not present, the installer will halt with the following error directly after the edition selection With shift+F10 open a commandline Enter "regedit" into the cmd and press enter. The registry editor should open up. Navigate to "HKEY_LOCAL_MACHINE\SYSTEM\Setup" create a new key called "LabConfig" on the left side bei right clicking on "Setup" and select new > key ad the following 3 DWORD (32-Bit) entries inside LabConfig on the right. BypassTPMCheck BypassSecureBootCheck BypassRAMCheck Double click each entry and change the hex entry from 0 to 1 After that close the registry editor and the commandline and go one step back to the edition selection screen, select the version you wanna install, press next et voila, Windows 11 should install fine. Doing all this straight after the installer has started on the language selection menue also works. No need to go to the edition selection first. For this to work I used the default Win10 template with a 70G vdisk 4G RAM and 8cores. Nothing else on the template or in the xml has changed. Keep in mind this is only a solution if you want to try the new Windows version. No one at this point can guarantee how long this will work and if a future update will break something. We all know MS is randomly "breaking" things with every update. Some reports say updates might not even possible with this reg tweak in the future, therefore my warning for all those can't await the next Unraid version which propably will come with a fix and an emulated TPM module. only use this for testing Windows 11! Happy testing folks
  11. @Falcosc Verify on disk 1 is finished. The file integrity control panel page still shows the the files from disk2 like in the screenshot of my fist post. I have a lot of *.tmp.end files in /var/tmp and a disk2.tmp.end. Some are from august some from today. I renamed the disk2.tmp.end refreshed the page and disk2 export showed "canceled with error". Refreshed the page again. Error is gone. Started a new export of disk2. No errors. I'am kinda confused right now.
  12. @Falcosc Maybe it helps to note that I am from germany and some of the files include the german letters Ää Öö Üü and ß for example */mnt/disk2/company/tmp/Präsentation/industrie-medium.png also I have a folder where backups from my android phone are placed, some with the following naming included with an @ for example */mnt/disk2/nextcloud/user/files_versions/.SeedVaultAndroidBackup/1678426041580/kv/@pm@/Y2ibnQudnVXN1cn9tLZleQ.v1614280421
  13. @Falcosc I have no /tmp/disk2* files in that folder and I can't really share the /var/tmp/disk2* filelist with you. I have a lot of personal and work content on that disk, some named with my real name or the name of the company I work for. I can try to remove the personal stuff if it helps. I guess not. On the main tab I only see reads happen on disk one where the verify process is still active. Looks like export for disk2 is already finished. Timestamp for disk2 is short after the time a started the process for a new export.
  14. Short report for something weird happened to me. Planned verify task for 2 disks started this morning, 1 disk finished and reported a corruption on disk 2. Verify task on disk 1 still running. The coruppted file in my case was the nextcloud.log file getting flooded. I cleared the logfile, verify on disk 1 still running. I selected disk 2 and started a export task and the following happened in the ui The ui shows as it looks like the full list of files beeing scanned on disk 1. Refreshing the page doesn't help. The counter for processed files is still counting up and constant read speeds on disk 1 showing that the process looks like it's still working. Only the page is messed up.
  15. @bonienl 2021.08.24b fixed it. Thanks!
  16. @bonienl 24a gives me the same error
  17. There is another update showing for me right now. current version: 2021.08.23a new version: 2021.08.24 pressing the update button gives me the following error.
  18. I bet you had that feature already in the app why should it ask for permissions like USE_BIOMETRIC and USE_FINGERPRINT 😂
  19. @jbrodriguez I checked a couple other apps for backing up APKs and I found one which backed up all split APKs from that new format and on my main phone V5.0.6 is running now. Thanks for the hint with the new split file format 😘 What's with my feature request? Are you already on it? Just kidding 😂 Would be nice if in the future the app start can be protected by a passcode or via finger print.
  20. So if I understand the new format correctly, as a developer delivering new updates is easier and smaller now. You kinda update only parts of the app. But on the enduser device your app still exists as an APK, right? I grabbed that APK and sideloaded it on my main phone and the install went fine. This doesn't explain, why the app won't launch. Did the app permissions changed compared to version 4? Is there a way to force the app to start in a debug mode so I can get some logs for you? Or do you have a test build for me with debug enabled? i'am kinda relativly sure that feature existed. If not, see it as a feature request 😄
  21. @jbrodriguez I have another problem with the Android version of the app starting with v5. I Tried 5.0.2, 5.0.4 and yesterday v5.0.6. and none are even starting on my phone. Version 4.17 is still working fine, but let me explain a bit more that might help. My phone is a Pixel5 with the custom AOSP based ROM CalyxOS installed with MicroG services to gain some of the google features like push notifications and access to google services. I don't use any Google accounts on that phone and have no access to the play store directly on this phone. The account I baught your app with is still active and I have to use it on a temporary phone to download app updates for paid apps like yours, back them up and install the apk on my Pixel. This procedure worked flawless for me until v5. The temporary phone is an old Galaxy S3 and is only used for this and is off if I don't need an update. Paid Apps can't be updated with the build in F-Droid or Aurora store under CalyxOS and I'am fine with that. I only have 2 paid apps anyways. App version 4.17 installs fine and works without issues. App version 5 was the first one I coudn't use. Clearing cache of the old version, uninstall it, install newest version, so fine so good. As soon as I try to start your app, nothing happens. No error message, nothing. Is there a way I can help to diagnos the issues and make that app work again? I know I'am a special case, but it would be nice to have an up to date version of your app working again on my privacy friendly phone where everything is working except of your really helpful app, and btw. in which version did you removed the password/fingerprint lock option inside the app? This was a feature I requested some time ago and you implemented it back than 😔
  22. First of all, don't use all available cores for your VM and especially not the core 0 and it's HT. Unraid always uses these core for itself to manage stuff in the background. Second thing, you have 2x 6core Xeons in your system, try it first to ONLY use the cores from a single CPU. 1-5 + HT or 6-11 + HT or even less and don't mix the cores from the different CPUs.
  23. Is nen Fehler, der nix mit dem Certbot selbst zu tun hat. Da haben die Jungs und Mädels, die SWAG bereitstellen nen Fehler drin gehabt. Bei mir wurde ne yt-downloader.conf bemängelt, die ich selbst nie erstellt oder den dazugehörigen Docker verwendet hab. Auskommentieren, Umbenennen oder löschen der Datei schafft abhilfe. Neustart oder Update des Containers generiert die Vorlagen eh neu. Wer bei der automatischen Erneuerung der Certs mit certbot Probleme haben sollte, sollte auch mal schauen, ob in der Firewall/Router (bei mir Pfsense) nen Geoblocking aktiv ist. Wenn ja, wie bei mir mit aktivem pfBlockerNG GeoIP Filer, dann diesen kurz abschalten und den Container neustarten.
  24. i get similar errors since last update which stops SWAG from staring up nginx: [emerg] "proxy_redirect" directive is duplicate in /config/nginx/proxy-confs/youtube-dl.subfolder.conf:22 nginx: [emerg] "proxy_redirect" directive is duplicate in /config/nginx/proxy-confs/youtube-dl.subfolder.conf:22 nginx: [emerg] "proxy_redirect" directive is duplicate in /config/nginx/proxy-confs/youtube-dl.subfolder.conf:22 nginx: [emerg] "proxy_redirect" directive is duplicate in /config/nginx/proxy-confs/youtube-dl.subfolder.conf:22 nginx: [emerg] "proxy_redirect" directive is duplicate in /config/nginx/proxy-confs/youtube-dl.subfolder.conf:22 nginx: [emerg] "proxy_redirect" directive is duplicate in /config/nginx/proxy-confs/youtube-dl.subfolder.conf:22
  25. Die original MS Isos sollten eigentlich von Haus aus garnicht mit virtio Treibern fürs Netzwerk daher kommen. Wie ich777 schon erwähnte sollte Standard bei der Windows Installation da garkein Internetzugriff möglich sein bis man auf dem Desktop ist und von Hand die Treiber von dem virtio.iso installiert. @DataCollector Kann es sein, dass du die Treiber in dein Windows Iso integriert hast? Anders kommt Windows nicht an die Treiber direkt bei einer Neuinstallation.