Greetings,

 

I'm scratching my head here because I am not sure why my windows 8.1 Pro is not booting up, or my SSD drives self-eject from the Cash pool.

 

Install went fine, now it won't boot past the windows Logo or display over anything other than VNC.

 

 If I restart unRaid. The SSD in the Cash Pool are ejected? 

 

I know I have a few different problems here, and I suspect the SSD self-ejecting is my computer jumping in the Sarlacc sand worm pit before I destroy it and turn to the Darkside. 

 

These are my specs, and a system log while the VM boots. I only have the one VM configured. 

 

- unSith 

 

 

Model: Custom
M/B: Gigabyte Technology Co., Ltd. - Z97X-UD5H-BK
CPU: Intel® Core™ i5-4570 CPU @ 3.20GHz
HVM: Enabled
IOMMU: Enabled
Cache: 256 kB, 1024 kB, 6144 kB
Memory: 16 GB (max. installable capacity 32 GB)
Network: bond0: fault-tolerance (active-backup), mtu 1500 
 eth0: not connected
 eth1: 1000 Mb/s, full duplex, mtu 1500
Kernel: Linux 4.9.19-unRAID x86_64
OpenSSL: 1.0.2k

ErrorWarningSystemArrayLogin


May 4 19:49:41 Master kernel: [<ffffffff81ccb3be>] x86_64_start_kernel+0xe6/0xf3
May 4 19:49:41 Master kernel: handlers:
May 4 19:49:41 Master kernel: [<ffffffff814f95ff>] usb_hcd_irq
May 4 19:49:41 Master kernel: Disabling IRQ #16
May 4 19:49:41 Master kernel: usb 3-3.3: reset full-speed USB device number 7 using xhci_hcd
May 4 19:49:42 Master kernel: usb 3-10: reset full-speed USB device number 4 using xhci_hcd
May 4 19:49:42 Master kernel: irq 16: nobody cared (try booting with the "irqpoll" option)
May 4 19:49:42 Master kernel: CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.9.19-unRAID #1
May 4 19:49:42 Master kernel: Hardware name: Gigabyte Technology Co., Ltd. Z97X-UD5H-BK/Z97X-UD5H-BK, BIOS F8 09/19/2015
May 4 19:49:42 Master kernel: ffff88042fa03ec8 ffffffff813a3bf2 ffff88041ad08800 ffff88041ad08800
May 4 19:49:42 Master kernel: ffff88042fa03ef0 ffffffff810863e1 ffff88041ad08800 0000000000000000
May 4 19:49:42 Master kernel: 0000000000000010 ffff88042fa03f28 ffffffff810866aa ffff88041ad08800
May 4 19:49:42 Master kernel: Call Trace:
May 4 19:49:42 Master kernel: <IRQ> 
May 4 19:49:42 Master kernel: [<ffffffff813a3bf2>] dump_stack+0x61/0x7e
May 4 19:49:42 Master kernel: [<ffffffff810863e1>] __report_bad_irq+0x2b/0xb4
May 4 19:49:42 Master kernel: [<ffffffff810866aa>] note_interrupt+0x1a0/0x22e
May 4 19:49:42 Master kernel: [<ffffffff81084294>] handle_irq_event_percpu+0x3d/0x46
May 4 19:49:42 Master kernel: [<ffffffff810842d3>] handle_irq_event+0x36/0x54
May 4 19:49:42 Master kernel: [<ffffffff810871f6>] handle_fasteoi_irq+0x90/0xf8
May 4 19:49:42 Master kernel: [<ffffffff81020515>] handle_irq+0x17/0x1b
May 4 19:49:42 Master kernel: [<ffffffff8101ff6a>] do_IRQ+0x46/0xc2
May 4 19:49:42 Master kernel: [<ffffffff8167e942>] common_interrupt+0x82/0x82
May 4 19:49:42 Master kernel: <EOI> 
May 4 19:49:42 Master kernel: [<ffffffff81551f5a>] ? cpuidle_enter_state+0xfe/0x156
May 4 19:49:42 Master kernel: [<ffffffff81551fd4>] cpuidle_enter+0x12/0x14
May 4 19:49:42 Master kernel: [<ffffffff8107c453>] call_cpuidle+0x33/0x35
May 4 19:49:42 Master kernel: [<ffffffff8107c635>] cpu_startup_entry+0x13a/0x1b2
May 4 19:49:42 Master kernel: [<ffffffff81673138>] rest_init+0x7f/0x82
May 4 19:49:42 Master kernel: [<ffffffff81ccbe8e>] start_kernel+0x3cf/0x3dc
May 4 19:49:42 Master kernel: [<ffffffff81ccb120>] ? early_idt_handler_array+0x120/0x120
May 4 19:49:42 Master kernel: [<ffffffff81ccb2d6>] x86_64_start_reservations+0x2a/0x2c
May 4 19:49:42 Master kernel: [<ffffffff81ccb3be>] x86_64_start_kernel+0xe6/0xf3
May 4 19:49:42 Master kernel: handlers:
May 4 19:49:42 Master kernel: [<ffffffff814f95ff>] usb_hcd_irq
May 4 19:49:42 Master kernel: [<ffffffff814ecfed>] vfio_intx_handler
May 4 19:49:42 Master kernel: Disabling IRQ #16
May 4 19:49:42 Master kernel: usb 3-3.3: reset full-speed USB device number 7 using xhci_hcd
May 4 19:49:42 Master kernel: usb 3-10: reset full-speed USB device number 4 using xhci_hcd
May 4 19:49:46 Master kernel: usb 3-3.3: reset full-speed USB device number 7 using xhci_hcd
May 4 19:49:46 Master kernel: usb 3-10: reset full-speed USB device number 4 using xhci_hcd
May 4 19:49:47 Master kernel: usb 3-3.3: reset full-speed USB device number 7 using xhci_hcd
May 4 19:49:47 Master kernel: usb 3-10: reset full-speed USB device number 4 using xhci_hcd
May 4 19:49:48 Master kernel: usb 3-3.3: reset full-speed USB device number 7 using xhci_hcd
May 4 19:49:48 Master kernel: usb 3-10: reset full-speed USB device number 4 using xhci_hcd
May 4 19:49:50 Master kernel: kvm: zapping shadow pages for mmio generation wraparound
May 4 19:49:50 Master kernel: kvm: zapping shadow pages for mmio generation wraparound
May 4 19:49:51 Master kernel: usb 3-3.3: reset full-speed USB device number 7 using xhci_hcd
May 4 19:49:51 Master kernel: usb 3-10: reset full-speed USB device number 4 using xhci_hcd
May 4 19:49:51 Master kernel: usb 3-3.3: reset full-speed USB device number 7 using xhci_hcd
May 4 19:49:51 Master kernel: usb 3-10: reset full-speed USB device number 4 using xhci_hcd
May 4 19:49:52 Master kernel: usb 3-3.3: reset full-speed USB device number 7 using xhci_hcd
May 4 19:49:52 Master kernel: usb 3-10: reset full-speed USB device number 4 using xhci_hcd
May 4 19:49:52 Master kernel: usb 3-3.3: reset full-speed USB device number 7 using xhci_hcd
May 4 19:49:52 Master kernel: usb 3-10: reset full-speed USB device number 4 using xhci_hcd
May 4 19:49:57 Master kernel: usb 3-3.3: reset full-speed USB device number 7 using xhci_hcd
May 4 19:49:57 Master kernel: usb 3-10: reset full-speed USB device number 4 using xhci_hcd
May 4 19:49:58 Master kernel: usb 3-3.3: reset full-speed USB device number 7 using xhci_hcd
May 4 19:49:58 Master kernel: usb 3-10: reset full-speed USB device number 4 using xhci_hcd
May 4 19:49:58 Master kernel: usb 3-3.3: reset full-speed USB device number 7 using xhci_hcd
May 4 19:49:59 Master kernel: usb 3-10: reset full-speed USB device number 4 using xhci_hcd
May 4 19:49:59 Master kernel: usb 3-3.3: reset full-speed USB device number 7 using xhci_hcd
May 4 19:50:00 Master kernel: usb 3-3.3: reset full-speed USB device number 7 using xhci_hcd
May 4 19:50:00 Master kernel: usb 3-10: reset full-speed USB device number 4 using xhci_hcd
May 4 19:50:00 Master kernel: usb 3-3.3: reset full-speed USB device number 7 using xhci_hcd
May 4 19:50:01 Master kernel: usb 3-10: reset full-speed USB device number 4 using xhci_hcd
May 4 19:50:01 Master kernel: usb 3-10: reset full-speed USB device number 4 using xhci_hcd

 

I would suggest that you post the diagnostics file with your next post.  It will provide the real Gurus who might be able to help you with your problem a lot more information.  You might provide a complete list of your hardware since you are having issues with a VM.  IF you don't have a GUI to get this file, log into the server via telnet/SSH and type diagnostics  on the command line.  That will write the diagnostics file to the logs directory/folder of your Flash Drive.

Thanks, Frank!

master-diagnostics-20170504-2017.zip