Cisnet

Members
  • Posts

    19
  • Joined

  • Last visited

Everything posted by Cisnet

  1. Noticed my unraid randomly freeze over night after being on for a while. Have to shut the whole PC down. I looked in the logs and saw a bunch of these errors. Mar 22 17:04:20 Tower kernel: pcieport 0000:00:03.2: [12] Replay Timer Timeout Mar 22 17:04:21 Tower kernel: pcieport 0000:00:03.2: AER: Corrected error received: 0000:00:03.2 Mar 22 17:04:21 Tower kernel: pcieport 0000:00:03.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Mar 22 17:04:21 Tower kernel: pcieport 0000:00:03.2: device [8086:2f0a] error status/mask=00000040/00002000 Mar 22 17:04:21 Tower kernel: pcieport 0000:00:03.2: [ 6] Bad TLP Mar 22 17:04:21 Tower kernel: pcieport 0000:00:03.2: AER: Corrected error received: 0000:00:03.2 Mar 22 17:04:21 Tower kernel: pcieport 0000:00:03.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Mar 22 17:04:21 Tower kernel: pcieport 0000:00:03.2: device [8086:2f0a] error status/mask=00000080/00002000 Mar 22 17:04:21 Tower kernel: pcieport 0000:00:03.2: [ 7] Bad DLLP Mar 22 17:04:22 Tower kernel: pcieport 0000:00:03.2: AER: Multiple Corrected error received: 0000:00:03.2 Mar 22 17:04:22 Tower kernel: pcieport 0000:00:03.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Mar 22 17:04:22 Tower kernel: pcieport 0000:00:03.2: device [8086:2f0a] error status/mask=00000040/00002000 Mar 22 17:04:22 Tower kernel: pcieport 0000:00:03.2: [ 6] Bad TLP Mar 22 17:05:23 Tower kernel: pcieport 0000:00:03.0: AER: Corrected error received: 0000:00:03.0 Mar 22 17:05:23 Tower kernel: pcieport 0000:00:03.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) Mar 22 17:05:23 Tower kernel: pcieport 0000:00:03.0: device [8086:2f08] error status/mask=00001000/00002000 Mar 22 17:05:23 Tower kernel: pcieport 0000:00:03.0: [12] Replay Timer Timeout Mar 22 17:05:47 Tower kernel: pcieport 0000:00:03.0: AER: Corrected error received: 0000:00:03.0 Mar 22 17:05:47 Tower kernel: pcieport 0000:00:03.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) Mar 22 17:05:47 Tower kernel: pcieport 0000:00:03.0: device [8086:2f08] error status/mask=00001000/00002000 Mar 22 17:05:47 Tower kernel: pcieport 0000:00:03.0: [12] Replay Timer Timeout Mar 22 17:06:15 Tower kernel: pcieport 0000:00:03.2: AER: Corrected error received: 0000:00:03.2 Mar 22 17:06:15 Tower kernel: pcieport 0000:00:03.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Mar 22 17:06:15 Tower kernel: pcieport 0000:00:03.2: device [8086:2f0a] error status/mask=00000080/00002000 Mar 22 17:06:15 Tower kernel: pcieport 0000:00:03.2: [ 7] Bad DLLP Mar 22 17:06:16 Tower kernel: pcieport 0000:00:03.2: AER: Corrected error received: 0000:00:03.2 Mar 22 17:06:16 Tower kernel: pcieport 0000:00:03.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) Mar 22 17:06:16 Tower kernel: pcieport 0000:00:03.2: device [8086:2f0a] error status/mask=00001000/00002000 Mar 22 17:06:16 Tower kernel: pcieport 0000:00:03.2: [12] Replay Timer Timeout Mar 22 17:06:32 Tower kernel: pcieport 0000:00:03.2: AER: Corrected error received: 0000:00:03.2 Mar 22 17:06:32 Tower kernel: pcieport 0000:00:03.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Mar 22 17:06:32 Tower kernel: pcieport 0000:00:03.2: device [8086:2f0a] error status/mask=00000040/00002000 Mar 22 17:06:32 Tower kernel: pcieport 0000:00:03.2: [ 6] Bad TLP Mar 22 17:07:13 Tower kernel: pcieport 0000:00:03.0: AER: Corrected error received: 0000:00:03.0 Mar 22 17:07:13 Tower kernel: pcieport 0000:00:03.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) Mar 22 17:07:13 Tower kernel: pcieport 0000:00:03.0: device [8086:2f08] error status/mask=00001000/00002000 Mar 22 17:07:13 Tower kernel: pcieport 0000:00:03.0: [12] Replay Timer Timeout Mar 22 17:07:55 Tower ntpd[2703]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Any ideas? tower-diagnostics-20190322-1712.zip
  2. This seems likely but it persisted even after reboot
  3. Thanks sorry for the late reply as I just tested it. It works now on 6.6.7!
  4. I ended up resetting the bios, and now everything is back to normal. Not sure what happened here, but I'll leave this open for you guys to look at.
  5. Woke up in the morning to find an unraid error stating the notifications were disabled. The VMs are on and running, but unraid shows them disabled. I cannot seem to access shares, or do anything that I can think of to fix this other than reboot. I checked the logs and they are spammed over and over with this. ErrorWarningSystemArrayLogin Mar 14 15:34:39 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/nextcloud.cfg Mar 14 15:34:39 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/syncbackup.cfg Mar 14 15:34:39 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/system.cfg Mar 14 15:34:39 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/vdisks.cfg Mar 14 15:34:39 Tower emhttpd: Starting services... Mar 14 15:34:39 Tower kernel: fat__get_entry: 310 callbacks suppressed Mar 14 15:34:39 Tower kernel: FAT-fs (sda1): Directory bread(block 16384) failed Mar 14 15:34:39 Tower kernel: FAT-fs (sda1): Directory bread(block 16385) failed Mar 14 15:34:39 Tower kernel: FAT-fs (sda1): Directory bread(block 16386) failed Mar 14 15:34:39 Tower kernel: FAT-fs (sda1): Directory bread(block 16387) failed Mar 14 15:34:39 Tower kernel: FAT-fs (sda1): Directory bread(block 16388) failed Mar 14 15:34:39 Tower kernel: FAT-fs (sda1): Directory bread(block 16389) failed Mar 14 15:34:39 Tower kernel: FAT-fs (sda1): Directory bread(block 16390) failed Mar 14 15:34:39 Tower kernel: FAT-fs (sda1): Directory bread(block 16391) failed Mar 14 15:34:39 Tower kernel: FAT-fs (sda1): Directory bread(block 16392) failed Mar 14 15:34:39 Tower kernel: FAT-fs (sda1): Directory bread(block 16393) failed Mar 14 15:34:40 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/appdata.cfg Mar 14 15:34:40 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/backup.cfg Mar 14 15:34:40 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/domains.cfg Mar 14 15:34:40 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/gamedisk.cfg Mar 14 15:34:40 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/isos.cfg Mar 14 15:34:40 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/keys.cfg Mar 14 15:34:40 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/nextcloud.cfg Mar 14 15:34:40 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/syncbackup.cfg Mar 14 15:34:40 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/system.cfg Mar 14 15:34:40 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/vdisks.cfg Mar 14 15:34:40 Tower emhttpd: Starting services... Mar 14 15:34:41 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/appdata.cfg Mar 14 15:34:41 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/backup.cfg Mar 14 15:34:41 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/domains.cfg Mar 14 15:34:41 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/gamedisk.cfg Mar 14 15:34:41 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/isos.cfg Mar 14 15:34:41 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/keys.cfg Mar 14 15:34:41 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/nextcloud.cfg Mar 14 15:34:41 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/syncbackup.cfg Mar 14 15:34:41 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/system.cfg Mar 14 15:34:41 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/vdisks.cfg Mar 14 15:34:41 Tower emhttpd: Starting services... Mar 14 15:34:42 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/appdata.cfg Mar 14 15:34:42 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/backup.cfg Mar 14 15:34:42 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/domains.cfg Mar 14 15:34:42 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/gamedisk.cfg Mar 14 15:34:42 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/isos.cfg Mar 14 15:34:42 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/keys.cfg Mar 14 15:34:42 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/nextcloud.cfg Mar 14 15:34:42 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/syncbackup.cfg Mar 14 15:34:42 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/system.cfg Mar 14 15:34:42 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/vdisks.cfg Mar 14 15:34:42 Tower emhttpd: Starting services... Mar 14 15:34:43 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/appdata.cfg Mar 14 15:34:43 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/backup.cfg Mar 14 15:34:43 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/domains.cfg Mar 14 15:34:43 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/gamedisk.cfg Mar 14 15:34:43 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/isos.cfg Mar 14 15:34:43 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/keys.cfg Mar 14 15:34:43 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/nextcloud.cfg Mar 14 15:34:43 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/syncbackup.cfg Mar 14 15:34:43 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/system.cfg Mar 14 15:34:43 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/vdisks.cfg Mar 14 15:34:43 Tower emhttpd: Starting services... Mar 14 15:34:44 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/appdata.cfg Mar 14 15:34:44 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/backup.cfg Mar 14 15:34:44 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/domains.cfg Mar 14 15:34:44 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/gamedisk.cfg Mar 14 15:34:44 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/isos.cfg Mar 14 15:34:44 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/keys.cfg Mar 14 15:34:44 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/nextcloud.cfg Mar 14 15:34:44 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/syncbackup.cfg Mar 14 15:34:44 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/system.cfg Mar 14 15:34:44 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/vdisks.cfg Mar 14 15:34:44 Tower emhttpd: Starting services... Mar 14 15:34:44 Tower kernel: fat__get_entry: 310 callbacks suppressed Mar 14 15:34:44 Tower kernel: FAT-fs (sda1): Directory bread(block 16384) failed Mar 14 15:34:44 Tower kernel: FAT-fs (sda1): Directory bread(block 16385) failed Mar 14 15:34:44 Tower kernel: FAT-fs (sda1): Directory bread(block 16386) failed Mar 14 15:34:44 Tower kernel: FAT-fs (sda1): Directory bread(block 16387) failed Mar 14 15:34:44 Tower kernel: FAT-fs (sda1): Directory bread(block 16388) failed Mar 14 15:34:44 Tower kernel: FAT-fs (sda1): Directory bread(block 16389) failed Mar 14 15:34:44 Tower kernel: FAT-fs (sda1): Directory bread(block 16390) failed Mar 14 15:34:44 Tower kernel: FAT-fs (sda1): Directory bread(block 16391) failed Mar 14 15:34:44 Tower kernel: FAT-fs (sda1): Directory bread(block 16392) failed Mar 14 15:34:44 Tower kernel: FAT-fs (sda1): Directory bread(block 16393) failed Mar 14 15:34:45 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/appdata.cfg Mar 14 15:34:45 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/backup.cfg Mar 14 15:34:45 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/domains.cfg Mar 14 15:34:45 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/gamedisk.cfg Mar 14 15:34:45 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/isos.cfg Mar 14 15:34:45 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/keys.cfg Mar 14 15:34:45 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/nextcloud.cfg Mar 14 15:34:45 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/syncbackup.cfg Mar 14 15:34:45 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/system.cfg Mar 14 15:34:45 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/vdisks.cfg Mar 14 15:34:45 Tower emhttpd: Starting services... Mar 14 15:34:45 Tower kernel: pcieport 0000:00:03.2: AER: Corrected error received: 0000:00:03.2 Mar 14 15:34:45 Tower kernel: pcieport 0000:00:03.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Mar 14 15:34:45 Tower kernel: pcieport 0000:00:03.2: device [8086:2f0a] error status/mask=00000040/00002000 Mar 14 15:34:45 Tower kernel: pcieport 0000:00:03.2: [ 6] Bad TLP Mar 14 15:34:46 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/appdata.cfg Mar 14 15:34:46 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/backup.cfg Mar 14 15:34:46 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/domains.cfg Mar 14 15:34:46 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/gamedisk.cfg Mar 14 15:34:46 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/isos.cfg Mar 14 15:34:46 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/keys.cfg Mar 14 15:34:46 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/nextcloud.cfg Mar 14 15:34:46 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/syncbackup.cfg Mar 14 15:34:46 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/system.cfg Mar 14 15:34:46 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/vdisks.cfg Mar 14 15:34:46 Tower emhttpd: Starting services... Mar 14 15:34:48 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/appdata.cfg Mar 14 15:34:48 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/backup.cfg Mar 14 15:34:48 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/domains.cfg Mar 14 15:34:48 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/gamedisk.cfg Mar 14 15:34:48 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/isos.cfg Mar 14 15:34:48 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/keys.cfg Mar 14 15:34:48 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/nextcloud.cfg Mar 14 15:34:48 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/syncbackup.cfg Mar 14 15:34:48 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/system.cfg Mar 14 15:34:48 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/vdisks.cfg Mar 14 15:34:48 Tower emhttpd: Starting services... Mar 14 15:34:49 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/appdata.cfg Mar 14 15:34:49 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/backup.cfg Mar 14 15:34:49 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/domains.cfg Mar 14 15:34:49 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/gamedisk.cfg Mar 14 15:34:49 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/isos.cfg Mar 14 15:34:49 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/keys.cfg Mar 14 15:34:49 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/nextcloud.cfg Mar 14 15:34:49 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/syncbackup.cfg Mar 14 15:34:49 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/system.cfg Mar 14 15:34:49 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/vdisks.cfg Mar 14 15:34:49 Tower emhttpd: Starting services... Mar 14 15:34:50 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/appdata.cfg Mar 14 15:34:50 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/backup.cfg Mar 14 15:34:50 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/domains.cfg Mar 14 15:34:50 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/gamedisk.cfg Mar 14 15:34:50 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/isos.cfg Mar 14 15:34:50 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/keys.cfg Mar 14 15:34:50 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/nextcloud.cfg Mar 14 15:34:50 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/syncbackup.cfg Mar 14 15:34:50 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/system.cfg Mar 14 15:34:50 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/vdisks.cfg Mar 14 15:34:50 Tower emhttpd: Starting services... Mar 14 15:34:50 Tower kernel: fat__get_entry: 310 callbacks suppressed Mar 14 15:34:50 Tower kernel: FAT-fs (sda1): Directory bread(block 16384) failed Mar 14 15:34:50 Tower kernel: FAT-fs (sda1): Directory bread(block 16385) failed Mar 14 15:34:50 Tower kernel: FAT-fs (sda1): Directory bread(block 16386) failed Mar 14 15:34:50 Tower kernel: FAT-fs (sda1): Directory bread(block 16387) failed Mar 14 15:34:50 Tower kernel: FAT-fs (sda1): Directory bread(block 16388) failed Mar 14 15:34:50 Tower kernel: FAT-fs (sda1): Directory bread(block 16389) failed Mar 14 15:34:50 Tower kernel: FAT-fs (sda1): Directory bread(block 16390) failed Mar 14 15:34:50 Tower kernel: FAT-fs (sda1): Directory bread(block 16391) failed Mar 14 15:34:50 Tower kernel: FAT-fs (sda1): Directory bread(block 16392) failed Mar 14 15:34:50 Tower kernel: FAT-fs (sda1): Directory bread(block 16393) failed Mar 14 15:34:51 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/appdata.cfg Mar 14 15:34:51 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/backup.cfg Mar 14 15:34:51 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/domains.cfg Mar 14 15:34:51 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/gamedisk.cfg Mar 14 15:34:51 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/isos.cfg Mar 14 15:34:51 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/keys.cfg Mar 14 15:34:51 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/nextcloud.cfg Mar 14 15:34:51 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/syncbackup.cfg Mar 14 15:34:51 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/system.cfg Mar 14 15:34:51 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/vdisks.cfg Mar 14 15:34:51 Tower emhttpd: Starting services... Mar 14 15:34:52 Tower kernel: pcieport 0000:00:03.2: AER: Corrected error received: 0000:00:03.2 Mar 14 15:34:52 Tower kernel: pcieport 0000:00:03.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Mar 14 15:34:52 Tower kernel: pcieport 0000:00:03.2: device [8086:2f0a] error status/mask=00000080/00002000 Mar 14 15:34:52 Tower kernel: pcieport 0000:00:03.2: [ 7] Bad DLLP Mar 14 15:34:52 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/appdata.cfg Mar 14 15:34:52 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/backup.cfg Mar 14 15:34:52 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/domains.cfg Mar 14 15:34:52 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/gamedisk.cfg Mar 14 15:34:52 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/isos.cfg Mar 14 15:34:52 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/keys.cfg Mar 14 15:34:52 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/nextcloud.cfg Mar 14 15:34:52 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/syncbackup.cfg Mar 14 15:34:52 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/system.cfg Mar 14 15:34:52 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/vdisks.cfg Mar 14 15:34:52 Tower emhttpd: Starting services... Mar 14 15:34:53 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/appdata.cfg Mar 14 15:34:53 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/backup.cfg Mar 14 15:34:53 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/domains.cfg Mar 14 15:34:53 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/gamedisk.cfg Mar 14 15:34:53 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/isos.cfg Mar 14 15:34:53 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fop The only thing I can think of is that I was messing with the overclocks on the system, but other than that we were just using the VMs. tower-diagnostics-20190314-1542.zip
  6. Update I was able to create a VM with the 3.0 option selected, and I can now update the VM without the error. I just cannot update existing VMs created with USB 2.0 selected.
  7. I have added the XML file & diagnostics to the original post. I re-tested with all usb devices unchecked, and I still received the same error.
  8. This issue never happened before v6.6. I have decided to re-create all my VMs just in case. I receive this error below when I try to apply USB 3.0: These are my default settings that work with USB 2.0: USB 3.0 controller setting that doesnt work: XML File: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='1'> <name>Windows 10</name> <uuid>184700bc-5563-7f04-a7d2-ebffe7e1cd1c</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='9'/> <vcpupin vcpu='1' cpuset='4'/> <vcpupin vcpu='2' cpuset='5'/> <vcpupin vcpu='3' cpuset='11'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-3.0'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/184700bc-5563-7f04-a7d2-ebffe7e1cd1c_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='2' threads='2'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/vdisks/reece.img'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <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/Win10_1809Oct_English_x64.iso'/> <backingStore/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <alias name='ide0-0-0'/> <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.160-1.iso'/> <backingStore/> <target dev='hdb' bus='ide'/> <readonly/> <alias name='ide0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='ide' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:ef:c0:4c'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-1-Windows 10/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='mouse' bus='ps2'> <alias name='input0'/> </input> <input type='keyboard' bus='ps2'> <alias name='input1'/> </input> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <rom file='/mnt/user/isos/gpubios.rom'/> <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='0x02' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc52b'/> <address bus='5' device='2'/> </source> <alias name='hostdev2'/> <address type='usb' bus='0' port='1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x04d8'/> <product id='0x00df'/> <address bus='3' device='3'/> </source> <alias name='hostdev3'/> <address type='usb' bus='0' port='2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x248a'/> <product id='0x8367'/> <address bus='5' device='3'/> </source> <alias name='hostdev4'/> <address type='usb' bus='0' port='3'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain> I was having a similar issue on 6.6.5 that was never fixed, but has stopped coming up in 6.6.6. It is now just this USB error. tower-diagnostics-20190103-1416.zip
  9. Unraid has become unusable at this point. Downgraded to v5.
  10. Just wanted to bump this & say I tried disabling ACS along with resetting my motherboard bios. No luck still cannot select USB 3.0.
  11. Thanks for the response. I've tried editing then applying without any changes which worked; then I tried adding my GPU but the update button still gave the error on both my VMs. Ive since then tried re-creating a new VM with the same settings this time with the OVMF virtualization which worked. I could change the settings & update but it wouldn't boot. I created another VM using Sealbios with the same settings. I can now boot & update. Seems like it was a issue with the old code & re-creating the VM worked. That being said I am still getting this issue - this time with the USB controller. I can select USB 2.0, but if I select any of the USB 3.0 options I get the same error. tower-diagnostics-20181114-0029.zip
  12. Thanks I have added these to the post. tower-diagnostics-20181111-0330.zip
  13. EDIT: After re-creating the VM I was able to update it sucessfully & add a GPU; however, now I can no longer change the USB controller to USB 3.0 without receiving the same error when I hit the update button. USB 2.0 works. When I add my GTX 1070s to any VM's & press the update button I receive the error message below: If I update the VM through the XML view it works fine. This machine has been running unraid since v4 with no issues until the latest few released this started happening. I cannot currently start one of my VMs due to thi. Once of my other VMs I have not touched works & starts up fine. I just cannot update usb devices. This happens on both my VMs with two different GTX 1070s. I checked the system log only to see this: Nov 10 12:27:22 Tower kernel: pcieport 0000:00:03.2: device [8086:2f0a] error status/mask=00001000/00002000 Nov 10 12:27:22 Tower kernel: pcieport 0000:00:03.2: [12] Replay Timer Timeout Nov 10 12:27:22 Tower kernel: pcieport 0000:00:03.2: AER: Corrected error received: 0000:00:03.2 Nov 10 12:27:22 Tower kernel: pcieport 0000:00:03.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) Nov 10 12:27:22 Tower kernel: pcieport 0000:00:03.2: device [8086:2f0a] error status/mask=00001000/00002000 Nov 10 12:27:22 Tower kernel: pcieport 0000:00:03.2: [12] Replay Timer Timeout Nov 10 12:27:24 Tower kernel: pcieport 0000:00:03.2: AER: Corrected error received: 0000:00:03.2 Nov 10 12:27:24 Tower kernel: pcieport 0000:00:03.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) Nov 10 12:27:24 Tower kernel: pcieport 0000:00:03.2: device [8086:2f0a] error status/mask=00001000/00002000 Nov 10 12:27:24 Tower kernel: pcieport 0000:00:03.2: [12] Replay Timer Timeout Nov 10 12:27:32 Tower kernel: pcieport 0000:00:03.2: AER: Multiple Corrected error received: 0000:00:03.2 Nov 10 12:27:32 Tower kernel: pcieport 0000:00:03.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Nov 10 12:27:32 Tower kernel: pcieport 0000:00:03.2: device [8086:2f0a] error status/mask=00000040/00002000 Nov 10 12:27:32 Tower kernel: pcieport 0000:00:03.2: [ 6] Bad TLP Nov 10 12:27:32 Tower kernel: pcieport 0000:00:03.2: AER: Multiple Corrected error received: 0000:00:03.2 Nov 10 12:27:32 Tower kernel: pcieport 0000:00:03.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Nov 10 12:27:32 Tower kernel: pcieport 0000:00:03.2: device [8086:2f0a] error status/mask=00000040/00002000 Nov 10 12:27:32 Tower kernel: pcieport 0000:00:03.2: [ 6] Bad TLP Nov 10 12:27:40 Tower kernel: pcieport 0000:00:03.2: AER: Corrected error received: 0000:00:03.2 Nov 10 12:27:40 Tower kernel: pcieport 0000:00:03.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) Nov 10 12:27:40 Tower kernel: pcieport 0000:00:03.2: device [8086:2f0a] error status/mask=00001000/00002000 Nov 10 12:27:40 Tower kernel: pcieport 0000:00:03.2: [12] Replay Timer Timeout Nov 10 12:27:40 Tower kernel: pcieport 0000:00:03.2: AER: Corrected error received: 0000:00:03.2 Nov 10 12:27:40 Tower kernel: pcieport 0000:00:03.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) Nov 10 12:27:40 Tower kernel: pcieport 0000:00:03.2: device [8086:2f0a] error status/mask=00001000/00002000 Nov 10 12:27:40 Tower kernel: pcieport 0000:00:03.2: [12] Replay Timer Timeout Nov 10 12:27:41 Tower kernel: pcieport 0000:00:03.2: AER: Corrected error received: 0000:00:03.2 Nov 10 12:27:41 Tower kernel: pcieport 0000:00:03.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) Nov 10 12:27:41 Tower kernel: pcieport 0000:00:03.2: device [8086:2f0a] error status/mask=00001000/00002000 Nov 10 12:27:41 Tower kernel: pcieport 0000:00:03.2: [12] Replay Timer Timeout Nov 10 12:27:42 Tower kernel: pcieport 0000:00:03.2: AER: Corrected error received: 0000:00:03.2 Nov 10 12:27:42 Tower kernel: pcieport 0000:00:03.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) Nov 10 12:27:42 Tower kernel: pcieport 0000:00:03.2: device [8086:2f0a] error status/mask=00001000/00002000 Nov 10 12:27:42 Tower kernel: pcieport 0000:00:03.2: [12] Replay Timer Timeout Nov 10 12:27:44 Tower kernel: pcieport 0000:00:03.2: AER: Corrected error received: 0000:00:03.2 Nov 10 12:27:44 Tower kernel: pcieport 0000:00:03.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) Nov 10 12:27:44 Tower kernel: pcieport 0000:00:03.2: device [8086:2f0a] error status/mask=00001000/00002000 Nov 10 12:27:44 Tower kernel: pcieport 0000:00:03.2: [12] Replay Timer Timeout Nov 10 12:29:15 Tower kernel: usb 3-10.2: reset full-speed USB device number 8 using xhci_hcd Nov 10 12:29:15 Tower kernel: usb 3-10.2: reset full-speed USB device number 8 using xhci_hcd Nov 10 12:29:16 Tower kernel: usb 3-10.2: reset full-speed USB device number 8 using xhci_hcd Nov 10 12:30:18 Tower kernel: pcieport 0000:00:03.2: AER: Corrected error received: 0000:00:03.2 Nov 10 12:30:18 Tower kernel: pcieport 0000:00:03.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) Nov 10 12:30:18 Tower kernel: pcieport 0000:00:03.2: device [8086:2f0a] error status/mask=00001000/00002000 Nov 10 12:30:18 Tower kernel: pcieport 0000:00:03.2: [12] Replay Timer Timeout Nov 10 12:30:20 Tower kernel: pcieport 0000:00:03.2: AER: Corrected error received: 0000:00:03.2 Nov 10 12:30:20 Tower kernel: pcieport 0000:00:03.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) Nov 10 12:30:20 Tower kernel: pcieport 0000:00:03.2: device [8086:2f0a] error status/mask=00001000/00002000 Nov 10 12:30:20 Tower kernel: pcieport 0000:00:03.2: [12] Replay Timer Timeout Nov 10 12:31:10 Tower kernel: usb 3-10.2: reset full-speed USB device number 8 using xhci_hcd Nov 10 12:31:10 Tower kernel: usb 3-10.2: reset full-speed USB device number 8 using xhci_hcd Nov 10 12:31:10 Tower kernel: usb 3-10.2: reset full-speed USB device number 8 using xhci_hcd Here is my XML File: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>vm1</name> <uuid>5c2de3e6-bc1b-d47d-db69-df51fc9c3ab4</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>6</vcpu> <cputune> <vcpupin vcpu='0' cpuset='3'/> <vcpupin vcpu='1' cpuset='9'/> <vcpupin vcpu='2' cpuset='4'/> <vcpupin vcpu='3' cpuset='10'/> <vcpupin vcpu='4' cpuset='5'/> <vcpupin vcpu='5' cpuset='11'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-3.0'>hvm</type> </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='3' threads='2'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/vdisks/vm1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/Windows.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.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='qemu-xhci' ports='15'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <controller type='pci' index='0' model='pci-root'/> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:2e:30:0b'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </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='tablet' bus='usb'> <address type='usb' bus='0' port='5'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <address bus='5' device='3'/> </source> <address type='usb' bus='0' port='2'/> </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='0x04d8'/> <product id='0x00df'/> </source> <address type='usb' bus='0' port='3'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x248a'/> <product id='0x8367'/> </source> <address type='usb' bus='0' port='4'/> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </memballoon> </devices> </domain> Here is my VM config: More VM settings:
  14. The VM starts up normally though as long as I dont update it
  15. I haven't experinced this before, and I have been using unraid since like v4 or something. Now out of no where I am experiencing this issue with the latest few updates. When I update a VM with a GPU, or if I have a GPU set to a VM & press the "update" button I receive the error "internal error: PCI host devices must use 'pci' address type" I It works when I update it through the XML view, or change my gpu to vnc. This happens on all my VMs