FritzsCorner

I rebuilt my Win10 Install media 2 more times and finally I got something to work. Not sure why my other two ISO's were corrupted but that seems to be what my problem was. Marking this as solved.

I have been a long-time Unraid user for about 10 years or so but have never attempted to use VM's on it until now. I am following this guide and currently on the "Start the VM" step. I power the VM on and press any key to boot to the ISO, I see a light blue background for maybe 15-30 seconds that looks like the Win10 setup is getting ready to launch, and then the VM just shut's down. In the VM log I see the following. -overcommit mem-lock=off \ -smp 8,sockets=1,dies=1,cores=4,threads=2 \ -uuid 4228e9d4-4f7d-629d-c568-fc1339623617 \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=31,server,nowait \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=localtime,driftfix=slew \ -global kvm-pit.lost_tick_policy=delay \ -no-hpet \ -no-shutdown \ -boot strict=on \ -device qemu-xhci,p2=15,p3=15,id=usb,bus=pci.0,addr=0x7 \ -device ahci,id=sata0,bus=pci.0,addr=0x4 \ -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 \ -blockdev '{"driver":"file","filename":"/mnt/user/domains/Windows 10/vdisk1.img","node-name":"libvirt-3-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-3-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"raw","file":"libvirt-3-storage"}' \ -device virtio-blk-pci,bus=pci.0,addr=0x6,drive=libvirt-3-format,id=virtio-disk2,bootindex=1,write-cache=on \ -blockdev '{"driver":"file","filename":"/mnt/user/isos/Windows.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=sata0.0,drive=libvirt-2-format,id=sata0-0-0,bootindex=2 \ -blockdev '{"driver":"file","filename":"/mnt/user/isos/virtio-win-0.1.190-1.iso","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-1-format","read-only":true,"driver":"raw","file":"libvirt-1-storage"}' \ -device ide-cd,bus=sata0.1,drive=libvirt-1-format,id=sata0-0-1 \ -netdev tap,fd=33,id=hostnet0 \ -device virtio-net,netdev=hostnet0,id=net0,mac=52:54:00:89:23:bb,bus=pci.0,addr=0x3 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0 \ -chardev socket,id=charchannel0,fd=34,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 virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on 2022-02-05 16:50:29.072+0000: Domain id=2 is tainted: high-privileges 2022-02-05 16:50:29.072+0000: Domain id=2 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2022-02-05T16:51:39.497079Z qemu-system-x86_64: terminating on signal 15 from pid 12217 (/usr/sbin/libvirtd) 2022-02-05 16:51:39.716+0000: shutting down, reason=shutdown I haven't gotten to the point where I am trying to pass through any devices and just trying to do the initial setup. I have watched the Space Invader One videos and scoured the forums looking for a possible solution but so far nothing seems to be working. Any ideas on where I should look first to try and identify the issue? Any more information I need to provide? Thanks! My Server: Unraid 6.9.2 AMD Ryzen 5 1600 3.2GHz CPU Micro-star B450-A PRO MAX (MS-7B86) mobo with the latest stable BIOS 32GB DDR4 3200 Ram ASUS RTX 2060 OC 12GB GPU 17 TB array with one Parity Disk (XFS) 1 TB nvme Cache Drive (btrfs) 500 GB SSD Unassigned Drive planned for the VM 1 TB HDD Unassigned Drive 12 TB External USB 3.0 HDD Unassigned Drive tower-diagnostics-20220205-1052.zip

Well I have progress! I thought I had my Old and New Parity drives on the same sata controller but it looks like I traced the wrong sata cable in the spaghetti mess. Once I got that part figured out and I unplugged all my other drives, it wouldn't allow me to copy.. so I went back and plugged in 2 of my working data disks to the mobo sata controller and left the cache drive and other data drives unplugged. The copy option was then available. The copy is now at 3% complete which is 3% further than I made it before. My guess is that my cheap PCI sata cards are just that... cheap. They have worked for the day to day operation of my NAS for over 2 years, but are probably introducing errors that I haven't noticed. I will need to go back and research some better PCI sata cards for my build assuming the copy completes successfully. This is my first drive failure I have had in the 5 years I have been using UnRaid.. *knock on wood* Thanks again for the help!

Unfortunately it is not.. once I start the copy process all remote and local access to the system become unavailable. However, I can power cycle and check that log before I begin the process again. I will post back what I find. Appreciate the assistance!

I recently had a 2tb data drive that failed and was running in emulated mode. My current Parity drive is 2TB as well, but my new drives are 3TB. I followed the guide here: https://lime-technology.com/wiki/index.php/The_parity_swap_procedure but every time I click the copy button the system hangs up and becomes unresponsive to any local input or remote connectivity. I can power cycle the system and regain access, but no data seems to have been copied. Looking at the system log it seems to freeze up about 30 seconds after the process begins. I thought this could possibly be a hardware issue with my SATA connection so I made sure that both drives were connected directly to the mobo and not the PCI SATA cards that I have installed. May 10 23:05:01 Tower emhttp: import 30 cache device: sdf May 10 23:05:01 Tower emhttp: import flash device: sda May 10 23:05:20 Tower emhttp: copy: disk4 to disk0 May 10 23:07:23 Tower kernel: sata_sil24 0000:04:00.0: IRQ status == 0xffffffff, PCI fault or device removal? I am currently running UnRaid 6.3.3

I am very interested in this as well.