Xixix

I have a VM that runs fine for some where around 3 hours then locks up. Each time it does so I have to use the Force Stop feature and am unable to reboot the VM until I reboot the entire server, because if I try to restart it I am given the error 'internal error: Unknown PCI header type '127'' The VM has a single ATI 580 graphics card passed through to it and is running a fully updated Windows 10. It should have plenty of hard drive space since I saw some people received similar warnings when they ran out. Here is the log of the VM just after I did a Force Stop. If any one could help me get this to be more stable I would greatly appreciate it. It never causes problems with anything else in the server, just that one VM. 2018-01-22 17:37:25.178+0000: starting up libvirt version: 3.8.0, qemu version: 2.10.2, hostname: Tower LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name guest=Win10,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-1-Win10/master-key.aes -machine pc-i440fx-2.7,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off -cpu host,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff,hv_vendor_id=none -drive file=/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/etc/libvirt/qemu/nvram/486bed12-63d1-1075-0b81-b872e9ea07d3_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 4096 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 486bed12-63d1-1075-0b81-b872e9ea07d3 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-1-Win10/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-hpet -no-shutdown -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x7.0x7 0 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-1-Win10/org.qemu.guest_agent.0,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=pci.0,addr=0x2 -device vfio-pci,host=0b:00.0,id=hostdev0,bus=pci.0,addr=0x6 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -msg timestamp=on 2018-01-22 17:37:25.178+0000: Domain id=1 is tainted: high-privileges 2018-01-22 17:37:25.178+0000: Domain id=1 is tainted: host-cpu 2018-01-22T17:37:25.225419Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0) ((null):813): SpiceWorker-Warning **: red_worker.c:163:rendering_incorrect: rendering incorrect from now on: get_drawable ehci warning: guest updated active QH ehci warning: guest updated active QH ehci warning: guest updated active QH ehci warning: guest updated active QH ehci warning: guest updated active QH 2018-01-22T21:42:21.172062Z qemu-system-x86_64: terminating on signal 15 from pid 11961 (/usr/sbin/libvirtd) 2018-01-22 21:42:21.372+0000: shutting down, reason=destroyed 2018-01-22 21:45:33.621+0000: shutting down, reason=failed

Thank you for your help. I ended up making my own DAS inside a Silver Stone case connected to a LSI 8088 card and have not had any issues at all.

Do you have a recommended enclosure or company that makes enclosures? I will just reorder the LSI I bought the first time but I would rather not get that same enclosure. And sadly I need the VT-d for the VM device pass through.(I think any way)

I had read that USB 3 could only detect one drive. So does that mean the only option to having it stable is some sort of 8088 connector or just 1:1 SATA cables? I originally got that specific SATA card because some one on the forums had success with this exact setup, except they had the 4 bay enclosure and I got the 8.

I have an array of 4 8TB WD Red drives, one of which was parity. I wanted to try out an enclosure and during the night the fan died and apparently caused the drives to over heat. One of the drives, drive 1, was dead when I woke up. I turned everything off, bought a completely different enclosure and a new 8TB WD Red. I put it into the enclosure and tried to rebuild. It ended up having an error. I realized I hadn't precleared it so I had it do that, in maintenance mode, for a while. Three full passes later and it seemed fine. I rebuilt the array in maintenance mode over another few days. Today I turned on the server in normal mode and everything seemed fine at first. I was able to access everything fine. I turned on Docker, updated things, and turned on my VM. There were lots of files being moved around but it seemed fine for a while. Then I got a message about Disk 1 being in an error state again and the contents being emulated. I have moved nothing and everything should be fine. I never reseated anything or touched any cables since it made it through preclear and rebuild. Any assistance would be appreciated. When the first drive died I had an LSI card in there just for an 8088 connector to the enclosure, but since then I got rid of that and put a SATA card in there with an eSATA connector for the new enclosure. The only thing even slightly out of the ordinary about the system is that it has a VM with some video card pass through. I don't suspect that to be involved, but I figured I should let you know any way. Unraid version 6.3.5 IO Crest SI-PEX40062 card for eSATA Mediasonic H82-SU3S2 ProBox enclosure tower-diagnostics-20171030-1739.zip

I had a share that exists only on my cache drive, but using that share in the path for the PGDATA did not work and had the exact same issues. Changing it to /mnt/cache/whatever worked. I don't like it, but it works.

Is it possible to get FFMPEG installed on this docker as an optional parameter? I ask because I want to use it with nzbToMedia and if I got it to work it would just be gone the next time I updated the docker image.