jasonmcroy Posted January 25, 2019 Share Posted January 25, 2019 (edited) Hey guys, This is my first post. I recently purchased Unraid and I am loving the software so far. I started out using it on one of my spare computers but after using it for a few days and really enjoying it I decided to move it over to a different computer that I like better because it has more RAM, better cpu, etc. Anyways, my motherboard is a Gigabyte GA-970A-DS3P. There is a known issue with IOMMU on this motherboard when using Linux software. What happens is that if you have IOMMU enabled then the ethernet input and USB 3.0 connections won't work. If you disable IOMMU you get ethernet and USB 3.0 back but you lose the USB 2.0 connections. I know the fix for this when running Ubuntu or other flavor of that OS is to open this file: /etc/default/grub and change a line in that file to IOMMU=SOFT. After doing that everything works like normal. Here is my issue - I can't seem to find a file with that name in Unraid. The only references I have seen pointing to IOMMU is the syslinux.cfg file. However, when I looked at that file on my system I don't see any mention of IOMMU in that file anywhere. So, my question is: does anyone have any idea where I would change this in Unraid? I assume it's based on a different Linux OS than Ubuntu so there is something different I should do to fix this issue. Thanks in advance. Edited January 26, 2019 by jasonmcroy Quote Link to comment
jasonmcroy Posted January 27, 2019 Author Share Posted January 27, 2019 Maybe I should rephrase what I need help with? Can someone tell me what file contains the IOMMU information that I can change and where it is located? Quote Link to comment
orangechrome Posted May 31, 2019 Share Posted May 31, 2019 I am also having an issue passing USB devices on a very similar MOBO (Gigabyte GA-970A-D3P.) when passing through a secondary graphics card via iommu (RX480). I can't even get to the Windows install because I can't hit the any key. Anyone have any luck or ideas on this? I tried the hotplug USB plugin, no luck Quote Link to comment
Taddeusz Posted May 31, 2019 Share Posted May 31, 2019 You can modify the syslinux.cfg from the UI. On the "Main" page click on Flash under "Boot Device". Scroll down and you can modify the kernel boot parameters there. For example here is my entry for "unRaid OS". kernel /bzimage append initrd=/bzroot iommu=pt In my case I was having issues with IOMMU affecting my NVMe drive. I don't know what the "soft" setting does but the "iommu=pt" setting only enables IOMMU for devices that are being used for that purpose and disables it for all other devices. This actually sounds like what you might need. Quote Link to comment
jasonmcroy Posted May 31, 2019 Author Share Posted May 31, 2019 (edited) 23 minutes ago, Taddeusz said: You can modify the syslinux.cfg from the UI. On the "Main" page click on Flash under "Boot Device". Scroll down and you can modify the kernel boot parameters there. For example here is my entry for "unRaid OS". kernel /bzimage append initrd=/bzroot iommu=pt In my case I was having issues with IOMMU affecting my NVMe drive. I don't know what the "soft" setting does but the "iommu=pt" setting only enables IOMMU for devices that are being used for that purpose and disables it for all other devices. This actually sounds like what you might need. So, perhaps if I add your lines above but instead of "iommu=pt" use "iommu=soft" may solve my issue? From my research the "soft" command tells the kernel to use a software implementation to remap memory. There is a lot of information when I google this issue for Debian using the grub file, but apparently UnRaid OS doesn't use a grub file? Edited May 31, 2019 by jasonmcroy Quote Link to comment
Taddeusz Posted May 31, 2019 Share Posted May 31, 2019 1 minute ago, jasonmcroy said: So, perhaps if I add your lines above but instead of iommu=soft may solve my issue? From my research the "soft" command tells the kernel to use a software implementation to remap memory. There is a lot of information when I google this issue for Debian using the grub file, but apparently UnRaid OS doesn't use a grub file? Syslinux is the bootloader. It doesn't use GRUB like other Linux distributions so the syslinux.cfg is the correct place to put kernel boot parameters. 1 Quote Link to comment
jasonmcroy Posted May 31, 2019 Author Share Posted May 31, 2019 4 minutes ago, Taddeusz said: Syslinux is the bootloader. It doesn't use GRUB like other Linux distributions so the syslinux.cfg is the correct place to put kernel boot parameters. Ok, thanks. I may try this over the weekend. I had quit using UnRaid because I couldn't figure out where/how to put that command. Quote Link to comment
orangechrome Posted June 5, 2019 Share Posted June 5, 2019 I'm still getting the same issues with the recommended fix I noticed a bunch of AMD-Vi errors in the boot: Jun 4 17:22:59 Tower root: Executing install script for fuse-exfat-1.2.8-x86_64-1_slonly.txz. Jun 4 17:22:59 Tower root: Package fuse-exfat-1.2.8-x86_64-1_slonly.txz installed. Jun 4 17:22:59 Tower root: plugin: skipping: /boot/config/plugins/unassigned.devices/packages/hfsprogs-332.25-x86_64-2sl.txz already exists Jun 4 17:22:59 Tower root: plugin: running: /boot/config/plugins/unassigned.devices/packages/hfsprogs-332.25-x86_64-2sl.txzJun 4 17:22:59 Tower root: Jun 4 17:22:59 Tower root: +============================================================================== Jun 4 17:22:59 Tower root: | Installing new package /boot/config/plugins/unassigned.devices/packages/hfsprogs-332.25-x86_64-2sl.txz Jun 4 17:22:59 Tower root: +============================================================================== Jun 4 17:22:59 Tower root: Jun 4 17:23:00 Tower root: Verifying package hfsprogs-332.25-x86_64-2sl.txz. Jun 4 17:23:00 Tower root: Installing package hfsprogs-332.25-x86_64-2sl.txz: Jun 4 17:23:00 Tower root: PACKAGE DESCRIPTION: Jun 4 17:23:00 Tower root: # hfsprogs - hfs+ user space utils Jun 4 17:23:00 Tower root: # Jun 4 17:23:00 Tower root: # The HFS+ file system used by Apple Computer for their Mac OS is Jun 4 17:23:00 Tower root: # supported by the Linux kernel. Apple provides mkfs and fsck for Jun 4 17:23:00 Tower root: # HFS+ with the Unix core of their operating system, Darwin. Jun 4 17:23:00 Tower root: # Jun 4 17:23:00 Tower root: # This package is a port of Apple's tools for HFS+ filesystems. Jun 4 17:23:00 Tower root: # Jun 4 17:23:00 Tower root: # http://www.opensource.apple.com Jun 4 17:23:00 Tower root: Package hfsprogs-332.25-x86_64-2sl.txz installed. Jun 4 17:23:00 Tower root: plugin: skipping: /boot/config/plugins/unassigned.devices/packages/libbsd-0.8.7-x86_64-1_slonly.txz already exists Jun 4 17:23:00 Tower root: plugin: running: /boot/config/plugins/unassigned.devices/packages/libbsd-0.8.7-x86_64-1_slonly.txz Jun 4 17:23:00 Tower root: Jun 4 17:23:00 Tower root: +============================================================================== Jun 4 17:23:00 Tower root: | Installing new package /boot/config/plugins/unassigned.devices/packages/libbsd-0.8.7-x86_64-1_slonly.txz Jun 4 17:23:00 Tower root: +============================================================================== Jun 4 17:23:00 Tower root: Jun 4 17:23:00 Tower root: Verifying package libbsd-0.8.7-x86_64-1_slonly.txz. Jun 4 17:23:00 Tower root: Installing package libbsd-0.8.7-x86_64-1_slonly.txz: Jun 4 17:23:00 Tower root: PACKAGE DESCRIPTION: Jun 4 17:23:00 Tower root: # libbsd (library of BSD functions) Jun 4 17:23:00 Tower root: # Jun 4 17:23:00 Tower root: # This library provides useful functions commonly found on BSD systems, Jun 4 17:23:00 Tower root: # and lacking on others like GNU systems, thus making it easier to port Jun 4 17:23:00 Tower root: # projects with strong BSD origins, without needing to embed the same Jun 4 17:23:00 Tower root: # code over and over again on each project. Jun 4 17:23:00 Tower root: # Jun 4 17:23:00 Tower root: # Homepage: http://libbsd.freedesktop.org/wiki/ Jun 4 17:23:00 Tower root: # Jun 4 17:23:00 Tower root: Executing install script for libbsd-0.8.7-x86_64-1_slonly.txz. Jun 4 17:23:00 Tower root: Package libbsd-0.8.7-x86_64-1_slonly.txz installed. Jun 4 17:23:00 Tower root: plugin: skipping: /boot/config/plugins/unassigned.devices/packages/parted-3.2-x86_64-2.txz already exists Jun 4 17:23:00 Tower root: plugin: running: /boot/config/plugins/unassigned.devices/packages/parted-3.2-x86_64-2.txz Jun 4 17:23:00 Tower root: Jun 4 17:23:00 Tower root: +============================================================================== Jun 4 17:23:00 Tower root: | Installing new package /boot/config/plugins/unassigned.devices/packages/parted-3.2-x86_64-2.txz Jun 4 17:23:00 Tower root: +============================================================================== Jun 4 17:23:00 Tower root: Jun 4 17:23:00 Tower root: Verifying package parted-3.2-x86_64-2.txz. Jun 4 17:23:00 Tower root: Installing package parted-3.2-x86_64-2.txz: Jun 4 17:23:00 Tower root: PACKAGE DESCRIPTION: Jun 4 17:23:00 Tower root: # parted (GNU disk partitioning tool) Jun 4 17:23:00 Tower root: # Jun 4 17:23:00 Tower root: # GNU Parted is a program for creating, destroying, resizing, checking Jun 4 17:23:00 Tower root: # and copying partitions, and the filesystems on them. This is useful Jun 4 17:23:00 Tower root: # for creating space for new operating systems, reorganizing disk Jun 4 17:23:00 Tower root: # usage, copying data between hard disks, and disk imaging. Jun 4 17:23:00 Tower root: # Jun 4 17:23:00 Tower root: Executing install script for parted-3.2-x86_64-2.txz. Jun 4 17:23:00 Tower root: Package parted-3.2-x86_64-2.txz installed. Jun 4 17:23:00 Tower root: plugin: skipping: /boot/config/plugins/unassigned.devices/packages/libnl-1.1.4-x86_64-1.txz already exists Jun 4 17:23:00 Tower root: plugin: running: /boot/config/plugins/unassigned.devices/packages/libnl-1.1.4-x86_64-1.txz Jun 4 17:23:00 Tower root: Jun 4 17:23:00 Tower root: +============================================================================== Jun 4 17:23:00 Tower root: | Installing new package /boot/config/plugins/unassigned.devices/packages/libnl-1.1.4-x86_64-1.txz Jun 4 17:23:00 Tower root: +============================================================================== Jun 4 17:23:00 Tower root: Jun 4 17:23:00 Tower root: Verifying package libnl-1.1.4-x86_64-1.txz. Jun 4 17:23:00 Tower root: Installing package libnl-1.1.4-x86_64-1.txz: Jun 4 17:23:00 Tower root: PACKAGE DESCRIPTION: Jun 4 17:23:00 Tower root: # libnl (netlink socket library) Jun 4 17:23:00 Tower root: # Jun 4 17:23:00 Tower root: # libnl is a library for applications dealing with netlink sockets. Jun 4 17:23:00 Tower root: # The library provides an interface for raw netlink messaging and Jun 4 17:23:00 Tower root: # various netlink family specific interfaces. Jun 4 17:23:00 Tower root: # Jun 4 17:23:00 Tower root: # Homepage: http://people.suug.ch/~tgr/libnl/ Jun 4 17:23:00 Tower root: # Jun 4 17:23:00 Tower root: # Jun 4 17:23:00 Tower root: Executing install script for libnl-1.1.4-x86_64-1.txz. Jun 4 17:23:01 Tower root: Package libnl-1.1.4-x86_64-1.txz installed. Jun 4 17:23:01 Tower root: plugin: creating: /tmp/start_unassigned_devices - from INLINE content Jun 4 17:23:01 Tower root: plugin: setting: /tmp/start_unassigned_devices - mode to 0770 Jun 4 17:23:01 Tower root: plugin: skipping: /boot/config/plugins/unassigned.devices/unassigned.devices.cfg already exists Jun 4 17:23:01 Tower root: plugin: skipping: /boot/config/plugins/unassigned.devices/samba_mount.cfg already exists Jun 4 17:23:01 Tower root: plugin: skipping: /boot/config/plugins/unassigned.devices/iso_mount.cfg already exists Jun 4 17:23:01 Tower root: plugin: creating: /tmp/unassigned.devices/smb-settings.conf - from INLINE content Jun 4 17:23:01 Tower root: plugin: creating: /tmp/unassigned.devices/config/smb-extra.conf - from INLINE content Jun 4 17:23:01 Tower root: plugin: creating: /tmp/unassigned.devices/add-smb-extra - from INLINE content Jun 4 17:23:01 Tower root: plugin: setting: /tmp/unassigned.devices/add-smb-extra - mode to 0770 Jun 4 17:23:01 Tower root: plugin: creating: /tmp/unassigned.devices/remove-smb-extra - from INLINE content Jun 4 17:23:01 Tower root: plugin: setting: /tmp/unassigned.devices/remove-smb-extra - mode to 0770 Jun 4 17:23:01 Tower root: plugin: running: anonymous Jun 4 17:23:01 Tower root: Jun 4 17:23:01 Tower root: ----------------------------------------------------------- Jun 4 17:23:01 Tower root: unassigned.devices has been installed. Jun 4 17:23:01 Tower root: This plugin requires Dynamix webGui to operate Jun 4 17:23:01 Tower root: Copyright 2015, gfjardim Jun 4 17:23:01 Tower root: Copyright 2016-2019, dlandon Jun 4 17:23:01 Tower root: Version: 2019.05.20 Jun 4 17:23:01 Tower root: ----------------------------------------------------------- Jun 4 17:23:01 Tower root: Jun 4 17:23:01 Tower root: plugin: installed Jun 4 17:23:01 Tower root: Starting go script Jun 4 17:23:01 Tower root: Starting emhttpd Jun 4 17:23:01 Tower emhttpd: Unraid(tm) System Management Utility version 6.7.0 Jun 4 17:23:01 Tower emhttpd: Copyright (C) 2005-2019, Lime Technology, Inc. Jun 4 17:23:01 Tower emhttpd: shcmd (6): /usr/local/emhttp/webGui/scripts/update_access Jun 4 17:23:01 Tower sshd[1504]: Received signal 15; terminating. Jun 4 17:23:02 Tower sshd[3823]: Server listening on 0.0.0.0 port 22. Jun 4 17:23:02 Tower sshd[3823]: Server listening on :: port 22. Jun 4 17:23:03 Tower emhttpd: shcmd (9): modprobe md-mod super=/boot/config/super.dat Jun 4 17:23:03 Tower kernel: md: unRAID driver 2.9.7 installed Jun 4 17:23:03 Tower emhttpd: Trial key detected, GUID: 0781-5571-2000-070312123462 FILE: /boot/config/Trial.key Jun 4 17:23:03 Tower emhttpd: Device inventory: Jun 4 17:23:03 Tower emhttpd: ST3500630AS_9QG10R36 (sdd) 512 976773168 Jun 4 17:23:03 Tower emhttpd: OCZ-AGILITY3_OCZ-C62QZNQ8SO394167 (sde) 512 234441648 Jun 4 17:23:03 Tower emhttpd: WDC_WD10EUCX-73YZ1Y0_WD-WCC0T0762883 (sdb) 512 1953525168 Jun 4 17:23:03 Tower emhttpd: WDC_WD10EUCX-73YZ1Y0_WD-WCC0T0761641 (sdc) 512 1953525168 Jun 4 17:23:03 Tower emhttpd: SanDisk_Cruzer_Fit_4C532000070312123462-0:0 (sda) 512 31266816 Jun 4 17:23:03 Tower kernel: mdcmd (1): import 0 sdb 63 976762552 0 WDC_WD10EUCX-73YZ1Y0_WD-WCC0T0762883 Jun 4 17:23:03 Tower kernel: md: import disk0: (sdb) WDC_WD10EUCX-73YZ1Y0_WD-WCC0T0762883 size: 976762552 Jun 4 17:23:03 Tower kernel: mdcmd (2): import 1 sdc 64 976762552 0 WDC_WD10EUCX-73YZ1Y0_WD-WCC0T0761641 Jun 4 17:23:03 Tower kernel: md: import disk1: (sdc) WDC_WD10EUCX-73YZ1Y0_WD-WCC0T0761641 size: 976762552 Jun 4 17:23:03 Tower kernel: mdcmd (3): import 2 sdd 63 488386552 0 ST3500630AS_9QG10R36 Jun 4 17:23:03 Tower kernel: md: import disk2: (sdd) ST3500630AS_9QG10R36 size: 488386552 Jun 4 17:23:03 Tower kernel: mdcmd (4): import 3 Jun 4 17:23:03 Tower kernel: mdcmd (5): import 4 Jun 4 17:23:03 Tower kernel: mdcmd (6): import 5 Jun 4 17:23:03 Tower kernel: mdcmd (7): import 6 Jun 4 17:23:03 Tower kernel: mdcmd (8): import 7 Jun 4 17:23:03 Tower kernel: mdcmd (9): import 8 Jun 4 17:23:03 Tower kernel: mdcmd (10): import 9 Jun 4 17:23:03 Tower kernel: mdcmd (11): import 10 Jun 4 17:23:03 Tower kernel: mdcmd (12): import 11 Jun 4 17:23:03 Tower kernel: mdcmd (13): import 12 Jun 4 17:23:03 Tower kernel: mdcmd (14): import 13 Jun 4 17:23:03 Tower kernel: mdcmd (15): import 14 Jun 4 17:23:03 Tower kernel: mdcmd (16): import 15 Jun 4 17:23:03 Tower kernel: mdcmd (17): import 16 Jun 4 17:23:03 Tower kernel: mdcmd (18): import 17 Jun 4 17:23:03 Tower kernel: mdcmd (19): import 18 Jun 4 17:23:03 Tower kernel: mdcmd (20): import 19 Jun 4 17:23:03 Tower kernel: mdcmd (21): import 20 Jun 4 17:23:03 Tower kernel: mdcmd (22): import 21 Jun 4 17:23:03 Tower kernel: mdcmd (23): import 22 Jun 4 17:23:03 Tower kernel: mdcmd (24): import 23 Jun 4 17:23:03 Tower kernel: mdcmd (25): import 24 Jun 4 17:23:03 Tower kernel: mdcmd (26): import 25 Jun 4 17:23:03 Tower kernel: mdcmd (27): import 26 Jun 4 17:23:03 Tower kernel: mdcmd (28): import 27 Jun 4 17:23:03 Tower kernel: mdcmd (29): import 28 Jun 4 17:23:03 Tower kernel: mdcmd (30): import 29 Jun 4 17:23:03 Tower kernel: md: import_slot: 29 empty Jun 4 17:23:03 Tower emhttpd: import 30 cache device: no device Jun 4 17:23:03 Tower emhttpd: import flash device: sda Jun 4 17:23:03 Tower emhttpd: Starting services... Jun 4 17:23:03 Tower emhttpd: shcmd (12): /etc/rc.d/rc.samba restart Jun 4 17:23:05 Tower root: Starting Samba: /usr/sbin/nmbd -D Jun 4 17:23:06 Tower root: /usr/sbin/smbd -D Jun 4 17:23:06 Tower root: /usr/sbin/winbindd -D Jun 4 17:23:06 Tower emhttpd: shcmd (17): /etc/rc.d/rc.avahidaemon start Jun 4 17:23:06 Tower root: Starting Avahi mDNS/DNS-SD Daemon: /usr/sbin/avahi-daemon -D Jun 4 17:23:06 Tower avahi-daemon[3895]: Found user 'avahi' (UID 61) and group 'avahi' (GID 214). Jun 4 17:23:06 Tower avahi-daemon[3895]: Successfully dropped root privileges. Jun 4 17:23:06 Tower avahi-daemon[3895]: avahi-daemon 0.7 starting up. Jun 4 17:23:06 Tower avahi-daemon[3895]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns! Jun 4 17:23:06 Tower avahi-daemon[3895]: Successfully called chroot(). Jun 4 17:23:06 Tower avahi-daemon[3895]: Successfully dropped remaining capabilities. Jun 4 17:23:06 Tower avahi-daemon[3895]: Loading service file /services/sftp-ssh.service. Jun 4 17:23:06 Tower avahi-daemon[3895]: Loading service file /services/smb.service. Jun 4 17:23:06 Tower avahi-daemon[3895]: Loading service file /services/ssh.service. Jun 4 17:23:06 Tower avahi-daemon[3895]: Joining mDNS multicast group on interface br0.IPv6 with address fe80::1c79:6aff:fec0:7c24. Jun 4 17:23:06 Tower avahi-daemon[3895]: New relevant interface br0.IPv6 for mDNS. Jun 4 17:23:06 Tower avahi-daemon[3895]: Joining mDNS multicast group on interface br0.IPv4 with address 192.168.0.200. Jun 4 17:23:06 Tower avahi-daemon[3895]: New relevant interface br0.IPv4 for mDNS. Jun 4 17:23:06 Tower avahi-daemon[3895]: Joining mDNS multicast group on interface bond0.IPv6 with address fe80::1e1b:dff:fe4b:b683. Jun 4 17:23:06 Tower avahi-daemon[3895]: New relevant interface bond0.IPv6 for mDNS. Jun 4 17:23:06 Tower avahi-daemon[3895]: Network interface enumeration completed. Jun 4 17:23:06 Tower avahi-daemon[3895]: Registering new address record for fe80::1c79:6aff:fec0:7c24 on br0.*. Jun 4 17:23:06 Tower avahi-daemon[3895]: Registering new address record for 192.168.0.200 on br0.IPv4. Jun 4 17:23:06 Tower avahi-daemon[3895]: Registering new address record for fe80::1e1b:dff:fe4b:b683 on bond0.*. Jun 4 17:23:06 Tower emhttpd: shcmd (18): /etc/rc.d/rc.avahidnsconfd start Jun 4 17:23:06 Tower root: Starting Avahi mDNS/DNS-SD DNS Server Configuration Daemon: /usr/sbin/avahi-dnsconfd -D Jun 4 17:23:06 Tower avahi-dnsconfd[3906]: Successfully connected to Avahi daemon. Jun 4 17:23:06 Tower emhttpd: shcmd (23): /etc/rc.d/rc.php-fpm start Jun 4 17:23:06 Tower root: Starting php-fpm done Jun 4 17:23:06 Tower emhttpd: shcmd (24): /etc/rc.d/rc.nginx start Jun 4 17:23:06 Tower root: Starting Nginx server daemon... Jun 4 17:23:06 Tower emhttpd: shcmd (25): /usr/local/sbin/set_ncq sdb 1 Jun 4 17:23:06 Tower kernel: mdcmd (31): set md_num_stripes 1280 Jun 4 17:23:06 Tower kernel: mdcmd (32): set md_sync_window 384 Jun 4 17:23:06 Tower kernel: mdcmd (33): set md_sync_thresh 192 Jun 4 17:23:06 Tower kernel: mdcmd (34): set md_write_method Jun 4 17:23:06 Tower kernel: mdcmd (35): set spinup_group 0 0 Jun 4 17:23:06 Tower kernel: mdcmd (36): set spinup_group 1 0 Jun 4 17:23:06 Tower kernel: mdcmd (37): set spinup_group 2 0 Jun 4 17:23:06 Tower root: set_ncq: setting sdb queue_depth to 1 Jun 4 17:23:06 Tower emhttpd: shcmd (26): echo 128 > /sys/block/sdb/queue/nr_requests Jun 4 17:23:06 Tower emhttpd: shcmd (27): /usr/local/sbin/set_ncq sdc 1 Jun 4 17:23:06 Tower root: set_ncq: setting sdc queue_depth to 1 Jun 4 17:23:06 Tower emhttpd: shcmd (28): echo 128 > /sys/block/sdc/queue/nr_requests Jun 4 17:23:06 Tower emhttpd: shcmd (29): /usr/local/sbin/set_ncq sdd 1 Jun 4 17:23:06 Tower root: set_ncq: setting sdd queue_depth to 1 Jun 4 17:23:06 Tower emhttpd: shcmd (30): echo 128 > /sys/block/sdd/queue/nr_requests Jun 4 17:23:06 Tower kernel: mdcmd (38): start STOPPED Jun 4 17:23:06 Tower kernel: unraid: allocating 20860K for 1280 stripes (4 disks) Jun 4 17:23:06 Tower kernel: md1: running, size: 976762552 blocks Jun 4 17:23:06 Tower kernel: md2: running, size: 488386552 blocks Jun 4 17:23:06 Tower emhttpd: shcmd (31): udevadm settle Jun 4 17:23:06 Tower emhttpd: Autostart enabled Jun 4 17:23:06 Tower root: Starting diskload Jun 4 17:23:06 Tower emhttpd: Mounting disks... Jun 4 17:23:06 Tower emhttpd: shcmd (34): /sbin/btrfs device scan Jun 4 17:23:06 Tower kernel: scsi_io_completion_action: 15 callbacks suppressed Jun 4 17:23:06 Tower kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Jun 4 17:23:06 Tower kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] Jun 4 17:23:06 Tower kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 Jun 4 17:23:06 Tower kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 01 dd 14 20 00 00 01 00 Jun 4 17:23:06 Tower kernel: print_req_error: 15 callbacks suppressed Jun 4 17:23:06 Tower kernel: print_req_error: critical medium error, dev sda, sector 31265824 Jun 4 17:23:06 Tower kernel: buffer_io_error: 20 callbacks suppressed Jun 4 17:23:06 Tower kernel: Buffer I/O error on dev sda1, logical block 31263776, async page read Jun 4 17:23:06 Tower kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Jun 4 17:23:06 Tower kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] Jun 4 17:23:06 Tower kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 Jun 4 17:23:06 Tower kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 01 dd 14 21 00 00 01 00 Jun 4 17:23:06 Tower kernel: print_req_error: critical medium error, dev sda, sector 31265825 Jun 4 17:23:06 Tower kernel: Buffer I/O error on dev sda1, logical block 31263777, async page read Jun 4 17:23:06 Tower kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Jun 4 17:23:06 Tower kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] Jun 4 17:23:06 Tower kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 Jun 4 17:23:06 Tower kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 01 dd 14 22 00 00 06 00 Jun 4 17:23:06 Tower kernel: print_req_error: critical medium error, dev sda, sector 31265826 Jun 4 17:23:06 Tower kernel: Buffer I/O error on dev sda1, logical block 31263778, async page read Jun 4 17:23:06 Tower kernel: Buffer I/O error on dev sda1, logical block 31263779, async page read Jun 4 17:23:06 Tower kernel: Buffer I/O error on dev sda1, logical block 31263780, async page read Jun 4 17:23:06 Tower kernel: Buffer I/O error on dev sda1, logical block 31263781, async page read Jun 4 17:23:06 Tower kernel: Buffer I/O error on dev sda1, logical block 31263782, async page read Jun 4 17:23:06 Tower kernel: Buffer I/O error on dev sda1, logical block 31263783, async page read Jun 4 17:23:06 Tower root: Scanning for Btrfs filesystems Jun 4 17:23:06 Tower emhttpd: shcmd (35): mkdir -p /mnt/disk1 Jun 4 17:23:06 Tower emhttpd: shcmd (36): mount -t reiserfs -o noatime,nodiratime /dev/md1 /mnt/disk1 Jun 4 17:23:06 Tower kernel: REISERFS (device md1): found reiserfs format "3.6" with standard journal Jun 4 17:23:06 Tower kernel: REISERFS (device md1): using ordered data mode Jun 4 17:23:06 Tower kernel: reiserfs: using flush barriers Jun 4 17:23:06 Tower avahi-daemon[3895]: Server startup complete. Host name is Tower.local. Local service cookie is 2889243169. Jun 4 17:23:06 Tower kernel: REISERFS (device md1): journal params: device md1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Jun 4 17:23:06 Tower kernel: REISERFS (device md1): checking transaction log (md1) Jun 4 17:23:07 Tower kernel: REISERFS (device md1): Using r5 hash to sort names Jun 4 17:23:07 Tower root: error: /webGui/include/ProcessStatus.php: wrong csrf_token Jun 4 17:23:07 Tower emhttpd: shcmd (37): mount -t reiserfs -o remount,user_xattr,acl,noatime,nodiratime /dev/md1 /mnt/disk1 Jun 4 17:23:07 Tower emhttpd: reiserfs: resizing /mnt/disk1 Jun 4 17:23:07 Tower emhttpd: shcmd (38): mkdir -p /mnt/disk2 Jun 4 17:23:07 Tower emhttpd: shcmd (39): mount -t reiserfs -o noatime,nodiratime /dev/md2 /mnt/disk2 Jun 4 17:23:07 Tower kernel: REISERFS (device md2): found reiserfs format "3.6" with standard journal Jun 4 17:23:07 Tower kernel: REISERFS (device md2): using ordered data mode Jun 4 17:23:07 Tower kernel: reiserfs: using flush barriers Jun 4 17:23:07 Tower kernel: REISERFS (device md2): journal params: device md2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Jun 4 17:23:07 Tower kernel: REISERFS (device md2): checking transaction log (md2) Jun 4 17:23:07 Tower kernel: REISERFS (device md2): Using r5 hash to sort names Jun 4 17:23:07 Tower emhttpd: shcmd (40): mount -t reiserfs -o remount,user_xattr,acl,noatime,nodiratime /dev/md2 /mnt/disk2 Jun 4 17:23:07 Tower avahi-daemon[3895]: Service "Tower" (/services/ssh.service) successfully established. Jun 4 17:23:07 Tower avahi-daemon[3895]: Service "Tower" (/services/smb.service) successfully established. Jun 4 17:23:07 Tower avahi-daemon[3895]: Service "Tower" (/services/sftp-ssh.service) successfully established. Jun 4 17:23:07 Tower emhttpd: reiserfs: resizing /mnt/disk2 Jun 4 17:23:08 Tower emhttpd: shcmd (41): sync Jun 4 17:23:08 Tower emhttpd: shcmd (42): mkdir /mnt/user Jun 4 17:23:08 Tower emhttpd: shcmd (43): /usr/local/sbin/shfs /mnt/user -disks 6 -o noatime,big_writes,allow_other -o remember=0 |& logger Jun 4 17:23:08 Tower shfs: stderr redirected to syslog Jun 4 17:23:08 Tower emhttpd: shcmd (45): /usr/local/sbin/update_cron Jun 4 17:23:08 Tower unassigned.devices: Mounting 'Auto Mount' Devices... Jun 4 17:23:08 Tower unassigned.devices: Adding disk '/dev/sde1'... Jun 4 17:23:08 Tower unassigned.devices: Mount drive command: /sbin/mount -t ntfs -o auto,async,noatime,nodiratime,nodev,nosuid,umask=000 '/dev/sde1' '/mnt/disks/System_Reserved' Jun 4 17:23:08 Tower ntfs-3g[4182]: Version 2017.3.23 integrated FUSE 27 Jun 4 17:23:08 Tower ntfs-3g[4182]: Mounted /dev/sde1 (Read-Only, label "System Reserved", NTFS 3.1) Jun 4 17:23:08 Tower ntfs-3g[4182]: Cmdline options: rw,noatime,nodiratime,nodev,nosuid,umask=000 Jun 4 17:23:08 Tower ntfs-3g[4182]: Mount options: rw,nodiratime,nodev,nosuid,allow_other,nonempty,noatime,ro,default_permissions,fsname=/dev/sde1,blkdev,blksize=4096 Jun 4 17:23:08 Tower ntfs-3g[4182]: Global ownership and permissions enforced, configuration type 1 Jun 4 17:23:08 Tower unassigned.devices: Mount error: The disk contains an unclean file system (0, 0). Metadata kept in Windows cache, refused to mount. Falling back to read-only mount because the NTFS partition is in an unsafe state. Please resume and shutdown Windows fully (no hibernation or fast restarting.) Jun 4 17:23:08 Tower unassigned.devices: Successfully mounted '/dev/sde1' on '/mnt/disks/System_Reserved'. Jun 4 17:23:08 Tower unassigned.devices: Disk with serial 'OCZ-AGILITY3_OCZ-C62QZNQ8SO394167', mountpoint 'System_Reserved' is not set as sharable and will not be shared... Jun 4 17:23:08 Tower unassigned.devices: Adding disk '/dev/sde2'... Jun 4 17:23:08 Tower unassigned.devices: Mount drive command: /sbin/mount -t ntfs -o auto,async,noatime,nodiratime,nodev,nosuid,umask=000 '/dev/sde2' '/mnt/disks/OCZ-AGILITY3_OCZ-C62QZNQ8SO394167-part2' Jun 4 17:23:08 Tower ntfs-3g[4221]: Version 2017.3.23 integrated FUSE 27 Jun 4 17:23:08 Tower ntfs-3g[4221]: Mounted /dev/sde2 (Read-Only, label "", NTFS 3.1) Jun 4 17:23:08 Tower ntfs-3g[4221]: Cmdline options: rw,noatime,nodiratime,nodev,nosuid,umask=000 Jun 4 17:23:08 Tower ntfs-3g[4221]: Mount options: rw,nodiratime,nodev,nosuid,allow_other,nonempty,noatime,ro,default_permissions,fsname=/dev/sde2,blkdev,blksize=4096 Jun 4 17:23:08 Tower ntfs-3g[4221]: Global ownership and permissions enforced, configuration type 1 Jun 4 17:23:08 Tower unassigned.devices: Mount error: The disk contains an unclean file system (0, 0). Metadata kept in Windows cache, refused to mount. Falling back to read-only mount because the NTFS partition is in an unsafe state. Please resume and shutdown Windows fully (no hibernation or fast restarting.) Jun 4 17:23:08 Tower unassigned.devices: Successfully mounted '/dev/sde2' on '/mnt/disks/OCZ-AGILITY3_OCZ-C62QZNQ8SO394167-part2'. Jun 4 17:23:08 Tower unassigned.devices: Defining share 'OCZ-AGILITY3_OCZ-C62QZNQ8SO394167-part2' with file '/etc/samba/unassigned-shares/OCZ-AGILITY3_OCZ-C62QZNQ8SO394167-part2.conf' Jun 4 17:23:08 Tower unassigned.devices: Adding share 'OCZ-AGILITY3_OCZ-C62QZNQ8SO394167-part2' to '/tmp/unassigned.devices/smb-settings.conf' Jun 4 17:23:08 Tower unassigned.devices: Reloading Samba configuration... Jun 4 17:23:08 Tower unassigned.devices: Directory '/mnt/disks/OCZ-AGILITY3_OCZ-C62QZNQ8SO394167-part2' shared successfully. Jun 4 17:23:08 Tower unassigned.devices: Adding disk '/dev/sde3'... Jun 4 17:23:08 Tower unassigned.devices: Mount drive command: /sbin/mount -t ntfs -o auto,async,noatime,nodiratime,nodev,nosuid,umask=000 '/dev/sde3' '/mnt/disks/OCZ-AGILITY3_OCZ-C62QZNQ8SO394167-part3' Jun 4 17:23:08 Tower ntfs-3g[4263]: Version 2017.3.23 integrated FUSE 27 Jun 4 17:23:08 Tower ntfs-3g[4263]: Mounted /dev/sde3 (Read-Only, label "", NTFS 3.1) Jun 4 17:23:08 Tower ntfs-3g[4263]: Cmdline options: rw,noatime,nodiratime,nodev,nosuid,umask=000 Jun 4 17:23:08 Tower ntfs-3g[4263]: Mount options: rw,nodiratime,nodev,nosuid,allow_other,nonempty,noatime,ro,default_permissions,fsname=/dev/sde3,blkdev,blksize=4096 Jun 4 17:23:08 Tower ntfs-3g[4263]: Global ownership and permissions enforced, configuration type 1 Jun 4 17:23:08 Tower unassigned.devices: Mount error: The disk contains an unclean file system (0, 0). Metadata kept in Windows cache, refused to mount. Falling back to read-only mount because the NTFS partition is in an unsafe state. Please resume and shutdown Windows fully (no hibernation or fast restarting.) Jun 4 17:23:08 Tower unassigned.devices: Successfully mounted '/dev/sde3' on '/mnt/disks/OCZ-AGILITY3_OCZ-C62QZNQ8SO394167-part3'. Jun 4 17:23:08 Tower unassigned.devices: Disk with serial 'OCZ-AGILITY3_OCZ-C62QZNQ8SO394167', mountpoint 'OCZ-AGILITY3_OCZ-C62QZNQ8SO394167-part3' is not set as sharable and will not be shared... Jun 4 17:23:08 Tower emhttpd: Starting services... Jun 4 17:23:08 Tower emhttpd: shcmd (47): /etc/rc.d/rc.samba restart Jun 4 17:23:10 Tower root: Starting Samba: /usr/sbin/nmbd -D Jun 4 17:23:10 Tower root: /usr/sbin/smbd -D Jun 4 17:23:10 Tower root: /usr/sbin/winbindd -D Jun 4 17:23:11 Tower emhttpd: shcmd (61): /usr/local/sbin/mount_image '/mnt/user/system/docker/docker.img' /var/lib/docker 20 Jun 4 17:23:11 Tower kernel: BTRFS: device fsid 15a9ae4a-fec0-4b61-9258-c298d4e0fef2 devid 1 transid 10959 /dev/loop2 Jun 4 17:23:11 Tower kernel: BTRFS info (device loop2): disk space caching is enabled Jun 4 17:23:11 Tower kernel: BTRFS info (device loop2): has skinny extents Jun 4 17:23:11 Tower kernel: BTRFS info (device loop2): bdev /dev/loop2 errs: wr 3, rd 84, flush 0, corrupt 0, gen 0 Jun 4 17:23:11 Tower root: Resize '/var/lib/docker' of 'max' Jun 4 17:23:11 Tower kernel: BTRFS info (device loop2): new size for /dev/loop2 is 21474836480 Jun 4 17:23:11 Tower emhttpd: shcmd (63): /etc/rc.d/rc.docker start Jun 4 17:23:11 Tower root: starting dockerd ... Jun 4 17:23:13 Tower avahi-daemon[3895]: Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1. Jun 4 17:23:13 Tower avahi-daemon[3895]: New relevant interface docker0.IPv4 for mDNS. Jun 4 17:23:13 Tower avahi-daemon[3895]: Registering new address record for 172.17.0.1 on docker0.IPv4. Jun 4 17:23:13 Tower kernel: IPv6: ADDRCONF(NETDEV_UP): docker0: link is not ready Jun 4 17:23:17 Tower emhttpd: shcmd (77): /usr/local/sbin/mount_image '/mnt/user/system/libvirt/libvirt.img' /etc/libvirt 1Jun 4 17:23:17 Tower kernel: BTRFS: device fsid 5b439a0b-b1ad-410d-b49d-95c30d774cac devid 1 transid 85 /dev/loop3 Jun 4 17:23:17 Tower kernel: BTRFS info (device loop3): disk space caching is enabled Jun 4 17:23:17 Tower kernel: BTRFS info (device loop3): has skinny extents Jun 4 17:23:17 Tower kernel: BTRFS info (device loop3): new size for /dev/loop3 is 1073741824 Jun 4 17:23:17 Tower root: Resize '/etc/libvirt' of 'max' Jun 4 17:23:17 Tower emhttpd: shcmd (79): /etc/rc.d/rc.libvirt start Jun 4 17:23:17 Tower root: Starting virtlockd... Jun 4 17:23:18 Tower root: Starting virtlogd... Jun 4 17:23:18 Tower useradd[4908]: new user: name=tss, UID=59, GID=59, home=/, shell=/bin/false Jun 4 17:23:18 Tower root: Starting libvirtd... Jun 4 17:23:18 Tower kernel: tun: Universal TUN/TAP device driver, 1.6 Jun 4 17:23:18 Tower emhttpd: nothing to sync Jun 4 17:23:18 Tower unassigned.devices: Mounting 'Auto Mount' Remote Shares... Jun 4 17:23:19 Tower kernel: virbr0: port 1(virbr0-nic) entered blocking state Jun 4 17:23:19 Tower kernel: virbr0: port 1(virbr0-nic) entered disabled state Jun 4 17:23:19 Tower kernel: device virbr0-nic entered promiscuous mode Jun 4 17:23:19 Tower avahi-daemon[3895]: Joining mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. Jun 4 17:23:19 Tower avahi-daemon[3895]: New relevant interface virbr0.IPv4 for mDNS. Jun 4 17:23:19 Tower avahi-daemon[3895]: Registering new address record for 192.168.122.1 on virbr0.IPv4. Jun 4 17:23:19 Tower kernel: virbr0: port 1(virbr0-nic) entered blocking state Jun 4 17:23:19 Tower kernel: virbr0: port 1(virbr0-nic) entered listening state Jun 4 17:23:19 Tower dnsmasq[5194]: started, version 2.80 cachesize 150 Jun 4 17:23:19 Tower dnsmasq[5194]: compile time options: IPv6 GNU-getopt no-DBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth no-DNSSEC loop-detect inotify dumpfile Jun 4 17:23:19 Tower dnsmasq-dhcp[5194]: DHCP, IP range 192.168.122.2 -- 192.168.122.254, lease time 1h Jun 4 17:23:19 Tower dnsmasq-dhcp[5194]: DHCP, sockets bound exclusively to interface virbr0 Jun 4 17:23:19 Tower dnsmasq[5194]: reading /etc/resolv.conf Jun 4 17:23:19 Tower dnsmasq[5194]: using nameserver 192.168.0.1#53 Jun 4 17:23:19 Tower dnsmasq[5194]: using nameserver 4.2.2.2#53 Jun 4 17:23:19 Tower dnsmasq[5194]: using nameserver 8.8.8.8#53 Jun 4 17:23:19 Tower dnsmasq[5194]: read /etc/hosts - 2 addresses Jun 4 17:23:19 Tower dnsmasq[5194]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses Jun 4 17:23:19 Tower dnsmasq-dhcp[5194]: read /var/lib/libvirt/dnsmasq/default.hostsfile Jun 4 17:23:19 Tower kernel: virbr0: port 1(virbr0-nic) entered disabled state Jun 4 17:23:20 Tower rc.docker: PlexMediaServer: started succesfully! Jun 4 17:24:18 Tower kernel: vfio-pci 0000:05:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=noneJun 4 17:24:19 Tower kernel: br0: port 2(vnet0) entered blocking state Jun 4 17:24:19 Tower kernel: br0: port 2(vnet0) entered disabled state Jun 4 17:24:19 Tower kernel: device vnet0 entered promiscuous mode Jun 4 17:24:19 Tower kernel: br0: port 2(vnet0) entered blocking state Jun 4 17:24:19 Tower kernel: br0: port 2(vnet0) entered forwarding state Jun 4 17:24:19 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:19 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:19 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:19 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:19 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:19 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:20 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:20 Tower avahi-daemon[3895]: Joining mDNS multicast group on interface vnet0.IPv6 with address fe80::fc54:ff:fec5:578. Jun 4 17:24:20 Tower avahi-daemon[3895]: New relevant interface vnet0.IPv6 for mDNS. Jun 4 17:24:20 Tower avahi-daemon[3895]: Registering new address record for fe80::fc54:ff:fec5:578 on vnet0.*. Jun 4 17:24:22 Tower kernel: vfio-pci 0000:05:00.0: enabling device (0000 -> 0003) Jun 4 17:24:22 Tower kernel: vfio_ecap_init: 0000:05:00.0 hiding ecap 0x19@0x270 Jun 4 17:24:22 Tower kernel: vfio_ecap_init: 0000:05:00.0 hiding ecap 0x1b@0x2d0 Jun 4 17:24:22 Tower kernel: vfio_ecap_init: 0000:05:00.0 hiding ecap 0x1e@0x370 Jun 4 17:24:22 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:22 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:22 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:22 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:23 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:23 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:23 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:23 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:23 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:23 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:23 Tower kernel: vfio-pci 0000:00:14.2: enabling device (0000 -> 0002) Jun 4 17:24:24 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:24 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:24 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:25 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:25 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:25 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:25 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:25 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:26 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:26 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:26 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:27 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:27 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:27 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:27 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:27 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:27 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:27 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:27 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:28 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:28 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:28 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:28 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:28 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:29 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:29 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:29 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:29 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:29 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:29 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:29 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:29 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:30 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:30 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:30 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:30 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:30 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:30 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:30 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:30 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:30 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:31 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:31 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:31 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:31 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:31 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:31 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:31 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:31 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:31 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:32 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:32 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:32 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:32 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:32 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:32 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:32 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:32 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:33 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:33 Tower acpid: input device has been disconnected, fd 4 Jun 4 17:24:33 Tower acpid: input device has been disconnected, fd 5 Jun 4 17:24:34 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:34 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:34 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:34 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:34 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:35 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:35 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:35 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:35 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:35 Tower kernel: usb 7-4: reset full-speed USB device number 2 using ohci-pci Jun 4 17:24:35 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:35 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:36 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:36 Tower kernel: usb 7-4: reset full-speed USB device number 2 using ohci-pci Jun 4 17:24:36 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:36 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:36 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:36 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:37 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:37 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:37 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:37 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:38 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:38 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:38 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:38 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:38 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:38 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:39 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:39 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:39 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:39 Tower kernel: AMD-Vi: Completion-Wait loop timed out Jun 4 17:24:39 Tower kernel: AMD-Vi: Completion-Wait loop timed out I've scoured the internet and it appears these boards lose USB capabilities when passing through the GPU. If I understand it all correctly.. playing with the IOMMU groupings wont even help me. Any other thoughts/recommendations? Quote Link to comment
jasonmcroy Posted June 13, 2019 Author Share Posted June 13, 2019 Just as a follow up on this thread in case someone runs into my same issue I originally posted about regarding iommu and issues with 3.0 usb working. As Taddeusz posted above - adding "iommu=soft" to the syslinux.cfg file does the trick! My internet, usb 2.0 and usb 3.0 are all working. Quote Link to comment
Wurztha Posted June 28, 2020 Share Posted June 28, 2020 Just wanted to share my experience on this and what worked for me in case anyone comes across this. I tried the fixes of adding 'iommu=pt' & 'iommu=soft' but they did not help unfortunately. The 'soft' made the GPU's unable to passthrough as they do not show and 'pt' did the same as no flag but wasn't quite as bad with the console spamming. The fix for me was to use 'pci=noats' so hopefully this will help others! Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.