thomas

Members
  • Posts

    76
  • Joined

  • Last visited

Everything posted by thomas

  1. Pinging 8.8.8.8 for internet alive, I don't think is the best practice. Maybe you should ping the first DNS server, that is defined, if it's external, or resolve an internet domain using 2 different DNS servers, from different providers...
  2. See below the results root@unRAID:~# traceroute 9.9.9.9 traceroute to 9.9.9.9 (9.9.9.9), 30 hops max, 60 byte packets 1 192.168.1.254 (192.168.1.254) 16.803 ms 16.798 ms 16.794 ms 2 * * * 3 * * * 4 149.248.92.141 (149.248.92.141) 34.132 ms 34.142 ms 41.240 ms 5 woodynet.torontointernetxchange.net (206.108.34.115) 41.204 ms 41.201 ms 41.197 ms 6 dns.quad9.net (9.9.9.9) 39.981 ms !X 15.685 ms !X 20.601 ms !X root@unRAID:~# traceroute 1.0.0.1 traceroute to 1.0.0.1 (1.0.0.1), 30 hops max, 60 byte packets 1 192.168.1.254 (192.168.1.254) 16.792 ms 16.785 ms 16.779 ms 2 * * * 3 * * * 4 149.248.92.141 (149.248.92.141) 25.321 ms 25.323 ms 25.318 ms 5 he.ip4.torontointernetxchange.net (206.108.34.112) 26.868 ms 26.869 ms 30.658 ms 6 198.32.181.56 (198.32.181.56) 33.326 ms cloudflare.ip4.torontointernetxchange.net (206.108.34.208) 17.442 ms as13335.toronto.megaport.com (206.53.203.8) 18.906 ms 7 1dot1dot1dot1.cloudflare-dns.com (1.0.0.1) 17.367 ms 17.353 ms 17.349 ms root@unRAID:~# traceroute 8.8.8.8 traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets 1 192.168.1.254 (192.168.1.254) 12.698 ms 12.693 ms 12.688 ms 2 192.168.1.254 (192.168.1.254) 3003.381 ms !H 3003.391 ms !H 3003.389 ms !H root@unRAID:~# traceroute 8.8.4.4 traceroute to 8.8.4.4 (8.8.4.4), 30 hops max, 60 byte packets 1 192.168.1.254 (192.168.1.254) 12.723 ms 12.722 ms 12.718 ms 2 192.168.1.254 (192.168.1.254) 3005.614 ms !H 3005.617 ms !H 3005.620 ms !H
  3. Unfortunately DD-WRT is not that smart. What I wanted to accomplish is all the devices that have google DNSs as default, to revert to the one that is running in the network. Those rules accomplish that. If I'm checking the DNS requests using the google DNSs they timeout.
  4. Destination LAN NET Subnet Mask Gateway Flags Metric Interface default 0.0.0.0 1xx.xx.x.x UG 0 WAN 8.8.4.4 255.255.255.255 192.168.1.254 UGH 2 LAN & WLAN 8.8.8.8 255.255.255.255 192.168.1.254 UGH 2 LAN & WLAN 1xx.xx.x.x 255.255.255.224 * U 0 WAN 169.254.0.0 255.255.0.0 * U 0 LAN & WLAN 192.168.1.0 255.255.255.0 * U 0 LAN & WLAN Those IPs are redirected to the router's IP, but this shouldn't matter as I'm using different DNSs.
  5. This is the result from the command and it looks ok. root@unRAID:~# cat /etc/resolv.conf # Generated DNSv4 entries: nameserver 9.9.9.9 nameserver 1.0.0.1 # Generated DNSv6 entries: I have a dd-wrt router with a static route for 8.8.8.8 and 8.8.4.4. As soon I remove those the update starts working...
  6. I have DNS1 set to 9.9.9.9 and DNS2 set to 1.0.0.1, but I'm blocking at the router level 8.8.8.8 and 8.8.4.4. With these settings, the update status for unraid and plugins is always "unknown". If I remove the blocking for google DNS, the update status works right away. I'm thinking that the checking for updates are done using only google DNSs and not the ones specified in the network setings. Attached is the diagnostics. unraid-diagnostics-20180803-1537.zip
  7. You can extract the .ova file with 7zip or another unarchiver and you'll see the 2 vmdk files
  8. You have to download the Virtualbox VM from GNS3 site, convert the two images from vmdk to raw. Then create a Linux VM and assign the 2 images manually. The VM needs to be Q35 type with SeaBios. After that it will boot normally and you can check it with VNC. You don't need to install Ubuntu or Virtual box.
  9. Sometimes the AMD gets "stuck" and the only way to recover is by powering down the unraid server and starting fresh. This is the case with my R9 370. This usually happens if I force close any VMs. Lately I'm passing through the GPU with the vbios file so I can use OVMF and I'm more careful with my VMs and it's working fine.
  10. Try to pass a graphics ROM BIOS and the "... expecting 0xaa55, got 0xffff" error should disappear. Also try to start the VM installation after shutting down and powering up the server, to see if it makes a difference...
  11. I created some files with whitespaces and they are properly identified. See the results below. LE: I found the files with the problem. See below. Now there are no issues. Thanks
  12. Hi, When I'm running the extended test I always get errors, but I can't find the files/directories with issues. See the picture below. How can I find them? Thanks, Thomas
  13. Hi, Can you add also this new gui for aria http://ariang.mayswind.net? Maybe on another port? Or create a new docker? I think this one is better... Thanks.
  14. Use SeaBIOS instead of OVMF for the VM and it should work. Your AMD doesn't have UEFI support, for OVMF use, though you might find some patched BIOSes on the internet if you want to pass the ROM file...
  15. I checked and I had one script being executed at startup of the array, I disabled it and now it's working properly. The script was finding and deleting some temp files on the array, but my VMs are located on the cache drive (SSD) so I thought they won't be impacted by this... If you have any scripts running at startup, the VMs will wait until the scripts are finished in order to load, or they are competing for resources (cpu,ram) and eventually will load? Thanks
  16. When I enable this plugin the time between the unraid displays the console login and the autostart of VM is increased to 60+ seconds. Without this plugin it's around 5 seconds. Is there anything that I should/can do to make this plugin "faster" to load? Thanks LE: I'm on 6.4.0, if it matters...
  17. I have an R9 390 and Intel cpu with integrated graphics, but I'm using only the R9 to display unraid console and to pass it through for my VMs and everything works properly. I don't think you need two discrete GPUs...
  18. Try to create a SeaBIOS VM intead of OVMF and see if it's working properly to pass through the GPU. If it's working fine, either use the SeaBIOS or power down the whole server and try again the OVMF one. Some AMD gpus have an issue with resetting and they can't be properly pass through if a crash or "force stop" occurs.
  19. I used the VirtualBox VM and I installed it with Q35, SeaBIOS and manually assigning the 2 img disks, after converting them from vmdk images to raw. You need to use "kvm-intel.nested=1" if you want to have KVM support, otherwise it will complain that it will be slow... Everything works properly.
  20. Another thing that you can try is to not pass the HDMI to the VM, pass only the graphic card and see if that helps. I have seen that most of the time if I try to shutdown and start my VM in a fast succession it will complain that the HDMI part is still used by previous used VM although the shutdown was successful and the screen is blank...
  21. In my case, it's working only if the bios rom is passed to the HDMI part. If it was passed to the 0000:01:00.0 the screen will remain blank...
  22. I think it's related to this https://forum.level1techs.com/t/linux-host-windows-guest-gpu-passthrough-reinitialization-fix/121097 . I have an R9 370 which behaves roughly the same. If I'm using the the Intel igd as primary gpu, most of the time the AMD R9 pass-through will fail with "Refused to change power state, currently in D3". If the R9 is the primary gpu, I don't have any issues with "Refused to change power...", but I get "Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff" and I can only boot Seabios VMs. For OVMF, it only works for first VM start, then I have to power down and then unplug the unRaid server to make it work again. After a lot of testing, I managed to make the OVMF boot to always start by providing the video rom file details only to the HDMI part ( 0000:01:00.1) in the XML file.
  23. You might try to dump the BIOS and add it to the VM xml. see post
  24. Thanks. I managed to fix the problem. At first, I tried to use the bios that I found on the techpowerup, but still the screen was blank so I use VNC as primary display and my GPU as secondary. That showed me an error about invalid ROM right after the OS was booting. I managed to get the right bios and add it to the VMs, but the machine wasn't booting all the time, or sometimes the GPU wasn't properly initialized. Testing further I realized that I was booting UNRAID with the GPU being the console display, and not the integrated graphics, which prevented OVMF from working properly and GPU's bios wasn't read properly from the card. After changing them in BIOS, everything is working normally and the OVMF works without providing any rom file. Now, for all the Seabios machines that I have may take up to 10 second just to show the seabios screen... This was my main reason for using my GPU as the console display... Anyway I'll change my VMs to OVMF and hopefully they'll work. Thanks again.