schale01

Members
  • Posts

    12
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

schale01's Achievements

Noob

Noob (1/14)

2

Reputation

  1. Interesting I also have a similar super micro board. The last stable system version that worked for me was 6.10.4. That version was rock solid and I never had any hangs. I've reported this hanging issue myself and seen it reported multiple times elsewhere. At this point I've just moved off of unRaid as it seems that I will be unable to upgrade to a stable version for my system configuration anytime soon.
  2. Update. Moved all Dockers to bridge interference br1. Docker settings are on ipvlan Server still becomes completely unresponsive. Added another interface on eth2, previously disabled. Confirmed able to access through this interface but server becomes unresponsive and this interface is also non-responsive. Rolled back to 6.10.3 and system has been stable since. Any recommendations or further logs needed I can reapply upgrade and gather.
  3. Server becomes unresponsive after upgrading to 6.12.3. Issue was also observed on 6.12.2 and 6.12.1 as well as 6.11 reverting to 6.10 does resolve the issue. Issue occurs with little to no server load after an 12 to 24 hours. Issue appears to be repeatable when running docker container transmission with wireguard network interface. Attached debug kernal log. 2023-07-21T23:25:52-04:00 Carbon14 kernel: mdcmd (31): set md_num_stripes 1280 2023-07-21T23:25:52-04:00 Carbon14 kernel: mdcmd (32): set md_queue_limit 80 2023-07-21T23:25:52-04:00 Carbon14 kernel: mdcmd (33): set md_sync_limit 5 2023-07-21T23:25:52-04:00 Carbon14 kernel: mdcmd (34): set md_write_method 2023-07-21T23:25:52-04:00 Carbon14 kernel: mdcmd (35): start STOPPED 2023-07-21T23:25:52-04:00 Carbon14 kernel: unraid: allocating 25990K for 1280 stripes (5 disks) 2023-07-21T23:25:52-04:00 Carbon14 kernel: md1p1: running, size: 1953514552 blocks 2023-07-21T23:25:52-04:00 Carbon14 kernel: md2p1: running, size: 1953514552 blocks 2023-07-21T23:25:52-04:00 Carbon14 kernel: md3p1: running, size: 1465138552 blocks 2023-07-21T23:25:53-04:00 Carbon14 kernel: SGI XFS with ACLs, security attributes, no debug enabled 2023-07-21T23:25:53-04:00 Carbon14 kernel: XFS (md1p1): Mounting V5 Filesystem 2023-07-21T23:25:53-04:00 Carbon14 kernel: XFS (md1p1): Starting recovery (logdev: internal) 2023-07-21T23:25:53-04:00 Carbon14 kernel: XFS (md1p1): Ending recovery (logdev: internal) 2023-07-21T23:25:53-04:00 Carbon14 kernel: xfs filesystem being mounted at /mnt/disk1 supports timestamps until 2038 (0x7fffffff) 2023-07-21T23:25:53-04:00 Carbon14 kernel: XFS (md2p1): Mounting V5 Filesystem 2023-07-21T23:25:53-04:00 Carbon14 kernel: XFS (md2p1): Starting recovery (logdev: internal) 2023-07-21T23:25:53-04:00 Carbon14 kernel: XFS (md2p1): Ending recovery (logdev: internal) 2023-07-21T23:25:53-04:00 Carbon14 kernel: xfs filesystem being mounted at /mnt/disk2 supports timestamps until 2038 (0x7fffffff) 2023-07-21T23:25:54-04:00 Carbon14 kernel: XFS (md3p1): Mounting V5 Filesystem 2023-07-21T23:25:54-04:00 Carbon14 kernel: XFS (md3p1): Starting recovery (logdev: internal) 2023-07-21T23:25:54-04:00 Carbon14 kernel: XFS (md3p1): Ending recovery (logdev: internal) 2023-07-21T23:25:54-04:00 Carbon14 kernel: xfs filesystem being mounted at /mnt/disk3 supports timestamps until 2038 (0x7fffffff) 2023-07-21T23:25:55-04:00 Carbon14 kernel: BTRFS info (device nvme0n1p1): using crc32c (crc32c-intel) checksum algorithm 2023-07-21T23:25:55-04:00 Carbon14 kernel: BTRFS info (device nvme0n1p1): using free space tree 2023-07-21T23:25:55-04:00 Carbon14 kernel: BTRFS info (device nvme0n1p1): enabling ssd optimizations 2023-07-21T23:25:55-04:00 Carbon14 kernel: BTRFS info (device nvme0n1p1: state M): turning on async discard 2023-07-21T23:25:55-04:00 Carbon14 kernel: BTRFS info (device sdf1): using crc32c (crc32c-intel) checksum algorithm 2023-07-21T23:25:55-04:00 Carbon14 kernel: BTRFS info (device sdf1): using free space tree 2023-07-21T23:25:55-04:00 Carbon14 kernel: BTRFS info (device sdf1: state M): turning on async discard 2023-07-21T23:26:02-04:00 Carbon14 kernel: loop2: detected capacity change from 0 to 41943040 2023-07-21T23:26:02-04:00 Carbon14 kernel: BTRFS: device fsid 8923b5f4-d5f2-4678-b493-0ab90b7ce0be devid 1 transid 9774336 /dev/loop2 scanned by mount (9644) 2023-07-21T23:26:02-04:00 Carbon14 kernel: BTRFS info (device loop2): using crc32c (crc32c-intel) checksum algorithm 2023-07-21T23:26:02-04:00 Carbon14 kernel: BTRFS info (device loop2): using free space tree 2023-07-21T23:26:02-04:00 Carbon14 kernel: BTRFS info (device loop2): start tree-log replay 2023-07-21T23:26:02-04:00 Carbon14 kernel: BTRFS info (device loop2): checking UUID tree 2023-07-21T23:26:06-04:00 Carbon14 kernel: Bridge firewalling registered 2023-07-21T23:26:06-04:00 Carbon14 kernel: Initializing XFRM netlink socket 2023-07-21T23:26:11-04:00 Carbon14 kernel: loop3: detected capacity change from 0 to 2097152 2023-07-21T23:26:11-04:00 Carbon14 kernel: BTRFS: device fsid 5c6f5ada-a0aa-4d1b-b311-15fc6b18fb7b devid 1 transid 2064 /dev/loop3 scanned by mount (10305) 2023-07-21T23:26:11-04:00 Carbon14 kernel: BTRFS info (device loop3): using crc32c (crc32c-intel) checksum algorithm 2023-07-21T23:26:11-04:00 Carbon14 kernel: BTRFS info (device loop3): using free space tree 2023-07-21T23:26:12-04:00 Carbon14 kernel: tun: Universal TUN/TAP device driver, 1.6 2023-07-21T23:26:12-04:00 Carbon14 kernel: mdcmd (36): check correct 2023-07-21T23:26:12-04:00 Carbon14 kernel: md: recovery thread: check P ... 2023-07-21T23:26:13-04:00 Carbon14 kernel: L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details. 2023-07-21T23:26:16-04:00 Carbon14 kernel: eth0: renamed from veth6751040 2023-07-21T23:26:26-04:00 Carbon14 kernel: mdcmd (37): nocheck cancel 2023-07-21T23:26:26-04:00 Carbon14 kernel: md: recovery thread: exit status: -4 2023-07-21T23:28:05-04:00 Carbon14 kernel: br-dd02cf62dc1e: port 1(veth4aac129) entered blocking state 2023-07-21T23:28:05-04:00 Carbon14 kernel: br-dd02cf62dc1e: port 1(veth4aac129) entered disabled state 2023-07-21T23:28:05-04:00 Carbon14 kernel: device veth4aac129 entered promiscuous mode 2023-07-21T23:28:05-04:00 Carbon14 kernel: br-dd02cf62dc1e: port 1(veth4aac129) entered blocking state 2023-07-21T23:28:05-04:00 Carbon14 kernel: br-dd02cf62dc1e: port 1(veth4aac129) entered forwarding state 2023-07-21T23:28:05-04:00 Carbon14 kernel: br-dd02cf62dc1e: port 1(veth4aac129) entered disabled state 2023-07-21T23:28:07-04:00 Carbon14 kernel: eth0: renamed from vethcf3b69f 2023-07-21T23:28:07-04:00 Carbon14 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth4aac129: link becomes ready 2023-07-21T23:28:07-04:00 Carbon14 kernel: br-dd02cf62dc1e: port 1(veth4aac129) entered blocking state 2023-07-21T23:28:07-04:00 Carbon14 kernel: br-dd02cf62dc1e: port 1(veth4aac129) entered forwarding state 2023-07-21T23:28:07-04:00 Carbon14 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): br-dd02cf62dc1e: link becomes ready carbon14-diagnostics-20230722-0112.zip
  4. After a recent upgrade to 6.11.5 I started getting server lock ups. No webgui, no ssh, no ping response, not even output from console. It seemed to happen when using apps such as Plex or transmission. Never had the issue before so I've currently rolled back to 6.10.3 and am no longer seeing issues. I'm starting to think that the recent kernel update really hates macvlan more then ever. When I have some time I'll try to update again and switch over all my Dockers to ipvlan to confirm if that was the cause.
  5. I had the same issue. Server would freeze up and no access via webgui, ssh it even physical console. I haven't made any hardware changes, use no VMs only Plex docker and transmission docker. Didn't get a chance to pull logs because I did not yet have a syslog server setup. Restored to 6.10.3 using the restore functionality and the issue has not yet reoccurred.
  6. Just posting for anyone that had any trouble getting the CloudReady VM images to boot. https://neverware.zendesk.com/hc/en-us/articles/214564457--UPDATED-Un-Official-CloudReady-Virtual-Machine-Images- Convert to raw img using: tar xvf CloudReady_48.1_x64_Virtualbox.ova $ qemu-img convert -O raw CloudReady_Free_x64-disk1.vmdk CloudReady_Free_x64-disk1.img This gave me a a raw disk img with several partitions $ fdisk -l CloudReady_Free_x64-disk1.img Disk CloudReady_Free_x64-disk1.img: 16 GiB, 17179869184 bytes, 33554432 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 95B869D9-9524-604B-B8E5-E739B78E9518 Device Start End Sectors Size Type CloudReady_Free_x64-disk1.img1 64 64 1 512B ChromeOS reserved CloudReady_Free_x64-disk1.img2 65 65 1 512B ChromeOS reserved CloudReady_Free_x64-disk1.img3 66 66 1 512B ChromeOS reserved CloudReady_Free_x64-disk1.img4 67 67 1 512B ChromeOS reserved CloudReady_Free_x64-disk1.img5 68 68 1 512B ChromeOS reserved CloudReady_Free_x64-disk1.img6 69 69 1 512B ChromeOS reserved CloudReady_Free_x64-disk1.img7 70 70 1 512B ChromeOS reserved CloudReady_Free_x64-disk1.img8 71 71 1 512B ChromeOS reserved CloudReady_Free_x64-disk1.img9 72 72 1 512B ChromeOS reserved CloudReady_Free_x64-disk1.img10 73 73 1 512B ChromeOS reserved CloudReady_Free_x64-disk1.img11 74 74 1 512B ChromeOS reserved CloudReady_Free_x64-disk1.img12 75 75 1 512B ChromeOS reserved CloudReady_Free_x64-disk1.img13 76 76 1 512B ChromeOS reserved CloudReady_Free_x64-disk1.img14 77 77 1 512B ChromeOS reserved CloudReady_Free_x64-disk1.img15 78 78 1 512B ChromeOS reserved CloudReady_Free_x64-disk1.img16 14831682 33554397 18722716 8.9G Microsoft basic data CloudReady_Free_x64-disk1.img17 20546 53313 32768 16M ChromeOS kernel CloudReady_Free_x64-disk1.img18 8589378 14831681 6242304 3G ChromeOS root fs CloudReady_Free_x64-disk1.img19 53314 86081 32768 16M ChromeOS kernel CloudReady_Free_x64-disk1.img20 2347074 8589377 6242304 3G ChromeOS root fs CloudReady_Free_x64-disk1.img21 16514 16514 1 512B ChromeOS kernel CloudReady_Free_x64-disk1.img22 16515 16515 1 512B ChromeOS root fs CloudReady_Free_x64-disk1.img23 86082 2183233 2097152 1G Microsoft basic data CloudReady_Free_x64-disk1.img24 16516 16516 1 512B ChromeOS reserved CloudReady_Free_x64-disk1.img25 16517 16517 1 512B ChromeOS reserved CloudReady_Free_x64-disk1.img26 130 16513 16384 8M unknown CloudReady_Free_x64-disk1.img27 2314306 2347073 32768 16M EFI System Set XML up as follows: <domain type='kvm' id='19'> <name>ChromeOS OVMF</name> <uuid>355e8d91-618e-e9bf-5469-4440741c75ac</uuid> <metadata> <vmtemplate xmlns="unraid" name="ChromeOS" icon="chromeos.png" os="chromeos"/> </metadata> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>2</vcpu> <cputune> <vcpupin vcpu='0' cpuset='3'/> <vcpupin vcpu='1' cpuset='7'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-2.7'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/355e8d91-618e-e9bf-5469-4440741c75ac_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='1' threads='2'/> </cpu> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/ChromeOS/CloudReady_Free_x64-disk1.img'/> <backingStore/> <target dev='hdc' bus='ide'/> <boot order='1'/> <alias name='ide0-1-0'/> <address type='drive' controller='0' bus='1' target='0' unit='0'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <controller type='ide' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <interface type='bridge'> <mac address='52:54:00:bf:9d:c7'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target port='0'/> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-19-ChromeOS OVMF/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='usb'> <address type='usb' bus='0' port='2'/> </input> <input type='keyboard' bus='ps2'/> <input type='mouse' bus='ps2'/> <graphics type='vnc' port='5900' autoport='yes' websocket='5700' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </memballoon> </devices> <seclabel type='none' model='none'/> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain> Image booted. And completed Setup. I was unable to use any mouse input thru VNC. If anyone finds a fix for that let me know. EDIT: Adding an additional input type fixed the issue. <input type='mouse' bus='usb'> EDIT2: May have spoken too soon. Looks like the mouse still has an issue with offset on VNC. Investigating.
  7. Bought this card: https://www.amazon.com/gp/product/B00FPIMJEW/ref=oh_aui_detailpage_o00_s00?ie=UTF8&psc=1 Appears to use the VIA VL812 Chipset. Stubbed the card and was able to passthrough to a Windows 10 VM. VM started and windows detected the card. However if I reset the VM, unraid becomes unresponsive. I get no video output from the Passthrough (VM) GPU or the integrated (Unraid Console) Unraid also stops responding to ping requests and I am unable to bring up the web interface. Only way I could find to recover was a hard reset. So I removed the card and the issue resolved. Is this just incompatible hardware or did I miss a step. If the former does anyone have any suggestions on known working PCIe USB cards? default /syslinux/menu.c32 menu title Lime Technology, Inc. prompt 0 timeout 50 label unRAID OS menu default kernel /bzimage append isolcpus=2,3,6,7 pci-stub.ids=1b73:1100 initrd=/bzroot label unRAID OS GUI Mode kernel /bzimage append initrd=/bzroot,/bzroot-gui label unRAID OS Safe Mode (no plugins, no GUI) kernel /bzimage append initrd=/bzroot unraidsafemode label Memtest86+ kernel /memtest IOMMU group 0 00:00.0 Host bridge [0600]: Intel Corporation Skylake Host Bridge/DRAM Registers [8086:191f] (rev 07) IOMMU group 1 00:01.0 PCI bridge [0604]: Intel Corporation Skylake PCIe Controller (x16) [8086:1901] (rev 07) 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) 01:00.1 Audio device [0403]: NVIDIA Corporation GP104 High Definition Audio Controller [10de:10f0] (rev a1) IOMMU group 2 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) IOMMU group 3 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller [8086:a12f] (rev 31) 00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-H Thermal subsystem [8086:a131] (rev 31) IOMMU group 4 00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-H CSME HECI #1 [8086:a13a] (rev 31) IOMMU group 5 00:17.0 SATA controller [0106]: Intel Corporation Sunrise Point-H SATA controller [AHCI mode] [8086:a102] (rev 31) IOMMU group 6 00:1b.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Root Port #17 [8086:a167] (rev f1) 00:1b.2 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Root Port #19 [8086:a169] (rev f1) 00:1b.3 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Root Port #20 [8086:a16a] (rev f1) 04:00.0 SATA controller [0106]: ASMedia Technology Inc. ASM1062 Serial ATA Controller [1b21:0612] (rev 02) IOMMU group 7 00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #1 [8086:a110] (rev f1) 00:1c.2 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #3 [8086:a112] (rev f1) 00:1c.4 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #5 [8086:a114] (rev f1) 06:00.0 Ethernet controller [0200]: Qualcomm Atheros Killer E2400 Gigabit Ethernet Controller [1969:e0a1] (rev 10) 07:00.0 PCI bridge [0604]: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] [8086:1578] 08:00.0 PCI bridge [0604]: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] [8086:1578] 08:01.0 PCI bridge [0604]: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] [8086:1578] 08:02.0 PCI bridge [0604]: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] [8086:1578] 08:04.0 PCI bridge [0604]: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] [8086:1578] 3d:00.0 USB controller [0c03]: Intel Corporation DSL6540 USB 3.1 Controller [Alpine Ridge] [8086:15b6] IOMMU group 8 03:00.0 USB controller [0c03]: Fresco Logic FL1100 USB 3.0 Host Controller [1b73:1100] (rev 10) 00:1d.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #9 [8086:a118] (rev f1) 00:1d.4 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #13 [8086:a11c] (rev f1) IOMMU group 9 00:1f.0 ISA bridge [0601]: Intel Corporation Sunrise Point-H LPC Controller [8086:a145] (rev 31) 00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-H PMC [8086:a121] (rev 31) 00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-H HD Audio [8086:a170] (rev 31) 00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-H SMBus [8086:a123] (rev 31) IOMMU group 10 00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (2) I219-V [8086:15b8] (rev 31)
  8. Anyone else having issues with downloaded files permissions. All downloads have a permissions set of -rw-r--r-- instead of -rw-rw-rw-
  9. Got unRAID up and running and installed a windows 10 VM. Working without issue for a while but now I occasionally get sound issues. Distorted/slow sound. I had these issues when I first setup the VM but switched to the onboard sound controller instead of the Video cards sound through HDMI. That worked for a while but the issue seems to have returned. I've attached my configs and hardware setup below. I've also been seeing these messages in terminal when starting the vm. Not sure if this is normal or not. Message from syslogd@Tower at Jul 30 12:34:38 ... kernel:Disabling IRQ #16 System: Model: Custom M/B: Gigabyte Technology Co., Ltd. - Z170X-Gaming 7 CPU: Intel® Core™ i7-6700 CPU @ 3.40GHz HVM: Enabled IOMMU: Enabled Cache: 128 kB, 1024 kB, 8192 kB Memory: 16 GB (max. installable capacity 64 GB) Network: eth0: 100 Mb/s, full duplex, mtu 1500 eth1: not connected Kernel: Linux 4.4.15-unRAID x86_64 OpenSSL: 1.0.2h Uptime:0 days, 17:46:37 Graphics card: GIGABYTE GeForce GTX 1070 DirectX 12 GV-N1070G1 GAMING-8GD 8GB 256-Bit GDDR5 PCI Express 3.0 x16 ATX Video Card Windows 10 VM XML <domain type='kvm'> <name>Windows 10</name> <uuid>3caf7ea0-6756-aa4d-7d12-dd8553dfae46</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>12582912</memory> <currentMemory unit='KiB'>12582912</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='3'/> <vcpupin vcpu='2' cpuset='6'/> <vcpupin vcpu='3' cpuset='7'/> <emulatorpin cpuset='0,4'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-2.5'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/3caf7ea0-6756-aa4d-7d12-dd8553dfae46_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor id='none'/> </hyperv> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='2' threads='2'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Windows 10/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/Windows10x64.iso'/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.118-2.iso'/> <target dev='hdb' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='nec-xhci'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <controller type='pci' index='0' model='pci-root'/> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:21:2f:44'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <source mode='connect'/> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x00' slot='0x1f' function='0x3'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x045e'/> <product id='0x02d1'/> </source> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc52b'/> </source> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </memballoon> </devices> </domain> Syslinux configuration default /syslinux/menu.c32 menu title Lime Technology, Inc. prompt 0 timeout 50 label unRAID OS menu default kernel /bzimage append isolcpus=2,3,6,7 initrd=/bzroot label unRAID OS GUI Mode kernel /bzimage append initrd=/bzroot,/bzroot-gui label unRAID OS Safe Mode (no plugins, no GUI) kernel /bzimage append initrd=/bzroot unraidsafemode label Memtest86+ kernel /memtest PCI Devices 00:00.0 Host bridge [0600]: Intel Corporation Skylake Host Bridge/DRAM Registers [8086:191f] (rev 07) 00:01.0 PCI bridge [0604]: Intel Corporation Skylake PCIe Controller (x16) [8086:1901] (rev 07) 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller [8086:a12f] (rev 31) 00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-H Thermal subsystem [8086:a131] (rev 31) 00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-H CSME HECI #1 [8086:a13a] (rev 31) 00:17.0 SATA controller [0106]: Intel Corporation Sunrise Point-H SATA controller [AHCI mode] [8086:a102] (rev 31) 00:1b.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Root Port #17 [8086:a167] (rev f1) 00:1b.3 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Root Port #20 [8086:a16a] (rev f1) 00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #1 [8086:a110] (rev f1) 00:1c.2 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #3 [8086:a112] (rev f1) 00:1c.4 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #5 [8086:a114] (rev f1) 00:1d.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #9 [8086:a118] (rev f1) 00:1d.4 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #13 [8086:a11c] (rev f1) 00:1f.0 ISA bridge [0601]: Intel Corporation Sunrise Point-H LPC Controller [8086:a145] (rev 31) 00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-H PMC [8086:a121] (rev 31) 00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-H HD Audio [8086:a170] (rev 31) 00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-H SMBus [8086:a123] (rev 31) 00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (2) I219-V [8086:15b8] (rev 31) 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP104 [10de:1b81] (rev a1) 01:00.1 Audio device [0403]: NVIDIA Corporation Device [10de:10f0] (rev a1) 03:00.0 SATA controller [0106]: ASMedia Technology Inc. ASM1062 Serial ATA Controller [1b21:0612] (rev 02) 05:00.0 Ethernet controller [0200]: Qualcomm Atheros Killer E2400 Gigabit Ethernet Controller [1969:e0a1] (rev 10) 06:00.0 PCI bridge [0604]: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] [8086:1578] 07:00.0 PCI bridge [0604]: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] [8086:1578] 07:01.0 PCI bridge [0604]: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] [8086:1578] 07:02.0 PCI bridge [0604]: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] [8086:1578] 07:04.0 PCI bridge [0604]: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] [8086:1578] 0a:00.0 USB controller [0c03]: Intel Corporation DSL6540 USB 3.1 Controller [Alpine Ridge] [8086:15b6] IOMMU Groups /sys/kernel/iommu_groups/0/devices/0000:00:00.0 /sys/kernel/iommu_groups/1/devices/0000:00:01.0 /sys/kernel/iommu_groups/1/devices/0000:01:00.0 /sys/kernel/iommu_groups/1/devices/0000:01:00.1 /sys/kernel/iommu_groups/2/devices/0000:00:02.0 /sys/kernel/iommu_groups/3/devices/0000:00:14.0 /sys/kernel/iommu_groups/3/devices/0000:00:14.2 /sys/kernel/iommu_groups/4/devices/0000:00:16.0 /sys/kernel/iommu_groups/5/devices/0000:00:17.0 /sys/kernel/iommu_groups/6/devices/0000:00:1b.0 /sys/kernel/iommu_groups/6/devices/0000:00:1b.3 /sys/kernel/iommu_groups/6/devices/0000:03:00.0 /sys/kernel/iommu_groups/7/devices/0000:00:1c.0 /sys/kernel/iommu_groups/7/devices/0000:00:1c.2 /sys/kernel/iommu_groups/7/devices/0000:00:1c.4 /sys/kernel/iommu_groups/7/devices/0000:05:00.0 /sys/kernel/iommu_groups/7/devices/0000:06:00.0 /sys/kernel/iommu_groups/7/devices/0000:07:00.0 /sys/kernel/iommu_groups/7/devices/0000:07:01.0 /sys/kernel/iommu_groups/7/devices/0000:07:02.0 /sys/kernel/iommu_groups/7/devices/0000:07:04.0 /sys/kernel/iommu_groups/7/devices/0000:0a:00.0 /sys/kernel/iommu_groups/8/devices/0000:00:1d.0 /sys/kernel/iommu_groups/8/devices/0000:00:1d.4 /sys/kernel/iommu_groups/9/devices/0000:00:1f.0 /sys/kernel/iommu_groups/9/devices/0000:00:1f.2 /sys/kernel/iommu_groups/9/devices/0000:00:1f.3 /sys/kernel/iommu_groups/9/devices/0000:00:1f.4 /sys/kernel/iommu_groups/10/devices/0000:00:1f.6 01:00.0 VGA compatible controller: NVIDIA Corporation GP104 (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device 3701 Flags: bus master, fast devsel, latency 0, IRQ 134 Memory at de000000 (32-bit, non-prefetchable) [size=16M] Memory at b0000000 (64-bit, prefetchable) [size=256M] Memory at c0000000 (64-bit, prefetchable) [size=32M] I/O ports at e000 [size=128] Expansion ROM at df000000 [disabled] [size=512K] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Legacy Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [250] Latency Tolerance Reporting Capabilities: [128] Power Budgeting <?> Capabilities: [420] Advanced Error Reporting Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?> Capabilities: [900] #19 Kernel driver in use: vfio-pci USB Devices Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 045b:0210 Hitachi, Ltd Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0781:55a0 SanDisk Corp. Bus 001 Device 005: ID 045e:02d1 Microsoft Corp. XBOX One Controller for Windows Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 045b:0209 Hitachi, Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub SCSI Devices [0:0:0:0] disk Sandisk Timeshift 1100 /dev/sda [1:0:0:0] disk ATA Hitachi HUA72302 A840 /dev/sdb [2:0:0:0] disk ATA Hitachi HUA72302 A840 /dev/sdc [4:0:0:0] disk ATA Samsung SSD 850 1B6Q /dev/sdd [6:0:0:0] disk ATA Hitachi HUA72302 A840 /dev/sde