domingothegamer

Members
  • Posts

    3
  • Joined

  • Last visited

Everything posted by domingothegamer

  1. I am attempting to install a Windows Server 2019 VM with no luck. Upon starting the VM I receive the “Loading Files…” dialogue which then loops back to the “Press any key to boot from CD or DVD” prompt. This is as far as I have been able to get. I found some errors in the LibVirt logs for the VM manager but don’t know what to make of them, I assume this has to due with the issue I am running into. Error is as follows: error : virDomainPCIAddressFlagsCompatible:415 : XML error: The device at PCI address 0000:00:02.2 cannot be plugged into the PCI controller with index='0'. It requires a controller that accepts a pcie-root-port. Here is a list of the various steps I have taken to try and resolve the issue; • Setting “logical CPU’s” to 1 thread • Using both OVMF and SeaBIOS • Using various versions of both i440fx & Q35 chipsets • Attempting to install various version of Win Ser and Win10 Desktop • Cycling through all 4 options for the CDRom Bus • Setting my primary vDisk Location to the Array as well as a mounted “Non-Array” drive All other VM options were left stock for consistency between attempts. Here is a breakdown of the hardware the server is running on • Mobo: ASUSTeK COMPUTER INC. ROG CROSSHAIR VI EXTREME Version Rev 1.xx • BIOS Ver: 7901 (07/30/2020) • Memory: 64 GiB DDR4 • CPU: AMD Ryzen 7 2700 Eight-Core @ 3200 MHz • HBA: LSI00301 SAS 9207-8i (X2) Motherboard BIOS configuration is mostly stock except, adjusted setting are as follows; - Fast boot Disabled - Wake on LAN Enabled - All AMD Boosting features are Disabled - Virtualization is Enabled - CSM Auto (I’ve had some problems with this but am unsure if it is the root cause) I have noticed that there have been very mixed reports on CSM and weather to have it enabled or not, various users have reported that their system booting into Unraid seems to be contingent on weather CSM is on of off, I have also seen claims that it can cause issues with VM’s. Here is a set of various logs: System Devices - https://pastebin.com/beW1jrrY Diagnostics Report has been attached to post. I’ve tried everything I can personally think of to solve this problem on my own with no success. storage-diagnostics-20210119-1941.zip
  2. Checked it out and yeah seems accurate to me. Hmm. It's not like cloudberry doesn't work at all, works fine on Backblaze and Wasabi among other things i've tried; though a bit of a noob on using my own solution through MinIO. Edit1: You know it might be truenas server system time inconsistency. Tested with duplicati and got a similar error. I'll see what's going on. Edit2: Fixed my problem, didn't configure Truenas enough on proper timezones and NTP servers out of the box. My end. Thanks!
  3. Hello! I was wondering if anyone else was having issues with the current version of the docker. I'm having time zone issues using MinIO which in my case is hosted on Truenas core s3 service feature. It sees the SSL and accepts connection, but gives a time zone issue. Searched earlier in this topic and seems to be something that has to be fixed on the build's end. Thanks for your time!