claira

They are on the same controller. and power cable. I will look at that.

How do I tell which drive is ATA2.00? Is it the cable? Drive? Controller? Aug 17 18:21:21 UNRAID kernel: ata2.00: cmd 61/40:b8:d0:fe:f0/05:00:5d:00:00/40 tag 23 ncq dma 688128 out Aug 17 18:21:21 UNRAID kernel: res 40/00:a0:50:f0:f0/00:00:5d:00:00/40 Emask 0x10 (ATA bus error) Aug 17 18:21:21 UNRAID kernel: ata2.00: status: { DRDY } Aug 17 18:21:21 UNRAID kernel: ata2.00: failed command: WRITE FPDMA QUEUED Aug 17 18:21:21 UNRAID kernel: ata2.00: cmd 61/80:c0:10:04:f1/00:00:5d:00:00/40 tag 24 ncq dma 65536 out Aug 17 18:21:21 UNRAID kernel: res 40/00:a0:50:f0:f0/00:00:5d:00:00/40 Emask 0x10 (ATA bus error) Aug 17 18:21:21 UNRAID kernel: ata2.00: status: { DRDY } Aug 17 18:21:21 UNRAID kernel: ata2.00: failed command: WRITE FPDMA QUEUED Aug 17 18:21:21 UNRAID kernel: ata2.00: cmd 61/40:c8:90:04:f1/05:00:5d:00:00/40 tag 25 ncq dma 688128 out Aug 17 18:21:21 UNRAID kernel: res 40/00:a0:50:f0:f0/00:00:5d:00:00/40 Emask 0x10 (ATA bus error) Aug 17 18:21:21 UNRAID kernel: ata2.00: status: { DRDY } Aug 17 18:21:21 UNRAID kernel: ata2.00: failed command: WRITE FPDMA QUEUED Aug 17 18:21:21 UNRAID kernel: ata2.00: cmd 61/40:d0:d0:09:f1/05:00:5d:00:00/40 tag 26 ncq dma 688128 out Aug 17 18:21:21 UNRAID kernel: res 40/00:a0:50:f0:f0/00:00:5d:00:00/40 Emask 0x10 (ATA bus error) Aug 17 18:21:21 UNRAID kernel: ata2.00: status: { DRDY } Aug 17 18:21:21 UNRAID kernel: ata2.00: failed command: WRITE FPDMA QUEUED Aug 17 18:21:21 UNRAID kernel: ata2.00: cmd 61/40:d8:10:0f:f1/01:00:5d:00:00/40 tag 27 ncq dma 163840 out Aug 17 18:21:21 UNRAID kernel: res 40/00:a0:50:f0:f0/00:00:5d:00:00/40 Emask 0x10 (ATA bus error) Aug 17 18:21:21 UNRAID kernel: ata2.00: status: { DRDY } Aug 17 18:21:21 UNRAID kernel: ata2: hard resetting link Aug 17 18:21:27 UNRAID kernel: ata2: link is slow to respond, please be patient (ready=0) Aug 17 18:21:31 UNRAID kernel: ata2: COMRESET failed (errno=-16) Aug 17 18:21:31 UNRAID kernel: ata2: hard resetting link Aug 17 18:21:37 UNRAID kernel: ata2: link is slow to respond, please be patient (ready=0) Aug 17 18:21:37 UNRAID kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Aug 17 18:21:38 UNRAID kernel: ata2.00: configured for UDMA/33 Aug 17 18:21:38 UNRAID kernel: ata2: EH complete Aug 17 18:21:38 UNRAID kernel: ata2.00: exception Emask 0x10 SAct 0x7f0 SErr 0x4890000 action 0xe frozen Aug 17 18:21:38 UNRAID kernel: ata2.00: irq_stat 0x08400040, interface fatal error, connection status changed Aug 17 18:21:38 UNRAID kernel: ata2: SError: { PHYRdyChg 10B8B LinkSeq DevExch } Aug 17 18:21:38 UNRAID kernel: ata2.00: failed command: WRITE FPDMA QUEUED Aug 17 18:21:38 UNRAID kernel: ata2.00: cmd 61/00:20:90:a1:f1/04:00:5d:00:00/40 tag 4 ncq dma 524288 out Aug 17 18:21:38 UNRAID kernel: res 40/00:20:90:a1:f1/00:00:5d:00:00/40 Emask 0x10 (ATA bus error) Aug 17 18:21:38 UNRAID kernel: ata2.00: status: { DRDY } Aug 17 18:21:38 UNRAID kernel: ata2.00: failed command: WRITE FPDMA QUEUED Aug 17 18:21:38 UNRAID kernel: ata2.00: cmd 61/40:28:90:a5:f1/05:00:5d:00:00/40 tag 5 ncq dma 688128 out Aug 17 18:21:38 UNRAID kernel: res 40/00:20:90:a1:f1/00:00:5d:00:00/40 Emask 0x10 (ATA bus error) Aug 17 18:21:38 UNRAID kernel: ata2.00: status: { DRDY } Aug 17 18:21:38 UNRAID kernel: ata2.00: failed command: WRITE FPDMA QUEUED Aug 17 18:21:38 UNRAID kernel: ata2.00: cmd 61/40:30:d0:aa:f1/05:00:5d:00:00/40 tag 6 ncq dma 688128 out Aug 17 18:21:38 UNRAID kernel: res 40/00:20:90:a1:f1/00:00:5d:00:00/40 Emask 0x10 (ATA bus error) Aug 17 18:21:38 UNRAID kernel: ata2.00: status: { DRDY } Aug 17 18:21:38 UNRAID kernel: ata2.00: failed command: WRITE FPDMA QUEUED Aug 17 18:21:38 UNRAID kernel: ata2.00: cmd 61/00:38:10:b0:f1/03:00:5d:00:00/40 tag 7 ncq dma 393216 out Aug 17 18:21:38 UNRAID kernel: res 40/00:20:90:a1:f1/00:00:5d:00:00/40 Emask 0x10 (ATA bus error) Aug 17 18:21:38 UNRAID kernel: ata2.00: status: { DRDY } Aug 17 18:21:38 UNRAID kernel: ata2.00: failed command: WRITE FPDMA QUEUED Aug 17 18:21:38 UNRAID kernel: ata2.00: cmd 61/40:40:10:b3:f1/05:00:5d:00:00/40 tag 8 ncq dma 688128 out Aug 17 18:21:38 UNRAID kernel: res 40/00:20:90:a1:f1/00:00:5d:00:00/40 Emask 0x10 (ATA bus error) Aug 17 18:21:38 UNRAID kernel: ata2.00: status: { DRDY } Aug 17 18:21:38 UNRAID kernel: ata2.00: failed command: WRITE FPDMA QUEUED Aug 17 18:21:38 UNRAID kernel: ata2.00: cmd 61/40:48:50:b8:f1/05:00:5d:00:00/40 tag 9 ncq dma 688128 out Aug 17 18:21:38 UNRAID kernel: res 40/00:20:90:a1:f1/00:00:5d:00:00/40 Emask 0x10 (ATA bus error) Aug 17 18:21:38 UNRAID kernel: ata2.00: status: { DRDY } Aug 17 18:21:38 UNRAID kernel: ata2.00: failed command: WRITE FPDMA QUEUED Aug 17 18:21:38 UNRAID kernel: ata2.00: cmd 61/00:50:90:bd:f1/04:00:5d:00:00/40 tag 10 ncq dma 524288 out Aug 17 18:21:38 UNRAID kernel: res 40/00:20:90:a1:f1/00:00:5d:00:00/40 Emask 0x10 (ATA bus error) Aug 17 18:21:38 UNRAID kernel: ata2.00: status: { DRDY } Aug 17 18:21:38 UNRAID kernel: ata2: hard resetting link Aug 17 18:21:44 UNRAID kernel: ata2: link is slow to respond, please be patient (ready=0) Aug 17 18:21:48 UNRAID kernel: ata2: COMRESET failed (errno=-16) Aug 17 18:21:48 UNRAID kernel: ata2: hard resetting link unraid-diagnostics-20210817-1822.zip

I have this same issue today. Is there anyway to progress? I put in the telnet to powerdown -r. will see what happens./

I am debating the same thing now. Upgrade to either AM4 Ryzen 3900 or qty 2 Intel xeon E5-2650V2. This MB looks like a good option: GA-7PESH2

Array was fine. Drive dropped out overnight. Parity was confirmed 2 days ago. Rebuilding now with hot spare while i analyse the drive. The bad drive dropped completely out of unraid. had to reboot to get it to register again. 5:57 AM (6 hours ago) Subject: Alert [UNRAID] - Disk 4 in error state (disk dsbl) Drive is reporting: # Attribute Name Flag Value Worst Threshold Type Updated Failed Raw Value 1 Raw read error rate 0x000f 116 099 006 Pre-fail Always Never 104747256 3 Spin up time 0x0003 091 090 000 Pre-fail Always Never 0 4 Start stop count 0x0032 100 100 020 Old age Always Never 382 5 Reallocated sector count 0x0033 100 100 010 Pre-fail Always Never 0 7 Seek error rate 0x000f 068 060 030 Pre-fail Always Never 189277484011 9 Power on hours 0x0032 088 088 000 Old age Always Never 11052 (1y, 3m, 5d, 12h) 10 Spin retry count 0x0013 100 100 097 Pre-fail Always Never 0 12 Power cycle count 0x0032 100 100 020 Old age Always Never 21 183 Runtime bad block 0x0032 100 100 000 Old age Always Never 0 184 End-to-end error 0x0032 100 100 099 Old age Always Never 0 187 Reported uncorrect 0x0032 099 099 000 Old age Always Never 1 188 Command timeout 0x0032 100 100 000 Old age Always Never 0 189 High fly writes 0x003a 100 100 000 Old age Always Never 0 190 Airflow temperature cel 0x0022 055 048 045 Old age Always Never 45 (min/max 43/46) 191 G-sense error rate 0x0032 100 100 000 Old age Always Never 0 192 Power-off retract count 0x0032 098 098 000 Old age Always Never 4226 193 Load cycle count 0x0032 088 088 000 Old age Always Never 24988 194 Temperature celsius 0x0022 045 052 000 Old age Always Never 45 (0 21 0 0 0) 195 Hardware ECC recovered 0x001a 116 099 000 Old age Always Never 104747256 197 Current pending sector 0x0012 074 074 000 Old age Always Never 8696 198 Offline uncorrectable 0x0010 074 074 000 Old age Offline Never 8696 199 UDMA CRC error count 0x003e 200 200 000 Old age Always Never 0 240 Head flying hours 0x0000 100 253 000 Old age Offline Never 6869 (0 67 0) 241 Total lbas written 0x0000 100 253 000 Old age Offline Never 72143411515 242 Total lbas read 0x0000 100 253 000 Old age Offline Never 834024704853 I like to pull drives from 8tb seagate externals, I have 10 of these in my system with 2 parity, 6 data, 2 hot spare. They are all ST8000AS0002 drives, meaning not the greatest drives. I have seen this happen 5 time in the last 2 years to drives. I warranted them 3 of them. The other 2 I have also had this happen on a smaller scale, only 1 or 2 uncorrectable offline sectors and simply removed them from the array. Ran a SMART test. A few preclears and then used them again. I am not sure what constitutes a through it away. Warranty is almost over on many of these. I may start replacing with better quality drives. Does anyone have an opinion on whether better drives are worth it? With dual parity and hot sparse at the ready. Do I need to look at higher quality drives? I suspect the NAS type drive might not drop out of the system in this scenario. Any opinions?

So the array started correctly. The cache drive is readable. The VM on it starts no problem. But not the docker container. Update. I moved the docker container to disk 1 and remapped and now it works. I think i'm going to move everything off the cache disk and reformat it. SO I can go back to just 1 drive. My cache disk looks like 64GB SSD and a 256Gb SSD. I have 150GB on it. Added the 64GB disk as a second disk a while ago. Now i'm getting cache disk full errors.

I cant start my docker Plex Server: THe docker tab doesn't show up even though it's enabled. ErrorWarningSystemArrayLogin Jan 19 19:52:06 UNRAID kernel: blk_update_request: I/O error, dev loop1, sector 2390400 Jan 19 19:52:06 UNRAID kernel: BTRFS: bdev /dev/loop1 errs: wr 2, rd 0, flush 0, corrupt 0, gen 0 Jan 19 19:52:06 UNRAID kernel: BTRFS: error (device loop1) in btrfs_commit_transaction:2071: errno=-5 IO failure (Error while writing out transaction) Jan 19 19:52:06 UNRAID kernel: BTRFS warning (device loop1): Skipping commit of aborted transaction. Jan 19 19:52:06 UNRAID kernel: ------------[ cut here ]------------ Jan 19 19:52:06 UNRAID kernel: WARNING: CPU: 2 PID: 11801 at fs/btrfs/super.c:260 __btrfs_abort_transaction+0x4d/0x10e() Jan 19 19:52:06 UNRAID kernel: BTRFS: Transaction aborted (error -5) Jan 19 19:52:06 UNRAID kernel: Modules linked in: kvm_intel kvm vhost_net vhost macvtap macvlan md_mod xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables iptable_filter ip_tables tun hid_logitech_hidpp i2c_i801 ahci libahci hid_logitech_dj e1000e mvsas ptp libsas scsi_transport_sas pps_core [last unloaded: md_mod] Jan 19 19:52:06 UNRAID kernel: CPU: 2 PID: 11801 Comm: mount Tainted: G W 4.1.15-unRAID #1 Jan 19 19:52:06 UNRAID kernel: Hardware name: ASUS All Series/Z97-A, BIOS 2501 04/27/2015 Jan 19 19:52:06 UNRAID kernel: 0000000000000009 ffff8800b9783978 ffffffff815f1ad0 0000000000000000 Jan 19 19:52:06 UNRAID kernel: ffff8800b97839c8 ffff8800b97839b8 ffffffff8104775b ffff8800b9783a08 Jan 19 19:52:06 UNRAID kernel: ffffffff81286ae4 00000000fffffffb ffff880429a3a800 ffff88041b029160 Jan 19 19:52:06 UNRAID kernel: Call Trace: Jan 19 19:52:06 UNRAID kernel: [<ffffffff815f1ad0>] dump_stack+0x4c/0x6e Jan 19 19:52:06 UNRAID kernel: [<ffffffff8104775b>] warn_slowpath_common+0x97/0xb1 Jan 19 19:52:06 UNRAID kernel: [<ffffffff81286ae4>] ? __btrfs_abort_transaction+0x4d/0x10e Jan 19 19:52:06 UNRAID kernel: [<ffffffff810477b6>] warn_slowpath_fmt+0x41/0x43 Jan 19 19:52:06 UNRAID kernel: [<ffffffff81286ae4>] __btrfs_abort_transaction+0x4d/0x10e Jan 19 19:52:06 UNRAID kernel: [<ffffffff812ac121>] cleanup_transaction+0x80/0x21d Jan 19 19:52:06 UNRAID kernel: [<ffffffff810724cb>] ? wait_woken+0x7d/0x7d Jan 19 19:52:06 UNRAID kernel: [<ffffffff812ad38b>] btrfs_commit_transaction+0xa6c/0xa81 Jan 19 19:52:06 UNRAID kernel: [<ffffffff812e43b1>] btrfs_recover_log_trees+0x30a/0x374 Jan 19 19:52:06 UNRAID kernel: [<ffffffff812e0ed0>] ? replay_one_dir_item+0xcc/0xcc Jan 19 19:52:06 UNRAID kernel: [<ffffffff812aaf96>] open_ctree+0x1aa2/0x1d9c Jan 19 19:52:06 UNRAID kernel: [<ffffffff81287fd2>] btrfs_mount+0x4ac/0x7ea Jan 19 19:52:06 UNRAID kernel: [<ffffffff810c8bba>] ? pcpu_alloc+0x408/0x4e7 Jan 19 19:52:06 UNRAID kernel: [<ffffffff811009a0>] mount_fs+0x12/0x8a Jan 19 19:52:06 UNRAID kernel: [<ffffffff81115957>] vfs_kern_mount+0x5f/0xf8 Jan 19 19:52:06 UNRAID kernel: [<ffffffff8111854f>] do_mount+0x985/0xa7c Jan 19 19:52:06 UNRAID kernel: [<ffffffff810c5733>] ? strndup_user+0x37/0x82 Jan 19 19:52:06 UNRAID kernel: [<ffffffff81118858>] SyS_mount+0x72/0xa1 Jan 19 19:52:06 UNRAID kernel: [<ffffffff815f71ee>] system_call_fastpath+0x12/0x71 Jan 19 19:52:06 UNRAID kernel: ---[ end trace 10222e51d5086f72 ]--- Jan 19 19:52:06 UNRAID kernel: BTRFS: error (device loop1) in cleanup_transaction:1692: errno=-5 IO failure Jan 19 19:52:06 UNRAID kernel: BTRFS info (device loop1): delayed_refs has NO entry Jan 19 19:52:06 UNRAID kernel: BTRFS: error (device loop1) in btrfs_replay_log:2334: errno=-5 IO failure (Failed to recover log tree) Jan 19 19:52:06 UNRAID logger: Not starting Docker: mount error Jan 19 19:52:06 UNRAID kernel: BTRFS: open_ctree failed

Before: Jan 19 19:06:25 UNRAID kernel: mdcmd (1): import 0 8,16 7814026532 ST8000AS0002-1NA17Z_Z8405XNL Jan 19 19:06:25 UNRAID kernel: md: import disk0: [8,16] (sdb) ST8000AS0002-1NA17Z_Z8405XNL size: 7814026532 Jan 19 19:06:25 UNRAID kernel: mdcmd (2): import 1 8,64 7814026532 ST8000AS0002-1NA17Z_Z8405Y1T Jan 19 19:06:25 UNRAID kernel: md: import disk1: [8,64] (sde) ST8000AS0002-1NA17Z_Z8405Y1T size: 7814026532 Jan 19 19:06:25 UNRAID kernel: mdcmd (3): import 2 8,48 2930266532 ST3000DM001-9YN166_W1F0MKEB Jan 19 19:06:25 UNRAID kernel: md: import disk2: [8,48] (sdd) ST3000DM001-9YN166_W1F0MKEB size: 2930266532 Jan 19 19:06:25 UNRAID kernel: mdcmd (4): import 3 8,32 7814026532 ST8000AS0002-1NA17Z_Z8405YKP Jan 19 19:06:25 UNRAID kernel: md: import disk3: [8,32] (sdc) ST8000AS0002-1NA17Z_Z8405YKP size: 7814026532 Jan 19 19:06:25 UNRAID kernel: mdcmd (5): import 4 8,80 2930266532 WDC_WD30EFRX-68EUZN0_WD-WMC4N1960401 Jan 19 19:06:25 UNRAID kernel: md: import disk4: [8,80] (sdf) WDC_WD30EFRX-68EUZN0_WD-WMC4N1960401 size: 2930266532 Jan 19 19:06:25 UNRAID kernel: mdcmd (6): import 5 8,128 7814026532 ST8000AS0002-1NA17Z_Z8409T0L Jan 19 19:06:25 UNRAID kernel: md: import disk5: [8,128] (sdi) ST8000AS0002-1NA17Z_Z8409T0L size: 7814026532 After: Jan 19 19:28:23 UNRAID kernel: mdcmd (1): import 0 8,16 7814026532 ST8000AS0002-1NA17Z_Z8405XNL Jan 19 19:28:23 UNRAID kernel: md: import disk0: [8,16] (sdb) ST8000AS0002-1NA17Z_Z8405XNL size: 7814026532 Jan 19 19:28:23 UNRAID kernel: md: disk0 new disk Jan 19 19:28:23 UNRAID kernel: mdcmd (2): import 1 8,64 7814026532 ST8000AS0002-1NA17Z_Z8405Y1T Jan 19 19:28:23 UNRAID kernel: md: import disk1: [8,64] (sde) ST8000AS0002-1NA17Z_Z8405Y1T size: 7814026532 Jan 19 19:28:23 UNRAID kernel: md: disk1 new disk Jan 19 19:28:23 UNRAID kernel: mdcmd (3): import 2 8,48 2930266532 ST3000DM001-9YN166_W1F0MKEB Jan 19 19:28:23 UNRAID kernel: md: import disk2: [8,48] (sdd) ST3000DM001-9YN166_W1F0MKEB size: 2930266532 Jan 19 19:28:23 UNRAID kernel: md: disk2 new disk Jan 19 19:28:23 UNRAID kernel: mdcmd (4): import 3 8,32 7814026532 ST8000AS0002-1NA17Z_Z8405YKP Jan 19 19:28:23 UNRAID kernel: md: import disk3: [8,32] (sdc) ST8000AS0002-1NA17Z_Z8405YKP size: 7814026532 Jan 19 19:28:23 UNRAID kernel: md: disk3 new disk Jan 19 19:28:23 UNRAID kernel: mdcmd (5): import 4 8,80 2930266532 WDC_WD30EFRX-68EUZN0_WD-WMC4N1960401 Jan 19 19:28:23 UNRAID kernel: md: import disk4: [8,80] (sdf) WDC_WD30EFRX-68EUZN0_WD-WMC4N1960401 size: 2930266532 Jan 19 19:28:23 UNRAID kernel: md: disk4 new disk Jan 19 19:28:23 UNRAID kernel: mdcmd (6): import 5 8,128 7814026532 ST8000AS0002-1NA17Z_Z8409T0L Jan 19 19:28:23 UNRAID kernel: md: import disk5: [8,128] (sdi) ST8000AS0002-1NA17Z_Z8409T0L size: 7814026532 Jan 19 19:28:23 UNRAID kernel: md: disk5 new disk So looks like I managed to put the drives back in place. Is it safe to start? Only change is 1 cache drive instead of 2. Should I check Parity is already valid? It should be in my opinion. As I put everything back as is.

Any chance the old drive order can be figured out form this log? Full log attached. Jan 19 18:57:08 UNRAID emhttp: ST8000AS0002-1NA17Z_Z8405XNL (sdb) 7814026584 Jan 19 18:57:08 UNRAID emhttp: ST8000AS0002-1NA17Z_Z8405YKP (sdc) 7814026584 Jan 19 18:57:08 UNRAID emhttp: ST3000DM001-9YN166_W1F0MKEB (sdd) 2930266584 Jan 19 18:57:08 UNRAID emhttp: ST8000AS0002-1NA17Z_Z8405Y1T (sde) 7814026584 Jan 19 18:57:08 UNRAID emhttp: WDC_WD30EFRX-68EUZN0_WD-WMC4N1960401 (sdf) 2930266584 Jan 19 18:57:08 UNRAID emhttp: SAMSUNG_SSD_830_Series_S0VVNEAC602793 (sdg) 250059096 Jan 19 18:57:08 UNRAID emhttp: INTEL_SSDSC2CT060A3_CVMP2216081G060AGN (sdh) 58615704 Jan 19 18:57:08 UNRAID emhttp: ST8000AS0002-1NA17Z_Z8409T0L (sdi) 7814026584 Jan 19 18:57:08 UNRAID emhttp: ST8000AS0002-1NA17Z_Z8409MLA (sdj) 7814026584 Jan 19 18:57:08 UNRAID emhttp: array slots: 23 Jan 19 18:57:08 UNRAID emhttp: cache slots: 2 Jan 19 18:57:08 UNRAID kernel: mdcmd (1): import 0 8,16 7814026532 ST8000AS0002-1NA17Z_Z8405XNL Jan 19 18:57:08 UNRAID kernel: md: import disk0: [8,16] (sdb) ST8000AS0002-1NA17Z_Z8405XNL size: 7814026532 Jan 19 18:57:08 UNRAID kernel: mdcmd (2): import 1 8,64 7814026532 ST8000AS0002-1NA17Z_Z8405Y1T Jan 19 18:57:08 UNRAID kernel: md: import disk1: [8,64] (sde) ST8000AS0002-1NA17Z_Z8405Y1T size: 7814026532 Jan 19 18:57:08 UNRAID kernel: mdcmd (3): import 2 8,48 2930266532 ST3000DM001-9YN166_W1F0MKEB Jan 19 18:57:08 UNRAID kernel: md: import disk2: [8,48] (sdd) ST3000DM001-9YN166_W1F0MKEB size: 2930266532 Jan 19 18:57:08 UNRAID kernel: mdcmd (4): import 3 8,32 7814026532 ST8000AS0002-1NA17Z_Z8405YKP Jan 19 18:57:08 UNRAID kernel: md: import disk3: [8,32] (sdc) ST8000AS0002-1NA17Z_Z8405YKP size: 7814026532 Jan 19 18:57:08 UNRAID kernel: mdcmd (5): import 4 8,80 2930266532 WDC_WD30EFRX-68EUZN0_WD-WMC4N1960401 Jan 19 18:57:08 UNRAID kernel: md: import disk4: [8,80] (sdf) WDC_WD30EFRX-68EUZN0_WD-WMC4N1960401 size: 2930266532 Jan 19 18:57:08 UNRAID kernel: mdcmd (6): import 5 8,128 7814026532 ST8000AS0002-1NA17Z_Z8409T0L Jan 19 18:57:08 UNRAID kernel: md: import disk5: [8,128] (sdi) ST8000AS0002-1NA17Z_Z8409T0L size: 7814026532 log.txt

I wanted to remove a 2nd cache drive. Click the new config to reset the array as guided. Now I don't know which drive to assign in which order. Got the following drives. Jan 19 19:11:40 UNRAID emhttp: ST8000AS0002-1NA17Z_Z8405XNL (sdb) 7814026584 Jan 19 19:11:40 UNRAID emhttp: ST8000AS0002-1NA17Z_Z8405YKP (sdc) 7814026584 Jan 19 19:11:40 UNRAID emhttp: ST3000DM001-9YN166_W1F0MKEB (sdd) 2930266584 Jan 19 19:11:40 UNRAID emhttp: ST8000AS0002-1NA17Z_Z8405Y1T (sde) 7814026584 Jan 19 19:11:40 UNRAID emhttp: WDC_WD30EFRX-68EUZN0_WD-WMC4N1960401 (sdf) 2930266584 Jan 19 19:11:40 UNRAID emhttp: SAMSUNG_SSD_830_Series_S0VVNEAC602793 (sdg) 250059096 Jan 19 19:11:40 UNRAID emhttp: INTEL_SSDSC2CT060A3_CVMP2216081G060AGN (sdh) 58615704 Jan 19 19:11:40 UNRAID emhttp: ST8000AS0002-1NA17Z_Z8409T0L (sdi) 7814026584 Jan 19 19:11:40 UNRAID emhttp: ST8000AS0002-1NA17Z_Z8409MLA (sdj) 7814026584 Is there a way to figure out what order to put them back in? One is the parity drive.

Is my only option ACS Override or a new motherboard? https://lime-technology.com/forum/index.php?topic=43728.0

I think the issue might be this: vfio: error, group 1 is not viable, please ensure all devices within the iommu_group are bound to their vfio bus driver. Both the GPU and the sata card are on the same IO MMU group. Inorder to solve this issue for usb I added a new usb controller for boot. As all existing usb controllers were in the same group. Motherboard config is x16(red, GPU), x16(red), x4(red, SATA controller), x1(black, usb controller), x1(red) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) 00:01.2 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x4 Controller (rev 06) /sys/kernel/iommu_groups/1/devices/0000:00:01.0 /sys/kernel/iommu_groups/1/devices/0000:00:01.2 /sys/kernel/iommu_groups/1/devices/0000:01:00.0 /sys/kernel/iommu_groups/1/devices/0000:01:00.1 /sys/kernel/iommu_groups/1/devices/0000:02:00.0 as the <qemu:arg value='vfio-pci,host=01:00.0,bus=pcie.0,multifunction=on,x-vga=on'/> grabs the whole bus. Anyone know how to separate these pci-e devices?

After getting the error, to groups list have changed. Not sure why. PCI Devices 00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) 00:01.2 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x4 Controller (rev 06) 00:14.0 USB controller: Intel Corporation 9 Series Chipset Family USB xHCI Controller 00:16.0 Communication controller: Intel Corporation 9 Series Chipset Family ME Interface #1 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-LM 00:1b.0 Audio device: Intel Corporation 9 Series Chipset Family HD Audio Controller 00:1c.0 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 1 (rev d0) 00:1c.6 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 7 (rev d0) 00:1f.0 ISA bridge: Intel Corporation 9 Series Chipset Family Z97 LPC Controller 00:1f.2 SATA controller: Intel Corporation 9 Series Chipset Family SATA Controller [AHCI Mode] 00:1f.3 SMBus: Intel Corporation 9 Series Chipset Family SMBus Controller 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cayman PRO [Radeon HD 6950] 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cayman/Antilles HDMI Audio [Radeon HD 6900 Series] 02:00.0 RAID bus controller: Marvell Technology Group Ltd. MV64460/64461/64462 System Controller, Revision B (rev 01) 04:00.0 USB controller: Renesas Technology Corp. uPD720201 USB 3.0 Host Controller (rev 03) IOMMU Groups /sys/kernel/iommu_groups/0/devices/0000:00:00.0 /sys/kernel/iommu_groups/1/devices/0000:00:01.0 /sys/kernel/iommu_groups/1/devices/0000:00:01.2 /sys/kernel/iommu_groups/1/devices/0000:01:00.0 /sys/kernel/iommu_groups/1/devices/0000:01:00.1 /sys/kernel/iommu_groups/1/devices/0000:02:00.0 /sys/kernel/iommu_groups/2/devices/0000:00:14.0 /sys/kernel/iommu_groups/3/devices/0000:00:16.0 /sys/kernel/iommu_groups/4/devices/0000:00:19.0 /sys/kernel/iommu_groups/5/devices/0000:00:1b.0 /sys/kernel/iommu_groups/6/devices/0000:00:1c.0 /sys/kernel/iommu_groups/6/devices/0000:00:1c.6 /sys/kernel/iommu_groups/6/devices/0000:04:00.0 /sys/kernel/iommu_groups/7/devices/0000:00:1f.0 /sys/kernel/iommu_groups/7/devices/0000:00:1f.2 /sys/kernel/iommu_groups/7/devices/0000:00:1f.3 USB Devices Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 0951:1603 Kingston Technology DataTraveler 1GB/2GB Pen Drive Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub SCSI Devices [0:0:0:0] disk Kingston DataTraveler 2.0 1.00 /dev/sda [1:0:0:0] disk ATA INTEL SSDSC2CT06 300i /dev/sdh [1:0:1:0] disk ATA ST8000AS0002-1NA AR15 /dev/sdi [1:0:2:0] disk ATA ST8000AS0002-1NA AR15 /dev/sdj [2:0:0:0] disk ATA ST8000AS0002-1NA AR13 /dev/sdb [3:0:0:0] disk ATA ST8000AS0002-1NA AR13 /dev/sdc [4:0:0:0] disk ATA ST8000AS0002-1NA AR13 /dev/sdd [5:0:0:0] disk ATA ST3000DM001-9YN1 CC4B /dev/sde [6:0:0:0] disk ATA SAMSUNG SSD 830 3B1Q /dev/sdf [7:0:0:0] disk ATA WDC WD30EFRX-68E 0A80 /dev/sdg

I just added a new pci express sata controller. I am no longer able to boot my unraid VM image. My understanding here is limited. I tried generating a new <qemu:commandline> section by creating a dummy vm and copping that section over. I need help or any insight. I have ruled out the recent upgrade to Unraid 6.1.4 as the cause of of this issue, removing the sata card allows it to boot. Execution error internal error: early end of file from monitor: possible problem: 2015-11-30T01:06:50.772708Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=pcie.0,multifunction=on,x-vga=on: vfio: error, group 1 is not viable, please ensure all devices within the iommu_group are bound to their vfio bus driver. 2015-11-30T01:06:50.772732Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=pcie.0,multifunction=on,x-vga=on: vfio: failed to get group 1 2015-11-30T01:06:50.772749Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=pcie.0,multifunction=on,x-vga=on: Device initialization failed 2015-11-30T01:06:50.772756Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=pcie.0,multifunction=on,x-vga=on: Device 'vfio-pci' could not be initialized <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>TV</name> <uuid>33b9695d-acfa-0641-8fa6-769acc37f2b3</uuid> <metadata> <vmtemplate name="Custom" icon="windows.png" os="windows"/> </metadata> <memory unit='KiB'>12582912</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='3'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-2.3'>hvm</type> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> </hyperv> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='4' 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/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/cache/Virtual Machines/TV/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/Downloads/PC System/OS/Windows 10/en_windows_10_multiple_editions_x64_dvd_6846432.iso'/> <target dev='hda' bus='sata'/> <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/Downloads/PC System/OS/virtio-win-0.1.102.iso'/> <target dev='hdb' bus='sata'/> <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='0x02' slot='0x02' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='dmi-to-pci-bridge'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/> </controller> <controller type='pci' index='2' model='pci-bridge'> <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:6b:3c:3f'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/TV.org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x02' slot='0x05' function='0x0'/> </memballoon> </devices> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=2,chassis=1,id=root.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.0,bus=pcie.0,multifunction=on,x-vga=on'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=00:14.0,bus=pcie.0'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=00:1b.0,bus=pcie.0'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.1,bus=pcie.0'/> </qemu:commandline> </domain> PCI Devices 00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) 00:01.2 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x4 Controller (rev 06) 00:14.0 USB controller: Intel Corporation 9 Series Chipset Family USB xHCI Controller 00:16.0 Communication controller: Intel Corporation 9 Series Chipset Family ME Interface #1 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-LM 00:1b.0 Audio device: Intel Corporation 9 Series Chipset Family HD Audio Controller 00:1c.0 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 1 (rev d0) 00:1c.6 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 7 (rev d0) 00:1f.0 ISA bridge: Intel Corporation 9 Series Chipset Family Z97 LPC Controller 00:1f.2 SATA controller: Intel Corporation 9 Series Chipset Family SATA Controller [AHCI Mode] 00:1f.3 SMBus: Intel Corporation 9 Series Chipset Family SMBus Controller 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cayman PRO [Radeon HD 6950] 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cayman/Antilles HDMI Audio [Radeon HD 6900 Series] 02:00.0 RAID bus controller: Marvell Technology Group Ltd. MV64460/64461/64462 System Controller, Revision B (rev 01) 04:00.0 USB controller: Renesas Technology Corp. uPD720201 USB 3.0 Host Controller (rev 03) IOMMU Groups /sys/kernel/iommu_groups/0/devices/0000:00:00.0 /sys/kernel/iommu_groups/1/devices/0000:00:01.0 /sys/kernel/iommu_groups/1/devices/0000:00:01.2 /sys/kernel/iommu_groups/1/devices/0000:01:00.0 /sys/kernel/iommu_groups/1/devices/0000:01:00.1 /sys/kernel/iommu_groups/1/devices/0000:02:00.0 /sys/kernel/iommu_groups/2/devices/0000:00:14.0 /sys/kernel/iommu_groups/3/devices/0000:00:16.0 /sys/kernel/iommu_groups/4/devices/0000:00:19.0 /sys/kernel/iommu_groups/5/devices/0000:00:1b.0 /sys/kernel/iommu_groups/6/devices/0000:00:1c.0 /sys/kernel/iommu_groups/6/devices/0000:00:1c.6 /sys/kernel/iommu_groups/6/devices/0000:04:00.0 /sys/kernel/iommu_groups/7/devices/0000:00:1f.0 /sys/kernel/iommu_groups/7/devices/0000:00:1f.2 /sys/kernel/iommu_groups/7/devices/0000:00:1f.3 USB Devices Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 0951:1603 Kingston Technology DataTraveler 1GB/2GB Pen Drive 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 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub SCSI Devices [0:0:0:0] disk Kingston DataTraveler 2.0 1.00 /dev/sda [1:0:0:0] disk ATA INTEL SSDSC2CT06 300i /dev/sdh [1:0:1:0] disk ATA ST8000AS0002-1NA AR15 /dev/sdi [1:0:2:0] disk ATA ST8000AS0002-1NA AR15 /dev/sdj [2:0:0:0] disk ATA ST8000AS0002-1NA AR13 /dev/sdb [3:0:0:0] disk ATA ST8000AS0002-1NA AR13 /dev/sdc [4:0:0:0] disk ATA ST8000AS0002-1NA AR13 /dev/sdd [5:0:0:0] disk ATA ST3000DM001-9YN1 CC4B /dev/sde [6:0:0:0] disk ATA SAMSUNG SSD 830 3B1Q /dev/sdf [7:0:0:0] disk ATA WDC WD30EFRX-68E 0A80 /dev/sdg

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 121294365 bytes) in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(276) : eval()'d code on line 16 Can't upload diagnostics file as is 3038KB.

Passed through whole usb controller and both controllers show up in device manager.

Can someone explain what I did wrong in the first section? The second code section works. The difference is in the " <qemu:commandline>" section. What the guide told me to do: <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>TV</name> <uuid>33b9695d-acfa-0641-8fa6-769acc37f2b3</uuid> <metadata> <vmtemplate name="Custom" icon="windows.png" os="windows"/> </metadata> <memory unit='KiB'>12582912</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='3'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-2.3'>hvm</type> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> </hyperv> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='4' 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/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/cache/Virtual Machines/TV/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/Downloads/PC System/OS/Windows 10/en_windows_10_multiple_editions_x64_dvd_6846432.iso'/> <target dev='hda' bus='sata'/> <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/Downloads/PC System/OS/virtio-win-0.1.102.iso'/> <target dev='hdb' bus='sata'/> <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='0x02' slot='0x02' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='dmi-to-pci-bridge'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/> </controller> <controller type='pci' index='2' model='pci-bridge'> <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:6b:3c:3f'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/TV.org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x02' slot='0x05' function='0x0'/> </memballoon> </devices> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=2,chassis=1,id=root.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.0,bus=pcie.0,multifunction=on,x-vga=on'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=00:1b.0,bus=pcie.0'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.1,bus=pcie.0'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=00:14.0,bus=root.1,addr=00.1'/> </qemu:commandline> </domain> This appears to work: <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>TV</name> <uuid>33b9695d-acfa-0641-8fa6-769acc37f2b3</uuid> <metadata> <vmtemplate name="Custom" icon="windows.png" os="windows"/> </metadata> <memory unit='KiB'>12582912</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='3'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-2.3'>hvm</type> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> </hyperv> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='4' 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/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/cache/Virtual Machines/TV/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/Downloads/PC System/OS/Windows 10/en_windows_10_multiple_editions_x64_dvd_6846432.iso'/> <target dev='hda' bus='sata'/> <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/Downloads/PC System/OS/virtio-win-0.1.102.iso'/> <target dev='hdb' bus='sata'/> <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='0x02' slot='0x02' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='dmi-to-pci-bridge'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/> </controller> <controller type='pci' index='2' model='pci-bridge'> <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:6b:3c:3f'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/TV.org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x02' slot='0x05' function='0x0'/> </memballoon> </devices> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=2,chassis=1,id=root.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.0,bus=pcie.0,multifunction=on,x-vga=on'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=00:14.0,bus=pcie.0'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=00:1b.0,bus=pcie.0'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.1,bus=pcie.0'/> </qemu:commandline> </domain>

Did this work for you? I just bought a 4 usb port pci-e card. Vantec UTG-PC345.

That is an option, just thought it would be more convenient. As there VM will be a gaming/TV vm in my living room. no real plans for other VMs.

I am trying to get 2 xbox one controllers on the VM but as they have the same vendor/product ID i tried this: <hostdev mode='subsystem' type='usb' managed='yes'> <source> <address bus='1' device='9'/> </source> <alias name='hostdev1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <address bus='1' device='8'/> </source> <alias name='hostdev2'/> </hostdev> However the second device shows up in windows as an unknown device.

My motherboard doesn't allow any usb handoff settings. just legacy mode support and usb 3.0 enabled or disabled.

Is there any compatibility issues with buying a usb pci-e card. Booting unraid off of that and mapping all of bus 1 to a VM?

Hi all, I was following this guide for USB passthrough. http://lime-technology.com/forum/index.php?topic=36768.45 However all the device on my back pannel (6x usb 2.0, 4x usb 3.0) and 4 front connectors (2x usb 2.0, 2x usb 3.0) are on bus 1. There is 1 spare usb 2.0 header on my motherboard that is untested so far. I am confused as to how to map just the ports i need. Ideally all ports except the set that has the boot usb device would be mapped. Any advice would be much appreciated. MB is a EVGA Z97 FTW Thanks root@UNRAID:~# lspci | grep USB 00:14.0 USB controller: Intel Corporation 9 Series Chipset Family USB xHCI Contr oller 00:1a.0 USB controller: Intel Corporation 9 Series Chipset Family USB EHCI Contr oller #2 00:1d.0 USB controller: Intel Corporation 9 Series Chipset Family USB EHCI Contr oller #1 root@UNRAID:~# lsusb Bus 004 Device 002: ID 8087:8001 Intel Corp. Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 8087:8009 Intel Corp. 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 045e:02d1 Microsoft Corp. XBOX One Controller for Windows Bus 001 Device 002: ID 0951:1603 Kingston Technology DataTraveler 1GB/2GB Pen Dr ive Bus 001 Device 005: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 045e:02d1 Microsoft Corp. XBOX One Controller for Windows Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub root@UNRAID:~# lsusb Bus 004 Device 002: ID 8087:8001 Intel Corp. Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 8087:8009 Intel Corp. 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 009: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 0951:1603 Kingston Technology DataTraveler 1GB/2GB Pen Dr ive Bus 001 Device 006: ID 045e:02d1 Microsoft Corp. XBOX One Controller for Windows Bus 001 Device 008: ID 045e:02d1 Microsoft Corp. XBOX One Controller for Windows Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub root@UNRAID:~# lsusb Bus 004 Device 002: ID 8087:8001 Intel Corp. Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 8087:8009 Intel Corp. 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 004: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 003: ID 045e:02d1 Microsoft Corp. XBOX One Controller for Windows Bus 001 Device 005: ID 045e:02d1 Microsoft Corp. XBOX One Controller for Windows Bus 001 Device 002: ID 0951:1603 Kingston Technology DataTraveler 1GB/2GB Pen Drive Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Or a zipped html document. 588KB unzipped. 14-drive-SMART-PRECLEAR.zip

Thanks for the info. Bought this mother board for less than $100CAD. So if just 2 of 8 ports wont work. Ill live with it. Got a AOC-SASLP-MV8 coming from ebay. Cant actually figure out how to disable VT-d on this motherboard. It was enabled by default. Which is strange. I do want VT-d. It was one of the reasons for picking this motherboard. Seems like most lga1150 motherboards only have six SATA ports these days anyways.