Jaster

-e "ACCEPT_EULA=Y" -e "SA_PASSWORD=Yourpasword1" -m 8g --ulimit stack=8192000:8192000 Adding this to the extra parameters does the magic! PS: Remeber to map the /var pathes and set a correct SA password

FYI: Disable UEFI boot, then it works

Did that, but keep receiving the very same error.knowlage-diagnostics-20190928-1329.zip

1060 3GB. Used to work like a charm, now suddenly stopped.

Hey guys, My VM suddenly stoped working, or at least the GPU has. I receive this error in the log: ErrorWarningSystemArrayLogin -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/099f3d54-9e14-3229-33e8-3ea946969e7f_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 \ -m 24576 \ -realtime mlock=off \ -smp 8,sockets=1,cores=4,threads=2 \ -uuid 099f3d54-9e14-3229-33e8-3ea946969e7f \ -display none \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=27,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 \ -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x7 \ -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x7.0x1 \ -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x7.0x2 \ -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 \ -drive file=/mnt/user/domains/Game1/vdisk1.img,format=qcow2,if=none,id=drive-virtio-disk2,cache=writeback \ -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk2,id=virtio-disk2,bootindex=1,write-cache=on \ -drive file=/mnt/user/domains/_shared/steam2.img,format=raw,if=none,id=drive-virtio-disk3,cache=writeback \ -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk3,id=virtio-disk3,write-cache=on \ -drive file=/mnt/user/isos/virtio-win-0.1.160-1.iso,format=raw,if=none,id=drive-ide0-0-1,readonly=on \ -device ide-cd,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1 \ -netdev tap,fd=29,id=hostnet0,vhost=on,vhostfd=31 \ -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:54:99:a3,bus=pci.0,addr=0x2 \ -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 vfio-pci,host=65:00.0,id=hostdev0,bus=pci.0,addr=0x6,romfile=/mnt/user/domains/asus.rom \ -device vfio-pci,host=65:00.1,id=hostdev1,bus=pci.0,addr=0x8 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on 2019-09-28 11:50:19.679+0000: Domain id=6 is tainted: high-privileges 2019-09-28 11:50:19.679+0000: Domain id=6 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2019-09-28T11:50:21.690037Z qemu-system-x86_64: -device vfio-pci,host=65:00.0,id=hostdev0,bus=pci.0,addr=0x6,romfile=/mnt/cache/domains/asus.rom: Failed to mmap 0000:65:00.0 BAR 3. Performance may be slow 2019-09-28T11:50:29.680345Z qemu-system-x86_64: vfio_region_write(0000:65:00.0:region3+0x40a8, 0xbffe101,8) failed: Device or resource busy 2019-09-28T11:50:29.680389Z qemu-system-x86_64: vfio_region_write(0000:65:00.0:region3+0x15000, 0x0,8) failed: Device or resource busy 2019-09-28T11:50:29.680397Z qemu-system-x86_64: vfio_region_write(0000:65:00.0:region3+0x15008, 0x0,8) failed: Device or resource busy 2019-09-28T11:50:29.680407Z qemu-system-x86_64: vfio_region_write(0000:65:00.0:region3+0x15010, 0x0,8) failed: Device or resource busy Whats wrong there and how to fix it?

Epic... I didn't add a 'G' at the end, so it created.... 200kb? Thanks!

ROOT# du -h --apparent-size /mnt/user/domains/_shared/steam.img 384K /mnt/user/domains/_shared/steam.img ROOT# du -h /mnt/user/domains/_shared/steam.img 324K /mnt/user/domains/_shared/steam.img

Hi Guys, I'm trying to add another vdisk to an existing VM. I added a qcow2 disk via the VM settings and booted the VM multiple times. However, when I want to init/add it in widnows this is what I receive: (Similar issue for MBR instead of GPT). What do I have to do to property init and use the disk?

I dont have any nocow shares. But it seems I cant backup anything -> cp: error reading 'vdisk1.img': Input/output erro Is there any way to save this? It is vital for me as I would lose some veryyyy imporant data is just received today (nightly backup did not run yet) It is a RAID6, how can it fail in a way I can not recover anything!? [/dev/sdm1].write_io_errs 0 [/dev/sdm1].read_io_errs 0 [/dev/sdm1].flush_io_errs 0 [/dev/sdm1].corruption_errs 0 [/dev/sdm1].generation_errs 0 [/dev/sdh1].write_io_errs 0 [/dev/sdh1].read_io_errs 0 [/dev/sdh1].flush_io_errs 0 [/dev/sdh1].corruption_errs 93230 [/dev/sdh1].generation_errs 2571 [/dev/sdk1].write_io_errs 0 [/dev/sdk1].read_io_errs 148 [/dev/sdk1].flush_io_errs 0 [/dev/sdk1].corruption_errs 0 [/dev/sdk1].generation_errs 0 [/dev/sdj1].write_io_errs 0 [/dev/sdj1].read_io_errs 0 [/dev/sdj1].flush_io_errs 0 [/dev/sdj1].corruption_errs 0 [/dev/sdj1].generation_errs 0 Why does the cache appear to be read only?!

Any other way? As the pool only contains VMs and docker data..?

Cool. Thanks. Back onlline and scrubbing.... How to deal with the resulting uncorrectables? scrub status for 841ae120-6e82-44b2-bd5f-ee9fd1de1907 scrub started at Tue Sep 10 17:55:12 2019, running for 00:00:41 total bytes scrubbed: 9.82GiB with 2595 errors error details: read=4 verify=2571 csum=20 corrected errors: 2588, uncorrectable errors: 7, unverified errors: 0

I see, I removed a VM disk which is backed up and rebooted, but now a dive dropped out of the cache: New Issue

Diagnostics after reboot: knowlage-diagnostics-20190910-1540.zip

Hey. My server come up and had a missing btrfs device (diagnostics) attached. I shut down, checked cables and the device returned. Now it is no longer part of the cache pool. How do I get it back in?... knowlage-diagnostics-20190910-1524.zip