cablecutter

Members
  • Posts

    55
  • Joined

  • Last visited

Everything posted by cablecutter

  1. Ran into this same issue and depending on your motherboard you may have to "disable all C-states" instead of using the disable c6 option. I have a x370 ASRock and was not stable with just disable c6 on. This is disappointing...but you can still save power by enabling "cool n quiet" operation. In my case, this drops the processor down to 1200Mhz along with the voltage.
  2. Hi All, I'm out of ideas and could use a push on the right direction. I have a new bit of hardware, a Ryzen AM4 build on an Asrock X370 Taichi board. I am running a windows 10 VM. There are two devices that I would like to pass through (highlighted in the image below): An integrated Wifi Controller with Bluetooth (09:00.0) A PCIE USB controller (0a:00.0) The trouble is that these devices share a n IOMMU grouping with my main NIC (also integrated), which I hear is a no-no. I've tried: Setting ACS Override to Y (results shown) Setting "Iommu Groupings" to 'enabled' in the bios Flipping other rather undocumented switches in the bios that seem to be related to PCIE cards...wish I could remember which ones. What can I try next? Best, Rob
  3. Hi All, Trying to pass through a PCI-E USB card to a windows 10 VM. The IOMMU groups with ACS override look like: IOMMU group 0: [1022:1452] 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge IOMMU group 1: [1022:1453] 00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge IOMMU group 2: [1022:1453] 00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge IOMMU group 3: [1022:1452] 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge IOMMU group 4: [1022:1452] 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge IOMMU group 5: [1022:1453] 00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge IOMMU group 6: [1022:1452] 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge IOMMU group 7: [1022:1452] 00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge IOMMU group 8: [1022:1454] 00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B IOMMU group 9: [1022:1452] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge IOMMU group 10: [1022:1454] 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B IOMMU group 11: [1022:790b] 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 59) [1022:790e] 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) IOMMU group 12: [1022:1460] 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 0 [1022:1461] 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 1 [1022:1462] 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 2 [1022:1463] 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 3 [1022:1464] 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 4 [1022:1465] 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 5 [1022:1466] 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric Device 18h Function 6 [1022:1467] 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 7 IOMMU group 13: [126f:2260] 01:00.0 Non-Volatile memory controller: Silicon Motion, Inc. Device 2260 (rev 03) IOMMU group 14: [1022:43b9] 03:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] Device 43b9 (rev 02) [1022:43b5] 03:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] Device 43b5 (rev 02) [1022:43b0] 03:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43b0 (rev 02) [1022:43b4] 04:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1022:43b4] 04:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1022:43b4] 04:03.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1022:43b4] 04:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1b21:0612] 06:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02) [1b21:1184] 07:00.0 PCI bridge: ASMedia Technology Inc. Device 1184 [1b21:1184] 08:01.0 PCI bridge: ASMedia Technology Inc. Device 1184 [1b21:1184] 08:03.0 PCI bridge: ASMedia Technology Inc. Device 1184 [1b21:1184] 08:05.0 PCI bridge: ASMedia Technology Inc. Device 1184 [1b21:1184] 08:07.0 PCI bridge: ASMedia Technology Inc. Device 1184 [8086:24fb] 09:00.0 Network controller: Intel Corporation Dual Band Wireless-AC 3168NGW [Stone Peak] (rev 10) [1106:3483] 0a:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller (rev 01) [8086:1539] 0b:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03) IOMMU group 15: [1002:67ff] 0e:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 560] (rev cf) [1002:aae0] 0e:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device aae0 IOMMU group 16: [1022:145a] 11:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Device 145a [1022:1456] 11:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor [1022:145c] 11:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) USB 3.0 Host Controller IOMMU group 17: [1022:1455] 12:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Device 1455 [1022:7901] 12:00.2 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) [1022:1457] 12:00.3 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) HD Audio Controller The important bit is Group 14, where the "VIA Technologies, INC host controller" lives. However, it shares a group with the network controller, and the main USB controller (where my unRaid OS lives). Obviously I can't pass through this group... so I'm not sure what to do? I spent $40 on a USB card hoping that this would make it simple, but it doesn't seem like it has. root@Tower:~# lspci | grep USB 03:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] Device 43b9 (rev 02) 0a:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller (re v 01) 11:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00 h-0fh) USB 3.0 Host Controller root@Tower:~# lsusb Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 004: ID 045e:0719 Microsoft Corp. Xbox 360 Wireless Adapter Bus 003 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 003 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0aa7 Intel Corp. Bus 001 Device 002: ID 0781:5571 SanDisk Corp. Cruzer Fit Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub root@Tower:~# readlink /sys/bus/usb/devices/usb3 ../../../devices/pci0000:00/0000:00:01.3/0000:03:00.2/0000:04:03.0/0000:07:00.0/0000:08:03.0/0000:0a:00.0/usb3 I have an ASROCK Taichi x370 motherboard my XML is: <domain type='kvm'> <name>Windows 10</name> <uuid>15667ac1-2465-fe33-d840-a54b512b265b</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>24641536</memory> <currentMemory unit='KiB'>24641536</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>10</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='3'/> <vcpupin vcpu='2' cpuset='4'/> <vcpupin vcpu='3' cpuset='5'/> <vcpupin vcpu='4' cpuset='6'/> <vcpupin vcpu='5' cpuset='7'/> <vcpupin vcpu='6' cpuset='8'/> <vcpupin vcpu='7' cpuset='9'/> <vcpupin vcpu='8' cpuset='10'/> <vcpupin vcpu='9' cpuset='11'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-2.10'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/15667ac1-2465-fe33-d840-a54b512b265b_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='10' threads='1'/> </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/Windows_10_x64.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.141-1.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='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <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'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </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:4e:e0:7e'/> <source bridge='virbr0'/> <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'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0e' 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='0x0e' slot='0x00' function='0x1'/> </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='0x0719'/> </source> <address type='usb' bus='0' port='1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc52b'/> </source> <address type='usb' bus='0' port='2'/> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </memballoon> </devices> </domain> Any help would be loved
  4. Hi All, Trying to pass through a PCI-E USB card to a windows 10 VM. The IOMMU groups with ACS override look like: IOMMU group 0: [1022:1452] 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge IOMMU group 1: [1022:1453] 00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge IOMMU group 2: [1022:1453] 00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge IOMMU group 3: [1022:1452] 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge IOMMU group 4: [1022:1452] 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge IOMMU group 5: [1022:1453] 00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge IOMMU group 6: [1022:1452] 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge IOMMU group 7: [1022:1452] 00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge IOMMU group 8: [1022:1454] 00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B IOMMU group 9: [1022:1452] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge IOMMU group 10: [1022:1454] 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B IOMMU group 11: [1022:790b] 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 59) [1022:790e] 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) IOMMU group 12: [1022:1460] 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 0 [1022:1461] 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 1 [1022:1462] 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 2 [1022:1463] 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 3 [1022:1464] 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 4 [1022:1465] 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 5 [1022:1466] 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric Device 18h Function 6 [1022:1467] 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 7 IOMMU group 13: [126f:2260] 01:00.0 Non-Volatile memory controller: Silicon Motion, Inc. Device 2260 (rev 03) IOMMU group 14: [1022:43b9] 03:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] Device 43b9 (rev 02) [1022:43b5] 03:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] Device 43b5 (rev 02) [1022:43b0] 03:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43b0 (rev 02) [1022:43b4] 04:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1022:43b4] 04:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1022:43b4] 04:03.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1022:43b4] 04:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1b21:0612] 06:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02) [1b21:1184] 07:00.0 PCI bridge: ASMedia Technology Inc. Device 1184 [1b21:1184] 08:01.0 PCI bridge: ASMedia Technology Inc. Device 1184 [1b21:1184] 08:03.0 PCI bridge: ASMedia Technology Inc. Device 1184 [1b21:1184] 08:05.0 PCI bridge: ASMedia Technology Inc. Device 1184 [1b21:1184] 08:07.0 PCI bridge: ASMedia Technology Inc. Device 1184 [8086:24fb] 09:00.0 Network controller: Intel Corporation Dual Band Wireless-AC 3168NGW [Stone Peak] (rev 10) [1106:3483] 0a:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller (rev 01) [8086:1539] 0b:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03) IOMMU group 15: [1002:67ff] 0e:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 560] (rev cf) [1002:aae0] 0e:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device aae0 IOMMU group 16: [1022:145a] 11:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Device 145a [1022:1456] 11:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor [1022:145c] 11:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) USB 3.0 Host Controller IOMMU group 17: [1022:1455] 12:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Device 1455 [1022:7901] 12:00.2 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) [1022:1457] 12:00.3 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) HD Audio Controller The important bit is Group 14, where the "VIA Technologies, INC host controller" lives. However, it shares a group with the network controller, and the main USB controller (where my unRaid OS lives). Obviously I can't pass through this group... so I'm not sure what to do? I spent $40 on a USB card hoping that this would make it simple, but it doesn't seem like it has. I have an ASROCK Taichi x370 motherboard my XML is: <domain type='kvm'> <name>Windows 10</name> <uuid>15667ac1-2465-fe33-d840-a54b512b265b</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>24641536</memory> <currentMemory unit='KiB'>24641536</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>10</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='3'/> <vcpupin vcpu='2' cpuset='4'/> <vcpupin vcpu='3' cpuset='5'/> <vcpupin vcpu='4' cpuset='6'/> <vcpupin vcpu='5' cpuset='7'/> <vcpupin vcpu='6' cpuset='8'/> <vcpupin vcpu='7' cpuset='9'/> <vcpupin vcpu='8' cpuset='10'/> <vcpupin vcpu='9' cpuset='11'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-2.10'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/15667ac1-2465-fe33-d840-a54b512b265b_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='10' threads='1'/> </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/Windows_10_x64.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.141-1.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='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <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'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </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:4e:e0:7e'/> <source bridge='virbr0'/> <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'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0e' 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='0x0e' slot='0x00' function='0x1'/> </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='0x0719'/> </source> <address type='usb' bus='0' port='1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc52b'/> </source> <address type='usb' bus='0' port='2'/> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </memballoon> </devices> </domain> Any help would be loved
  5. Hi All, I ran some searches and came up empty - figured it couldn't hurt to ask. I have recently set up a windows 10 VM on a UnRaid 6.4 machine. I'm new to VM configuration and the method for passing through peripheral devices is not 100% clear to me. My motherboard is an Asrock Taichi x370. It has on-board bluetooth which I would like to use for Logitech Harmony Hub control of my windows VM. However, I have not been able to figure out how to pass through the Bluetooth to the VM and am not really sure where to start. Any help would be sincerely appreciated. Best, Rob
  6. [Solved] For some reason my port changed... Contents of ident.cfg NAME="Tower" timeZone="America/New_York" COMMENT="Media server" SECURITY="user" [[[[[OBSCURED]]]]] SYS_CACHE_SLOTS="1" USE_SSL="auto" PORT="81" PORTSSL="443"
  7. Also running processes: PID TTY TIME CMD 1 ? 00:00:07 init 2 ? 00:00:00 kthreadd 3 ? 00:00:00 kworker/0:0 4 ? 00:00:00 kworker/0:0H 6 ? 00:00:00 mm_percpu_wq 7 ? 00:00:00 ksoftirqd/0 8 ? 00:00:00 rcu_preempt 9 ? 00:00:00 rcu_sched 10 ? 00:00:00 rcu_bh 11 ? 00:00:00 migration/0 12 ? 00:00:00 cpuhp/0 13 ? 00:00:00 cpuhp/1 14 ? 00:00:00 migration/1 15 ? 00:00:00 ksoftirqd/1 16 ? 00:00:00 kworker/1:0 17 ? 00:00:00 kworker/1:0H 18 ? 00:00:00 cpuhp/2 19 ? 00:00:00 migration/2 20 ? 00:00:00 ksoftirqd/2 22 ? 00:00:00 kworker/2:0H 23 ? 00:00:00 cpuhp/3 24 ? 00:00:00 migration/3 25 ? 00:00:00 ksoftirqd/3 26 ? 00:00:00 kworker/3:0 27 ? 00:00:00 kworker/3:0H 28 ? 00:00:00 cpuhp/4 29 ? 00:00:00 migration/4 30 ? 00:00:00 ksoftirqd/4 31 ? 00:00:00 kworker/4:0 32 ? 00:00:00 kworker/4:0H 33 ? 00:00:00 cpuhp/5 34 ? 00:00:00 migration/5 35 ? 00:00:00 ksoftirqd/5 36 ? 00:00:00 kworker/5:0 37 ? 00:00:00 kworker/5:0H 38 ? 00:00:00 cpuhp/6 39 ? 00:00:00 migration/6 40 ? 00:00:00 ksoftirqd/6 41 ? 00:00:00 kworker/6:0 42 ? 00:00:00 kworker/6:0H 43 ? 00:00:00 cpuhp/7 44 ? 00:00:00 migration/7 45 ? 00:00:00 ksoftirqd/7 46 ? 00:00:00 kworker/7:0 47 ? 00:00:00 kworker/7:0H 48 ? 00:00:00 cpuhp/8 49 ? 00:00:00 migration/8 50 ? 00:00:00 ksoftirqd/8 51 ? 00:00:00 kworker/8:0 52 ? 00:00:00 kworker/8:0H 53 ? 00:00:00 cpuhp/9 54 ? 00:00:00 migration/9 55 ? 00:00:00 ksoftirqd/9 56 ? 00:00:00 kworker/9:0 57 ? 00:00:00 kworker/9:0H 58 ? 00:00:00 cpuhp/10 59 ? 00:00:00 migration/10 60 ? 00:00:00 ksoftirqd/10 61 ? 00:00:00 kworker/10:0 62 ? 00:00:00 kworker/10:0H 63 ? 00:00:00 cpuhp/11 64 ? 00:00:00 migration/11 65 ? 00:00:00 ksoftirqd/11 66 ? 00:00:00 kworker/11:0 67 ? 00:00:00 kworker/11:0H 68 ? 00:00:00 kdevtmpfs 69 ? 00:00:00 netns 83 ? 00:00:00 kworker/7:1 86 ? 00:00:00 kworker/4:1 90 ? 00:00:00 kworker/8:1 117 ? 00:00:00 kworker/6:1 120 ? 00:00:00 kworker/5:1 132 ? 00:00:00 kworker/3:1 135 ? 00:00:00 kworker/10:1 146 ? 00:00:00 kworker/11:1 151 ? 00:00:00 kworker/1:1 346 ? 00:00:00 oom_reaper 347 ? 00:00:00 writeback 349 ? 00:00:00 kcompactd0 350 ? 00:00:00 ksmd 351 ? 00:00:00 khugepaged 352 ? 00:00:00 crypto 353 ? 00:00:00 kintegrityd 355 ? 00:00:00 kblockd 606 ? 00:00:00 kworker/9:1 607 ? 00:00:00 ata_sff 627 ? 00:00:00 edac-poller 628 ? 00:00:00 devfreq_wq 730 ? 00:00:00 irq/25-AMD-Vi 790 ? 00:00:00 kswapd0 899 ? 00:00:00 kthrotld 1021 ? 00:00:00 amd_iommu_v2 1068 ? 00:00:00 vfio-irqfd-clea 1128 ? 00:00:00 kworker/u32:6 1166 ? 00:00:00 ipv6_addrconf 1199 ? 00:00:00 kworker/2:2 1200 ? 00:00:00 kworker/2:3 1204 ? 00:00:00 scsi_eh_0 1205 ? 00:00:00 scsi_tmf_0 1206 ? 00:00:00 usb-storage 1351 ? 00:00:00 udevd 1420 ? 00:00:00 loop0 1421 ? 00:00:00 kworker/11:1H 1422 ? 00:00:00 kworker/2:1H 1423 ? 00:00:00 kworker/7:1H 1424 ? 00:00:00 loop1 1425 ? 00:00:00 kworker/0:1H 1426 ? 00:00:00 kworker/4:1H 1436 ? 00:00:00 kworker/9:1H 1465 ? 00:00:00 kworker/8:1H 1482 ? 00:00:00 kworker/1:1H 1494 ? 00:00:00 kworker/10:1H 1495 ? 00:00:00 kworker/3:1H 1496 ? 00:00:00 nvme-wq 1497 ? 00:00:00 ccp-1-q2 1498 ? 00:00:00 ccp-1-q3 1499 ? 00:00:00 ccp-1-q4 1500 ? 00:00:00 kworker/6:1H 1501 ? 00:00:00 scsi_eh_1 1502 ? 00:00:00 scsi_tmf_1 1503 ? 00:00:00 scsi_eh_2 1504 ? 00:00:00 scsi_tmf_2 1505 ? 00:00:00 scsi_eh_3 1506 ? 00:00:00 scsi_tmf_3 1507 ? 00:00:00 scsi_eh_4 1508 ? 00:00:00 scsi_tmf_4 1509 ? 00:00:00 scsi_eh_5 1510 ? 00:00:00 scsi_tmf_5 1511 ? 00:00:00 scsi_eh_6 1512 ? 00:00:00 scsi_tmf_6 1513 ? 00:00:00 scsi_eh_7 1514 ? 00:00:00 scsi_tmf_7 1515 ? 00:00:00 scsi_eh_8 1516 ? 00:00:00 scsi_tmf_8 1518 ? 00:00:00 kworker/u32:8 1520 ? 00:00:00 scsi_eh_9 1521 ? 00:00:00 scsi_tmf_9 1522 ? 00:00:00 scsi_eh_10 1523 ? 00:00:00 scsi_tmf_10 1524 ? 00:00:00 kworker/u32:10 1525 ? 00:00:00 kworker/u32:11 1526 ? 00:00:00 scsi_eh_11 1527 ? 00:00:00 scsi_tmf_11 1623 ? 00:00:00 rsyslogd 1773 ? 00:00:00 kworker/0:2 1812 ? 00:00:00 dhcpcd 1826 ? 00:00:00 dbus-daemon 1834 ? 00:00:00 rpcbind 1838 ? 00:00:00 rpc.statd 1848 ? 00:00:00 inetd 1856 ? 00:00:00 sshd 1873 ? 00:00:00 ntpd 1879 ? 00:00:00 acpid 1889 ? 00:00:00 crond 1891 ? 00:00:00 atd 1897 ? 00:00:00 nmbd 1899 ? 00:00:00 smbd 1901 ? 00:00:00 smbd-notifyd 1902 ? 00:00:00 cleanupd 1904 ? 00:00:00 winbindd 1906 ? 00:00:00 winbindd 3677 ? 00:00:00 udevd 3678 ? 00:00:00 udevd 3679 ? 00:00:00 udevd 4082 tty1 00:00:00 agetty 4083 tty2 00:00:00 agetty 4084 tty3 00:00:00 agetty 4085 tty4 00:00:00 agetty 4086 tty5 00:00:00 agetty 4087 tty6 00:00:00 agetty 4089 ? 00:00:00 udevd 4105 ? 00:00:00 md 4106 ? 00:00:00 mdrecoveryd 4110 ? 00:00:00 spinupd 4111 ? 00:00:00 spinupd 4112 ? 00:00:00 spinupd 4113 ? 00:00:00 spinupd 4141 ? 00:00:00 avahi-daemon 4142 ? 00:00:00 avahi-daemon 4151 ? 00:00:00 avahi-dnsconfd 4166 ? 00:00:03 emhttpd 4171 ? 00:00:00 php-fpm 4193 ? 00:00:01 ttyd 4196 ? 00:00:00 nginx 4197 ? 00:00:00 nginx 4540 ? 00:00:00 sshd 4566 pts/0 00:00:00 bash 5339 ? 00:00:00 kworker/u32:0 5374 ? 00:00:00 winbindd 5697 ? 00:00:00 kworker/5:1H 6438 pts/0 00:00:00 ps
  8. This might also help: My unRaid box is also networked in an unconventional and unflattering way. Though at this point I'm not sure that's the issue since I can telnet / see the web from the box etc. This is a new setup for this build and is temporary as we'll be moving in a few months. Verizon Fios Modem -> Verizon Fios Quantum Gateway (Router) -> Ubiquiti Unifi UAP Pro (access point) -> ~5ghz~ -> e3200 router running tomato firmware (Wireless ethernet bridge) -> Unraid Box Best, Rob
  9. Hi all, I'm about to lose my mind. I have had a unRaid server running for a few years and just upgraded all of my hardware. I moved all drives / USB over to a new box and everything booted up just fine. I cannot access the webGUI Some quick info: UnRaid starts, gets to login, promts for user / pass able to log in, able to view ifconfig running v6.4 (was stable on last box) able to SSH to the box from desktop where I'm trying to access the GUI Able to get ping google from the unRaid box (network access) Desktop I'm trying to access the UI from is inside my network I am trying to access the webGUI using 192.168.1.218:80 I have not changed the default port All hardware except for the HDD's is new ifConfig results: @Tower:~# ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.218 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::7285:c2ff:fe6b:180c prefixlen 64 scopeid 0x20<link> ether 70:85:c2:6b:18:0c txqueuelen 1000 (Ethernet) RX packets 3063 bytes 503516 (491.7 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 3846 bytes 845054 (825.2 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device memory 0xfe000000-fe01ffff lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 2 bytes 140 (140.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2 bytes 140 (140.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 Netstat results: @Tower:~# netstat -plnt Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:37 0.0.0.0:* LISTEN 1827/inetd tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN 1877/smbd tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 1813/rpcbind tcp 0 0 0.0.0.0:81 0.0.0.0:* LISTEN 4189/nginx: master tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN 1827/inetd tcp 0 0 0.0.0.0:51061 0.0.0.0:* LISTEN 1817/rpc.statd tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1835/sshd tcp 0 0 0.0.0.0:23 0.0.0.0:* LISTEN 1827/inetd tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 4189/nginx: master tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN 1877/smbd tcp6 0 0 :::53035 :::* LISTEN 1817/rpc.statd tcp6 0 0 :::139 :::* LISTEN 1877/smbd tcp6 0 0 :::111 :::* LISTEN 1813/rpcbind tcp6 0 0 :::81 :::* LISTEN 4189/nginx: master tcp6 0 0 :::22 :::* LISTEN 1835/sshd tcp6 0 0 :::443 :::* LISTEN 4189/nginx: master tcp6 0 0 :::445 :::* LISTEN 1877/smbd Full log: Feb 5 14:47:27 Tower kernel: Linux version 4.14.13-unRAID (root@develop64) (gcc version 7.2.0 (GCC)) #1 SMP PREEMPT Wed Jan 10 10:27:09 PST 2018 Feb 5 14:47:27 Tower kernel: Command line: BOOT_IMAGE=/bzimage initrd=/bzroot Feb 5 14:47:27 Tower kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' Feb 5 14:47:27 Tower kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' Feb 5 14:47:27 Tower kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' Feb 5 14:47:27 Tower kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 Feb 5 14:47:27 Tower kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format. Feb 5 14:47:27 Tower kernel: e820: BIOS-provided physical RAM map: Feb 5 14:47:27 Tower kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009d3ff] usable Feb 5 14:47:27 Tower kernel: BIOS-e820: [mem 0x000000000009d400-0x000000000009ffff] reserved Feb 5 14:47:27 Tower kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved Feb 5 14:47:27 Tower kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000009cfffff] usable Feb 5 14:47:27 Tower kernel: BIOS-e820: [mem 0x0000000009d00000-0x0000000009ffffff] reserved Feb 5 14:47:27 Tower kernel: BIOS-e820: [mem 0x000000000a000000-0x00000000dadecfff] usable Feb 5 14:47:27 Tower kernel: BIOS-e820: [mem 0x00000000daded000-0x00000000dc356fff] reserved Feb 5 14:47:27 Tower kernel: BIOS-e820: [mem 0x00000000dc357000-0x00000000dc449fff] usable Feb 5 14:47:27 Tower kernel: BIOS-e820: [mem 0x00000000dc44a000-0x00000000dc81bfff] ACPI NVS Feb 5 14:47:27 Tower kernel: BIOS-e820: [mem 0x00000000dc81c000-0x00000000dd23ffff] reserved Feb 5 14:47:27 Tower kernel: BIOS-e820: [mem 0x00000000dd240000-0x00000000deffffff] usable Feb 5 14:47:27 Tower kernel: BIOS-e820: [mem 0x00000000df000000-0x00000000dfffffff] reserved Feb 5 14:47:27 Tower kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved Feb 5 14:47:27 Tower kernel: BIOS-e820: [mem 0x00000000fdf00000-0x00000000fdffffff] reserved Feb 5 14:47:27 Tower kernel: BIOS-e820: [mem 0x00000000fea00000-0x00000000fea0ffff] reserved Feb 5 14:47:27 Tower kernel: BIOS-e820: [mem 0x00000000feb80000-0x00000000fec01fff] reserved Feb 5 14:47:27 Tower kernel: BIOS-e820: [mem 0x00000000fec10000-0x00000000fec10fff] reserved Feb 5 14:47:27 Tower kernel: BIOS-e820: [mem 0x00000000fec30000-0x00000000fec30fff] reserved Feb 5 14:47:27 Tower kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved Feb 5 14:47:27 Tower kernel: BIOS-e820: [mem 0x00000000fed40000-0x00000000fed44fff] reserved Feb 5 14:47:27 Tower kernel: BIOS-e820: [mem 0x00000000fed80000-0x00000000fed8ffff] reserved Feb 5 14:47:27 Tower kernel: BIOS-e820: [mem 0x00000000fedc2000-0x00000000fedcffff] reserved Feb 5 14:47:27 Tower kernel: BIOS-e820: [mem 0x00000000fedd4000-0x00000000fedd5fff] reserved Feb 5 14:47:27 Tower kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000feefffff] reserved Feb 5 14:47:27 Tower kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved Feb 5 14:47:27 Tower kernel: BIOS-e820: [mem 0x0000000100000000-0x000000081f37ffff] usable Feb 5 14:47:27 Tower kernel: NX (Execute Disable) protection: active Feb 5 14:47:27 Tower kernel: random: fast init done Feb 5 14:47:27 Tower kernel: SMBIOS 3.0.0 present. Feb 5 14:47:27 Tower kernel: DMI: To Be Filled By O.E.M. To Be Filled By O.E.M./X370 Taichi, BIOS P3.20 09/08/2017 Feb 5 14:47:27 Tower kernel: tsc: Fast TSC calibration failed Feb 5 14:47:27 Tower kernel: tsc: Using PIT calibration value Feb 5 14:47:27 Tower kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved Feb 5 14:47:27 Tower kernel: e820: remove [mem 0x000a0000-0x000fffff] usable Feb 5 14:47:27 Tower kernel: e820: last_pfn = 0x81f380 max_arch_pfn = 0x400000000 Feb 5 14:47:27 Tower kernel: MTRR default type: uncachable Feb 5 14:47:27 Tower kernel: MTRR fixed ranges enabled: Feb 5 14:47:27 Tower kernel: 00000-9FFFF write-back Feb 5 14:47:27 Tower kernel: A0000-BFFFF write-through Feb 5 14:47:27 Tower kernel: C0000-FFFFF write-protect Feb 5 14:47:27 Tower kernel: MTRR variable ranges enabled: Feb 5 14:47:27 Tower kernel: 0 base 000000000000 mask FFFF80000000 write-back Feb 5 14:47:27 Tower kernel: 1 base 000080000000 mask FFFFC0000000 write-back Feb 5 14:47:27 Tower kernel: 2 base 0000C0000000 mask FFFFE0000000 write-back Feb 5 14:47:27 Tower kernel: 3 base 0000DF000000 mask FFFFFF000000 uncachable Feb 5 14:47:27 Tower kernel: 4 disabled Feb 5 14:47:27 Tower kernel: 5 disabled Feb 5 14:47:27 Tower kernel: 6 disabled Feb 5 14:47:27 Tower kernel: 7 disabled Feb 5 14:47:27 Tower kernel: TOM2: 0000000820000000 aka 33280M Feb 5 14:47:27 Tower kernel: x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT Feb 5 14:47:27 Tower kernel: e820: update [mem 0xdf000000-0xffffffff] usable ==> reserved Feb 5 14:47:27 Tower kernel: e820: last_pfn = 0xdf000 max_arch_pfn = 0x400000000 Feb 5 14:47:27 Tower kernel: Base memory trampoline at [ffff880000097000] 97000 size 24576 Feb 5 14:47:27 Tower kernel: Using GB pages for direct mapping Feb 5 14:47:27 Tower kernel: BRK [0x0202d000, 0x0202dfff] PGTABLE Feb 5 14:47:27 Tower kernel: BRK [0x0202e000, 0x0202efff] PGTABLE Feb 5 14:47:27 Tower kernel: BRK [0x0202f000, 0x0202ffff] PGTABLE Feb 5 14:47:27 Tower kernel: BRK [0x02030000, 0x02030fff] PGTABLE Feb 5 14:47:27 Tower kernel: BRK [0x02031000, 0x02031fff] PGTABLE Feb 5 14:47:27 Tower kernel: BRK [0x02032000, 0x02032fff] PGTABLE Feb 5 14:47:27 Tower kernel: RAMDISK: [mem 0x7b143000-0x7fffffff] Feb 5 14:47:27 Tower kernel: ACPI: Early table checksum verification disabled Feb 5 14:47:27 Tower kernel: ACPI: RSDP 0x00000000000F05B0 000024 (v02 ALASKA) Feb 5 14:47:27 Tower kernel: ACPI: XSDT 0x00000000DC44A098 0000AC (v01 ALASKA A M I 01072009 AMI 00010013) Feb 5 14:47:27 Tower kernel: ACPI: FACP 0x00000000DC450030 000114 (v06 ALASKA A M I 01072009 AMI 00010013) Feb 5 14:47:27 Tower kernel: ACPI BIOS Warning (bug): Optional FADT field Pm2ControlBlock has valid Length but zero Address: 0x0000000000000000/0x1 (20170728/tbfadt-658) Feb 5 14:47:27 Tower kernel: ACPI: DSDT 0x00000000DC44A1D8 005E57 (v02 ALASKA A M I 01072009 INTL 20120913) Feb 5 14:47:27 Tower kernel: ACPI: FACS 0x00000000DC819C80 000040 Feb 5 14:47:27 Tower kernel: ACPI: APIC 0x00000000DC450148 0000DE (v03 ALASKA A M I 01072009 AMI 00010013) Feb 5 14:47:27 Tower kernel: ACPI: FPDT 0x00000000DC450228 000044 (v01 ALASKA A M I 01072009 AMI 00010013) Feb 5 14:47:27 Tower kernel: ACPI: SSDT 0x00000000DC450270 008C4C (v02 AMD AMD ALIB 00000002 MSFT 04000000) Feb 5 14:47:27 Tower kernel: ACPI: FIDT 0x00000000DC458EC0 00009C (v01 ALASKA A M I 01072009 AMI 00010013) Feb 5 14:47:27 Tower kernel: ACPI: SSDT 0x00000000DC458F60 0018B4 (v01 AMD AMD CPU 00000001 AMD 00000001) Feb 5 14:47:27 Tower kernel: ACPI: CRAT 0x00000000DC45A818 000BD0 (v01 AMD AMD CRAT 00000001 AMD 00000001) Feb 5 14:47:27 Tower kernel: ACPI: CDIT 0x00000000DC45B3E8 000029 (v01 AMD AMD CDIT 00000001 AMD 00000001) Feb 5 14:47:27 Tower kernel: ACPI: SSDT 0x00000000DC45B418 001721 (v01 AMD AMD AOD 00000001 INTL 20120913) Feb 5 14:47:27 Tower kernel: ACPI: MCFG 0x00000000DC45CB40 00003C (v01 ALASKA A M I 01072009 MSFT 00010013) Feb 5 14:47:27 Tower kernel: ACPI: AAFT 0x00000000DC45CB80 00032C (v01 ALASKA OEMAAFT 01072009 MSFT 00000097) Feb 5 14:47:27 Tower kernel: ACPI: HPET 0x00000000DC45CEB0 000038 (v01 ALASKA A M I 01072009 AMI 00000005) Feb 5 14:47:27 Tower kernel: ACPI: SSDT 0x00000000DC45CEE8 000024 (v01 AMDFCH FCHZP 00001000 INTL 20120913) Feb 5 14:47:27 Tower kernel: ACPI: UEFI 0x00000000DC45CF10 000042 (v01 00000000 00000000) Feb 5 14:47:27 Tower kernel: ACPI: IVRS 0x00000000DC45CF58 0000D0 (v02 AMD AMD IVRS 00000001 AMD 00000000) Feb 5 14:47:27 Tower kernel: ACPI: SSDT 0x00000000DC45D028 0000F8 (v01 AMD AMD PT 00001000 INTL 20120913) Feb 5 14:47:27 Tower kernel: ACPI: SSDT 0x00000000DC45D120 001664 (v01 AMD CPMCMN 00000001 INTL 20120913) Feb 5 14:47:27 Tower kernel: ACPI: Local APIC address 0xfee00000 Feb 5 14:47:27 Tower kernel: system APIC only can use physical flat Feb 5 14:47:27 Tower kernel: Setting APIC routing to physical flat. Feb 5 14:47:27 Tower kernel: No NUMA configuration found Feb 5 14:47:27 Tower kernel: Faking a node at [mem 0x0000000000000000-0x000000081f37ffff] Feb 5 14:47:27 Tower kernel: NODE_DATA(0) allocated [mem 0x81f37c000-0x81f37ffff] Feb 5 14:47:27 Tower kernel: Zone ranges: Feb 5 14:47:27 Tower kernel: DMA [mem 0x0000000000001000-0x0000000000ffffff] Feb 5 14:47:27 Tower kernel: DMA32 [mem 0x0000000001000000-0x00000000ffffffff] Feb 5 14:47:27 Tower kernel: Normal [mem 0x0000000100000000-0x000000081f37ffff] Feb 5 14:47:27 Tower kernel: Movable zone start for each node Feb 5 14:47:27 Tower kernel: Early memory node ranges Feb 5 14:47:27 Tower kernel: node 0: [mem 0x0000000000001000-0x000000000009cfff] Feb 5 14:47:27 Tower kernel: node 0: [mem 0x0000000000100000-0x0000000009cfffff] Feb 5 14:47:27 Tower kernel: node 0: [mem 0x000000000a000000-0x00000000dadecfff] Feb 5 14:47:27 Tower kernel: node 0: [mem 0x00000000dc357000-0x00000000dc449fff] Feb 5 14:47:27 Tower kernel: node 0: [mem 0x00000000dd240000-0x00000000deffffff] Feb 5 14:47:27 Tower kernel: node 0: [mem 0x0000000100000000-0x000000081f37ffff] Feb 5 14:47:27 Tower kernel: Initmem setup node 0 [mem 0x0000000000001000-0x000000081f37ffff] Feb 5 14:47:27 Tower kernel: On node 0 totalpages: 8371388 Feb 5 14:47:27 Tower kernel: DMA zone: 64 pages used for memmap Feb 5 14:47:27 Tower kernel: DMA zone: 21 pages reserved Feb 5 14:47:27 Tower kernel: DMA zone: 3996 pages, LIFO batch:0 Feb 5 14:47:27 Tower kernel: DMA32 zone: 14055 pages used for memmap Feb 5 14:47:27 Tower kernel: DMA32 zone: 899488 pages, LIFO batch:31 Feb 5 14:47:27 Tower kernel: Normal zone: 116686 pages used for memmap Feb 5 14:47:27 Tower kernel: Normal zone: 7467904 pages, LIFO batch:31 Feb 5 14:47:27 Tower kernel: ACPI: PM-Timer IO Port: 0x808 Feb 5 14:47:27 Tower kernel: ACPI: Local APIC address 0xfee00000 Feb 5 14:47:27 Tower kernel: system APIC only can use physical flat Feb 5 14:47:27 Tower kernel: ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1]) Feb 5 14:47:27 Tower kernel: IOAPIC[0]: apic_id 13, version 33, address 0xfec00000, GSI 0-23 Feb 5 14:47:27 Tower kernel: IOAPIC[1]: apic_id 14, version 33, address 0xfec01000, GSI 24-55 Feb 5 14:47:27 Tower kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) Feb 5 14:47:27 Tower kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level) Feb 5 14:47:27 Tower kernel: ACPI: IRQ0 used by override. Feb 5 14:47:27 Tower kernel: ACPI: IRQ9 used by override. Feb 5 14:47:27 Tower kernel: Using ACPI (MADT) for SMP configuration information Feb 5 14:47:27 Tower kernel: ACPI: HPET id: 0x10228201 base: 0xfed00000 Feb 5 14:47:27 Tower kernel: smpboot: Allowing 16 CPUs, 4 hotplug CPUs Feb 5 14:47:27 Tower kernel: e820: [mem 0xe0000000-0xf7ffffff] available for PCI devices Feb 5 14:47:27 Tower kernel: Booting paravirtualized kernel on bare hardware Feb 5 14:47:27 Tower kernel: clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1910969940391419 ns Feb 5 14:47:27 Tower kernel: setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:1 Feb 5 14:47:27 Tower kernel: percpu: Embedded 43 pages/cpu @ffff88081ec00000 s139032 r8192 d28904 u262144 Feb 5 14:47:27 Tower kernel: pcpu-alloc: s139032 r8192 d28904 u262144 alloc=1*2097152 Feb 5 14:47:27 Tower kernel: pcpu-alloc: [0] 00 01 02 03 04 05 06 07 [0] 08 09 10 11 12 13 14 15 Feb 5 14:47:27 Tower kernel: Built 1 zonelists, mobility grouping on. Total pages: 8240562 Feb 5 14:47:27 Tower kernel: Policy zone: Normal Feb 5 14:47:27 Tower kernel: Kernel command line: BOOT_IMAGE=/bzimage initrd=/bzroot Feb 5 14:47:27 Tower kernel: PID hash table entries: 4096 (order: 3, 32768 bytes) Feb 5 14:47:27 Tower kernel: Memory: 32795120K/33485552K available (8204K kernel code, 702K rwdata, 1944K rodata, 1076K init, 508K bss, 690432K reserved, 0K cma-reserved) Feb 5 14:47:27 Tower kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=1 Feb 5 14:47:27 Tower kernel: Preemptible hierarchical RCU implementation. Feb 5 14:47:27 Tower kernel: RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16. Feb 5 14:47:27 Tower kernel: Tasks RCU enabled. Feb 5 14:47:27 Tower kernel: RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=16 Feb 5 14:47:27 Tower kernel: NR_IRQS: 16640, nr_irqs: 1096, preallocated irqs: 16 Feb 5 14:47:27 Tower kernel: Offload RCU callbacks from CPUs: . Feb 5 14:47:27 Tower kernel: Console: colour VGA+ 80x25 Feb 5 14:47:27 Tower kernel: console [tty0] enabled Feb 5 14:47:27 Tower kernel: clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 133484873504 ns Feb 5 14:47:27 Tower kernel: hpet clockevent registered Feb 5 14:47:27 Tower kernel: tsc: Fast TSC calibration failed Feb 5 14:47:27 Tower kernel: tsc: PIT calibration matches HPET. 1 loops Feb 5 14:47:27 Tower kernel: tsc: Detected 3199.937 MHz processor Feb 5 14:47:27 Tower kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 6399.87 BogoMIPS (lpj=3199937) Feb 5 14:47:27 Tower kernel: pid_max: default: 32768 minimum: 301 Feb 5 14:47:27 Tower kernel: ACPI: Core revision 20170728 Feb 5 14:47:27 Tower kernel: ACPI: 7 ACPI AML tables successfully acquired and loaded Feb 5 14:47:27 Tower kernel: Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes) Feb 5 14:47:27 Tower kernel: Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes) Feb 5 14:47:27 Tower kernel: Mount-cache hash table entries: 65536 (order: 7, 524288 bytes) Feb 5 14:47:27 Tower kernel: Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes) Feb 5 14:47:27 Tower kernel: CPU: Physical Processor ID: 0 Feb 5 14:47:27 Tower kernel: CPU: Processor Core ID: 0 Feb 5 14:47:27 Tower kernel: mce: CPU supports 23 MCE banks Feb 5 14:47:27 Tower kernel: LVT offset 1 assigned for vector 0xf9 Feb 5 14:47:27 Tower kernel: LVT offset 2 assigned for vector 0xf4 Feb 5 14:47:27 Tower kernel: Last level iTLB entries: 4KB 1024, 2MB 1024, 4MB 512 Feb 5 14:47:27 Tower kernel: Last level dTLB entries: 4KB 1536, 2MB 1536, 4MB 768, 1GB 0 Feb 5 14:47:27 Tower kernel: Freeing SMP alternatives memory: 28K Feb 5 14:47:27 Tower kernel: smpboot: Max logical packages: 3 Feb 5 14:47:27 Tower kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 Feb 5 14:47:27 Tower kernel: smpboot: CPU0: AMD Ryzen 5 1600 Six-Core Processor (family: 0x17, model: 0x1, stepping: 0x1) Feb 5 14:47:27 Tower kernel: Performance Events: Fam17h core perfctr, AMD PMU driver. Feb 5 14:47:27 Tower kernel: ... version: 0 Feb 5 14:47:27 Tower kernel: ... bit width: 48 Feb 5 14:47:27 Tower kernel: ... generic registers: 6 Feb 5 14:47:27 Tower kernel: ... value mask: 0000ffffffffffff Feb 5 14:47:27 Tower kernel: ... max period: 00007fffffffffff Feb 5 14:47:27 Tower kernel: ... fixed-purpose events: 0 Feb 5 14:47:27 Tower kernel: ... event mask: 000000000000003f Feb 5 14:47:27 Tower kernel: Hierarchical SRCU implementation. Feb 5 14:47:27 Tower kernel: smp: Bringing up secondary CPUs ... Feb 5 14:47:27 Tower kernel: x86: Booting SMP configuration: Feb 5 14:47:27 Tower kernel: .... node #0, CPUs: #1 #2 #3 #4 #5 Feb 5 14:47:27 Tower kernel: mce: [Hardware Error]: Machine check events logged Feb 5 14:47:27 Tower kernel: mce: [Hardware Error]: CPU 5: Machine Check: 0 Bank 5: bea0000000000108 Feb 5 14:47:27 Tower kernel: mce: [Hardware Error]: TSC 0 ADDR 1ffff815d4d50 MISC d012000101000000 SYND 4d000000 IPID 500b000000000 Feb 5 14:47:27 Tower kernel: mce: [Hardware Error]: PROCESSOR 2:800f11 TIME 1517860030 SOCKET 0 APIC 5 microcode 8001129 Feb 5 14:47:27 Tower kernel: #6 #7 #8 #9 #10 #11 Feb 5 14:47:27 Tower kernel: smp: Brought up 1 node, 12 CPUs Feb 5 14:47:27 Tower kernel: smpboot: Total of 12 processors activated (76798.48 BogoMIPS) Feb 5 14:47:27 Tower kernel: devtmpfs: initialized Feb 5 14:47:27 Tower kernel: x86/mm: Memory block size: 128MB Feb 5 14:47:27 Tower kernel: PM: Registering ACPI NVS region [mem 0xdc44a000-0xdc81bfff] (4005888 bytes) Feb 5 14:47:27 Tower kernel: clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275000 ns Feb 5 14:47:27 Tower kernel: futex hash table entries: 4096 (order: 6, 262144 bytes) Feb 5 14:47:27 Tower kernel: xor: automatically using best checksumming function avx Feb 5 14:47:27 Tower kernel: pinctrl core: initialized pinctrl subsystem Feb 5 14:47:27 Tower kernel: NET: Registered protocol family 16 Feb 5 14:47:27 Tower kernel: cpuidle: using governor ladder Feb 5 14:47:27 Tower kernel: cpuidle: using governor menu Feb 5 14:47:27 Tower kernel: ACPI: bus type PCI registered Feb 5 14:47:27 Tower kernel: PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000) Feb 5 14:47:27 Tower kernel: PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820 Feb 5 14:47:27 Tower kernel: PCI: Using configuration type 1 for base access Feb 5 14:47:27 Tower kernel: raid6: sse2x1 gen() 7324 MB/s Feb 5 14:47:27 Tower kernel: raid6: sse2x1 xor() 6248 MB/s Feb 5 14:47:27 Tower kernel: raid6: sse2x2 gen() 14292 MB/s Feb 5 14:47:27 Tower kernel: raid6: sse2x2 xor() 9912 MB/s Feb 5 14:47:27 Tower kernel: raid6: sse2x4 gen() 15144 MB/s Feb 5 14:47:27 Tower kernel: raid6: sse2x4 xor() 7480 MB/s Feb 5 14:47:27 Tower kernel: raid6: avx2x1 gen() 16777 MB/s Feb 5 14:47:27 Tower kernel: raid6: avx2x1 xor() 12330 MB/s Feb 5 14:47:27 Tower kernel: raid6: avx2x2 gen() 22667 MB/s Feb 5 14:47:27 Tower kernel: raid6: avx2x2 xor() 13382 MB/s Feb 5 14:47:27 Tower kernel: raid6: avx2x4 gen() 23632 MB/s Feb 5 14:47:27 Tower kernel: raid6: avx2x4 xor() 12658 MB/s Feb 5 14:47:27 Tower kernel: raid6: using algorithm avx2x4 gen() 23632 MB/s Feb 5 14:47:27 Tower kernel: raid6: .... xor() 12658 MB/s, rmw enabled Feb 5 14:47:27 Tower kernel: raid6: using avx2x2 recovery algorithm Feb 5 14:47:27 Tower kernel: ACPI: Added _OSI(Module Device) Feb 5 14:47:27 Tower kernel: ACPI: Added _OSI(Processor Device) Feb 5 14:47:27 Tower kernel: ACPI: Added _OSI(3.0 _SCP Extensions) Feb 5 14:47:27 Tower kernel: ACPI: Added _OSI(Processor Aggregator Device) Feb 5 14:47:27 Tower kernel: ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored Feb 5 14:47:27 Tower kernel: ACPI: Executed 2 blocks of module-level executable AML code Feb 5 14:47:27 Tower kernel: ACPI: Interpreter enabled Feb 5 14:47:27 Tower kernel: ACPI: (supports S0 S3 S5) Feb 5 14:47:27 Tower kernel: ACPI: Using IOAPIC for interrupt routing Feb 5 14:47:27 Tower kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug Feb 5 14:47:27 Tower kernel: ACPI: Enabled 2 GPEs in block 00 to 1F Feb 5 14:47:27 Tower kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff]) Feb 5 14:47:27 Tower kernel: acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] Feb 5 14:47:27 Tower kernel: acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability] Feb 5 14:47:27 Tower kernel: acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-3f] only partially covers this bridge Feb 5 14:47:27 Tower kernel: PCI host bridge to bus 0000:00 Feb 5 14:47:27 Tower kernel: pci_bus 0000:00: root bus resource [io 0x0000-0x03af window] Feb 5 14:47:27 Tower kernel: pci_bus 0000:00: root bus resource [io 0x03e0-0x0cf7 window] Feb 5 14:47:27 Tower kernel: pci_bus 0000:00: root bus resource [io 0x03b0-0x03df window] Feb 5 14:47:27 Tower kernel: pci_bus 0000:00: root bus resource [io 0x0d00-0xffff window] Feb 5 14:47:27 Tower kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window] Feb 5 14:47:27 Tower kernel: pci_bus 0000:00: root bus resource [mem 0x000c0000-0x000dffff window] Feb 5 14:47:27 Tower kernel: pci_bus 0000:00: root bus resource [mem 0xe0000000-0xfec2ffff window] Feb 5 14:47:27 Tower kernel: pci_bus 0000:00: root bus resource [mem 0xfee00000-0xffffffff window] Feb 5 14:47:27 Tower kernel: pci_bus 0000:00: root bus resource [bus 00-ff] Feb 5 14:47:27 Tower kernel: pci 0000:00:00.0: [1022:1450] type 00 class 0x060000 Feb 5 14:47:27 Tower kernel: pci 0000:00:00.2: [1022:1451] type 00 class 0x080600 Feb 5 14:47:27 Tower kernel: pci 0000:00:01.0: [1022:1452] type 00 class 0x060000 Feb 5 14:47:27 Tower kernel: pci 0000:00:01.1: [1022:1453] type 01 class 0x060400 Feb 5 14:47:27 Tower kernel: pci 0000:00:01.1: PME# supported from D0 D3hot D3cold Feb 5 14:47:27 Tower kernel: pci 0000:00:01.3: [1022:1453] type 01 class 0x060400 Feb 5 14:47:27 Tower kernel: pci 0000:00:01.3: PME# supported from D0 D3hot D3cold Feb 5 14:47:27 Tower kernel: pci 0000:00:02.0: [1022:1452] type 00 class 0x060000 Feb 5 14:47:27 Tower kernel: pci 0000:00:03.0: [1022:1452] type 00 class 0x060000 Feb 5 14:47:27 Tower kernel: pci 0000:00:03.1: [1022:1453] type 01 class 0x060400 Feb 5 14:47:27 Tower kernel: pci 0000:00:03.1: PME# supported from D0 D3hot D3cold Feb 5 14:47:27 Tower kernel: pci 0000:00:04.0: [1022:1452] type 00 class 0x060000 Feb 5 14:47:27 Tower kernel: pci 0000:00:07.0: [1022:1452] type 00 class 0x060000 Feb 5 14:47:27 Tower kernel: pci 0000:00:07.1: [1022:1454] type 01 class 0x060400 Feb 5 14:47:27 Tower kernel: pci 0000:00:07.1: enabling Extended Tags Feb 5 14:47:27 Tower kernel: pci 0000:00:07.1: PME# supported from D0 D3hot D3cold Feb 5 14:47:27 Tower kernel: pci 0000:00:08.0: [1022:1452] type 00 class 0x060000 Feb 5 14:47:27 Tower kernel: pci 0000:00:08.1: [1022:1454] type 01 class 0x060400 Feb 5 14:47:27 Tower kernel: pci 0000:00:08.1: enabling Extended Tags Feb 5 14:47:27 Tower kernel: pci 0000:00:08.1: PME# supported from D0 D3hot D3cold Feb 5 14:47:27 Tower kernel: pci 0000:00:14.0: [1022:790b] type 00 class 0x0c0500 Feb 5 14:47:27 Tower kernel: pci 0000:00:14.3: [1022:790e] type 00 class 0x060100 Feb 5 14:47:27 Tower kernel: pci 0000:00:18.0: [1022:1460] type 00 class 0x060000 Feb 5 14:47:27 Tower kernel: pci 0000:00:18.1: [1022:1461] type 00 class 0x060000 Feb 5 14:47:27 Tower kernel: pci 0000:00:18.2: [1022:1462] type 00 class 0x060000 Feb 5 14:47:27 Tower kernel: pci 0000:00:18.3: [1022:1463] type 00 class 0x060000 Feb 5 14:47:27 Tower kernel: pci 0000:00:18.4: [1022:1464] type 00 class 0x060000 Feb 5 14:47:27 Tower kernel: pci 0000:00:18.5: [1022:1465] type 00 class 0x060000 Feb 5 14:47:27 Tower kernel: pci 0000:00:18.6: [1022:1466] type 00 class 0x060000 Feb 5 14:47:27 Tower kernel: pci 0000:00:18.7: [1022:1467] type 00 class 0x060000 Feb 5 14:47:27 Tower kernel: pci 0000:01:00.0: [126f:2260] type 00 class 0x010802 Feb 5 14:47:27 Tower kernel: pci 0000:01:00.0: reg 0x10: [mem 0xfe900000-0xfe903fff 64bit] Feb 5 14:47:27 Tower kernel: pci 0000:00:01.1: PCI bridge to [bus 01] Feb 5 14:47:27 Tower kernel: pci 0000:00:01.1: bridge window [mem 0xfe900000-0xfe9fffff] Feb 5 14:47:27 Tower kernel: pci 0000:03:00.0: [1022:43b9] type 00 class 0x0c0330 Feb 5 14:47:27 Tower kernel: pci 0000:03:00.0: reg 0x10: [mem 0xfe3a0000-0xfe3a7fff 64bit] Feb 5 14:47:27 Tower kernel: pci 0000:03:00.0: PME# supported from D3hot D3cold Feb 5 14:47:27 Tower kernel: pci 0000:03:00.1: [1022:43b5] type 00 class 0x010601 Feb 5 14:47:27 Tower kernel: pci 0000:03:00.1: reg 0x24: [mem 0xfe380000-0xfe39ffff] Feb 5 14:47:27 Tower kernel: pci 0000:03:00.1: reg 0x30: [mem 0xfe300000-0xfe37ffff pref] Feb 5 14:47:27 Tower kernel: pci 0000:03:00.1: PME# supported from D3hot D3cold Feb 5 14:47:27 Tower kernel: pci 0000:03:00.2: [1022:43b0] type 01 class 0x060400 Feb 5 14:47:27 Tower kernel: pci 0000:03:00.2: PME# supported from D3hot D3cold Feb 5 14:47:27 Tower kernel: pci 0000:00:01.3: PCI bridge to [bus 03-0d] Feb 5 14:47:27 Tower kernel: pci 0000:00:01.3: bridge window [io 0xd000-0xefff] Feb 5 14:47:27 Tower kernel: pci 0000:00:01.3: bridge window [mem 0xfe000000-0xfe3fffff] Feb 5 14:47:27 Tower kernel: pci 0000:04:00.0: [1022:43b4] type 01 class 0x060400 Feb 5 14:47:27 Tower kernel: pci 0000:04:00.0: PME# supported from D3hot D3cold Feb 5 14:47:27 Tower kernel: pci 0000:04:02.0: [1022:43b4] type 01 class 0x060400 Feb 5 14:47:27 Tower kernel: pci 0000:04:02.0: PME# supported from D3hot D3cold Feb 5 14:47:27 Tower kernel: pci 0000:04:03.0: [1022:43b4] type 01 class 0x060400 Feb 5 14:47:27 Tower kernel: pci 0000:04:03.0: PME# supported from D3hot D3cold Feb 5 14:47:27 Tower kernel: pci 0000:04:04.0: [1022:43b4] type 01 class 0x060400 Feb 5 14:47:27 Tower kernel: pci 0000:04:04.0: PME# supported from D3hot D3cold Feb 5 14:47:27 Tower kernel: pci 0000:03:00.2: PCI bridge to [bus 04-0d] Feb 5 14:47:27 Tower kernel: pci 0000:03:00.2: bridge window [io 0xd000-0xefff] Feb 5 14:47:27 Tower kernel: pci 0000:03:00.2: bridge window [mem 0xfe000000-0xfe2fffff] Feb 5 14:47:27 Tower kernel: pci 0000:04:00.0: PCI bridge to [bus 05] Feb 5 14:47:27 Tower kernel: pci 0000:06:00.0: [1b21:0612] type 00 class 0x010601 Feb 5 14:47:27 Tower kernel: pci 0000:06:00.0: reg 0x10: [io 0xe050-0xe057] Feb 5 14:47:27 Tower kernel: pci 0000:06:00.0: reg 0x14: [io 0xe040-0xe043] Feb 5 14:47:27 Tower kernel: pci 0000:06:00.0: reg 0x18: [io 0xe030-0xe037] Feb 5 14:47:27 Tower kernel: pci 0000:06:00.0: reg 0x1c: [io 0xe020-0xe023] Feb 5 14:47:27 Tower kernel: pci 0000:06:00.0: reg 0x20: [io 0xe000-0xe01f] Feb 5 14:47:27 Tower kernel: pci 0000:06:00.0: reg 0x24: [mem 0xfe200000-0xfe2001ff] Feb 5 14:47:27 Tower kernel: pci 0000:04:02.0: PCI bridge to [bus 06] Feb 5 14:47:27 Tower kernel: pci 0000:04:02.0: bridge window [io 0xe000-0xefff] Feb 5 14:47:27 Tower kernel: pci 0000:04:02.0: bridge window [mem 0xfe200000-0xfe2fffff] Feb 5 14:47:27 Tower kernel: pci 0000:07:00.0: [1b21:1184] type 01 class 0x060400 Feb 5 14:47:27 Tower kernel: pci 0000:07:00.0: PME# supported from D0 D3hot D3cold Feb 5 14:47:27 Tower kernel: pci 0000:04:03.0: PCI bridge to [bus 07-0c] Feb 5 14:47:27 Tower kernel: pci 0000:04:03.0: bridge window [io 0xd000-0xdfff] Feb 5 14:47:27 Tower kernel: pci 0000:04:03.0: bridge window [mem 0xfe000000-0xfe1fffff] Feb 5 14:47:27 Tower kernel: pci 0000:08:01.0: [1b21:1184] type 01 class 0x060400 Feb 5 14:47:27 Tower kernel: pci 0000:08:01.0: PME# supported from D0 D3hot D3cold Feb 5 14:47:27 Tower kernel: pci 0000:08:03.0: [1b21:1184] type 01 class 0x060400 Feb 5 14:47:27 Tower kernel: pci 0000:08:03.0: PME# supported from D0 D3hot D3cold Feb 5 14:47:27 Tower kernel: pci 0000:08:05.0: [1b21:1184] type 01 class 0x060400 Feb 5 14:47:27 Tower kernel: pci 0000:08:05.0: PME# supported from D0 D3hot D3cold Feb 5 14:47:27 Tower kernel: pci 0000:08:07.0: [1b21:1184] type 01 class 0x060400 Feb 5 14:47:27 Tower kernel: pci 0000:08:07.0: PME# supported from D0 D3hot D3cold Feb 5 14:47:27 Tower kernel: pci 0000:07:00.0: PCI bridge to [bus 08-0c] Feb 5 14:47:27 Tower kernel: pci 0000:07:00.0: bridge window [io 0xd000-0xdfff] Feb 5 14:47:27 Tower kernel: pci 0000:07:00.0: bridge window [mem 0xfe000000-0xfe1fffff] Feb 5 14:47:27 Tower kernel: pci 0000:09:00.0: [8086:24fb] type 00 class 0x028000 Feb 5 14:47:27 Tower kernel: pci 0000:09:00.0: reg 0x10: [mem 0xfe100000-0xfe101fff 64bit] Feb 5 14:47:27 Tower kernel: pci 0000:09:00.0: PME# supported from D0 D3hot D3cold Feb 5 14:47:27 Tower kernel: pci 0000:08:01.0: PCI bridge to [bus 09] Feb 5 14:47:27 Tower kernel: pci 0000:08:01.0: bridge window [mem 0xfe100000-0xfe1fffff] Feb 5 14:47:27 Tower kernel: pci 0000:08:03.0: PCI bridge to [bus 0a] Feb 5 14:47:27 Tower kernel: pci 0000:0b:00.0: [8086:1539] type 00 class 0x020000 Feb 5 14:47:27 Tower kernel: pci 0000:0b:00.0: reg 0x10: [mem 0xfe000000-0xfe01ffff] Feb 5 14:47:27 Tower kernel: pci 0000:0b:00.0: reg 0x18: [io 0xd000-0xd01f] Feb 5 14:47:27 Tower kernel: pci 0000:0b:00.0: reg 0x1c: [mem 0xfe020000-0xfe023fff] Feb 5 14:47:27 Tower kernel: pci 0000:0b:00.0: PME# supported from D0 D3hot D3cold Feb 5 14:47:27 Tower kernel: pci 0000:08:05.0: PCI bridge to [bus 0b] Feb 5 14:47:27 Tower kernel: pci 0000:08:05.0: bridge window [io 0xd000-0xdfff] Feb 5 14:47:27 Tower kernel: pci 0000:08:05.0: bridge window [mem 0xfe000000-0xfe0fffff] Feb 5 14:47:27 Tower kernel: pci 0000:08:07.0: PCI bridge to [bus 0c] Feb 5 14:47:27 Tower kernel: pci 0000:04:04.0: PCI bridge to [bus 0d] Feb 5 14:47:27 Tower kernel: pci 0000:0e:00.0: [1002:67ff] type 00 class 0x030000 Feb 5 14:47:27 Tower kernel: pci 0000:0e:00.0: reg 0x10: [mem 0xe0000000-0xefffffff 64bit pref] Feb 5 14:47:27 Tower kernel: pci 0000:0e:00.0: reg 0x18: [mem 0xf0000000-0xf01fffff 64bit pref] Feb 5 14:47:27 Tower kernel: pci 0000:0e:00.0: reg 0x20: [io 0xf000-0xf0ff] Feb 5 14:47:27 Tower kernel: pci 0000:0e:00.0: reg 0x24: [mem 0xfe800000-0xfe83ffff] Feb 5 14:47:27 Tower kernel: pci 0000:0e:00.0: reg 0x30: [mem 0xfe840000-0xfe85ffff pref] Feb 5 14:47:27 Tower kernel: pci 0000:0e:00.0: supports D1 D2 Feb 5 14:47:27 Tower kernel: pci 0000:0e:00.0: PME# supported from D1 D2 D3hot D3cold Feb 5 14:47:27 Tower kernel: pci 0000:0e:00.1: [1002:aae0] type 00 class 0x040300 Feb 5 14:47:27 Tower kernel: pci 0000:0e:00.1: reg 0x10: [mem 0xfe860000-0xfe863fff 64bit] Feb 5 14:47:27 Tower kernel: pci 0000:0e:00.1: supports D1 D2 Feb 5 14:47:27 Tower kernel: pci 0000:00:03.1: PCI bridge to [bus 0e] Feb 5 14:47:27 Tower kernel: pci 0000:00:03.1: bridge window [io 0xf000-0xffff] Feb 5 14:47:27 Tower kernel: pci 0000:00:03.1: bridge window [mem 0xfe800000-0xfe8fffff] Feb 5 14:47:27 Tower kernel: pci 0000:00:03.1: bridge window [mem 0xe0000000-0xf01fffff 64bit pref] Feb 5 14:47:27 Tower kernel: pci 0000:11:00.0: [1022:145a] type 00 class 0x130000 Feb 5 14:47:27 Tower kernel: pci 0000:11:00.0: enabling Extended Tags Feb 5 14:47:27 Tower kernel: pci 0000:11:00.2: [1022:1456] type 00 class 0x108000 Feb 5 14:47:27 Tower kernel: pci 0000:11:00.2: reg 0x18: [mem 0xfe500000-0xfe5fffff] Feb 5 14:47:27 Tower kernel: pci 0000:11:00.2: reg 0x24: [mem 0xfe600000-0xfe601fff] Feb 5 14:47:27 Tower kernel: pci 0000:11:00.2: enabling Extended Tags Feb 5 14:47:27 Tower kernel: pci 0000:11:00.3: [1022:145c] type 00 class 0x0c0330 Feb 5 14:47:27 Tower kernel: pci 0000:11:00.3: reg 0x10: [mem 0xfe400000-0xfe4fffff 64bit] Feb 5 14:47:27 Tower kernel: pci 0000:11:00.3: enabling Extended Tags Feb 5 14:47:27 Tower kernel: pci 0000:11:00.3: PME# supported from D0 D3hot D3cold Feb 5 14:47:27 Tower kernel: pci 0000:00:07.1: PCI bridge to [bus 11] Feb 5 14:47:27 Tower kernel: pci 0000:00:07.1: bridge window [mem 0xfe400000-0xfe6fffff] Feb 5 14:47:27 Tower kernel: pci 0000:12:00.0: [1022:1455] type 00 class 0x130000 Feb 5 14:47:27 Tower kernel: pci 0000:12:00.0: enabling Extended Tags Feb 5 14:47:27 Tower kernel: pci 0000:12:00.2: [1022:7901] type 00 class 0x010601 Feb 5 14:47:27 Tower kernel: pci 0000:12:00.2: reg 0x24: [mem 0xfe708000-0xfe708fff] Feb 5 14:47:27 Tower kernel: pci 0000:12:00.2: enabling Extended Tags Feb 5 14:47:27 Tower kernel: pci 0000:12:00.2: PME# supported from D3hot D3cold Feb 5 14:47:27 Tower kernel: pci 0000:12:00.3: [1022:1457] type 00 class 0x040300 Feb 5 14:47:27 Tower kernel: pci 0000:12:00.3: reg 0x10: [mem 0xfe700000-0xfe707fff] Feb 5 14:47:27 Tower kernel: pci 0000:12:00.3: enabling Extended Tags Feb 5 14:47:27 Tower kernel: pci 0000:12:00.3: PME# supported from D0 D3hot D3cold Feb 5 14:47:27 Tower kernel: pci 0000:00:08.1: PCI bridge to [bus 12] Feb 5 14:47:27 Tower kernel: pci 0000:00:08.1: bridge window [mem 0xfe700000-0xfe7fffff] Feb 5 14:47:27 Tower kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 4 5 7 10 11 14 15) *0 Feb 5 14:47:27 Tower kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 4 5 7 10 11 14 15) *0 Feb 5 14:47:27 Tower kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 4 5 7 10 11 14 15) *0 Feb 5 14:47:27 Tower kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 4 5 7 10 11 14 15) *0 Feb 5 14:47:27 Tower kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 4 5 7 10 11 14 15) *0 Feb 5 14:47:27 Tower kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 4 5 7 10 11 14 15) *0 Feb 5 14:47:27 Tower kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 4 5 7 10 11 14 15) *0 Feb 5 14:47:27 Tower kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 4 5 7 10 11 14 15) *0 Feb 5 14:47:27 Tower kernel: pci 0000:0e:00.0: vgaarb: setting as boot VGA device Feb 5 14:47:27 Tower kernel: pci 0000:0e:00.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none Feb 5 14:47:27 Tower kernel: pci 0000:0e:00.0: vgaarb: bridge control possible Feb 5 14:47:27 Tower kernel: vgaarb: loaded Feb 5 14:47:27 Tower kernel: SCSI subsystem initialized Feb 5 14:47:27 Tower kernel: libata version 3.00 loaded. Feb 5 14:47:27 Tower kernel: ACPI: bus type USB registered Feb 5 14:47:27 Tower kernel: usbcore: registered new interface driver usbfs Feb 5 14:47:27 Tower kernel: usbcore: registered new interface driver hub Feb 5 14:47:27 Tower kernel: usbcore: registered new device driver usb Feb 5 14:47:27 Tower kernel: EDAC MC: Ver: 3.0.0 Feb 5 14:47:27 Tower kernel: PCI: Using ACPI for IRQ routing Feb 5 14:47:27 Tower kernel: PCI: pci_cache_line_size set to 64 bytes Feb 5 14:47:27 Tower kernel: e820: reserve RAM buffer [mem 0x0009d400-0x0009ffff] Feb 5 14:47:27 Tower kernel: e820: reserve RAM buffer [mem 0x09d00000-0x0bffffff] Feb 5 14:47:27 Tower kernel: e820: reserve RAM buffer [mem 0xdaded000-0xdbffffff] Feb 5 14:47:27 Tower kernel: e820: reserve RAM buffer [mem 0xdc44a000-0xdfffffff] Feb 5 14:47:27 Tower kernel: e820: reserve RAM buffer [mem 0xdf000000-0xdfffffff] Feb 5 14:47:27 Tower kernel: e820: reserve RAM buffer [mem 0x81f380000-0x81fffffff] Feb 5 14:47:27 Tower kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0 Feb 5 14:47:27 Tower kernel: hpet0: 3 comparators, 32-bit 14.318180 MHz counter Feb 5 14:47:27 Tower kernel: clocksource: Switched to clocksource hpet Feb 5 14:47:27 Tower kernel: FS-Cache: Loaded Feb 5 14:47:27 Tower kernel: pnp: PnP ACPI init Feb 5 14:47:27 Tower kernel: system 00:00: [mem 0xf8000000-0xfbffffff] has been reserved Feb 5 14:47:27 Tower kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active) Feb 5 14:47:27 Tower kernel: system 00:01: [mem 0xfeb80000-0xfebfffff] could not be reserved Feb 5 14:47:27 Tower kernel: system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active) Feb 5 14:47:27 Tower kernel: pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active) Feb 5 14:47:27 Tower kernel: system 00:03: [io 0x0280-0x028f] has been reserved Feb 5 14:47:27 Tower kernel: system 00:03: [io 0x0290-0x029f] has been reserved Feb 5 14:47:27 Tower kernel: system 00:03: [io 0x02a0-0x02af] has been reserved Feb 5 14:47:27 Tower kernel: system 00:03: [io 0x02b0-0x02bf] has been reserved Feb 5 14:47:27 Tower kernel: system 00:03: Plug and Play ACPI device, IDs PNP0c02 (active) Feb 5 14:47:27 Tower kernel: system 00:04: [io 0x04d0-0x04d1] has been reserved Feb 5 14:47:27 Tower kernel: system 00:04: [io 0x040b] has been reserved Feb 5 14:47:27 Tower kernel: system 00:04: [io 0x04d6] has been reserved Feb 5 14:47:27 Tower kernel: system 00:04: [io 0x0c00-0x0c01] has been reserved Feb 5 14:47:27 Tower kernel: system 00:04: [io 0x0c14] has been reserved Feb 5 14:47:27 Tower kernel: system 00:04: [io 0x0c50-0x0c51] has been reserved Feb 5 14:47:27 Tower kernel: system 00:04: [io 0x0c52] has been reserved Feb 5 14:47:27 Tower kernel: system 00:04: [io 0x0c6c] has been reserved Feb 5 14:47:27 Tower kernel: system 00:04: [io 0x0c6f] has been reserved Feb 5 14:47:27 Tower kernel: system 00:04: [io 0x0cd0-0x0cd1] has been reserved Feb 5 14:47:27 Tower kernel: system 00:04: [io 0x0cd2-0x0cd3] has been reserved Feb 5 14:47:27 Tower kernel: system 00:04: [io 0x0cd4-0x0cd5] has been reserved Feb 5 14:47:27 Tower kernel: system 00:04: [io 0x0cd6-0x0cd7] has been reserved Feb 5 14:47:27 Tower kernel: system 00:04: [io 0x0cd8-0x0cdf] has been reserved Feb 5 14:47:27 Tower kernel: system 00:04: [io 0x0800-0x089f] has been reserved Feb 5 14:47:27 Tower kernel: system 00:04: [io 0x0b00-0x0b0f] has been reserved Feb 5 14:47:27 Tower kernel: system 00:04: [io 0x0b20-0x0b3f] has been reserved Feb 5 14:47:27 Tower kernel: system 00:04: [io 0x0900-0x090f] has been reserved Feb 5 14:47:27 Tower kernel: system 00:04: [io 0x0910-0x091f] has been reserved Feb 5 14:47:27 Tower kernel: system 00:04: [mem 0xfec00000-0xfec00fff] could not be reserved Feb 5 14:47:27 Tower kernel: system 00:04: [mem 0xfec01000-0xfec01fff] could not be reserved Feb 5 14:47:27 Tower kernel: system 00:04: [mem 0xfedc0000-0xfedc0fff] has been reserved Feb 5 14:47:27 Tower kernel: system 00:04: [mem 0xfee00000-0xfee00fff] has been reserved Feb 5 14:47:27 Tower kernel: system 00:04: [mem 0xfed80000-0xfed8ffff] could not be reserved Feb 5 14:47:27 Tower kernel: system 00:04: [mem 0xfec10000-0xfec10fff] has been reserved Feb 5 14:47:27 Tower kernel: system 00:04: [mem 0xff000000-0xffffffff] has been reserved Feb 5 14:47:27 Tower kernel: system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active) Feb 5 14:47:27 Tower kernel: pnp: PnP ACPI: found 5 devices Feb 5 14:47:27 Tower kernel: clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns Feb 5 14:47:27 Tower kernel: pci 0000:00:01.1: PCI bridge to [bus 01] Feb 5 14:47:27 Tower kernel: pci 0000:00:01.1: bridge window [mem 0xfe900000-0xfe9fffff] Feb 5 14:47:27 Tower kernel: pci 0000:04:00.0: PCI bridge to [bus 05] Feb 5 14:47:27 Tower kernel: pci 0000:04:02.0: PCI bridge to [bus 06] Feb 5 14:47:27 Tower kernel: pci 0000:04:02.0: bridge window [io 0xe000-0xefff] Feb 5 14:47:27 Tower kernel: pci 0000:04:02.0: bridge window [mem 0xfe200000-0xfe2fffff] Feb 5 14:47:27 Tower kernel: pci 0000:08:01.0: PCI bridge to [bus 09] Feb 5 14:47:27 Tower kernel: pci 0000:08:01.0: bridge window [mem 0xfe100000-0xfe1fffff] Feb 5 14:47:27 Tower kernel: pci 0000:08:03.0: PCI bridge to [bus 0a] Feb 5 14:47:27 Tower kernel: pci 0000:08:05.0: PCI bridge to [bus 0b] Feb 5 14:47:27 Tower kernel: pci 0000:08:05.0: bridge window [io 0xd000-0xdfff] Feb 5 14:47:27 Tower kernel: pci 0000:08:05.0: bridge window [mem 0xfe000000-0xfe0fffff] Feb 5 14:47:27 Tower kernel: pci 0000:08:07.0: PCI bridge to [bus 0c] Feb 5 14:47:27 Tower kernel: pci 0000:07:00.0: PCI bridge to [bus 08-0c] Feb 5 14:47:27 Tower kernel: pci 0000:07:00.0: bridge window [io 0xd000-0xdfff] Feb 5 14:47:27 Tower kernel: pci 0000:07:00.0: bridge window [mem 0xfe000000-0xfe1fffff] Feb 5 14:47:27 Tower kernel: pci 0000:04:03.0: PCI bridge to [bus 07-0c] Feb 5 14:47:27 Tower kernel: pci 0000:04:03.0: bridge window [io 0xd000-0xdfff] Feb 5 14:47:27 Tower kernel: pci 0000:04:03.0: bridge window [mem 0xfe000000-0xfe1fffff] Feb 5 14:47:27 Tower kernel: pci 0000:04:04.0: PCI bridge to [bus 0d] Feb 5 14:47:27 Tower kernel: pci 0000:03:00.2: PCI bridge to [bus 04-0d] Feb 5 14:47:27 Tower kernel: pci 0000:03:00.2: bridge window [io 0xd000-0xefff] Feb 5 14:47:27 Tower kernel: pci 0000:03:00.2: bridge window [mem 0xfe000000-0xfe2fffff] Feb 5 14:47:27 Tower kernel: pci 0000:00:01.3: PCI bridge to [bus 03-0d] Feb 5 14:47:27 Tower kernel: pci 0000:00:01.3: bridge window [io 0xd000-0xefff] Feb 5 14:47:27 Tower kernel: pci 0000:00:01.3: bridge window [mem 0xfe000000-0xfe3fffff] Feb 5 14:47:27 Tower kernel: pci 0000:00:03.1: PCI bridge to [bus 0e] Feb 5 14:47:27 Tower kernel: pci 0000:00:03.1: bridge window [io 0xf000-0xffff] Feb 5 14:47:27 Tower kernel: pci 0000:00:03.1: bridge window [mem 0xfe800000-0xfe8fffff] Feb 5 14:47:27 Tower kernel: pci 0000:00:03.1: bridge window [mem 0xe0000000-0xf01fffff 64bit pref] Feb 5 14:47:27 Tower kernel: pci 0000:00:07.1: PCI bridge to [bus 11] Feb 5 14:47:27 Tower kernel: pci 0000:00:07.1: bridge window [mem 0xfe400000-0xfe6fffff] Feb 5 14:47:27 Tower kernel: pci 0000:00:08.1: PCI bridge to [bus 12] Feb 5 14:47:27 Tower kernel: pci 0000:00:08.1: bridge window [mem 0xfe700000-0xfe7fffff] Feb 5 14:47:27 Tower kernel: pci_bus 0000:00: resource 4 [io 0x0000-0x03af window] Feb 5 14:47:27 Tower kernel: pci_bus 0000:00: resource 5 [io 0x03e0-0x0cf7 window] Feb 5 14:47:27 Tower kernel: pci_bus 0000:00: resource 6 [io 0x03b0-0x03df window] Feb 5 14:47:27 Tower kernel: pci_bus 0000:00: resource 7 [io 0x0d00-0xffff window] Feb 5 14:47:27 Tower kernel: pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff window] Feb 5 14:47:27 Tower kernel: pci_bus 0000:00: resource 9 [mem 0x000c0000-0x000dffff window] Feb 5 14:47:27 Tower kernel: pci_bus 0000:00: resource 10 [mem 0xe0000000-0xfec2ffff window] Feb 5 14:47:27 Tower kernel: pci_bus 0000:00: resource 11 [mem 0xfee00000-0xffffffff window] Feb 5 14:47:27 Tower kernel: pci_bus 0000:01: resource 1 [mem 0xfe900000-0xfe9fffff] Feb 5 14:47:27 Tower kernel: pci_bus 0000:03: resource 0 [io 0xd000-0xefff] Feb 5 14:47:27 Tower kernel: pci_bus 0000:03: resource 1 [mem 0xfe000000-0xfe3fffff] Feb 5 14:47:27 Tower kernel: pci_bus 0000:04: resource 0 [io 0xd000-0xefff] Feb 5 14:47:27 Tower kernel: pci_bus 0000:04: resource 1 [mem 0xfe000000-0xfe2fffff] Feb 5 14:47:27 Tower kernel: pci_bus 0000:06: resource 0 [io 0xe000-0xefff] Feb 5 14:47:27 Tower kernel: pci_bus 0000:06: resource 1 [mem 0xfe200000-0xfe2fffff] Feb 5 14:47:27 Tower kernel: pci_bus 0000:07: resource 0 [io 0xd000-0xdfff] Feb 5 14:47:27 Tower kernel: pci_bus 0000:07: resource 1 [mem 0xfe000000-0xfe1fffff] Feb 5 14:47:27 Tower kernel: pci_bus 0000:08: resource 0 [io 0xd000-0xdfff] Feb 5 14:47:27 Tower kernel: pci_bus 0000:08: resource 1 [mem 0xfe000000-0xfe1fffff] Feb 5 14:47:27 Tower kernel: pci_bus 0000:09: resource 1 [mem 0xfe100000-0xfe1fffff] Feb 5 14:47:27 Tower kernel: pci_bus 0000:0b: resource 0 [io 0xd000-0xdfff] Feb 5 14:47:27 Tower kernel: pci_bus 0000:0b: resource 1 [mem 0xfe000000-0xfe0fffff] Feb 5 14:47:27 Tower kernel: pci_bus 0000:0e: resource 0 [io 0xf000-0xffff] Feb 5 14:47:27 Tower kernel: pci_bus 0000:0e: resource 1 [mem 0xfe800000-0xfe8fffff] Feb 5 14:47:27 Tower kernel: pci_bus 0000:0e: resource 2 [mem 0xe0000000-0xf01fffff 64bit pref] Feb 5 14:47:27 Tower kernel: pci_bus 0000:11: resource 1 [mem 0xfe400000-0xfe6fffff] Feb 5 14:47:27 Tower kernel: pci_bus 0000:12: resource 1 [mem 0xfe700000-0xfe7fffff] Feb 5 14:47:27 Tower kernel: NET: Registered protocol family 2 Feb 5 14:47:27 Tower kernel: TCP established hash table entries: 262144 (order: 9, 2097152 bytes) Feb 5 14:47:27 Tower kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) Feb 5 14:47:27 Tower kernel: TCP: Hash tables configured (established 262144 bind 65536) Feb 5 14:47:27 Tower kernel: UDP hash table entries: 16384 (order: 7, 524288 bytes) Feb 5 14:47:27 Tower kernel: UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes) Feb 5 14:47:27 Tower kernel: NET: Registered protocol family 1 Feb 5 14:47:27 Tower kernel: pci 0000:0e:00.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff] Feb 5 14:47:27 Tower kernel: PCI: CLS 64 bytes, default 64 Feb 5 14:47:27 Tower kernel: Unpacking initramfs... Feb 5 14:47:27 Tower kernel: Freeing initrd memory: 80628K Feb 5 14:47:27 Tower kernel: AMD-Vi: IOMMU performance counters supported Feb 5 14:47:27 Tower kernel: pci 0000:00:00.2: can't derive routing for PCI INT A Feb 5 14:47:27 Tower kernel: pci 0000:00:00.2: PCI INT A: not connected Feb 5 14:47:27 Tower kernel: iommu: Adding device 0000:00:01.0 to group 0 Feb 5 14:47:27 Tower kernel: iommu: Using direct mapping for device 0000:00:01.0 Feb 5 14:47:27 Tower kernel: iommu: Adding device 0000:00:01.1 to group 1 Feb 5 14:47:27 Tower kernel: iommu: Using direct mapping for device 0000:00:01.1 Feb 5 14:47:27 Tower kernel: iommu: Adding device 0000:00:01.3 to group 2 Feb 5 14:47:27 Tower kernel: iommu: Using direct mapping for device 0000:00:01.3 Feb 5 14:47:27 Tower kernel: iommu: Adding device 0000:00:02.0 to group 3 Feb 5 14:47:27 Tower kernel: iommu: Using direct mapping for device 0000:00:02.0 Feb 5 14:47:27 Tower kernel: iommu: Adding device 0000:00:03.0 to group 4 Feb 5 14:47:27 Tower kernel: iommu: Using direct mapping for device 0000:00:03.0 Feb 5 14:47:27 Tower kernel: iommu: Adding device 0000:00:03.1 to group 5 Feb 5 14:47:27 Tower kernel: iommu: Using direct mapping for device 0000:00:03.1 Feb 5 14:47:27 Tower kernel: iommu: Adding device 0000:00:04.0 to group 6 Feb 5 14:47:27 Tower kernel: iommu: Using direct mapping for device 0000:00:04.0 Feb 5 14:47:27 Tower kernel: iommu: Adding device 0000:00:07.0 to group 7 Feb 5 14:47:27 Tower kernel: iommu: Using direct mapping for device 0000:00:07.0 Feb 5 14:47:27 Tower kernel: iommu: Adding device 0000:00:07.1 to group 7 Feb 5 14:47:27 Tower kernel: iommu: Adding device 0000:00:08.0 to group 8 Feb 5 14:47:27 Tower kernel: iommu: Using direct mapping for device 0000:00:08.0 Feb 5 14:47:27 Tower kernel: iommu: Adding device 0000:00:08.1 to group 8 Feb 5 14:47:27 Tower kernel: iommu: Adding device 0000:00:14.0 to group 9 Feb 5 14:47:27 Tower kernel: iommu: Using direct mapping for device 0000:00:14.0 Feb 5 14:47:27 Tower kernel: iommu: Adding device 0000:00:14.3 to group 9 Feb 5 14:47:27 Tower kernel: iommu: Adding device 0000:00:18.0 to group 10 Feb 5 14:47:27 Tower kernel: iommu: Using direct mapping for device 0000:00:18.0 Feb 5 14:47:27 Tower kernel: iommu: Adding device 0000:00:18.1 to group 10 Feb 5 14:47:27 Tower kernel: iommu: Adding device 0000:00:18.2 to group 10 Feb 5 14:47:27 Tower kernel: iommu: Adding device 0000:00:18.3 to group 10 Feb 5 14:47:27 Tower kernel: iommu: Adding device 0000:00:18.4 to group 10 Feb 5 14:47:27 Tower kernel: iommu: Adding device 0000:00:18.5 to group 10 Feb 5 14:47:27 Tower kernel: iommu: Adding device 0000:00:18.6 to group 10 Feb 5 14:47:27 Tower kernel: iommu: Adding device 0000:00:18.7 to group 10 Feb 5 14:47:27 Tower kernel: iommu: Adding device 0000:01:00.0 to group 11 Feb 5 14:47:27 Tower kernel: iommu: Using direct mapping for device 0000:01:00.0 Feb 5 14:47:27 Tower kernel: iommu: Adding device 0000:03:00.0 to group 12 Feb 5 14:47:27 Tower kernel: iommu: Using direct mapping for device 0000:03:00.0 Feb 5 14:47:27 Tower kernel: iommu: Adding device 0000:03:00.1 to group 12 Feb 5 14:47:27 Tower kernel: iommu: Adding device 0000:03:00.2 to group 12 Feb 5 14:47:27 Tower kernel: iommu: Adding device 0000:04:00.0 to group 12 Feb 5 14:47:27 Tower kernel: iommu: Adding device 0000:04:02.0 to group 12 Feb 5 14:47:27 Tower kernel: iommu: Adding device 0000:04:03.0 to group 12 Feb 5 14:47:27 Tower kernel: iommu: Adding device 0000:04:04.0 to group 12 Feb 5 14:47:27 Tower kernel: iommu: Adding device 0000:06:00.0 to group 12 Feb 5 14:47:27 Tower kernel: iommu: Adding device 0000:07:00.0 to group 12 Feb 5 14:47:27 Tower kernel: iommu: Adding device 0000:08:01.0 to group 12 Feb 5 14:47:27 Tower kernel: iommu: Adding device 0000:08:03.0 to group 12 Feb 5 14:47:27 Tower kernel: iommu: Adding device 0000:08:05.0 to group 12 Feb 5 14:47:27 Tower kernel: iommu: Adding device 0000:08:07.0 to group 12 Feb 5 14:47:27 Tower kernel: iommu: Adding device 0000:09:00.0 to group 12 Feb 5 14:47:27 Tower kernel: iommu: Adding device 0000:0b:00.0 to group 12 Feb 5 14:47:27 Tower kernel: iommu: Adding device 0000:0e:00.0 to group 13 Feb 5 14:47:27 Tower kernel: iommu: Using direct mapping for device 0000:0e:00.0 Feb 5 14:47:27 Tower kernel: iommu: Adding device 0000:0e:00.1 to group 13 Feb 5 14:47:27 Tower kernel: iommu: Adding device 0000:11:00.0 to group 7 Feb 5 14:47:27 Tower kernel: iommu: Adding device 0000:11:00.2 to group 7 Feb 5 14:47:27 Tower kernel: iommu: Adding device 0000:11:00.3 to group 7 Feb 5 14:47:27 Tower kernel: iommu: Adding device 0000:12:00.0 to group 8 Feb 5 14:47:27 Tower kernel: iommu: Adding device 0000:12:00.2 to group 8 Feb 5 14:47:27 Tower kernel: iommu: Adding device 0000:12:00.3 to group 8 Feb 5 14:47:27 Tower kernel: AMD-Vi: Found IOMMU at 0000:00:00.2 cap 0x40 Feb 5 14:47:27 Tower kernel: AMD-Vi: Extended features (0xf77ef22294ada): Feb 5 14:47:27 Tower kernel: PPR NX GT IA GA PC GA_vAPIC Feb 5 14:47:27 Tower kernel: AMD-Vi: Interrupt remapping enabled Feb 5 14:47:27 Tower kernel: AMD-Vi: virtual APIC enabled Feb 5 14:47:27 Tower kernel: AMD-Vi: Lazy IO/TLB flushing enabled Feb 5 14:47:27 Tower kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB) Feb 5 14:47:27 Tower kernel: software IO TLB [mem 0xd6ded000-0xdaded000] (64MB) mapped at [ffff8800d6ded000-ffff8800dadecfff] Feb 5 14:47:27 Tower kernel: amd_uncore: AMD NB counters detected Feb 5 14:47:27 Tower kernel: amd_uncore: AMD LLC counters detected Feb 5 14:47:27 Tower kernel: perf/amd_iommu: Detected AMD IOMMU #0 (2 banks, 4 counters/bank). Feb 5 14:47:27 Tower kernel: workingset: timestamp_bits=40 max_order=23 bucket_order=0 Feb 5 14:47:27 Tower kernel: squashfs: version 4.0 (2009/01/31) Phillip Lougher Feb 5 14:47:27 Tower kernel: fuse init (API version 7.26) Feb 5 14:47:27 Tower kernel: Key type asymmetric registered Feb 5 14:47:27 Tower kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) Feb 5 14:47:27 Tower kernel: io scheduler noop registered (default) Feb 5 14:47:27 Tower kernel: io scheduler deadline registered Feb 5 14:47:27 Tower kernel: io scheduler cfq registered Feb 5 14:47:27 Tower kernel: io scheduler mq-deadline registered Feb 5 14:47:27 Tower kernel: io scheduler kyber registered Feb 5 14:47:27 Tower kernel: pcieport 0000:00:01.1: AER enabled with IRQ 26 Feb 5 14:47:27 Tower kernel: pcieport 0000:00:01.3: AER enabled with IRQ 27 Feb 5 14:47:27 Tower kernel: pcieport 0000:00:03.1: AER enabled with IRQ 28 Feb 5 14:47:27 Tower kernel: pcieport 0000:00:01.1: Signaling PME with IRQ 26 Feb 5 14:47:27 Tower kernel: pcieport 0000:00:01.3: Signaling PME with IRQ 27 Feb 5 14:47:27 Tower kernel: pcieport 0000:00:03.1: Signaling PME with IRQ 28 Feb 5 14:47:27 Tower kernel: pcieport 0000:00:07.1: Signaling PME with IRQ 29 Feb 5 14:47:27 Tower kernel: pcieport 0000:00:08.1: Signaling PME with IRQ 31 Feb 5 14:47:27 Tower kernel: ipmi message handler version 39.2 Feb 5 14:47:27 Tower kernel: Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled Feb 5 14:47:27 Tower kernel: lp: driver loaded but no devices found Feb 5 14:47:27 Tower kernel: Hangcheck: starting hangcheck timer 0.9.1 (tick is 180 seconds, margin is 60 seconds). Feb 5 14:47:27 Tower kernel: AMD IOMMUv2 driver by Joerg Roedel <[email protected]> Feb 5 14:47:27 Tower kernel: loop: module loaded Feb 5 14:47:27 Tower kernel: VFIO - User Level meta-driver version: 0.3 Feb 5 14:47:27 Tower kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver Feb 5 14:47:27 Tower kernel: ehci-pci: EHCI PCI platform driver Feb 5 14:47:27 Tower kernel: ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver Feb 5 14:47:27 Tower kernel: ohci-pci: OHCI PCI platform driver Feb 5 14:47:27 Tower kernel: uhci_hcd: USB Universal Host Controller Interface driver Feb 5 14:47:27 Tower kernel: QUIRK: Enable AMD PLL fix Feb 5 14:47:27 Tower kernel: xhci_hcd 0000:03:00.0: xHCI Host Controller Feb 5 14:47:27 Tower kernel: xhci_hcd 0000:03:00.0: new USB bus registered, assigned bus number 1 Feb 5 14:47:27 Tower kernel: xhci_hcd 0000:03:00.0: hcc params 0x0200ef81 hci version 0x110 quirks 0x00000418 Feb 5 14:47:27 Tower kernel: hub 1-0:1.0: USB hub found Feb 5 14:47:27 Tower kernel: hub 1-0:1.0: 14 ports detected Feb 5 14:47:27 Tower kernel: xhci_hcd 0000:03:00.0: xHCI Host Controller Feb 5 14:47:27 Tower kernel: xhci_hcd 0000:03:00.0: new USB bus registered, assigned bus number 2 Feb 5 14:47:27 Tower kernel: xhci_hcd 0000:03:00.0: Host supports USB 3.1 Enhanced SuperSpeed Feb 5 14:47:27 Tower kernel: usb usb2: We don't know the algorithms for LPM for this host, disabling LPM. Feb 5 14:47:27 Tower kernel: hub 2-0:1.0: USB hub found Feb 5 14:47:27 Tower kernel: hub 2-0:1.0: 8 ports detected Feb 5 14:47:27 Tower kernel: xhci_hcd 0000:11:00.3: xHCI Host Controller Feb 5 14:47:27 Tower kernel: xhci_hcd 0000:11:00.3: new USB bus registered, assigned bus number 3 Feb 5 14:47:27 Tower kernel: xhci_hcd 0000:11:00.3: hcc params 0x0270f665 hci version 0x100 quirks 0x00000418 Feb 5 14:47:27 Tower kernel: hub 3-0:1.0: USB hub found Feb 5 14:47:27 Tower kernel: hub 3-0:1.0: 4 ports detected Feb 5 14:47:27 Tower kernel: xhci_hcd 0000:11:00.3: xHCI Host Controller Feb 5 14:47:27 Tower kernel: xhci_hcd 0000:11:00.3: new USB bus registered, assigned bus number 4 Feb 5 14:47:27 Tower kernel: usb usb4: We don't know the algorithms for LPM for this host, disabling LPM. Feb 5 14:47:27 Tower kernel: hub 4-0:1.0: USB hub found Feb 5 14:47:27 Tower kernel: hub 4-0:1.0: 4 ports detected Feb 5 14:47:27 Tower kernel: usbcore: registered new interface driver usb-storage Feb 5 14:47:27 Tower kernel: i8042: PNP: No PS/2 controller found. Feb 5 14:47:27 Tower kernel: mousedev: PS/2 mouse device common for all mice Feb 5 14:47:27 Tower kernel: usbcore: registered new interface driver synaptics_usb Feb 5 14:47:27 Tower kernel: input: PC Speaker as /devices/platform/pcspkr/input/input0 Feb 5 14:47:27 Tower kernel: rtc_cmos 00:02: RTC can wake from S4 Feb 5 14:47:27 Tower kernel: rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0 Feb 5 14:47:27 Tower kernel: rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs Feb 5 14:47:27 Tower kernel: IR NEC protocol handler initialized Feb 5 14:47:27 Tower kernel: IR RC5(x/sz) protocol handler initialized Feb 5 14:47:27 Tower kernel: IR RC6 protocol handler initialized Feb 5 14:47:27 Tower kernel: IR JVC protocol handler initialized Feb 5 14:47:27 Tower kernel: IR Sony protocol handler initialized Feb 5 14:47:27 Tower kernel: IR SANYO protocol handler initialized Feb 5 14:47:27 Tower kernel: IR Sharp protocol handler initialized Feb 5 14:47:27 Tower kernel: IR MCE Keyboard/mouse protocol handler initialized Feb 5 14:47:27 Tower kernel: IR XMP protocol handler initialized Feb 5 14:47:27 Tower kernel: hidraw: raw HID events driver (C) Jiri Kosina Feb 5 14:47:27 Tower kernel: usbcore: registered new interface driver usbhid Feb 5 14:47:27 Tower kernel: usbhid: USB HID core driver Feb 5 14:47:27 Tower kernel: Netfilter messages via NETLINK v0.30. Feb 5 14:47:27 Tower kernel: nfnl_acct: registering with nfnetlink. Feb 5 14:47:27 Tower kernel: nf_conntrack version 0.5.0 (65536 buckets, 262144 max) Feb 5 14:47:27 Tower kernel: nf_tables: (c) 2007-2009 Patrick McHardy <[email protected]> Feb 5 14:47:27 Tower kernel: nf_tables_compat: (c) 2012 Pablo Neira Ayuso <[email protected]> Feb 5 14:47:27 Tower kernel: xt_time: kernel timezone is -0000 Feb 5 14:47:27 Tower kernel: ipip: IPv4 and MPLS over IPv4 tunneling driver Feb 5 14:47:27 Tower kernel: gre: GRE over IPv4 demultiplexor driver Feb 5 14:47:27 Tower kernel: ip_gre: GRE over IPv4 tunneling driver Feb 5 14:47:27 Tower kernel: IPv4 over IPsec tunneling driver Feb 5 14:47:27 Tower kernel: Initializing XFRM netlink socket Feb 5 14:47:27 Tower kernel: NET: Registered protocol family 10 Feb 5 14:47:27 Tower kernel: Segment Routing with IPv6 Feb 5 14:47:27 Tower kernel: sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver Feb 5 14:47:27 Tower kernel: NET: Registered protocol family 17 Feb 5 14:47:27 Tower kernel: Bridge firewalling registered Feb 5 14:47:27 Tower kernel: 8021q: 802.1Q VLAN Support v1.8 Feb 5 14:47:27 Tower kernel: 9pnet: Installing 9P2000 support Feb 5 14:47:27 Tower kernel: Key type dns_resolver registered Feb 5 14:47:27 Tower kernel: microcode: CPU0: patch_level=0x08001129 Feb 5 14:47:27 Tower kernel: microcode: CPU1: patch_level=0x08001129 Feb 5 14:47:27 Tower kernel: microcode: CPU2: patch_level=0x08001129 Feb 5 14:47:27 Tower kernel: microcode: CPU3: patch_level=0x08001129 Feb 5 14:47:27 Tower kernel: microcode: CPU4: patch_level=0x08001129 Feb 5 14:47:27 Tower kernel: microcode: CPU5: patch_level=0x08001129 Feb 5 14:47:27 Tower kernel: microcode: CPU6: patch_level=0x08001129 Feb 5 14:47:27 Tower kernel: microcode: CPU7: patch_level=0x08001129 Feb 5 14:47:27 Tower kernel: microcode: CPU8: patch_level=0x08001129 Feb 5 14:47:27 Tower kernel: microcode: CPU9: patch_level=0x08001129 Feb 5 14:47:27 Tower kernel: microcode: CPU10: patch_level=0x08001129 Feb 5 14:47:27 Tower kernel: microcode: CPU11: patch_level=0x08001129 Feb 5 14:47:27 Tower kernel: microcode: Microcode Update Driver: v2.2. Feb 5 14:47:27 Tower kernel: sched_clock: Marking stable (7701925319, 0)->(7884104534, -182179215) Feb 5 14:47:27 Tower kernel: registered taskstats version 1 Feb 5 14:47:27 Tower kernel: Btrfs loaded, crc32c=crc32c-generic Feb 5 14:47:27 Tower kernel: rtc_cmos 00:02: setting system clock to 2018-02-05 19:47:18 UTC (1517860038) Feb 5 14:47:27 Tower kernel: usb 3-1: new high-speed USB device number 2 using xhci_hcd Feb 5 14:47:27 Tower kernel: usb 1-9: new full-speed USB device number 2 using xhci_hcd Feb 5 14:47:27 Tower kernel: usb-storage 3-1:1.0: USB Mass Storage device detected Feb 5 14:47:27 Tower kernel: scsi host0: usb-storage 3-1:1.0 Feb 5 14:47:27 Tower kernel: tsc: Refined TSC clocksource calibration: 3200.222 MHz Feb 5 14:47:27 Tower kernel: clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x2e211c15c78, max_idle_ns: 440795331494 ns Feb 5 14:47:27 Tower kernel: scsi 0:0:0:0: Direct-Access SanDisk Cruzer Fit 1.27 PQ: 0 ANSI: 6 Feb 5 14:47:27 Tower kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0 Feb 5 14:47:27 Tower kernel: sd 0:0:0:0: [sda] 31266816 512-byte logical blocks: (16.0 GB/14.9 GiB) Feb 5 14:47:27 Tower kernel: sd 0:0:0:0: [sda] Write Protect is off Feb 5 14:47:27 Tower kernel: sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00 Feb 5 14:47:27 Tower kernel: sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA Feb 5 14:47:27 Tower kernel: sda: sda1 Feb 5 14:47:27 Tower kernel: sd 0:0:0:0: [sda] Attached SCSI removable disk Feb 5 14:47:27 Tower kernel: clocksource: Switched to clocksource tsc Feb 5 14:47:27 Tower kernel: floppy0: no floppy controllers found Feb 5 14:47:27 Tower kernel: Freeing unused kernel memory: 1076K Feb 5 14:47:27 Tower kernel: Write protecting the kernel read-only data: 12288k Feb 5 14:47:27 Tower kernel: Freeing unused kernel memory: 2012K Feb 5 14:47:27 Tower kernel: Freeing unused kernel memory: 104K Feb 5 14:47:27 Tower kernel: rodata_test: all tests were successful Feb 5 14:47:27 Tower kernel: random: crng init done Feb 5 14:47:27 Tower kernel: acpi_cpufreq: overriding BIOS provided _PSD data Feb 5 14:47:27 Tower kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 Feb 5 14:47:27 Tower kernel: ACPI: Power Button [PWRB] Feb 5 14:47:27 Tower kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 Feb 5 14:47:27 Tower kernel: ACPI: Power Button [PWRF] Feb 5 14:47:27 Tower kernel: ccp 0000:11:00.2: ccp enabled Feb 5 14:47:27 Tower kernel: ccp 0000:11:00.2: enabled Feb 5 14:47:27 Tower kernel: piix4_smbus 0000:00:14.0: SMBus Host Controller at 0xb00, revision 0 Feb 5 14:47:27 Tower kernel: piix4_smbus 0000:00:14.0: Using register 0x02 for SMBus port selection Feb 5 14:47:27 Tower kernel: nvme nvme0: pci function 0000:01:00.0 Feb 5 14:47:27 Tower kernel: pps_core: LinuxPPS API ver. 1 registered Feb 5 14:47:27 Tower kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <[email protected]> Feb 5 14:47:27 Tower kernel: PTP clock support registered Feb 5 14:47:27 Tower kernel: ahci 0000:03:00.1: version 3.0 Feb 5 14:47:27 Tower kernel: ahci 0000:03:00.1: SSS flag set, parallel bus scan disabled Feb 5 14:47:27 Tower kernel: ahci 0000:03:00.1: AHCI 0001.0301 32 slots 8 ports 6 Gbps 0xff impl SATA mode Feb 5 14:47:27 Tower kernel: ahci 0000:03:00.1: flags: 64bit ncq sntf stag pm led clo only pmp pio slum part sxs deso sadm sds apst Feb 5 14:47:27 Tower kernel: scsi host1: ahci Feb 5 14:47:27 Tower kernel: scsi host2: ahci Feb 5 14:47:27 Tower kernel: scsi host3: ahci Feb 5 14:47:27 Tower kernel: scsi host4: ahci Feb 5 14:47:27 Tower kernel: scsi host5: ahci Feb 5 14:47:27 Tower kernel: scsi host6: ahci Feb 5 14:47:27 Tower kernel: scsi host7: ahci Feb 5 14:47:27 Tower kernel: scsi host8: ahci Feb 5 14:47:27 Tower kernel: ata1: SATA max UDMA/133 abar m131072@0xfe380000 port 0xfe380100 irq 54 Feb 5 14:47:27 Tower kernel: ata2: SATA max UDMA/133 abar m131072@0xfe380000 port 0xfe380180 irq 54 Feb 5 14:47:27 Tower kernel: ata3: SATA max UDMA/133 abar m131072@0xfe380000 port 0xfe380200 irq 54 Feb 5 14:47:27 Tower kernel: ata4: SATA max UDMA/133 abar m131072@0xfe380000 port 0xfe380280 irq 54 Feb 5 14:47:27 Tower kernel: ata5: SATA max UDMA/133 abar m131072@0xfe380000 port 0xfe380300 irq 54 Feb 5 14:47:27 Tower kernel: ata6: SATA max UDMA/133 abar m131072@0xfe380000 port 0xfe380380 irq 54 Feb 5 14:47:27 Tower kernel: ata7: SATA max UDMA/133 abar m131072@0xfe380000 port 0xfe380400 irq 54 Feb 5 14:47:27 Tower kernel: ata8: SATA max UDMA/133 abar m131072@0xfe380000 port 0xfe380480 irq 54 Feb 5 14:47:27 Tower kernel: ahci 0000:06:00.0: SSS flag set, parallel bus scan disabled Feb 5 14:47:27 Tower kernel: ahci 0000:06:00.0: AHCI 0001.0200 32 slots 2 ports 6 Gbps 0x3 impl SATA mode Feb 5 14:47:27 Tower kernel: ahci 0000:06:00.0: flags: 64bit ncq sntf stag led clo pmp pio slum part ccc sxs Feb 5 14:47:27 Tower kernel: scsi host9: ahci Feb 5 14:47:27 Tower kernel: scsi host10: ahci Feb 5 14:47:27 Tower kernel: ata9: SATA max UDMA/133 abar m512@0xfe200000 port 0xfe200100 irq 55 Feb 5 14:47:27 Tower kernel: ata10: SATA max UDMA/133 abar m512@0xfe200000 port 0xfe200180 irq 55 Feb 5 14:47:27 Tower kernel: ahci 0000:12:00.2: AHCI 0001.0301 32 slots 1 ports 6 Gbps 0x1 impl SATA mode Feb 5 14:47:27 Tower kernel: ahci 0000:12:00.2: flags: 64bit ncq sntf ilck pm led clo only pmp fbs pio slum part Feb 5 14:47:27 Tower kernel: scsi host11: ahci Feb 5 14:47:27 Tower kernel: ata11: SATA max UDMA/133 abar m4096@0xfe708000 port 0xfe708100 irq 57 Feb 5 14:47:27 Tower kernel: igb: Intel(R) Gigabit Ethernet Network Driver - version 5.4.0-k Feb 5 14:47:27 Tower kernel: igb: Copyright (c) 2007-2014 Intel Corporation. Feb 5 14:47:27 Tower kernel: AVX2 version of gcm_enc/dec engaged. Feb 5 14:47:27 Tower kernel: AES CTR mode by8 optimization enabled Feb 5 14:47:27 Tower kernel: kvm: Nested Virtualization enabled Feb 5 14:47:27 Tower kernel: kvm: Nested Paging enabled Feb 5 14:47:27 Tower kernel: SVM: Virtual VMLOAD VMSAVE supported Feb 5 14:47:27 Tower kernel: SVM: Virtual GIF supported Feb 5 14:47:27 Tower kernel: MCE: In-kernel MCE decoding enabled. Feb 5 14:47:27 Tower kernel: EDAC amd64: Node 0: DRAM ECC disabled. Feb 5 14:47:27 Tower kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Feb 5 14:47:27 Tower kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'. Feb 5 14:47:27 Tower kernel: (Note that use of the override may cause unknown side effects.) Feb 5 14:47:27 Tower kernel: EDAC amd64: Node 0: DRAM ECC disabled. Feb 5 14:47:27 Tower kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Feb 5 14:47:27 Tower kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'. Feb 5 14:47:27 Tower kernel: (Note that use of the override may cause unknown side effects.) Feb 5 14:47:27 Tower kernel: EDAC amd64: Node 0: DRAM ECC disabled. Feb 5 14:47:27 Tower kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Feb 5 14:47:27 Tower kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'. Feb 5 14:47:27 Tower kernel: (Note that use of the override may cause unknown side effects.) Feb 5 14:47:27 Tower kernel: EDAC amd64: Node 0: DRAM ECC disabled. Feb 5 14:47:27 Tower kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Feb 5 14:47:27 Tower kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'. Feb 5 14:47:27 Tower kernel: (Note that use of the override may cause unknown side effects.) Feb 5 14:47:27 Tower kernel: EDAC amd64: Node 0: DRAM ECC disabled. Feb 5 14:47:27 Tower kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Feb 5 14:47:27 Tower kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'. Feb 5 14:47:27 Tower kernel: (Note that use of the override may cause unknown side effects.) Feb 5 14:47:27 Tower kernel: EDAC amd64: Node 0: DRAM ECC disabled. Feb 5 14:47:27 Tower kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Feb 5 14:47:27 Tower kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'. Feb 5 14:47:27 Tower kernel: (Note that use of the override may cause unknown side effects.) Feb 5 14:47:27 Tower kernel: EDAC amd64: Node 0: DRAM ECC disabled. Feb 5 14:47:27 Tower kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Feb 5 14:47:27 Tower kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'. Feb 5 14:47:27 Tower kernel: (Note that use of the override may cause unknown side effects.) Feb 5 14:47:27 Tower kernel: EDAC amd64: Node 0: DRAM ECC disabled. Feb 5 14:47:27 Tower kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Feb 5 14:47:27 Tower kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'. Feb 5 14:47:27 Tower kernel: (Note that use of the override may cause unknown side effects.) Feb 5 14:47:27 Tower kernel: EDAC amd64: Node 0: DRAM ECC disabled. Feb 5 14:47:27 Tower kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Feb 5 14:47:27 Tower kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'. Feb 5 14:47:27 Tower kernel: (Note that use of the override may cause unknown side effects.) Feb 5 14:47:27 Tower kernel: pps pps0: new PPS source ptp0 Feb 5 14:47:27 Tower kernel: igb 0000:0b:00.0: added PHC on eth0 Feb 5 14:47:27 Tower kernel: igb 0000:0b:00.0: Intel(R) Gigabit Ethernet Network Connection Feb 5 14:47:27 Tower kernel: igb 0000:0b:00.0: eth0: (PCIe:2.5Gb/s:Width x1) 70:85:c2:6b:18:0c Feb 5 14:47:27 Tower kernel: igb 0000:0b:00.0: eth0: PBA No: FFFFFF-0FF Feb 5 14:47:27 Tower kernel: igb 0000:0b:00.0: Using MSI-X interrupts. 2 rx queue(s), 2 tx queue(s) Feb 5 14:47:27 Tower kernel: EDAC amd64: Node 0: DRAM ECC disabled. Feb 5 14:47:27 Tower kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Feb 5 14:47:27 Tower kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'. Feb 5 14:47:27 Tower kernel: (Note that use of the override may cause unknown side effects.) Feb 5 14:47:27 Tower kernel: EDAC amd64: Node 0: DRAM ECC disabled. Feb 5 14:47:27 Tower kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Feb 5 14:47:27 Tower kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'. Feb 5 14:47:27 Tower kernel: (Note that use of the override may cause unknown side effects.) Feb 5 14:47:27 Tower kernel: ata11: SATA link down (SStatus 0 SControl 300) Feb 5 14:47:27 Tower kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Feb 5 14:47:27 Tower kernel: ata1.00: ATA-9: ST4000DM000-1F2168, S301P805, CC54, max UDMA/133 Feb 5 14:47:27 Tower kernel: ata1.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA Feb 5 14:47:27 Tower kernel: ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Feb 5 14:47:27 Tower kernel: ata9.00: ATA-9: WDC WD80EMAZ-00WJTA0, 7SGTU9EC, 83.H0A83, max UDMA/133 Feb 5 14:47:27 Tower kernel: ata9.00: 15628053168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA Feb 5 14:47:27 Tower kernel: ata1.00: configured for UDMA/133 Feb 5 14:47:27 Tower kernel: scsi 1:0:0:0: Direct-Access ATA ST4000DM000-1F21 CC54 PQ: 0 ANSI: 5 Feb 5 14:47:27 Tower kernel: sd 1:0:0:0: Attached scsi generic sg1 type 0 Feb 5 14:47:27 Tower kernel: sd 1:0:0:0: [sdb] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB) Feb 5 14:47:27 Tower kernel: sd 1:0:0:0: [sdb] 4096-byte physical blocks Feb 5 14:47:27 Tower kernel: sd 1:0:0:0: [sdb] Write Protect is off Feb 5 14:47:27 Tower kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Feb 5 14:47:27 Tower kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Feb 5 14:47:27 Tower kernel: ata9.00: configured for UDMA/133 Feb 5 14:47:27 Tower kernel: sdb: sdb1 Feb 5 14:47:27 Tower kernel: sd 1:0:0:0: [sdb] Attached SCSI disk Feb 5 14:47:27 Tower kernel: ata2: SATA link down (SStatus 0 SControl 300) Feb 5 14:47:27 Tower kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Feb 5 14:47:27 Tower kernel: ata3.00: ATA-9: ST4000DM000-1F2168, S301KSNJ, CC54, max UDMA/133 Feb 5 14:47:27 Tower kernel: ata3.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA Feb 5 14:47:27 Tower kernel: ata3.00: configured for UDMA/133 Feb 5 14:47:27 Tower kernel: scsi 3:0:0:0: Direct-Access ATA ST4000DM000-1F21 CC54 PQ: 0 ANSI: 5 Feb 5 14:47:27 Tower kernel: sd 3:0:0:0: [sdc] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB) Feb 5 14:47:27 Tower kernel: sd 3:0:0:0: Attached scsi generic sg2 type 0 Feb 5 14:47:27 Tower kernel: sd 3:0:0:0: [sdc] 4096-byte physical blocks Feb 5 14:47:27 Tower kernel: sd 3:0:0:0: [sdc] Write Protect is off Feb 5 14:47:27 Tower kernel: sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00 Feb 5 14:47:27 Tower kernel: sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Feb 5 14:47:27 Tower kernel: sdc: sdc1 Feb 5 14:47:27 Tower kernel: sd 3:0:0:0: [sdc] Attached SCSI disk Feb 5 14:47:27 Tower kernel: ata4: SATA link down (SStatus 0 SControl 300) Feb 5 14:47:27 Tower kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Feb 5 14:47:27 Tower kernel: ata5.00: ATA-9: ST4000DM000-1F2168, S301KS2H, CC54, max UDMA/133 Feb 5 14:47:27 Tower kernel: ata5.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA Feb 5 14:47:27 Tower kernel: ata5.00: configured for UDMA/133 Feb 5 14:47:27 Tower kernel: scsi 5:0:0:0: Direct-Access ATA ST4000DM000-1F21 CC54 PQ: 0 ANSI: 5 Feb 5 14:47:27 Tower kernel: sd 5:0:0:0: Attached scsi generic sg3 type 0 Feb 5 14:47:27 Tower kernel: sd 5:0:0:0: [sdd] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB) Feb 5 14:47:27 Tower kernel: sd 5:0:0:0: [sdd] 4096-byte physical blocks Feb 5 14:47:27 Tower kernel: sd 5:0:0:0: [sdd] Write Protect is off Feb 5 14:47:27 Tower kernel: sd 5:0:0:0: [sdd] Mode Sense: 00 3a 00 00 Feb 5 14:47:27 Tower kernel: sd 5:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Feb 5 14:47:27 Tower kernel: sdd: sdd1 Feb 5 14:47:27 Tower kernel: sd 5:0:0:0: [sdd] Attached SCSI disk Feb 5 14:47:27 Tower kernel: ata6: SATA link down (SStatus 0 SControl 300) Feb 5 14:47:27 Tower kernel: ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Feb 5 14:47:27 Tower kernel: ata7.00: ATA-9: ST4000DM000-1F2168, S301KS2V, CC54, max UDMA/133 Feb 5 14:47:27 Tower kernel: ata7.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA Feb 5 14:47:27 Tower kernel: ata7.00: configured for UDMA/133 Feb 5 14:47:27 Tower kernel: scsi 7:0:0:0: Direct-Access ATA ST4000DM000-1F21 CC54 PQ: 0 ANSI: 5 Feb 5 14:47:27 Tower kernel: sd 7:0:0:0: Attached scsi generic sg4 type 0 Feb 5 14:47:27 Tower kernel: sd 7:0:0:0: [sde] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB) Feb 5 14:47:27 Tower kernel: sd 7:0:0:0: [sde] 4096-byte physical blocks Feb 5 14:47:27 Tower kernel: sd 7:0:0:0: [sde] Write Protect is off Feb 5 14:47:27 Tower kernel: sd 7:0:0:0: [sde] Mode Sense: 00 3a 00 00 Feb 5 14:47:27 Tower kernel: sd 7:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Feb 5 14:47:27 Tower kernel: sde: sde1 Feb 5 14:47:27 Tower kernel: sd 7:0:0:0: [sde] Attached SCSI disk Feb 5 14:47:27 Tower kernel: ata8: SATA link down (SStatus 0 SControl 300) Feb 5 14:47:27 Tower kernel: scsi 9:0:0:0: Direct-Access ATA WDC WD80EMAZ-00W 0A83 PQ: 0 ANSI: 5 Feb 5 14:47:27 Tower kernel: sd 9:0:0:0: Attached scsi generic sg5 type 0 Feb 5 14:47:27 Tower kernel: sd 9:0:0:0: [sdf] 15628053168 512-byte logical blocks: (8.00 TB/7.28 TiB) Feb 5 14:47:27 Tower kernel: sd 9:0:0:0: [sdf] 4096-byte physical blocks Feb 5 14:47:27 Tower kernel: sd 9:0:0:0: [sdf] Write Protect is off Feb 5 14:47:27 Tower kernel: sd 9:0:0:0: [sdf] Mode Sense: 00 3a 00 00 Feb 5 14:47:27 Tower kernel: sd 9:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Feb 5 14:47:27 Tower kernel: GPT:Primary header thinks Alt. header is not at the end of the disk. Feb 5 14:47:27 Tower kernel: GPT:15628052479 != 15628053167 Feb 5 14:47:27 Tower kernel: GPT:Alternate GPT header not at the end of the disk. Feb 5 14:47:27 Tower kernel: GPT:15628052479 != 15628053167 Feb 5 14:47:27 Tower kernel: GPT: Use GNU Parted to correct GPT errors. Feb 5 14:47:27 Tower kernel: sdf: sdf1 Feb 5 14:47:27 Tower kernel: sd 9:0:0:0: [sdf] Attached SCSI disk Feb 5 14:47:27 Tower kernel: ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Feb 5 14:47:27 Tower kernel: ata10.00: ATA-9: WDC WD80EMAZ-00WJTA0, 7SH0XGYC, 83.H0A83, max UDMA/133 Feb 5 14:47:27 Tower kernel: ata10.00: 15628053168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA Feb 5 14:47:27 Tower kernel: ata10.00: configured for UDMA/133 Feb 5 14:47:27 Tower kernel: scsi 10:0:0:0: Direct-Access ATA WDC WD80EMAZ-00W 0A83 PQ: 0 ANSI: 5 Feb 5 14:47:27 Tower kernel: sd 10:0:0:0: [sdg] 15628053168 512-byte logical blocks: (8.00 TB/7.28 TiB) Feb 5 14:47:27 Tower kernel: sd 10:0:0:0: Attached scsi generic sg6 type 0 Feb 5 14:47:27 Tower kernel: sd 10:0:0:0: [sdg] 4096-byte physical blocks Feb 5 14:47:27 Tower kernel: sd 10:0:0:0: [sdg] Write Protect is off Feb 5 14:47:27 Tower kernel: sd 10:0:0:0: [sdg] Mode Sense: 00 3a 00 00 Feb 5 14:47:27 Tower kernel: sd 10:0:0:0: [sdg] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Feb 5 14:47:27 Tower kernel: GPT:Primary header thinks Alt. header is not at the end of the disk. Feb 5 14:47:27 Tower kernel: GPT:15628052479 != 15628053167 Feb 5 14:47:27 Tower kernel: GPT:Alternate GPT header not at the end of the disk. Feb 5 14:47:27 Tower kernel: GPT:15628052479 != 15628053167 Feb 5 14:47:27 Tower kernel: GPT: Use GNU Parted to correct GPT errors. Feb 5 14:47:27 Tower kernel: sdg: sdg1 Feb 5 14:47:27 Tower kernel: sd 10:0:0:0: [sdg] Attached SCSI disk Feb 5 14:47:27 Tower kernel: EDAC amd64: Node 0: DRAM ECC disabled. Feb 5 14:47:27 Tower kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Feb 5 14:47:27 Tower kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'. Feb 5 14:47:27 Tower kernel: (Note that use of the override may cause unknown side effects.) Feb 5 14:47:27 Tower rc.inet1: ip -4 addr add 127.0.0.1/8 dev lo Feb 5 14:47:27 Tower rc.inet1: ip -6 addr add ::1/128 dev lo Feb 5 14:47:27 Tower rc.inet1: ip link set lo up Feb 5 14:47:27 Tower rc.inet1: polling up to 60 sec for DHCP server on interface eth0 Feb 5 14:47:27 Tower rc.inet1: timeout 60 dhcpcd -w -q -t 10 -h Tower -4 eth0 Feb 5 14:47:27 Tower dhcpcd[1731]: eth0: waiting for carrier Feb 5 14:47:27 Tower kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready Feb 5 14:47:27 Tower kernel: 8021q: adding VLAN 0 to HW filter on device eth0 Feb 5 14:47:28 Tower rsyslogd: [origin software="rsyslogd" swVersion="8.29.0" x-pid="1623" x-info="http://www.rsyslog.com"] start Feb 5 14:47:30 Tower kernel: igb 0000:0b:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX Feb 5 14:47:30 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Feb 5 14:47:30 Tower dhcpcd[1731]: eth0: carrier acquired Feb 5 14:47:31 Tower dhcpcd[1731]: eth0: soliciting a DHCP lease Feb 5 14:47:32 Tower dhcpcd[1731]: eth0: offered 192.168.1.218 from 192.168.1.1 Feb 5 14:47:32 Tower dhcpcd[1731]: eth0: probing address 192.168.1.218/24 Feb 5 14:47:37 Tower dhcpcd[1731]: eth0: leased 192.168.1.218 for 86400 seconds Feb 5 14:47:37 Tower dhcpcd[1731]: eth0: adding route to 192.168.1.0/24 Feb 5 14:47:37 Tower dhcpcd[1731]: eth0: adding default route via 192.168.1.1 Feb 5 14:47:37 Tower dhcpcd[1731]: forked to background, child pid 1791 Feb 5 14:47:37 Tower rc.inet1: ip link set eth0 up Feb 5 14:47:37 Tower rpc.statd[1817]: Version 2.1.1 starting Feb 5 14:47:37 Tower sm-notify[1818]: Version 2.1.1 starting Feb 5 14:47:37 Tower rpc.statd[1817]: Failed to read /var/lib/nfs/state: Success Feb 5 14:47:37 Tower rpc.statd[1817]: Initializing NSM state Feb 5 14:47:37 Tower sshd[1835]: Server listening on 0.0.0.0 port 22. Feb 5 14:47:37 Tower sshd[1835]: Server listening on :: port 22. Feb 5 14:47:37 Tower useradd[1844]: new user: name=ntp, UID=44, GID=44, home=/, shell=/bin/false Feb 5 14:47:37 Tower ntpd[1850]: ntpd [email protected] Thu Oct 5 18:26:25 UTC 2017 (1): Starting Feb 5 14:47:37 Tower ntpd[1850]: Command line: /usr/sbin/ntpd -g -u ntp:ntp Feb 5 14:47:37 Tower ntpd[1852]: proto: precision = 0.060 usec (-24) Feb 5 14:47:37 Tower ntpd[1852]: Listen normally on 0 lo 127.0.0.1:123 Feb 5 14:47:37 Tower ntpd[1852]: Listen normally on 1 eth0 192.168.1.218:123 Feb 5 14:47:37 Tower ntpd[1852]: Listen normally on 2 lo [::1]:123 Feb 5 14:47:37 Tower ntpd[1852]: Listening on routing socket on fd #19 for interface updates Feb 5 14:47:37 Tower crond[1868]: /usr/sbin/crond 4.5 dillon's cron daemon, started with loglevel notice Feb 5 14:47:37 Tower acpid: starting up with netlink and the input layer Feb 5 14:47:37 Tower acpid: 1 rule loaded Feb 5 14:47:37 Tower acpid: waiting for events: event logging is off Feb 5 14:47:37 Tower root: Installing user plugins Feb 5 14:47:37 Tower root: plugin: installing: /boot/config/plugins/Embyserver.plg Feb 5 14:47:37 Tower root: plugin: creating: /tmp/Embyserver-script - from INLINE content Feb 5 14:47:37 Tower root: plugin: running: /tmp/Embyserver-script Feb 5 14:47:37 Tower root: Installing Embyserver plugin Feb 5 14:47:37 Tower root: Checking for current bundle files Feb 5 14:47:37 Tower root: Control file: Found correct version Feb 5 14:47:41 Tower root: Dependency file: Found correct version Feb 5 14:47:43 Tower root: Mono file: Found correct version Feb 5 14:47:43 Tower root: Check OK! Feb 5 14:47:44 Tower root: Running install script for Emby Server Feb 5 14:47:44 Tower root: Installing control file Feb 5 14:47:44 Tower root: Control file install OK! Feb 5 14:47:44 Tower root: Cleaning up temp files and folders Feb 5 14:47:44 Tower root: Install complete! Feb 5 14:47:44 Tower root: plugin: installed Feb 5 14:47:44 Tower root: plugin: installing: /boot/config/plugins/Filebot.plg Feb 5 14:47:44 Tower root: plugin: creating: /tmp/Filebot-script - from INLINE content Feb 5 14:47:44 Tower root: plugin: running: /tmp/Filebot-script Feb 5 14:47:44 Tower root: Installing Filebot plugin Feb 5 14:47:44 Tower root: Checking for current bundle files Feb 5 14:47:44 Tower root: Control file: Found correct version Feb 5 14:47:46 Tower root: Dependency file: Found correct version Feb 5 14:47:46 Tower root: Check OK! Feb 5 14:47:46 Tower root: Running install script for FileBot Feb 5 14:47:46 Tower root: Installing control file Feb 5 14:47:46 Tower root: Control file install OK! Feb 5 14:47:46 Tower root: Cleaning up temp files and folders Feb 5 14:47:46 Tower root: Install complete! Feb 5 14:47:46 Tower root: plugin: installed Feb 5 14:47:46 Tower root: plugin: installing: /boot/config/plugins/Resilio.plg Feb 5 14:47:46 Tower root: plugin: creating: /tmp/Resilio-script - from INLINE content Feb 5 14:47:46 Tower root: plugin: running: /tmp/Resilio-script Feb 5 14:47:46 Tower root: Installing Resilio plugin Feb 5 14:47:46 Tower root: Checking for current bundle files Feb 5 14:47:46 Tower root: Control file: Found correct version Feb 5 14:47:46 Tower root: Dependency file: Not found Feb 5 14:47:46 Tower root: Check OK! Feb 5 14:47:46 Tower root: Running install script for Resilio Feb 5 14:47:46 Tower root: Installing control file Feb 5 14:47:47 Tower root: Control file install OK! Feb 5 14:47:47 Tower root: Cleaning up temp files and folders Feb 5 14:47:47 Tower root: Install complete! Feb 5 14:47:47 Tower root: plugin: installed Feb 5 14:47:47 Tower root: plugin: installing: /boot/config/plugins/ca.backup.plg Feb 5 14:47:47 Tower root: plugin: running: anonymous Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: plugin: running: anonymous Feb 5 14:47:47 Tower root: plugin: skipping: /boot/config/plugins/ca.backup/ca.backup-2017.10.28-x86_64-1.txz already exists Feb 5 14:47:47 Tower root: plugin: running: /boot/config/plugins/ca.backup/ca.backup-2017.10.28-x86_64-1.txz Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: +============================================================================== Feb 5 14:47:47 Tower root: | Installing new package /boot/config/plugins/ca.backup/ca.backup-2017.10.28-x86_64-1.txz Feb 5 14:47:47 Tower root: +============================================================================== Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: Verifying package ca.backup-2017.10.28-x86_64-1.txz. Feb 5 14:47:47 Tower root: Installing package ca.backup-2017.10.28-x86_64-1.txz: Feb 5 14:47:47 Tower root: PACKAGE DESCRIPTION: Feb 5 14:47:47 Tower root: Package ca.backup-2017.10.28-x86_64-1.txz installed. Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: plugin: running: anonymous Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: ---------------------------------------------------- Feb 5 14:47:47 Tower root: ca.backup has been installed. Feb 5 14:47:47 Tower root: Copyright 2015-2016, Andrew Zawadzki Feb 5 14:47:47 Tower root: Version: 2017.10.28 Feb 5 14:47:47 Tower root: ---------------------------------------------------- Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: plugin: installed Feb 5 14:47:47 Tower root: plugin: installing: /boot/config/plugins/ca.cleanup.appdata.plg Feb 5 14:47:47 Tower root: plugin: running: anonymous Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: plugin: running: anonymous Feb 5 14:47:47 Tower root: plugin: skipping: /boot/config/plugins/ca.cleanup.appdata/ca.cleanup.appdata-2017.11.23-x86_64-1.txz already exists Feb 5 14:47:47 Tower root: plugin: running: /boot/config/plugins/ca.cleanup.appdata/ca.cleanup.appdata-2017.11.23-x86_64-1.txz Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: +============================================================================== Feb 5 14:47:47 Tower root: | Installing new package /boot/config/plugins/ca.cleanup.appdata/ca.cleanup.appdata-2017.11.23-x86_64-1.txz Feb 5 14:47:47 Tower root: +============================================================================== Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: Verifying package ca.cleanup.appdata-2017.11.23-x86_64-1.txz. Feb 5 14:47:47 Tower root: Installing package ca.cleanup.appdata-2017.11.23-x86_64-1.txz: Feb 5 14:47:47 Tower root: PACKAGE DESCRIPTION: Feb 5 14:47:47 Tower root: Package ca.cleanup.appdata-2017.11.23-x86_64-1.txz installed. Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: plugin: running: anonymous Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: ---------------------------------------------------- Feb 5 14:47:47 Tower root: ca.cleanup.appdata has been installed. Feb 5 14:47:47 Tower root: Copyright 2015-2016, Andrew Zawadzki Feb 5 14:47:47 Tower root: Version: 2017.11.23 Feb 5 14:47:47 Tower root: ---------------------------------------------------- Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: plugin: installed Feb 5 14:47:47 Tower root: plugin: installing: /boot/config/plugins/community.applications.plg Feb 5 14:47:47 Tower root: plugin: running: anonymous Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: Cleaning Up Old Versions Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: plugin: running: anonymous Feb 5 14:47:47 Tower root: plugin: skipping: /boot/config/plugins/community.applications/community.applications-2018.01.20b.txz already exists Feb 5 14:47:47 Tower root: plugin: running: /boot/config/plugins/community.applications/community.applications-2018.01.20b.txz Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: +============================================================================== Feb 5 14:47:47 Tower root: | Installing new package /boot/config/plugins/community.applications/community.applications-2018.01.20b.txz Feb 5 14:47:47 Tower root: +============================================================================== Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: Verifying package community.applications-2018.01.20b.txz. Feb 5 14:47:47 Tower root: Installing package community.applications-2018.01.20b.txz: Feb 5 14:47:47 Tower root: PACKAGE DESCRIPTION: Feb 5 14:47:47 Tower root: Package community.applications-2018.01.20b.txz installed. Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: plugin: skipping: ca-tooltipster.txz - unRAID version too high, requires at most version 6.3.2 Feb 5 14:47:47 Tower root: plugin: running: anonymous Feb 5 14:47:47 Tower root: Creating Directories Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: ---------------------------------------------------- Feb 5 14:47:47 Tower root: community.applications has been installed. Feb 5 14:47:47 Tower root: Copyright 2015-2018, Andrew Zawadzki Feb 5 14:47:47 Tower root: Version: 2018.01.20b Feb 5 14:47:47 Tower root: ---------------------------------------------------- Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: plugin: installed Feb 5 14:47:47 Tower root: plugin: installing: /boot/config/plugins/dynamix.cache.dirs.plg Feb 5 14:47:47 Tower root: plugin: running: anonymous Feb 5 14:47:47 Tower root: plugin: skipping: /boot/config/plugins/dynamix.cache.dirs/dynamix.cache.dirs.txz already exists Feb 5 14:47:47 Tower root: plugin: running: /boot/config/plugins/dynamix.cache.dirs/dynamix.cache.dirs.txz Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: +============================================================================== Feb 5 14:47:47 Tower root: | Installing new package /boot/config/plugins/dynamix.cache.dirs/dynamix.cache.dirs.txz Feb 5 14:47:47 Tower root: +============================================================================== Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: Verifying package dynamix.cache.dirs.txz. Feb 5 14:47:47 Tower root: Installing package dynamix.cache.dirs.txz: Feb 5 14:47:47 Tower root: PACKAGE DESCRIPTION: Feb 5 14:47:47 Tower root: Package dynamix.cache.dirs.txz installed. Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: plugin: creating: /tmp/start_service - from INLINE content Feb 5 14:47:47 Tower root: plugin: setting: /tmp/start_service - mode to 0770 Feb 5 14:47:47 Tower root: plugin: running: anonymous Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: ----------------------------------------------------------- Feb 5 14:47:47 Tower root: Plugin dynamix.cache.dirs is installed. Feb 5 14:47:47 Tower root: This plugin requires Dynamix webGui to operate Feb 5 14:47:47 Tower root: Copyright 2016, Bergware International Feb 5 14:47:47 Tower root: Version: 2016.08.26 Feb 5 14:47:47 Tower root: ----------------------------------------------------------- Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: plugin: installed Feb 5 14:47:47 Tower root: plugin: installing: /boot/config/plugins/dynamix.schedules.plg Feb 5 14:47:47 Tower root: plugin: running: anonymous Feb 5 14:47:47 Tower root: plugin: skipping: /boot/config/plugins/dynamix.schedules/dynamix.schedules.txz already exists Feb 5 14:47:47 Tower root: plugin: running: /boot/config/plugins/dynamix.schedules/dynamix.schedules.txz Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: +============================================================================== Feb 5 14:47:47 Tower root: | Installing new package /boot/config/plugins/dynamix.schedules/dynamix.schedules.txz Feb 5 14:47:47 Tower root: +============================================================================== Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: Verifying package dynamix.schedules.txz. Feb 5 14:47:47 Tower root: Installing package dynamix.schedules.txz: Feb 5 14:47:47 Tower root: PACKAGE DESCRIPTION: Feb 5 14:47:47 Tower root: Package dynamix.schedules.txz installed. Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: plugin: running: anonymous Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: ----------------------------------------------------------- Feb 5 14:47:47 Tower root: Plugin dynamix.schedules is installed. Feb 5 14:47:47 Tower root: This plugin requires Dynamix webGui to operate Feb 5 14:47:47 Tower root: Copyright 2016, Bergware International Feb 5 14:47:47 Tower root: Version: 2016.08.26 Feb 5 14:47:47 Tower root: ----------------------------------------------------------- Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: plugin: installed Feb 5 14:47:47 Tower root: plugin: installing: /boot/config/plugins/dynamix.system.autofan.plg Feb 5 14:47:47 Tower root: plugin: running: anonymous Feb 5 14:47:47 Tower root: plugin: skipping: /boot/config/plugins/dynamix.system.autofan/dynamix.system.autofan.txz already exists Feb 5 14:47:47 Tower root: plugin: running: /boot/config/plugins/dynamix.system.autofan/dynamix.system.autofan.txz Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: +============================================================================== Feb 5 14:47:47 Tower root: | Installing new package /boot/config/plugins/dynamix.system.autofan/dynamix.system.autofan.txz Feb 5 14:47:47 Tower root: +============================================================================== Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: Verifying package dynamix.system.autofan.txz. Feb 5 14:47:47 Tower root: Installing package dynamix.system.autofan.txz: Feb 5 14:47:47 Tower root: PACKAGE DESCRIPTION: Feb 5 14:47:47 Tower root: Package dynamix.system.autofan.txz installed. Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: plugin: creating: /tmp/start_service - from INLINE content Feb 5 14:47:47 Tower root: plugin: setting: /tmp/start_service - mode to 0770 Feb 5 14:47:47 Tower root: plugin: running: anonymous Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: ----------------------------------------------------------- Feb 5 14:47:47 Tower root: Plugin dynamix.system.autofan is installed. Feb 5 14:47:47 Tower root: This plugin requires Dynamix webGui to operate Feb 5 14:47:47 Tower root: Copyright 2016, Bergware International Feb 5 14:47:47 Tower root: Version: 2017.10.15 Feb 5 14:47:47 Tower root: ----------------------------------------------------------- Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: plugin: installed Feb 5 14:47:47 Tower root: plugin: installing: /boot/config/plugins/dynamix.system.buttons.plg Feb 5 14:47:47 Tower root: plugin: running: anonymous Feb 5 14:47:47 Tower root: plugin: skipping: /boot/config/plugins/dynamix.system.buttons/dynamix.system.buttons.txz already exists Feb 5 14:47:47 Tower root: plugin: running: /boot/config/plugins/dynamix.system.buttons/dynamix.system.buttons.txz Feb 5 14:47:47 Tower root: Feb 5 14:47:47 Tower root: +============================================================================== Feb 5 14:47:47 Tower root: | Installing new package /boot/config/plugins/dynamix.system.buttons/dynamix.system.buttons.txz Feb 5 14:47:47 Tower root: +============================================================================== Feb 5 14:47:47 Tower root: Feb 5 14:47:48 Tower root: Verifying package dynamix.system.buttons.txz. Feb 5 14:47:48 Tower root: Installing package dynamix.system.buttons.txz: Feb 5 14:47:48 Tower root: PACKAGE DESCRIPTION: Feb 5 14:47:48 Tower root: Package dynamix.system.buttons.txz installed. Feb 5 14:47:48 Tower root: Feb 5 14:47:48 Tower root: Feb 5 14:47:48 Tower root: plugin: running: anonymous Feb 5 14:47:48 Tower root: Feb 5 14:47:48 Tower root: ----------------------------------------------------------- Feb 5 14:47:48 Tower root: Plugin dynamix.system.buttons is installed. Feb 5 14:47:48 Tower root: This plugin requires Dynamix webGui to operate Feb 5 14:47:48 Tower root: Copyright 2016, Bergware International Feb 5 14:47:48 Tower root: Version: 2017.12.30 Feb 5 14:47:48 Tower root: ----------------------------------------------------------- Feb 5 14:47:48 Tower root: Feb 5 14:47:48 Tower root: plugin: installed Feb 5 14:47:48 Tower root: plugin: installing: /boot/config/plugins/dynamix.system.stats.plg Feb 5 14:47:48 Tower root: plugin: running: anonymous Feb 5 14:47:48 Tower root: plugin: skipping: /boot/config/plugins/dynamix.system.stats/dynamix.system.stats.txz already exists Feb 5 14:47:48 Tower root: plugin: running: /boot/config/plugins/dynamix.system.stats/dynamix.system.stats.txz Feb 5 14:47:48 Tower root: Feb 5 14:47:48 Tower root: +============================================================================== Feb 5 14:47:48 Tower root: | Installing new package /boot/config/plugins/dynamix.system.stats/dynamix.system.stats.txz Feb 5 14:47:48 Tower root: +============================================================================== Feb 5 14:47:48 Tower root: Feb 5 14:47:48 Tower root: Verifying package dynamix.system.stats.txz. Feb 5 14:47:48 Tower root: Installing package dynamix.system.stats.txz: Feb 5 14:47:48 Tower root: PACKAGE DESCRIPTION: Feb 5 14:47:48 Tower root: Package dynamix.system.stats.txz installed. Feb 5 14:47:48 Tower root: Feb 5 14:47:48 Tower root: Feb 5 14:47:48 Tower root: plugin: running: anonymous Feb 5 14:47:48 Tower root: Feb 5 14:47:48 Tower root: ----------------------------------------------------------- Feb 5 14:47:48 Tower root: Plugin dynamix.system.stats is installed. Feb 5 14:47:48 Tower root: This plugin requires Dynamix webGui to operate Feb 5 14:47:48 Tower root: Copyright 2012-2018, Bergware International Feb 5 14:47:48 Tower root: Version: 2018.01.20a Feb 5 14:47:48 Tower root: ----------------------------------------------------------- Feb 5 14:47:48 Tower root: Feb 5 14:47:48 Tower root: plugin: installed Feb 5 14:47:48 Tower root: plugin: installing: /boot/config/plugins/dynamix.system.temp.plg Feb 5 14:47:48 Tower root: plugin: running: anonymous Feb 5 14:47:48 Tower root: plugin: skipping: /boot/config/plugins/dynamix.system.temp/dynamix.system.temp.txz already exists Feb 5 14:47:48 Tower root: plugin: running: /boot/config/plugins/dynamix.system.temp/dynamix.system.temp.txz Feb 5 14:47:48 Tower root: Feb 5 14:47:48 Tower root: +============================================================================== Feb 5 14:47:48 Tower root: | Installing new package /boot/config/plugins/dynamix.system.temp/dynamix.system.temp.txz Feb 5 14:47:48 Tower root: +============================================================================== Feb 5 14:47:48 Tower root: Feb 5 14:47:48 Tower root: Verifying package dynamix.system.temp.txz. Feb 5 14:47:48 Tower root: Installing package dynamix.system.temp.txz: Feb 5 14:47:48 Tower root: PACKAGE DESCRIPTION: Feb 5 14:47:48 Tower root: Package dynamix.system.temp.txz installed. Feb 5 14:47:48 Tower root: Feb 5 14:47:48 Tower root: Feb 5 14:47:48 Tower root: plugin: skipping: /boot/config/plugins/dynamix.system.temp/sensors-detect already exists Feb 5 14:47:48 Tower root: plugin: creating: /usr/sbin/sensors-detect - copying LOCAL file /boot/config/plugins/dynamix.system.temp/sensors-detect Feb 5 14:47:48 Tower root: plugin: setting: /usr/sbin/sensors-detect - mode to 0755 Feb 5 14:47:48 Tower root: plugin: running: anonymous Feb 5 14:47:48 Tower root: Feb 5 14:47:48 Tower root: ----------------------------------------------------------- Feb 5 14:47:48 Tower root: Plugin dynamix.system.temp is installed. Feb 5 14:47:48 Tower root: This plugin requires Dynamix webGui to operate Feb 5 14:47:48 Tower root: Copyright 2017, Bergware International Feb 5 14:47:48 Tower root: Version: 2017.12.06 Feb 5 14:47:48 Tower root: ----------------------------------------------------------- Feb 5 14:47:48 Tower root: Feb 5 14:47:48 Tower root: plugin: installed Feb 5 14:47:48 Tower root: plugin: installing: /boot/config/plugins/ipmi.plg Feb 5 14:47:48 Tower root: plugin: skipping: /boot/config/plugins/ipmi/freeipmi-1.5.7-x86_64-2.txz already exists Feb 5 14:47:48 Tower root: plugin: running: /boot/config/plugins/ipmi/freeipmi-1.5.7-x86_64-2.txz Feb 5 14:47:48 Tower root: Feb 5 14:47:48 Tower root: +============================================================================== Feb 5 14:47:48 Tower root: | Installing new package /boot/config/plugins/ipmi/freeipmi-1.5.7-x86_64-2.txz Feb 5 14:47:48 Tower root: +============================================================================== Feb 5 14:47:48 Tower root: Feb 5 14:47:48 Tower root: Verifying package freeipmi-1.5.7-x86_64-2.txz. Feb 5 14:47:48 Tower root: Installing package freeipmi-1.5.7-x86_64-2.txz: Feb 5 14:47:48 Tower root: PACKAGE DESCRIPTION: Feb 5 14:47:48 Tower root: # FreeIPMI (GNU implementation of the IPMI protocol) Feb 5 14:47:48 Tower root: # Feb 5 14:47:48 Tower root: # FreeIPMI provides in-band and out-of-band IPMI software based on Feb 5 14:47:48 Tower root: # the IPMI v1.5/2.0 specification. The IPMI specification defines a Feb 5 14:47:48 Tower root: # set of interfaces for platform management and is implemented by a Feb 5 14:47:48 Tower root: # number vendors for system management. The features of IPMI that Feb 5 14:47:48 Tower root: # most users will be interested in are sensor monitoring, system event Feb 5 14:47:48 Tower root: # monitoring, power control, and serial-over-LAN (SOL). The FreeIPMI Feb 5 14:47:48 Tower root: # tools and libraries provide users with the ability to access and Feb 5 14:47:48 Tower root: # utilize these and many other features. A number of useful features Feb 5 14:47:48 Tower root: # for large HPC or cluster environments have also been implemented Feb 5 14:47:48 Tower root: # into FreeIPMI. Feb 5 14:47:48 Tower root: # Feb 5 14:47:48 Tower root: # Packaged by Derek Macias Feb 5 14:47:48 Tower root: Executing install script for freeipmi-1.5.7-x86_64-2.txz. Feb 5 14:47:48 Tower root: Package freeipmi-1.5.7-x86_64-2.txz installed. Feb 5 14:47:48 Tower root: Feb 5 14:47:48 Tower root: Feb 5 14:47:49 Tower root: plugin: skipping: freeipmi-1.4.11-x86_64-3.txz - unRAID version too high, requires at most version 6.1.99 Feb 5 14:47:49 Tower root: plugin: skipping: /boot/config/plugins/ipmi/ipmi.cfg already exists Feb 5 14:47:49 Tower root: plugin: skipping: /boot/config/plugins/ipmi/fan.cfg already exists Feb 5 14:47:49 Tower root: plugin: skipping: /boot/config/plugins/ipmi/ipmi-2017.12.14-x86_64-1.txz already exists Feb 5 14:47:49 Tower root: plugin: skipping: /boot/config/plugins/ipmi/ipmi-2017.12.14-x86_64-1.md5 already exists Feb 5 14:47:49 Tower root: plugin: creating: /tmp/start_ipmi - from INLINE content Feb 5 14:47:49 Tower root: plugin: setting: /tmp/start_ipmi - mode to 0770 Feb 5 14:47:49 Tower root: plugin: running: anonymous Feb 5 14:47:49 Tower root: Feb 5 14:47:49 Tower root: +============================================================================== Feb 5 14:47:49 Tower root: | Installing new package /boot/config/plugins/ipmi/ipmi-2017.12.14-x86_64-1.txz Feb 5 14:47:49 Tower root: +============================================================================== Feb 5 14:47:49 Tower root: Feb 5 14:47:49 Tower root: Verifying package ipmi-2017.12.14-x86_64-1.txz. Feb 5 14:47:49 Tower root: Installing package ipmi-2017.12.14-x86_64-1.txz: Feb 5 14:47:49 Tower root: PACKAGE DESCRIPTION: Feb 5 14:47:49 Tower root: # IPMI unRAID Plugin Feb 5 14:47:49 Tower root: # Feb 5 14:47:49 Tower root: # The ipmi plugin allows you to view your system sensors and Feb 5 14:47:49 Tower root: # events using your ipmi hardware. Allows for local or remote Feb 5 14:47:49 Tower root: # access and event notification. Feb 5 14:47:49 Tower root: # Feb 5 14:47:49 Tower root: # https://github.com/dmacias72/unRAID-plugins Feb 5 14:47:49 Tower root: # Feb 5 14:47:49 Tower root: # Feb 5 14:47:49 Tower root: Executing install script for ipmi-2017.12.14-x86_64-1.txz. Feb 5 14:47:49 Tower root: Package ipmi-2017.12.14-x86_64-1.txz installed. Feb 5 14:47:49 Tower root: Feb 5 14:47:49 Tower root: Feb 5 14:47:49 Tower root: loading ipmi drivers... Feb 5 14:47:49 Tower kernel: ipmi device interface Feb 5 14:47:49 Tower kernel: IPMI System Interface driver. Feb 5 14:47:49 Tower kernel: ipmi_si: Unable to find any System Interface(s) Feb 5 14:47:49 Tower root: starting ipmi services... Feb 5 14:47:50 Tower root: Feb 5 14:47:50 Tower root: ----------------------------------------------------------- Feb 5 14:47:50 Tower root: ipmi has been installed. Feb 5 14:47:50 Tower root: Copyright 2016-2017, dmacias72 Feb 5 14:47:50 Tower root: Version: 2017.12.14 Feb 5 14:47:50 Tower root: ----------------------------------------------------------- Feb 5 14:47:50 Tower root: Feb 5 14:47:50 Tower root: plugin: installed Feb 5 14:47:50 Tower root: plugin: installing: /boot/config/plugins/shellinabox.plg Feb 5 14:47:50 Tower root: plugin: skipping: /boot/config/plugins/shellinabox/shellinabox-2.19-x86_64-1sl.txz already exists Feb 5 14:47:50 Tower root: plugin: running: /boot/config/plugins/shellinabox/shellinabox-2.19-x86_64-1sl.txz Feb 5 14:47:50 Tower root: Feb 5 14:47:50 Tower root: +============================================================================== Feb 5 14:47:50 Tower root: | Installing new package /boot/config/plugins/shellinabox/shellinabox-2.19-x86_64-1sl.txz Feb 5 14:47:50 Tower root: +============================================================================== Feb 5 14:47:50 Tower root: Feb 5 14:47:50 Tower root: Verifying package shellinabox-2.19-x86_64-1sl.txz. Feb 5 14:47:50 Tower root: Installing package shellinabox-2.19-x86_64-1sl.txz: Feb 5 14:47:50 Tower root: PACKAGE DESCRIPTION: Feb 5 14:47:50 Tower root: # shellinabox - Web based AJAX terminal emulator Feb 5 14:47:50 Tower root: # Feb 5 14:47:50 Tower root: # Shell In A Box implements a web server that can export arbitrary Feb 5 14:47:50 Tower root: # command line tools to a web based terminal emulator. Feb 5 14:47:50 Tower root: # Feb 5 14:47:50 Tower root: # This emulator is accessible to any JavaScript and CSS enabled Feb 5 14:47:50 Tower root: # web browser and does not require any additional browser plugins. Feb 5 14:47:50 Tower root: # Feb 5 14:47:50 Tower root: # http://code.google.com/p/shellinabox/ Feb 5 14:47:50 Tower root: # Feb 5 14:47:50 Tower root: Package shellinabox-2.19-x86_64-1sl.txz installed. Feb 5 14:47:50 Tower root: Feb 5 14:47:50 Tower root: Feb 5 14:47:50 Tower root: plugin: skipping: /boot/config/plugins/shellinabox/linux-pam-1.1.8-x86_64-1gds.txz already exists Feb 5 14:47:50 Tower root: plugin: running: /boot/config/plugins/shellinabox/linux-pam-1.1.8-x86_64-1gds.txz Feb 5 14:47:50 Tower root: Feb 5 14:47:50 Tower root: +============================================================================== Feb 5 14:47:50 Tower root: | Installing new package /boot/config/plugins/shellinabox/linux-pam-1.1.8-x86_64-1gds.txz Feb 5 14:47:50 Tower root: +============================================================================== Feb 5 14:47:50 Tower root: Feb 5 14:47:50 Tower root: Verifying package linux-pam-1.1.8-x86_64-1gds.txz. Feb 5 14:47:50 Tower root: Installing package linux-pam-1.1.8-x86_64-1gds.txz: Feb 5 14:47:50 Tower root: PACKAGE DESCRIPTION: Feb 5 14:47:50 Tower root: # Linux-PAM (Pluggable Authentication Modules for Linux) Feb 5 14:47:50 Tower root: # Feb 5 14:47:50 Tower root: # Linux-PAM is a library that enables the local system administrator Feb 5 14:47:50 Tower root: # to choose how individual applications authenticate users. Feb 5 14:47:50 Tower root: # The purpose of the Linux-PAM project is to liberate the development Feb 5 14:47:50 Tower root: # of privilege granting software from the development of secure and Feb 5 14:47:50 Tower root: # appropriate authentication schemes. This is accomplished by Feb 5 14:47:50 Tower root: # providing a documented library of functions that an application Feb 5 14:47:50 Tower root: # may use for all forms of user authentication management. This Feb 5 14:47:50 Tower root: # library dynamically loads locally configured authentication Feb 5 14:47:50 Tower root: # modules that actually perform the authentication tasks. Feb 5 14:47:50 Tower root: # Feb 5 14:47:50 Tower root: # Packaged by Georgi D. Sotirov <[email protected]> Feb 5 14:47:50 Tower root: Executing install script for linux-pam-1.1.8-x86_64-1gds.txz. Feb 5 14:47:50 Tower root: Package linux-pam-1.1.8-x86_64-1gds.txz installed. Feb 5 14:47:50 Tower root: Feb 5 14:47:50 Tower root: Feb 5 14:47:50 Tower root: plugin: skipping: /boot/config/plugins/shellinabox/shellinabox-2015.09.20.tar.gz already exists Feb 5 14:47:50 Tower root: plugin: running: anonymous Feb 5 14:47:50 Tower root: Feb 5 14:47:50 Tower root: ----------------------------------------------------------- Feb 5 14:47:50 Tower root: shellinabox has been installed. Feb 5 14:47:50 Tower root: This plugin requires Dynamix webGui to operate Feb 5 14:47:50 Tower root: Copyright 2015, dmacias72 Feb 5 14:47:50 Tower root: Version: 2015.09.20 Feb 5 14:47:50 Tower root: ----------------------------------------------------------- Feb 5 14:47:50 Tower root: Feb 5 14:47:50 Tower root: plugin: creating: /tmp/shellinabox-chkconf - from INLINE content Feb 5 14:47:50 Tower root: plugin: running: /tmp/shellinabox-chkconf Feb 5 14:47:50 Tower root: plugin: installed Feb 5 14:47:50 Tower root: plugin: installing: /boot/config/plugins/user.scripts.plg Feb 5 14:47:50 Tower root: plugin: skipping: /boot/config/plugins/user.scripts/user.scripts-2017.11.18-x86_64-1.txz already exists Feb 5 14:47:50 Tower root: plugin: running: /boot/config/plugins/user.scripts/user.scripts-2017.11.18-x86_64-1.txz Feb 5 14:47:50 Tower root: Feb 5 14:47:50 Tower root: +============================================================================== Feb 5 14:47:50 Tower root: | Installing new package /boot/config/plugins/user.scripts/user.scripts-2017.11.18-x86_64-1.txz Feb 5 14:47:50 Tower root: +============================================================================== Feb 5 14:47:50 Tower root: Feb 5 14:47:50 Tower root: Verifying package user.scripts-2017.11.18-x86_64-1.txz. Feb 5 14:47:50 Tower root: Installing package user.scripts-2017.11.18-x86_64-1.txz: Feb 5 14:47:50 Tower root: PACKAGE DESCRIPTION: Feb 5 14:47:50 Tower root: Package user.scripts-2017.11.18-x86_64-1.txz installed. Feb 5 14:47:50 Tower root: Feb 5 14:47:50 Tower root: Feb 5 14:47:50 Tower root: plugin: running: anonymous Feb 5 14:47:50 Tower root: Feb 5 14:47:50 Tower root: Feb 5 14:47:50 Tower root: Feb 5 14:47:50 Tower root: Feb 5 14:47:50 Tower root: plugin: running: anonymous Feb 5 14:47:50 Tower root: Feb 5 14:47:50 Tower root: ---------------------------------------------------- Feb 5 14:47:50 Tower root: user.scripts has been installed. Feb 5 14:47:50 Tower root: Copyright 2016, Andrew Zawadzki Feb 5 14:47:50 Tower root: Version: 2017.11.18 Feb 5 14:47:50 Tower root: ---------------------------------------------------- Feb 5 14:47:50 Tower root: Feb 5 14:47:50 Tower root: plugin: installed Feb 5 14:47:50 Tower root: Starting go script Feb 5 14:47:50 Tower root: Starting emhttpd Feb 5 14:47:50 Tower emhttpd: unRAID System Management Utility version 6.4.0 Feb 5 14:47:50 Tower emhttpd: Copyright (C) 2005-2017, Lime Technology, Inc. Feb 5 14:47:50 Tower emhttpd: shcmd (6): echo 'root:$5$Iwgg//KW5QU//$P0fXU2AFwz2g8j2QT6YbXIWmVyEw665U3Tm8B2yRlGB' >/etc/nginx/htpasswd Feb 5 14:47:50 Tower emhttpd: shcmd (8): modprobe md-mod super=/boot/config/super.dat Feb 5 14:47:50 Tower kernel: md: unRAID driver 2.9.3 installed Feb 5 14:47:50 Tower emhttpd: Basic key detected, GUID: 0781-5571-0008-010807103220 FILE: /boot/config/Basic.key Feb 5 14:47:50 Tower emhttpd: Device inventory: Feb 5 14:47:50 Tower emhttpd: WDC_WD80EMAZ-00WJTA0_7SH0XGYC (sdg) 512 15628053168 Feb 5 14:47:50 Tower emhttpd: ST4000DM000-1F2168_S301KS2H (sdd) 512 7814037168 Feb 5 14:47:50 Tower emhttpd: ST4000DM000-1F2168_S301KS2V (sde) 512 7814037168 Feb 5 14:47:50 Tower emhttpd: ST4000DM000-1F2168_S301P805 (sdb) 512 7814037168 Feb 5 14:47:50 Tower emhttpd: WDC_WD80EMAZ-00WJTA0_7SGTU9EC (sdf) 512 15628053168 Feb 5 14:47:50 Tower emhttpd: ST4000DM000-1F2168_S301KSNJ (sdc) 512 7814037168 Feb 5 14:47:50 Tower emhttpd: ADATA_SX7000NP_2H5220023786 (nvme0n1) 512 1000215216 Feb 5 14:47:50 Tower emhttpd: SanDisk_Cruzer_Fit_4C530008010807103220-0:0 (sda) 512 31266816 Feb 5 14:47:50 Tower kernel: mdcmd (1): import 0 sdc 64 3907018532 0 ST4000DM000-1F2168_S301KSNJ Feb 5 14:47:50 Tower kernel: md: import disk0: (sdc) ST4000DM000-1F2168_S301KSNJ size: 3907018532 Feb 5 14:47:50 Tower kernel: mdcmd (2): import 1 sde 64 3907018532 0 ST4000DM000-1F2168_S301KS2V Feb 5 14:47:50 Tower kernel: md: import disk1: (sde) ST4000DM000-1F2168_S301KS2V size: 3907018532 Feb 5 14:47:50 Tower kernel: mdcmd (3): import 2 sdd 64 3907018532 0 ST4000DM000-1F2168_S301KS2H Feb 5 14:47:50 Tower kernel: md: import disk2: (sdd) ST4000DM000-1F2168_S301KS2H size: 3907018532 Feb 5 14:47:50 Tower kernel: mdcmd (4): import 3 sdb 64 3907018532 0 ST4000DM000-1F2168_S301P805 Feb 5 14:47:50 Tower kernel: md: import disk3: (sdb) ST4000DM000-1F2168_S301P805 size: 3907018532 Feb 5 14:47:50 Tower kernel: mdcmd (5): import 4 Feb 5 14:47:50 Tower kernel: mdcmd (6): import 5 Feb 5 14:47:50 Tower kernel: mdcmd (7): import 6 Feb 5 14:47:50 Tower kernel: mdcmd (8): import 7 Feb 5 14:47:50 Tower kernel: mdcmd (9): import 8 Feb 5 14:47:50 Tower kernel: mdcmd (10): import 9 Feb 5 14:47:50 Tower kernel: mdcmd (11): import 10 Feb 5 14:47:50 Tower kernel: mdcmd (12): import 11 Feb 5 14:47:50 Tower kernel: mdcmd (13): import 12 Feb 5 14:47:50 Tower kernel: mdcmd (14): import 13 Feb 5 14:47:50 Tower kernel: mdcmd (15): import 14 Feb 5 14:47:50 Tower kernel: mdcmd (16): import 15 Feb 5 14:47:50 Tower kernel: mdcmd (17): import 16 Feb 5 14:47:50 Tower kernel: mdcmd (18): import 17 Feb 5 14:47:50 Tower kernel: mdcmd (19): import 18 Feb 5 14:47:50 Tower kernel: mdcmd (20): import 19 Feb 5 14:47:50 Tower kernel: mdcmd (21): import 20 Feb 5 14:47:50 Tower kernel: mdcmd (22): import 21 Feb 5 14:47:50 Tower kernel: mdcmd (23): import 22 Feb 5 14:47:50 Tower kernel: mdcmd (24): import 23 Feb 5 14:47:50 Tower kernel: mdcmd (25): import 24 Feb 5 14:47:50 Tower kernel: mdcmd (26): import 25 Feb 5 14:47:50 Tower kernel: mdcmd (27): import 26 Feb 5 14:47:50 Tower kernel: mdcmd (28): import 27 Feb 5 14:47:50 Tower kernel: mdcmd (29): import 28 Feb 5 14:47:50 Tower kernel: mdcmd (30): import 29 Feb 5 14:47:50 Tower kernel: md: import_slot: 29 empty Feb 5 14:47:50 Tower emhttpd: import 30 cache device: no device Feb 5 14:47:50 Tower emhttpd: import flash device: sda Feb 5 14:47:51 Tower emhttpd: Starting services... Feb 5 14:47:51 Tower emhttpd: shcmd (16): /etc/rc.d/rc.avahidaemon start Feb 5 14:47:51 Tower root: Starting Avahi mDNS/DNS-SD Daemon: /usr/sbin/avahi-daemon -D Feb 5 14:47:51 Tower avahi-daemon[4120]: Found user 'avahi' (UID 61) and group 'avahi' (GID 214). Feb 5 14:47:51 Tower avahi-daemon[4120]: Successfully dropped root privileges. Feb 5 14:47:51 Tower avahi-daemon[4120]: avahi-daemon 0.7 starting up. Feb 5 14:47:51 Tower avahi-daemon[4120]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns! Feb 5 14:47:51 Tower avahi-daemon[4120]: Successfully called chroot(). Feb 5 14:47:51 Tower avahi-daemon[4120]: Successfully dropped remaining capabilities. Feb 5 14:47:51 Tower avahi-daemon[4120]: Loading service file /services/sftp-ssh.service. Feb 5 14:47:51 Tower avahi-daemon[4120]: Loading service file /services/smb.service. Feb 5 14:47:51 Tower avahi-daemon[4120]: Loading service file /services/ssh.service. Feb 5 14:47:51 Tower avahi-daemon[4120]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::7285:c2ff:fe6b:180c. Feb 5 14:47:51 Tower avahi-daemon[4120]: New relevant interface eth0.IPv6 for mDNS. Feb 5 14:47:51 Tower avahi-daemon[4120]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.218. Feb 5 14:47:51 Tower avahi-daemon[4120]: New relevant interface eth0.IPv4 for mDNS. Feb 5 14:47:51 Tower avahi-daemon[4120]: Network interface enumeration completed. Feb 5 14:47:51 Tower avahi-daemon[4120]: Registering new address record for fe80::7285:c2ff:fe6b:180c on eth0.*. Feb 5 14:47:51 Tower avahi-daemon[4120]: Registering new address record for 192.168.1.218 on eth0.IPv4. Feb 5 14:47:51 Tower emhttpd: shcmd (17): /etc/rc.d/rc.avahidnsconfd start Feb 5 14:47:51 Tower root: Starting Avahi mDNS/DNS-SD DNS Server Configuration Daemon: /usr/sbin/avahi-dnsconfd -D Feb 5 14:47:51 Tower avahi-dnsconfd[4132]: Successfully connected to Avahi daemon. Feb 5 14:47:51 Tower emhttpd: shcmd (22): /etc/rc.d/rc.php-fpm start Feb 5 14:47:51 Tower root: Starting php-fpm done Feb 5 14:47:51 Tower emhttpd: shcmd (23): /etc/rc.d/rc.nginx start Feb 5 14:47:52 Tower avahi-daemon[4120]: Server startup complete. Host name is Tower.local. Local service cookie is 1258163532. Feb 5 14:47:52 Tower avahi-daemon[4120]: Service "Tower" (/services/ssh.service) successfully established. Feb 5 14:47:52 Tower avahi-daemon[4120]: Service "Tower" (/services/smb.service) successfully established. Feb 5 14:47:52 Tower avahi-daemon[4120]: Service "Tower" (/services/sftp-ssh.service) successfully established. Feb 5 14:47:56 Tower root: Starting Nginx server daemon... Feb 5 14:47:56 Tower emhttpd: too many devices Feb 5 14:51:14 Tower kernel: usb 1-3: new full-speed USB device number 3 using xhci_hcd Feb 5 14:51:14 Tower kernel: input: Corsair Corsair K65 Gaming Keyboard as /devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-3/1-3:1.0/0003:1B1C:1B07.0001/input/input3 Feb 5 14:51:14 Tower kernel: hid-generic 0003:1B1C:1B07.0001: input,hidraw0: USB HID v1.11 Keyboard [Corsair Corsair K65 Gaming Keyboard] on usb-0000:03:00.0-3/input0 Feb 5 14:51:14 Tower kernel: input: Corsair Corsair K65 Gaming Keyboard as /devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-3/1-3:1.1/0003:1B1C:1B07.0002/input/input4 Feb 5 14:51:14 Tower kernel: hid-generic 0003:1B1C:1B07.0002: input,hidraw1: USB HID v1.11 Device [Corsair Corsair K65 Gaming Keyboard] on usb-0000:03:00.0-3/input1 Feb 5 14:51:14 Tower kernel: input: Corsair Corsair K65 Gaming Keyboard as /devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-3/1-3:1.2/0003:1B1C:1B07.0003/input/input5 Feb 5 14:51:14 Tower kernel: hid-generic 0003:1B1C:1B07.0003: input,hidraw2: USB HID v1.11 Keyboard [Corsair Corsair K65 Gaming Keyboard] on usb-0000:03:00.0-3/input2 Feb 5 14:51:23 Tower login[4059]: invalid password for 'UNKNOWN' on '/dev/tty1' Feb 5 14:51:30 Tower login[4059]: ROOT LOGIN on '/dev/tty1' Feb 5 14:52:49 Tower ntpd[1852]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Feb 5 14:53:24 Tower kernel: usb 1-3: USB disconnect, device number 3 Feb 5 14:53:24 Tower acpid: input device has been disconnected, fd 9 Feb 5 14:53:24 Tower acpid: input device has been disconnected, fd 10 Feb 5 14:53:24 Tower acpid: input device has been disconnected, fd 11 Feb 5 14:54:41 Tower kernel: usb 1-3: new full-speed USB device number 4 using xhci_hcd Feb 5 14:54:42 Tower kernel: input: Corsair Corsair K65 Gaming Keyboard as /devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-3/1-3:1.0/0003:1B1C:1B07.0004/input/input6 Feb 5 14:54:42 Tower kernel: hid-generic 0003:1B1C:1B07.0004: input,hidraw0: USB HID v1.11 Keyboard [Corsair Corsair K65 Gaming Keyboard] on usb-0000:03:00.0-3/input0 Feb 5 14:54:42 Tower kernel: input: Corsair Corsair K65 Gaming Keyboard as /devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-3/1-3:1.1/0003:1B1C:1B07.0005/input/input7 Feb 5 14:54:42 Tower kernel: hid-generic 0003:1B1C:1B07.0005: input,hidraw1: USB HID v1.11 Device [Corsair Corsair K65 Gaming Keyboard] on usb-0000:03:00.0-3/input1 Feb 5 14:54:42 Tower kernel: input: Corsair Corsair K65 Gaming Keyboard as /devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-3/1-3:1.2/0003:1B1C:1B07.0006/input/input8 Feb 5 14:54:42 Tower kernel: hid-generic 0003:1B1C:1B07.0006: input,hidraw2: USB HID v1.11 Keyboard [Corsair Corsair K65 Gaming Keyboard] on usb-0000:03:00.0-3/input2 Feb 5 14:58:26 Tower kernel: usb 1-3: USB disconnect, device number 4 Feb 5 14:58:26 Tower acpid: input device has been disconnected, fd 9 Feb 5 14:58:26 Tower acpid: input device has been disconnected, fd 10 Feb 5 14:58:26 Tower acpid: input device has been disconnected, fd 11 Feb 5 15:06:13 Tower nginx: 2018/02/05 15:06:13 [error] 4190#4190: *687 user "cablecutter" was not found in "/etc/nginx/htpasswd", client: 192.168.1.196, server: , request: "GET /Main HTTP/1.1", host: "192.168.1.218:81" Feb 5 15:06:13 Tower nginx: 2018/02/05 15:06:13 [error] 4190#4190: *687 user "cablecutter" was not found in "/etc/nginx/htpasswd", client: 192.168.1.196, server: , request: "GET /Main HTTP/1.1", host: "192.168.1.218:81" Feb 5 15:10:07 Tower sshd[8182]: Accepted password for root from 192.168.1.196 port 52816 ssh2
  10. Hi, First, I want to take a chance to thank you for both releasing this and for helping people out in this thread. I've got it installed and have the following working: Can search for an add books / authors Have connected to my Deluge instance on a remote Seedbox Am downloading successfully to my seedbox Outside of this app - I am successfully syncing files to my unRaid box using resilio I am having trouble with the following: Books in the "download" directory are not being imported / moved to the Book directory torznab processors specified in Jackett, and used by my Couchpotato / Sonarr instance result in errors My docker is set up as: My processing tab is set up as: (and I have tried leaving base destination folder blank) My download directory is set to: /mnt/user/Warehouse/cablecutter/Inbox/ (have also tried leaving it blank) I get errors such as: 2018-02-03 12:41:21 WARNING Download dir not usable, using / 2018-02-03 12:34:31 ERROR Failed to download torrent from DELUGERPC, magnet:?xt=urn:btih:CA95D8B06A5D14AD3E20749C43D37EA3992018DA&dn=Keep%20the%20Aspidistra%20Flying%20by%20George%20Orwell%20EPUB 2018-02-03 12:30:44 ERROR Error reading data from http://192.168.1.163:9117/api/v2.0/indexers/torrentleech/results/torznab/: Not Found 2018-02-03 12:30:44 WARNING Unable to get capabilities for http://192.168.1.163:9117/api/v2.0/indexers/torrentleech/results/torznab//api?t=caps&apikey=g9t2gs0bm77l93pv4xtflrc3lj0l8emm: No data returned 2018-02-03 12:30:44 ERROR Error reading data from http://192.168.1.163:9117/api/v2.0/indexers/iptorrents/results/torznab/: Not Found 2018-02-03 12:30:44 WARNING Unable to get capabilities for http://192.168.1.163:9117/api/v2.0/indexers/iptorrents/results/torznab//api?t=caps&apikey=g9t2gs0bm77l93pv4xtflrc3lj0l8emm: No data returned 2018-02-03 12:30:44 ERROR Error reading data from http://192.168.1.163:9117/api/v2.0/indexers/torrentleech/results/torznab/: Not Found 2018-02-03 12:30:44 WARNING Unable to get capabilities for http://192.168.1.163:9117/api/v2.0/indexers/torrentleech/results/torznab//api?t=caps&apikey=g9t2gs0bm77l93pv4xtflrc3lj0l8emm: No data returned 2018-02-03 12:30:44 ERROR Error reading data from http://192.168.1.163:9117/api/v2.0/indexers/iptorrents/results/torznab/: Not Found 2018-02-03 12:30:44 WARNING Unable to get capabilities for http://192.168.1.163:9117/api/v2.0/indexers/iptorrents/results/torznab//api?t=caps&apikey=g9t2gs0bm77l93pv4xtflrc3lj0l8emm: No data returned 2018-02-03 12:48:20 INFO No snatched books/mags have been found 2018-02-03 12:48:20 INFO Looking for Britt-Marie Was Here by Fredrik Backman EPUB in / Books are being marked as "Snatched" when found / downloaded via Deluge Thank you for any help you can provide Best Regards Edit: After changing the download dir to /downloads and import dir to /books I am getting: 2018-02-03 12:54:56 INFO 6 books/mags processed. 2018-02-03 12:54:56 INFO Successfully processed: Britt-Marie Was Here - Fredrik Backman However, the books are not being moved to my /books dir. They are staying in place.
  11. Thanks Frank. The motherboard doesn't have a PCI slot though. I'm curious if it will allow me to run UnRaid headless and pass through the GPU to the VM. I think your answer implies yes, but I just want to be sure.
  12. Hi All, I'm working on a new build now and want to be sure that I'm not going to gimp myself. Will I be able to use the ONLY GPU in the system for a VM (leaving no GPU for UnRaid)? Typically I only access UnRaid VIA Web interface, really have no need for a dedicated GPU just so that I can look at the UI. Best, Rob
  13. Hi All, TLDR: Media Center (windows) / Gaming (windows) / large NAS (unRaid) / DNS Host + Plex + Torrent related Dockers (unRaid) - Looking for the optimal drive configuration when considering Cache SSD (or HDD) vs SSD outside of the array. I've done a bit of searching on this subject but haven't found a solid recommendation. My configuration options seem to be: Single PCIE SSD cache (512GB) Multiple drives set up as cache - not sure if it would be possible to separate file transfer (write to main array) cache from VM only cache 1X 256-512GB Cache (HDD or SSD) & 1x 256-512GB PCIE SSD outside of the array (Is there any benefit to doing this?) The use cases are: Docker images that run regularly Windows VM Applications which use the windows VM I don't want to spend more than I need to, and if possible I would like to reduce complexity by limiting the number of drives that I have (In favor of Cache only). However, I want to ensure that the windows VM is not unnecessarily spinning up drives, and is not bottlenecked by other processes which may be happening on cache - I will be using the windows VM regularly for gaming and media center. Best, Rob
  14. Hey All, I'm dying... I need help. There's no perfect case for my neeeds! HW Specs: 8x 3.5" HDD's (don't care if I have to hack some more space or 3d print additional racks - just needs enough volume to hold them) 1-2x SSD or M.2 ATX or Micro ATX / AM4 / Tower cooler (for silence) / Full ATX PSU GTX 1070 GPU or similar / full size card Case Requirements: Shit needs to look GOOD and fit in - or worst case ontop of a salamander cherry AV rack (picture below) By look good, I mean clean face, metal. If I could buy a solid block of steel or aluminum with no features...except a power button - that's what I'd get. To go with the above - it should either be a horizontal or cube form factor. It can't be more than 18" wide, and also shouldn't be too much more than 15" deep. I suppose it can hang off the back a little bit, but too much and my OCD will start to flare. It needs to be quiet. And when I say quiet - I mean fucking QUIET!!! A little woosh is fine, but resonance has to be kept to a minimum. What I'm looking at: Silverstone Grandia 07 or 09 - http://silverstonetek.com/product.php?area=en&pid=330 ... Not sure why... I just don't like this case...And that's why it gets a low res image. Maybe it's because this case was released in 2012, has design issues (fitment with newer GPU standards / cpu coolers), and has not been updated in 5 years...That's just lazy. Lian Li PC 720 (a little deep at 18 inches - would prefer 16 max) http://www.lian-li.com/13633-2/ Streacom F12C - (sounds like it might be a pain in the ass to work on...and $$$ - But LOOK AT IT http://www.streacom.com/products/f12c-chassis/ So I need help. Probably in more ways than one, but for now - just help me find my case.
  15. For anyone stuck in a similar boat - this was a pretty painless process. All of the configs were maintained (I thought they'd have to be set up again). Now I understand why it is the go-to solution. I backed up my docker.img by going to disk1 using CD (where my image is stored) and renaming it with mv docker.img docker_backup.img I disabled the docker service in the UI and re-enabled it. Docker started up without issue. For anyone that's really new - this is what it looked like in the terminal: XXXXXX@Tower:/mnt# cd disk1 XXXXXX@Tower:/mnt/disk1# ls CommunityApplicationsAppdataBackup/ Warehouse/ appdata/ docker.img XXXXXX@Tower:/mnt/disk1# mv docker.img docker_backup.img XXXXXX@Tower:/mnt/disk1# ls CommunityApplicationsAppdataBackup/ Warehouse/ appdata/ docker_backup.img (after restoring my apps) XXXXXX@Tower:/mnt/disk1# rm docker_backup.img XXXXXX@Tower:/mnt/disk1# ls CommunityApplicationsAppdataBackup/ Warehouse/ appdata/ docker.img
  16. Thanks. I was hoping to avoid that if possible, but...seems it might be what I have to do.
  17. Hi all, Having some trouble getting docker to fire up after updating to 6.4 (from 6.1.3). Stopping and starting the docker service doesn't give any errors: Jan 21 18:26:13 Tower root: starting dockerd ... Jan 21 18:26:23 Tower emhttpd: shcmd (185): umount /var/lib/docker Docker Settings: https://pasteboard.co/H41gjvH.png What I've checked: Unraid starts up just fine and is able to connect to the web. Disks show no read or write errors Parity looks good Disks have enough space for docker image Docker image disk is spun up and I am able to read from it without issue I did not change any docker settings / config during the update process I did update community plugins Any help would be appreciated. Without errors I'm at a bit of a loss. Best, Rob
  18. Thanks, I was hoping to leverage MadVR.
  19. Still looking for any suggestions. Should I use a VM with Windows or one of the Linux HTPC builds? Is there any native support without VM?
  20. Hi all, thinking that I'd like to consolidate a bit and was wondering if anyone is using a UnRaid box as an HTPC (directly). What I do now: Unraid in the closet (hard wired) Running Plex / hosting content / backup for PC's in the house Wifi Nvidia Shield (plex or SPMC[kodi]) -> AVR -> Samsung 4k Reasons I want to do this: Nvidia shield is good, but the content scaling is terrible and it's a little laggier than I'd like. It's one more thing to troubleshoot. There exist some great 1080p scaling algorithms and smooth motion algorithms that are better than what exists on the shield or in the samsung TV - I'd like to leverage these to improve playback of 1080 content. The Unraid server will have a better processor than any set top box I feel like my server is underutilized The network would not be taxed when streaming content. Potential for gaming down the line? Windows VM? Better upgrade path for video output / compatibility with future standards Cheaper / fewer devices More flexibility in HTPC applications than an android or amazon box My unraid server will finally have a monitor...a glorious 65" monitor. Can I do this? Are there any guides? I had a surprisingly hard time finding one.
  21. Hi all, I have a 6 year old server that I use primarily as a NAS backup + Plex box. I do need the ability to transcoded 1080 and 4k. Specs: 3U Server Tyan S7012 2x Intel Xeon X5570 Quad Core 24GB ASR-5805 RAID 9 HD JBOD I have three main issues I'd like to solve: -the asr-5805 has been a problem for me and I have been unable to expand beyond the 3 onboard data ports -the server is not energy efficient. I'd like to spend less money on electricity -the server is in a closet and the CPUs need better cooling I'm looking to get a micro/mini form factor single processor motherboard with onboard raid and an energy efficient CPU. Any suggestions? Much thanks, Rob
  22. Hi all, I have a server box with an Adaptec ASR-5805 card. I plug in a hard drive. Boot, and hit ctrl-a. I get this message. Any ideas?
  23. You're the best RX. That got me exactly where i needed to be. Ip was listed on my router.
  24. Thanks - this is very helpful but so far I have been unable to load the aster guide (going to https://192.168.1.163/page/login . html - this is my unraid box's ip)
  25. Also following along - I'm in the same boat and want to idle at the lowest power consumption possible (intel Xeon Gainestown) - do you have a recommendation for general bios settings? Right now I see: "2801000 2800000 2667000 2533000 2400000 2267000 2133000 2000000 1867000 1733000 1600000" and I do idle at 1600000 - but this is still way too high.