hi, wondering if anyone can help me please. i upgraded my cpu to e5-2699 from a 17-5820. and started off ok. but then after another restart the pf sense became unable to load so i did a fresh install of pf sense and the fixed that. but my windows 10 vm or linux mint vm wont start. they give different errors each time or freezes and gtx 1070ti wont start up at all

 

execution error

internal error: qemu unexpectly closed monitor: 2020- 11- 01t16:20:01.871733z qemu-system-x86_64: -device pcie-pci-bridge,id=pci.8,bus=pc1,addr=0x0: bus 'pci.1' not found

 

if you try a fresh install of windows 10. after install and try firing up it come with this..

 

execution error

cannot access storage file ' ':no such file or directory

 

some time windows 10 will start but only on the second radeon card and not the primary gtx1070ti card

any ideas please??

 

 

 

 

 

the log and libvirt log below

 

 

 

log

-name 'guest=Windows 10 Big Tv GTX1070 RADION,debug-threads=on' \
-S \
-object 'secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-9-Windows 10 Big Tv GT/master-key.aes' \
-machine pc-i440fx-5.0,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off \
-cpu host,migratable=on,hv-time,hv-relaxed,hv-vapic,hv-spinlocks=0x1fff,hv-vendor-id=none,host-cache-info=on,l3-cache=off \
-m 10240 \
-overcommit mem-lock=off \
-smp 22,sockets=1,dies=1,cores=11,threads=2 \
-uuid 2b3572b2-823e-59b4-4895-378913a75c60 \
-display none \
-no-user-config \
-nodefaults \
-chardev socket,id=charmonitor,fd=33,server,nowait \
-mon chardev=charmonitor,id=monitor,mode=control \
-rtc base=localtime \
-no-hpet \
-no-shutdown \
-boot strict=on \
-device qemu-xhci,p2=15,p3=15,id=usb,bus=pci.0,addr=0x7 \
-device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 \
-blockdev '{"driver":"host_device","filename":"/dev/sdb","node-name":"libvirt-1-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \
-blockdev '{"node-name":"libvirt-1-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"raw","file":"libvirt-1-storage"}' \
-device virtio-blk-pci,bus=pci.0,addr=0x4,drive=libvirt-1-format,id=virtio-disk2,bootindex=1,write-cache=on \
-netdev tap,fd=36,id=hostnet0 \
-device virtio-net,netdev=hostnet0,id=net0,mac=52:54:00:78:99:d1,bus=pci.0,addr=0x2 \
-chardev pty,id=charserial0 \
-device isa-serial,chardev=charserial0,id=serial0 \
-chardev socket,id=charchannel0,fd=38,server,nowait \
-device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \
-device vfio-pci,host=0000:03:00.0,id=hostdev0,x-vga=on,bus=pci.0,addr=0x5 \
-device vfio-pci,host=0000:02:00.0,id=hostdev1,bus=pci.0,addr=0x6 \
-device vfio-pci,host=0000:03:00.1,id=hostdev2,bus=pci.0,addr=0x8 \
-device vfio-pci,host=0000:02:00.1,id=hostdev3,bus=pci.0,addr=0x9 \
-device usb-host,hostbus=3,hostaddr=13,id=hostdev4,bus=usb.0,port=1 \
-device usb-host,hostbus=3,hostaddr=12,id=hostdev5,bus=usb.0,port=2 \
-sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \
-msg timestamp=on
2020-11-02 10:39:42.846+0000: Domain id=9 is tainted: high-privileges
2020-11-02 10:39:42.846+0000: Domain id=9 is tainted: host-cpu
char device redirected to /dev/pts/1 (label charserial0)

libvirt logs

2020-11-01 19:47:43.117+0000: 7783: error : virFileIsSharedFixFUSE:3384 : unable to canonicalize /mnt/user/domains/Windows 10 testing/vdisk1.img: No such file or directory
2020-11-01 19:47:43.118+0000: 7783: error : qemuOpenFileAs:3175 : Failed to open file '/mnt/user/domains/Windows 10 testing/vdisk1.img': No such file or directory
2020-11-01 19:47:43.120+0000: 7783: error : qemuDomainGetBlockInfo:11942 : invalid argument: invalid path not assigned to domain
2020-11-01 19:47:43.121+0000: 7785: error : qemuDomainGetBlockInfo:11942 : invalid argument: invalid path not assigned to domain
2020-11-01 19:47:49.300+0000: 7784: warning : qemuDomainObjTaint:6075 : Domain id=4 name='Windows 10' uuid=83f1cd0b-b0fb-b70d-29a5-3484bd475bce is tainted: high-privileges
2020-11-01 19:47:49.300+0000: 7784: warning : qemuDomainObjTaint:6075 : Domain id=4 name='Windows 10' uuid=83f1cd0b-b0fb-b70d-29a5-3484bd475bce is tainted: host-cpu
2020-11-01 19:47:51.858+0000: 7784: error : virFileIsSharedFixFUSE:3384 : unable to canonicalize /mnt/user/domains/Windows 10/vdisk1.img: No such file or directory
2020-11-01 19:47:51.858+0000: 7784: error : qemuOpenFileAs:3175 : Failed to open file '/mnt/user/domains/Windows 10/vdisk1.img': No such file or directory
2020-11-01 19:47:51.876+0000: 7782: error : virFileIsSharedFixFUSE:3384 : unable to canonicalize /mnt/user/domains/Windows 10/vdisk1.img: No such file or directory
2020-11-01 19:47:51.876+0000: 7782: error : qemuOpenFileAs:3175 : Failed to open file '/mnt/user/domains/Windows 10/vdisk1.img': No such file or directory
2020-11-01 19:47:51.879+0000: 7782: error : virFileIsSharedFixFUSE:3384 : unable to canonicalize /mnt/user/domains/Windows 10/vdisk1.img: No such file or directory
2020-11-01 19:47:51.879+0000: 7782: error : qemuOpenFileAs:3175 : Failed to open file '/mnt/user/domains/Windows 10/vdisk1.img': No such file or directory
2020-11-01 19:47:51.882+0000: 7782: error : virFileIsSharedFixFUSE:3384 : unable to canonicalize /mnt/user/domains/Windows 10/vdisk1.img: No such file or directory
2020-11-01 19:47:51.882+0000: 7782: error : qemuOpenFileAs:3175 : Failed to open file '/mnt/user/domains/Windows 10/vdisk1.img': No such file or directory
2020-11-01 19:47:51.885+0000: 7783: error : virFileIsSharedFixFUSE:3384 : unable to canonicalize /mnt/user/domains/Windows 10/vdisk1.img: No such file or directory
2020-11-01 19:47:51.885+0000: 7783: error : qemuOpenFileAs:3175 : Failed to open file '/mnt/user/domains/Windows 10/vdisk1.img': No such file or directory
2020-11-01 19:47:51.925+0000: 7784: error : qemuDomainGetBlockInfo:11942 : invalid argument: invalid path not assigned to domain
2020-11-01 19:47:51.926+0000: 7781: error : qemuDomainGetBlockInfo:11942 : invalid argument: invalid path not assigned to domain
2020-11-01 19:47:51.929+0000: 7781: error : virFileIsSharedFixFUSE:3384 : unable to canonicalize /mnt/user/domains/Windows 10 testing/vdisk1.img: No such file or directory
2020-11-01 19:47:51.929+0000: 7781: error : qemuOpenFileAs:3175 : Failed to open file '/mnt/user/domains/Windows 10 testing/vdisk1.img': No such file or directory
2020-11-01 19:47:51.946+0000: 7783: error : virFileIsSharedFixFUSE:3384 : unable to canonicalize /mnt/user/domains/Windows 10 testing/vdisk1.img: No such file or directory
2020-11-01 19:47:51.946+0000: 7783: error : qemuOpenFileAs:3175 : Failed to open file '/mnt/user/domains/Windows 10 testing/vdisk1.img': No such file or directory
2020-11-01 19:47:51.949+0000: 7783: error : virFileIsSharedFixFUSE:3384 : unable to canonicalize /mnt/user/domains/Windows 10 testing/vdisk1.img: No such file or directory
2020-11-01 19:47:51.950+0000: 7783: error : qemuOpenFileAs:3175 : Failed to open file '/mnt/user/domains/Windows 10 testing/vdisk1.img': No such file or directory
2020-11-01 19:47:51.953+0000: 7783: error : virFileIsSharedFixFUSE:3384 : unable to canonicalize /mnt/user/domains/Windows 10 testing/vdisk1.img: No such file or directory
2020-11-01 19:47:51.953+0000: 7783: error : qemuOpenFileAs:3175 : Failed to open file '/mnt/user/domains/Windows 10 testing/vdisk1.img': No such file or directory
2020-11-01 19:47:51.956+0000: 7784: error : virFileIsSharedFixFUSE:3384 : unable to canonicalize /mnt/user/domains/Windows 10 testing/vdisk1.img: No such file or directory
2020-11-01 19:47:51.956+0000: 7784: error : qemuOpenFileAs:3175 : Failed to open file '/mnt/user/domains/Windows 10 testing/vdisk1.img': No such file or directory
2020-11-01 19:47:51.959+0000: 7784: error : qemuDomainGetBlockInfo:11942 : invalid argument: invalid path not assigned to domain
2020-11-01 19:47:51.960+0000: 7781: error : qemuDomainGetBlockInfo:11942 : invalid argument: invalid path not assigned to domain
2020-11-01 19:56:00.660+0000: 7781: warning : qemuDomainObjTaint:6075 : Domain id=5 name='Linux' uuid=8305e727-945c-6b93-52f8-87145ed73f46 is tainted: high-privileges
2020-11-01 19:56:00.660+0000: 7781: warning : qemuDomainObjTaint:6075 : Domain id=5 name='Linux' uuid=8305e727-945c-6b93-52f8-87145ed73f46 is tainted: host-cpu
2020-11-01 19:58:30.832+0000: 7784: error : virStorageFileReportBrokenChain:5178 : Cannot access storage file ' ': No such file or directory
2020-11-01 19:58:47.524+0000: 7781: error : qemuDomainGetBlockInfo:11942 : invalid argument: invalid path not assigned to domain
2020-11-02 10:35:37.303+0000: 7782: error : qemuDomainGetBlockInfo:11942 : invalid argument: invalid path not assigned to domain
2020-11-02 10:36:17.522+0000: 7784: error : virStorageFileReportBrokenChain:5178 : Cannot access storage file ' ': No such file or directory
2020-11-02 10:37:50.559+0000: 7782: warning : qemuDomainObjTaint:6075 : Domain id=8 name='Windows 10 GT1070 test' uuid=451f210b-25e3-c095-5fec-22bb496603f5 is tainted: high-privileges
2020-11-02 10:37:50.559+0000: 7782: warning : qemuDomainObjTaint:6075 : Domain id=8 name='Windows 10 GT1070 test' uuid=451f210b-25e3-c095-5fec-22bb496603f5 is tainted: host-cpu
2020-11-02 10:39:42.846+0000: 7784: warning : qemuDomainObjTaint:6075 : Domain id=9 name='Windows 10 Big Tv GTX1070 RADION' uuid=2b3572b2-823e-59b4-4895-378913a75c60 is tainted: high-privileges
2020-11-02 10:39:42.846+0000: 7784: warning : qemuDomainObjTaint:6075 : Domain id=9 name='Windows 10 Big Tv GTX1070 RADION' uuid=2b3572b2-823e-59b4-4895-378913a75c60 is tainted: host-cpu

 

 

 

ive tried un assigning the cores and gpus and reattaching and fresh new installs of windows 10 and linux. ive checked iommu is enabled and vt-d. and checked the iommu groups are split in devices like before upgrade.

the cpu i upgraded too is a retail version e5-2699v4. which is fully supported

 

the system spec:

Model: Custom

M/B: ASUSTeK COMPUTER INC. X99-PRO/USB 3.1 Version Rev 1.xx - s/n: 150955212800080

BIOS: American Megatrends Inc. Version 4101. Dated: 07/10/2019

CPU: Intel® Xeon® CPU E5-2699 v4 @ 2.20GHz

HVM: Enabled

IOMMU: Enabled

Cache: 1408 KiB, 5632 KiB, 56320 KiB

Memory: 32 GiB DDR4 (max. installable capacity 512 GiB)

Network: eth0: 1000 Mbps, full duplex, mtu 1500

Kernel: Linux 5.8.13-Unraid x86_64

OpenSSL: 1.1.1h

Hi there,

 

So if you create a new VM from scratch, new virtual disk, and install Windows, does that not work at all?  If you changed the motherboard/CPU, your PCI devices may have new IDs and therefore you may need to reassign them to your VMs by editing the VM and then saving.

no i just changed the cpu and not the motherboard. ive tried a few attempts at starting a new vm  and most freeze. one installed fully but on restart it would after install it said error could not find the storage

created new vm and message is

Execution error

Cannot access storage file ' ': No such file or directory

if i fire up the big vm with the hard drive external. no execution error. but no gpu started and log says this

 

QEMU_AUDIO_DRV=none \
/usr/local/sbin/qemu \
-name 'guest=Windows 10 Big Tv GTX1070 RADION,debug-threads=on' \
-S \
-object 'secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-12-Windows 10 Big Tv GT/master-key.aes' \
-machine pc-i440fx-5.0,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off \
-cpu host,migratable=on,hv-time,hv-relaxed,hv-vapic,hv-spinlocks=0x1fff,hv-vendor-id=none,host-cache-info=on,l3-cache=off \
-m 10240 \
-overcommit mem-lock=off \
-smp 26,sockets=1,dies=1,cores=13,threads=2 \
-uuid 2b3572b2-823e-59b4-4895-378913a75c60 \
-display none \
-no-user-config \
-nodefaults \
-chardev socket,id=charmonitor,fd=33,server,nowait \
-mon chardev=charmonitor,id=monitor,mode=control \
-rtc base=localtime \
-no-hpet \
-no-shutdown \
-boot strict=on \
-device qemu-xhci,p2=15,p3=15,id=usb,bus=pci.0,addr=0x7 \
-device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 \
-blockdev '{"driver":"host_device","filename":"/dev/sdb","node-name":"libvirt-1-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \
-blockdev '{"node-name":"libvirt-1-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"raw","file":"libvirt-1-storage"}' \
-device virtio-blk-pci,bus=pci.0,addr=0x4,drive=libvirt-1-format,id=virtio-disk2,bootindex=1,write-cache=on \
-netdev tap,fd=35,id=hostnet0 \
-device virtio-net,netdev=hostnet0,id=net0,mac=52:54:00:78:99:d1,bus=pci.0,addr=0x2 \
-chardev pty,id=charserial0 \
-device isa-serial,chardev=charserial0,id=serial0 \
-chardev socket,id=charchannel0,fd=36,server,nowait \
-device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \
-device vfio-pci,host=0000:03:00.0,id=hostdev0,x-vga=on,bus=pci.0,addr=0x5 \
-device vfio-pci,host=0000:03:00.1,id=hostdev1,bus=pci.0,addr=0x6 \
-device usb-host,hostbus=3,hostaddr=13,id=hostdev2,bus=usb.0,port=1 \
-device usb-host,hostbus=3,hostaddr=12,id=hostdev3,bus=usb.0,port=2 \
-sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \
-msg timestamp=on
2020-11-03 23:57:09.055+0000: Domain id=12 is tainted: high-privileges
2020-11-03 23:57:09.055+0000: Domain id=12 is tainted: host-cpu
char device redirected to /dev/pts/1 (label charserial0)

is there away of wiping vm software and restarting it from scatch???

what happens if i remove the graphics card and reboot the system and then shutdown and reinstall it??? wil that help?

is there away of downgrading to back to stable version? im currently on beta-30 and only shows downgrade to beta-25

ive removed the graphics card and fired the system up and shutdown and reinstaled it. it seems to be trying more but still not working. the cores fire up but instead of staying flat out they go down now and hdmi socket on tv is showing but still no picture. also vm pf sense dint work but after a few vm restarts it did but notice in log it says this

 

some thing about vfio-pci can not read????

 

ErrorWarningSystemArrayLogin

-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/isos/pfSense-CE-2.4.4-RELEASE-p3-amd64.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/domains/PF SEnse/vdisk1.img","node-name":"libvirt-1-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \
-blockdev '{"node-name":"libvirt-1-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"qcow2","file":"libvirt-1-storage","backing":null}' \
-device ide-hd,bus=ide.2,drive=libvirt-1-format,id=sata0-0-2,bootindex=1,write-cache=on \
-chardev pty,id=charserial0 \
-device isa-serial,chardev=charserial0,id=serial0 \
-chardev socket,id=charchannel0,fd=32,server,nowait \
-device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \
-device usb-tablet,id=input0,bus=usb.0,port=1 \
-vnc 0.0.0.0:0,websocket=5700 \
-k en-us \
-device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pcie.0,addr=0x1 \
-device vfio-pci,host=0000:09:00.0,id=hostdev0,bus=pci.1,addr=0x0 \
-device vfio-pci,host=0000:09:00.1,id=hostdev1,bus=pci.3,addr=0x0 \
-device vfio-pci,host=0000:0a:00.0,id=hostdev2,bus=pci.4,addr=0x0 \
-device vfio-pci,host=0000:0a:00.1,id=hostdev3,bus=pci.5,addr=0x0 \
-sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \
-msg timestamp=on
2000-01-01 01:21:29.034+0000: Domain id=1 is tainted: high-privileges
2000-01-01 01:21:29.034+0000: Domain id=1 is tainted: host-cpu
char device redirected to /dev/pts/0 (label charserial0)
2000-01-01T01:21:34.015127Z qemu-system-x86_64: vfio-pci: Cannot read device rom at 0000:09:00.0
Device option ROM contents are probably invalid (check dmesg).
Skip option ROM probe with rombar=0, or load from file with romfile=
2000-01-01T01:21:34.017890Z qemu-system-x86_64: vfio-pci: Cannot read device rom at 0000:09:00.1
Device option ROM contents are probably invalid (check dmesg).
Skip option ROM probe with rombar=0, or load from file with romfile=
2000-01-01T01:21:34.020370Z qemu-system-x86_64: vfio-pci: Cannot read device rom at 0000:0a:00.0
Device option ROM contents are probably invalid (check dmesg).
Skip option ROM probe with rombar=0, or load from file with romfile=
2000-01-01T01:21:34.022842Z qemu-system-x86_64: vfio-pci: Cannot read device rom at 0000:0a:00.1
Device option ROM contents are probably invalid (check dmesg).
Skip option ROM probe with rombar=0, or load from file with romfile=

the other thing is its also saying its not done a party check for 7612 days even know it does it every weeked? weekend just gone came up ok. only says this since i rebooted the system. for removing graphic card and reinstall. i also took the bios battery out for a bit too and reinstalled

ok. so ive restarted the windows vm repeatedly like i did with the pf sense one and now have windows 10 on the main graphics card work 🙂 🙂 🙂 now gonna run a parity check which will take 22hrs... and then reboot the hole system.. fingures crossed this is all fixed 🙂

silly question but is there a date settings on here? as history shows this lol

 

Last check completed on Mon 02 Nov 2020 11:30:29 AM PST (7612 days ago)
Finding 0 errors Duration: 22 hours, 12 minutes, 33 seconds. Average speed: 100.1 MB/sec

found date and time lol changed to london as i live in uk but it says this now Sat 01 Jan 2000 02:06:28 AM GMT lol ill leave it like this till after parity check done and been restart. hopefully all good now. ill put an update tomorrow after restart 🙂 anyone knows how to edit the date would be handy lol thank you

There's a lot going on here. You should set the system date and time in BIOS. It should have a current time unless you reset the CMOS. If you did not reset the CMOS, then check the motherboard battery to see if it needs replacement. 

 

There are a lot of errors in your logs that you seemed to have ignored, like QEMU being unable to find your vdisk images.

 

I would not, as a matter of best practices, use an external hard drive to host anything that requires realtime interaction like a VM. External drives, unless connected via eSATA or SAS should be used for storage only. Put your VMs either on the cache drive or on an internal drive outside the array using the unassigned devices app.

 

 

Hi Lance,

 

With everything going on here, you may need to work with an expert to review the system and figure out the problem.  All of your posts here contain lots of information, but nothing really crystal clear as to what is causing the issue.  We do offer professional services for a fee if you're interested.  You can schedule a session with us via https://unraid.net/services.  If you'd rather keep working through here, what I would do is completely start from scratch.  Also I wouldn't use an external hard drive the way you are.  I'm also confused as to how libvirt can't find the storage for your VMs unless you're doing something like passing through the storage device that also contains the vdisk images themselves.

so if i start from scratch. how do i get the key re-set??

im just trying to install windows 10 on cache drive and see if there are any errors. seem far better today. since this morning it seem to be working. but yes ive got the vm external at the moment as couldnt find vm after install..

ok... after install and install the device manage virtio drives and windows updates... restart windows 10 vm on cache still has the problem with

Execution error

Cannot access storage file ' ': No such file or directory.

 

anyone able to reset my key and ill install a fresh copy of unraid? do i need to make a note of array assignment. then after install just place them back in correct location???

 

unraid will only boot in gui mode. if you boot normal. seems ok but network down and cant access it.

Still not resolved. Upgraded nvme cache drive and used old nvme to put my windows 10 on. Won’t boot in normal mode.. only gui mode and can’t create vms unless on separate drive to cache and array. Only works in unassigned devices... ☹️  Still can’t get to work correctly 

On 11/5/2020 at 7:40 PM, DarkKnight said:

There's a lot going on here. You should set the system date and time in BIOS. It should have a current time unless you reset the CMOS. If you did not reset the CMOS, then check the motherboard battery to see if it needs replacement. 

 

There are a lot of errors in your logs that you seemed to have ignored, like QEMU being unable to find your vdisk images.

 

I would not, as a matter of best practices, use an external hard drive to host anything that requires realtime interaction like a VM. External drives, unless connected via eSATA or SAS should be used for storage only. Put your VMs either on the cache drive or on an internal drive outside the array using the unassigned devices app.

 

 

I’ve brought a new nvme drive to replace my old one as the cache drive and put windows 10 on the old one. So no longer external. Still got the same problems with qemu. I do have my big graphics card working. But still can only boot in gui mode in unraid. Any ideas please??? 😊