SimpleDino

Members
  • Posts

    65
  • Joined

  • Last visited

Recent Profile Visitors

359 profile views

SimpleDino's Achievements

Rookie

Rookie (2/14)

4

Reputation

  1. Thanks, recreating the image helped. I have not figured it unfortunately, the only big change I've made is updating the OS. Is there any good guide for frp, image --> folder? Thanks in advance! I run memtest and got zero errors this time...but I did this after I solved the issue above with @Squid's help and a restart.
  2. I backed up the flash drive before updating from 6.10.2 to 6.10.3. After updating Docker Services refuse to start, please see warning texts below. How can those warnings be fixed? I've attached diagnostics as well. tower-diagnostics-20220617-1305.zip
  3. Bump! Any ideas? Skickat från min iPhone med Tapatalk
  4. I do not know if this questions has been answered, at least I couldn't find any. On Plex (linuxserver.io) can I upgrade the libraries within plex as seen in the picture or will this mess everything up? (see attached screenshot)
  5. I have not upgraded yet to RC4, still on RC2 Maybe @SpaceInvaderOne can confirm? Br,
  6. @SpaceInvaderOne Thanks a lot for the container update and your guides per usual! Appreciated! @ghost82 Thanks for all of your good and explanatory inputs! You have helped a lot of rookies like me! Just want to report a success for once and not an issue/error. Steps I took when updating to new macinabox and using the new scripts on current VMs with complete success: Remove Macinabox plus the scripts and also rm -r /mnt/user/appdata/macinabox. Download Macinabox with the desired new settings, wait for scripts to load. Copy the name of whatever macOS VM you want to update with and input it into the new helper script. Run script twice, now XML of that VM is updated. Now I can make whatever changes (remove/attach PCI & USB devices, HDDs/SSDs) I want in the VM and then just run the script once or twice without further manual XML editing. All inputs are welcome if I have forgotten or misunderstood something in the update Goodnights!
  7. I need help with containers that are routed through NordVPN & DelugeVPN container. On the local network I can access all of the routed containers WebUI but remotely (outside of lan network) when accessing through the wireguard vpn I can not access the same containers WebUI. Do I make any sense? I've tried these peers without any luck: Remote access to server Remote access to lan Remote tunneled access I have not tried lan to lan access, because honestly I do not know how to set this up if this is the solution.
  8. Yeah sorry, I see others has already commented. I forgot the install part in sudo apt install speedtest-cli. I have edited the post now also.
  9. Don't know why it doesn't work for you. could post your input commands and the following texts?
  10. For anyone that wants to test the speed of the container they can run speedtest-cli: Open NordVPN console and run these commands: sudo apt update sudo apt install speedtest-cli speedtest-cli If you reboot or restart the container then you must run the commands again.
  11. It does not work which is very odd. Because all the VMs work perfectly with VNC. Probably something wrong with the mappings. Anyhow I will continue troubleshooting this odd behaviour hopefully I'll get figured out or just reinstall VM's. unRAID is very fragile when it comes to changes in vm (I've probably mentioned this earlier).
  12. Yes, true. I do have the Vendor plugin installed. It worked during one reboot. But now I only get to Shell Script (I do type exit and continue) and no further. Something is wrong, maybe the order of BUS:s for the vdisk or something? ErrorWarningSystemArrayLogin -device pcie-root-port,port=0x8,chassis=6,id=pci.6,bus=pcie.0,multifunction=on,addr=0x1 \ -device pcie-root-port,port=0x9,chassis=7,id=pci.7,bus=pcie.0,addr=0x1.0x1 \ -device pcie-root-port,port=0xa,chassis=8,id=pci.8,bus=pcie.0,addr=0x1.0x2 \ -device pcie-root-port,port=0xe,chassis=9,id=pci.9,bus=pcie.0,addr=0x1.0x6 \ -device pcie-pci-bridge,id=pci.10,bus=pci.1,addr=0x0 \ -device ich9-usb-ehci1,id=usb,bus=pcie.0,addr=0x7.0x7 \ -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pcie.0,multifunction=on,addr=0x7 \ -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pcie.0,addr=0x7.0x1 \ -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pcie.0,addr=0x7.0x2 \ -device virtio-serial-pci,id=virtio-serial0,bus=pci.2,addr=0x0 \ -blockdev '{"driver":"file","filename":"/mnt/user/domains/Windows 11/vdisk1.img","node-name":"libvirt-3-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-3-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"qcow2","file":"libvirt-3-storage","backing":null}' \ -device virtio-blk-pci,bus=pci.4,addr=0x0,drive=libvirt-3-format,id=virtio-disk2,bootindex=1,write-cache=on \ -blockdev '{"driver":"file","filename":"/mnt/user/isos/Windows/Win11_Swedish_x64.iso","node-name":"libvirt-2-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-2-format","read-only":true,"driver":"raw","file":"libvirt-2-storage"}' \ -device ide-cd,bus=ide.0,drive=libvirt-2-format,id=sata0-0-0,bootindex=2 \ -blockdev '{"driver":"file","filename":"/mnt/user/isos/Virtio/virtio-win-0.1.208-1.iso","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-1-format","read-only":true,"driver":"raw","file":"libvirt-1-storage"}' \ -device ide-cd,bus=ide.1,drive=libvirt-1-format,id=sata0-0-1 \ -netdev tap,fd=37,id=hostnet0 \ -device virtio-net,netdev=hostnet0,id=net0,mac=52:54:00:0f:e5:9e,bus=pci.5,addr=0x0 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0 \ -chardev socket,id=charchannel0,fd=38,server=on,wait=off \ -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ -tpmdev emulator,id=tpm-tpm0,chardev=chrtpm \ -chardev 'socket,id=chrtpm,path=/run/libvirt/qemu/swtpm/2-Windows 11-swtpm.sock' \ -device tpm-tis,tpmdev=tpm-tpm0,id=tpm0 \ -device usb-tablet,id=input0,bus=usb.0,port=1 \ -audiodev id=audio1,driver=none \ -device 'vfio-pci,host=0000:0f:00.0,id=hostdev0,bus=pci.3,multifunction=on,addr=0x0,romfile=/mnt/user/isos/vbios/rx 480v3.rom' \ -device vfio-pci,host=0000:0f:00.1,id=hostdev1,bus=pci.3,addr=0x0.0x1 \ -device usb-host,hostdevice=/dev/bus/usb/003/008,id=hostdev2,bus=usb.0,port=2 \ -device usb-host,hostdevice=/dev/bus/usb/005/003,id=hostdev3,bus=usb.0,port=3 \ -device usb-host,hostdevice=/dev/bus/usb/003/007,id=hostdev4,bus=usb.0,port=4 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on char device redirected to /dev/pts/0 (label charserial0) 2022-01-25T09:09:22.231649Z qemu-system-x86_64: vfio: Cannot reset device 0000:0f:00.1, no available reset mechanism. 2022-01-25T09:09:22.235623Z qemu-system-x86_64: vfio: Cannot reset device 0000:0f:00.1, no available reset mechanism. It's RX 480 GB.
  13. No, first it's not possible and I try to be thorough! It's this message that comes up on all VM's with GPU & sound part passed through: 2022-01-25T07:24:07.859000Z qemu-system-x86_64: vfio: Cannot reset device 0000:0f:00.1, no available reset mechanism. 2022-01-25T07:24:07.863951Z qemu-system-x86_64: vfio: Cannot reset device 0000:0f:00.1, no available reset mechanism. But I've notice with the amd vendor plugin, when win11 sometimes crashes or does not get past uefi shell script POST install then I can still run the gpu in Fedora VM. So no need for @Squids fantastic script (this time) 🙂. Edit: Fedora also crashes periodically and we are back to shell script!