planetwilson

I am getting an error when it backs up syslog which causes the whole job to fail. [22.01.2023 08:43:43] Verifying Backup sonarr4K [22.01.2023 08:43:43] Backing Up: swag [22.01.2023 08:43:47] Verifying Backup swag [22.01.2023 08:43:48] Backing Up: syslog-192.168.44.10.log [22.01.2023 08:43:48] Verifying Backup syslog-192.168.44.10.log syslog-192.168.44.10.log: Size differs [22.01.2023 08:43:48] tar verify failed! [22.01.2023 08:43:48] Backing Up: syslog-192.168.44.10.log.1 [22.01.2023 08:43:48] Backing Up: tailscale [22.01.2023 08:43:48] Backing Up: tautulli Syslog will update though during the backup process won't it? If it helps, I have unpaid acting as a syslog server posting its own syslog to itself, that is so the syslog data is retained post reboot. Perhaps the logic is only expecting a single syslog file?

Confirmed this workaround works for me for now. My VPN provider knows about the issue and is working on new certs.

Also my cert is SHA-256 so I don't understand how it is too weak?

What was the workaround please? This has happened to me as well (has been working fine for years, I guess OPenSSL or similar updated and I don't have any options for stronger intermediate certs)

I too am trying to get this to work. I have an argo tunnel setup through Cloudflare and that all looks to be working. I have a single ingress rule sending everything to my swag docker and from there to various dockers. I have tried in the nginx config for any particular app to place the websocket specific http upgrade code but it hasn't made any difference. I am not sure if it is the argo tunnel or nginx which is the issue currently.

Did you ever get to the bottom of this?

OMG...I have been running for several years it would seem plugged into the surge only socket....I only came to this post as I just had a power cut and got an immediate parity check which didn't feel right.

I found that updating from Penryn to passthrough of the host game me a 20% approx speed boost. My CPU params become:- <qemu:arg value='-cpu'/> <qemu:arg value='host,vendor=GenuineIntel,+hypervisor,+invtsc,kvm=on,+fma,+avx,+avx2,+aes,+ssse3,+sse4_2,+popcnt,+sse4a,+bmi1,+bmi2'/> Geekbench with Penryn: Single 835, Multi 3477 Geekbench with Host: Single 1021, Multi 3736 (4 cores passed to VM)

Ah brilliant thanks, didn't know I could do that.

I bought a second hand drive from ebay but having plugged it in it says UDMA CRC errors (raw value = 482) Now from looking about this could simply be a bad cable from the person who previously had the drive and SMART tests come back fine. Should I return the drive or just keep an eye on it and ensure it doesn't go up? unRAID keeps warning me though every time I reboot the box...

Any plans to include the required libraries for Intel hardware based HDR->SDR tone mapping? https://support.plex.tv/articles/hdr-to-sdr-tone-mapping/

How did you work out which ones are good for shucking? Anything to look for?

I have the tips and tweaks plugin installed and wondering how much difference the power saving vs performance setting for unraid will have on VM peformance when playing a game? Looking at CPU speeds, it runs constantly at full whack when in performance, but drops to the low 800MHz or so when idle. But it still does boost up if there is work to do for the processor...so is there an issue in leaving it on power saving which is the default setting after all? The propertion of time I am playing games on it is very small compared to the time the server being on 24/7 doing it's unraid thing.

As an update to this - I actualy stopped doing this and just passed through a separate USB 3 card instead because the unplugging of the TB3 cable from the AIC card to my MBP and back again causes weirdness with the VM. The USB controller which is part of the monitor gets in a stuck state and can't be used without a reboot. Passing through individual USB devices or a 3rd card is a better solution

I’d like to know this too. The docker page suggests so but there’s nothing in the gui for it. I get an error about 2020/10/27 22:30:55 Failed to get the value from the keyring: keyring/dbus: Error connecting to dbus session, not registering SecretService provider: dbus: DBUS_SESSION_BUS_ADDRESS not set does that mean it’s not checking? will it stop working?

One of SpaceInvader's videos talks about a workaround to reset the gfx card without rebooting the server using a script:- https://www.youtube.com/watch?v=0uZODoPQH9c

I have a Gigabyte Titan Ridge AIC. It takes 2 DisplayPort cables from my Radeon 570 as inputs and outputs on a thunderbolt 3 cable to my LG 5K Ultrafine monitor - the one LG made in partnership with Apple. I love this monitor and didn't want to only be able to use it with my Macbook but also my gaming VM and this works perfectly for that. The card itself appears as several different devices under System devices and passing those through never really worked correctly. The card mixing the DisplayPort inputs and outputting via TB3 only requires power so doesn't need to be passed to the VM. However I wanted to be able to use the USB ports on the back of the monitor so I had a single mouse and keyboard whether using Mac or PC. Once the monitor is hooked up to the AIC card it exposes a USB controller device which I can then passthrough as a PCI device to the VM. This works best. Passing individual USB devices was very flaky and they would often disappear.

Okay found the solution - I was being daft mixing up passing individual USB devices and controllers. Once I isolated the USB controller that is on the LG 5K monitor (which has the same chipset name as a separate card I use for a hackintosh hence much confusion) - I can pass that alone using VIFO-PCI config and everythings works just great.

I have a Windows 10 VM and a Gigabyte THunderbolt 3 AIC working fine with an LG 5K ultrafine monitor. When I start up I can pass all the USB devices it finds including those plugged into the LG monitor. Everything works swimmingly until I either reboot the VM or I unplug the TB3 cable. Plugging it back in or waiting for the VM to come up again leads to no USB devices being available. They don't show in the system devices list any more so I can't choose them in the hot plug/unplug plugin. My log looks like this when it happens:- Sep 7 19:46:37 PWNAS kernel: xhci_hcd 0000:40:00.0: xHCI host controller not responding, assume dead Sep 7 19:46:37 PWNAS kernel: xhci_hcd 0000:40:00.0: HC died; cleaning up Sep 7 19:46:37 PWNAS kernel: usb 7-1: USB disconnect, device number 2 Sep 7 19:46:37 PWNAS kernel: usb 7-1.3: USB disconnect, device number 3 Sep 7 19:46:37 PWNAS kernel: usb 7-1.3.1: USB disconnect, device number 7 Sep 7 19:46:37 PWNAS kernel: usb 8-1: USB disconnect, device number 2 Sep 7 19:46:37 PWNAS kernel: usb 8-1.3: USB disconnect, device number 5 Sep 7 19:46:37 PWNAS kernel: usb 8-1.3.2: USB disconnect, device number 7 Sep 7 19:46:37 PWNAS kernel: xhci_hcd 0000:40:00.0: Timeout while waiting for configure endpoint command Sep 7 19:46:37 PWNAS kernel: usb 7-1.4.1: Not enough bandwidth for altsetting 1 Sep 7 19:46:37 PWNAS kernel: usb 7-1.3.3: USB disconnect, device number 8 Sep 7 19:46:37 PWNAS kernel: usb 7-1.3.3.1: USB disconnect, device number 9 Sep 7 19:46:37 PWNAS kernel: usb 8-1.3.4: USB disconnect, device number 6 Sep 7 19:46:37 PWNAS kernel: usb 8-1.4: USB disconnect, device number 3 Sep 7 19:46:37 PWNAS kernel: usb 8-1.4.3: USB disconnect, device number 4 Sep 7 19:46:37 PWNAS kernel: usb 7-1.3.3.3: USB disconnect, device number 11 Sep 7 19:46:37 PWNAS kernel: usb 7-1.4: USB disconnect, device number 4 Sep 7 19:46:37 PWNAS kernel: usb 7-1.4.1: USB disconnect, device number 5 Sep 7 19:46:37 PWNAS kernel: usb 7-1.4.2: USB disconnect, device number 6 Sep 7 19:47:53 PWNAS kernel: usb 1-11: new low-speed USB device number 8 using xhci_hcd Sep 7 19:47:53 PWNAS kernel: usb 1-11: device descriptor read/64, error -71 Sep 7 19:47:54 PWNAS kernel: usb 1-11: device descriptor read/64, error -71 Sep 7 19:47:54 PWNAS kernel: usb 1-11: new low-speed USB device number 9 using xhci_hcd Sep 7 19:47:54 PWNAS kernel: usb 1-11: device descriptor read/64, error -71 Sep 7 19:47:54 PWNAS kernel: usb 1-11: device descriptor read/64, error -71 Sep 7 19:47:54 PWNAS kernel: usb usb1-port11: attempt power cycle Sep 7 19:47:55 PWNAS kernel: usb 1-11: new low-speed USB device number 10 using xhci_hcd Sep 7 19:47:55 PWNAS kernel: usb 1-11: Device not responding to setup address. Sep 7 19:47:55 PWNAS kernel: usb 1-11: Device not responding to setup address. Sep 7 19:47:55 PWNAS kernel: usb 1-11: device not accepting address 10, error -71 Sep 7 19:47:55 PWNAS kernel: usb 1-11: new low-speed USB device number 11 using xhci_hcd Sep 7 19:47:55 PWNAS kernel: usb 1-11: Device not responding to setup address. Sep 7 19:47:56 PWNAS kernel: usb 1-11: Device not responding to setup address. Sep 7 19:47:56 PWNAS kernel: usb 1-11: device not accepting address 11, error -71 Sep 7 19:47:56 PWNAS kernel: usb usb1-port11: unable to enumerate USB device Sep 7 19:48:59 PWNAS avahi-daemon[8269]: Interface vnet1.IPv6 no longer relevant for mDNS. Sep 7 19:48:59 PWNAS avahi-daemon[8269]: Leaving mDNS multicast group on interface vnet1.IPv6 with address fe80::fc54:ff:fe85:3e36. Sep 7 19:48:59 PWNAS kernel: br0: port 3(vnet1) entered disabled state Sep 7 19:48:59 PWNAS kernel: device vnet1 left promiscuous mode Sep 7 19:48:59 PWNAS kernel: br0: port 3(vnet1) entered disabled state Sep 7 19:48:59 PWNAS avahi-daemon[8269]: Withdrawing address record for fe80::fc54:ff:fe85:3e36 on vnet1. Sep 7 19:49:00 PWNAS kernel: vfio-pci 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Is there any way to make the server attempt to re-scan or discover devices?

What have you tried so far?

SpaceInvader's videos are very good but those methods using Clover in general present the Mac as an older Penryn machine. I had mine up and running as one of those but it was fairly easy to switch over to OpenCore and have it present as an iMac pro in my case. Also this:- https://github.com/Leoyzen/KVM-Opencore

Is your M.2 slot one which supports NVMe drives or only SATA. The Windows VM will benfit from being on the fast drive it can be. The cache drive will be fine as a SATA SSD I think. I would personally have the VM running on its own SSD. I have an M.2 NVMe drive for desktop VMs with GPU passthrough and a normal SATA SSD for a cache drive. It really is easier to just leave the machine running than start messing about with sleep modes and the effect on VMs etc. I actually downgraded from a 14 core/96GB unraid box to a 6 core i5/32GB machine as it used a lot less power, to the point where I don't care about leaving it running 24/7. My family are used to running Macs so I have a "desktop" iMac in my office they can just sit down and start using which is a VM with a Radeon RX570 passed through. when I want a game of something, I turned that off and fireup a Win 10 VM instead. Once you start down the docker route, you can run things like a Plex docker for a media server - whcih could use your iGPU for transcoding as well.

So using HOOB/Homebridge I’ve got the ability to turn on my VMs by asking Siri using my Apple Watch! Feels quite cool but I would still like to sleep/wake cleanly with macOS

I had the same, i could change the container port value, I had to delete the old mapping completely and create a new one like in the image. It then worked on :8282 for me

Thanks for your script @naughty beatle it has given me some ideas. I have some iOS Shortcuts on my daughter and wife's phones which simply make an SSH call with virsh but I don't like it because they have to have my root password in there. I wanted something a bit easier like a button but Alexa and voice control might work too... Did you get to the bottom of clean shutdown of MacOS? I haven't ben able to find a way to get it to respond to the qemu shutdown. I suppose you might need to have something listening inside the VM which initiates the shutdown but that feels very messy