inva_zimm

Thanks again, Jorge! Have had a few other things to deal with, and being away for a little while, but working on it slowly here and there. Looks like I've at least got the server array back up and running along with my docker services, etc. The NVMe shows up in the unassigned devices as I removed it from the cache pool for the moment while doing some clean up and reworking. So I think I'm back in a good spot to continue with everything. Thanks again! Considering this solved for now!

I've been able to backup the smaller SSD, though took a little longer than I would've liked. Actually did it a couple times just to be cautious. Though, definitely appreciate the link in regards to restoring/handling btrfs related drives. Helped a bit in doing the back ups. Setting the Cache to just 1 and empty seems to have allowed me to start the normal array fine. This obviously does remove access to my docker setups and vm, but not really that surprising. When I go to re-add the original Evo SSD to the Cache (in current state), I end up with the same error as above: ``` BTRFS: error (device sdh1) in cleanup_transaction:1942: errno=-28 No space left BTRFS: error (device sdh1) in reset_balance_state:3327: errno=-28 No space left ``` I thought about checking the NVMe and perhaps either re-adding it by itself to the Cache first, or perhaps just reformatting. But when checking the drive with `sgdisk` I received the following which has me hesitating ``` *************************************************************** Found invalid GPT and valid MBR; converting MBR to GPT format in memory. *************************************************************** Warning! Secondary partition table overlaps the last partition by 33 blocks! You will need to delete this partition or resize it in another utility. Disk /dev/nvme0n1: 1953525168 sectors, 931.5 GiB Model: WDBRP********-**** Sector size (logical/physical): 512/512 bytes Disk identifier (GUID): FA9DBD11-2D26-****-****-************ Partition table holds up to 128 entries Main partition table begins at sector 2 and ends at sector 33 First usable sector is 34, last usable sector is 1953525134 Partitions will be aligned on 2048-sector boundaries Total free space is 2014 sectors (1007.0 KiB) Number Start (sector) End (sector) Size Code Name 1 2048 1953525167 931.5 GiB 8300 Linux filesystem ``` Would it be better to clear this drive before attempting to do anything with it in the Cache? Thanks, again!

Thanks for the heads up, Jorge! I kind of figured that might be the case sadly. I'm going to see what I can do about at least getting the smaller one backed up before continuing forward. That said, is there a way to make it only recognize the smaller one as it seems to be attempting to access the NVMe or at least something of that size? Like if I reset the pool slots to the original 1 rather than it being at 2 now

Earlier in the week I updated to 6.9.1 and everything seemed fine. Then I recently tried adding an NVMe to my system as a cache drive and it appeared to be stuck in the array starting mode with this particular drive continually stating 'Mounting' for over an hour. Not sure if it was formatting and just not reporting that back. Due to that I restarted the machine and now I can no longer start the array and the new drive no longer shows up as one to be added to the cache pool or even within Unassigned Drives. Made sure that BIOS was updated to the latest for the board prior to attempting any changes to the Unraid array or cache, etc. Plugging in a monitor I see the following error: ``` BTRFS: error (device sdh1) in cleanup_transaction:1942: errno=-28 No space left BTRFS: error (device sdh1) in reset_balance_state:3327: errno=-28 No space left ``` Which I guess makes sense given that sdh1 appears to be my previous 250 GB Samsung Evo SSD, but given that I can not set the NVMe to any slot leads me to worry if I can salvage this. According to the terminal the original `/mnt/cache` still contains all the data it had before hand, but obviously do not want to lose any of that. Trying to back up the cache to an array disk is taking forever in the terminal with rsync. I feel I kind of made a mistake in increasing the cache pool to 2 and then swapping positions of the cache drives before clicking start initially. I'm adding one of my more recent diagnostics since this has happened. The only downside, is it's prior to starting the array as I can not get to run it while it's stuck in start mode. Anyone have any thoughts on how to handle this, even if it's just to get to before trying to add the NVMe? Thanks for any help, suggestions, etc.! Let me know if there might be anything else that I can provide if needed. alexandria-diagnostics-20210312-1452.zip

Ok, so after digging around and troubleshooting some more I think I finally got it working correctly. I currently have it setup using both archedraft's 11.a technique and jonp's USB3 method. Yeah, it could be a bit of an overkill or rather just working coincidentally, but hey, I have it working ha.. I'm not sure why the former method didn't work the last few times I tried it out, but it's likely I definitely missed something. All they sticky's are great here, I guess I just need to stop multitasking while attempting any of them and I can actually get things working properly ha

[sOLVED] Came across this during my recent testing and I wanted to check if anyone else was still having this issue and given how new the post was, I didn't think starting a new thread with a similar name was the best option. Let me know if I should move this to a new one. I've been having issues attempting to get my Steam Controller or even a Xbox One (recently returned a wireless adapter) controller working through a Win10 VM as well on Unraid 6.1.6. Before anyone attacks me, especially if this is my first post, I have tried out multiple suggestions on here and elsewhere. I've tried out JonP's USB 3 method which I know works as both my wireless Logitech keyboard and mouse are fine and in the same bus. Prior to that I was even trying to attempt archedraft's Passthrough Guide which sadly my XML file would revert moments after I would click 'Update'. And multiple thread suggestions on Steam. Both wired and wireless adapter. I know for a fact that the Steam Controller is being recognized by at least Unraid as plugging it in wired results in the following (unplugging and plugging back in to double check consistency): Feb 25 21:22:49 Alexandria kernel: input: Valve Software Wired Controller as /devices/pci0000:00/0000:00:1c.3/0000:06:00.0/usb3/3-1/3-1.2/3-1.2:1.0/0003:28DE:1102.0017/input/input16 Feb 25 21:22:49 Alexandria kernel: hid-generic 0003:28DE:1102.0017: input,hidraw0: USB HID v1.11 Keyboard [Valve Software Wired Controller] on usb-0000:06:00.0-1.2/input0 Feb 25 21:22:49 Alexandria kernel: input: Valve Software Wired Controller as /devices/pci0000:00/0000:00:1c.3/0000:06:00.0/usb3/3-1/3-1.2/3-1.2:1.1/0003:28DE:1102.0018/input/input17 Feb 25 21:22:49 Alexandria kernel: hid-generic 0003:28DE:1102.0018: input,hidraw1: USB HID v1.11 Mouse [Valve Software Wired Controller] on usb-0000:06:00.0-1.2/input1 Feb 25 21:22:49 Alexandria kernel: hid-generic 0003:28DE:1102.0019: hiddev0,hidraw2: USB HID v1.11 Device [Valve Software Wired Controller] on usb-0000:06:00.0-1.2/input2 Feb 25 21:22:55 Alexandria kernel: usb 3-1.2: USB disconnect, device number 7 Feb 25 21:22:59 Alexandria kernel: usb 3-1.2: new full-speed USB device number 8 using xhci_hcd Feb 25 21:22:59 Alexandria kernel: usb 3-1.2: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes Feb 25 21:22:59 Alexandria kernel: usb 3-1.2: ep 0x82 - rounding interval to 32 microframes, ep desc says 48 microframes Feb 25 21:22:59 Alexandria kernel: usb 3-1.2: ep 0x83 - rounding interval to 32 microframes, ep desc says 48 microframes Feb 25 21:22:59 Alexandria kernel: input: Valve Software Wired Controller as /devices/pci0000:00/0000:00:1c.3/0000:06:00.0/usb3/3-1/3-1.2/3-1.2:1.0/0003:28DE:1102.001A/input/input18 Feb 25 21:22:59 Alexandria kernel: hid-generic 0003:28DE:1102.001A: input,hidraw0: USB HID v1.11 Keyboard [Valve Software Wired Controller] on usb-0000:06:00.0-1.2/input0 Feb 25 21:22:59 Alexandria kernel: input: Valve Software Wired Controller as /devices/pci0000:00/0000:00:1c.3/0000:06:00.0/usb3/3-1/3-1.2/3-1.2:1.1/0003:28DE:1102.001B/input/input19 Feb 25 21:22:59 Alexandria kernel: hid-generic 0003:28DE:1102.001B: input,hidraw1: USB HID v1.11 Mouse [Valve Software Wired Controller] on usb-0000:06:00.0-1.2/input1 Feb 25 21:22:59 Alexandria kernel: hid-generic 0003:28DE:1102.001C: hiddev0,hidraw2: USB HID v1.11 Device [Valve Software Wired Controller] on usb-0000:06:00.0-1.2/input2 Feb 25 21:23:06 Alexandria kernel: usb 3-1.2: USB disconnect, device number 8 Feb 25 21:23:15 Alexandria kernel: usb 3-1.2: new full-speed USB device number 9 using xhci_hcd Feb 25 21:23:15 Alexandria kernel: usb 3-1.2: ep 0x82 - rounding interval to 32 microframes, ep desc says 48 microframes Feb 25 21:23:15 Alexandria kernel: usb 3-1.2: ep 0x83 - rounding interval to 32 microframes, ep desc says 48 microframes Feb 25 21:23:15 Alexandria kernel: usb 3-1.2: ep 0x84 - rounding interval to 32 microframes, ep desc says 48 microframes Feb 25 21:23:15 Alexandria kernel: usb 3-1.2: ep 0x85 - rounding interval to 32 microframes, ep desc says 48 microframes Feb 25 21:23:15 Alexandria kernel: input: Valve Software Steam Controller as /devices/pci0000:00/0000:00:1c.3/0000:06:00.0/usb3/3-1/3-1.2/3-1.2:1.0/0003:28DE:1142.001D/input/input20 Feb 25 21:23:15 Alexandria kernel: hid-generic 0003:28DE:1142.001D: input,hidraw0: USB HID v1.11 Keyboard [Valve Software Steam Controller] on usb-0000:06:00.0-1.2/input0 Feb 25 21:23:15 Alexandria kernel: hid-generic 0003:28DE:1142.001E: hiddev0,hidraw1: USB HID v1.11 Device [Valve Software Steam Controller] on usb-0000:06:00.0-1.2/input1 Feb 25 21:23:15 Alexandria kernel: hid-generic 0003:28DE:1142.001F: hiddev0,hidraw2: USB HID v1.11 Device [Valve Software Steam Controller] on usb-0000:06:00.0-1.2/input2 Feb 25 21:23:15 Alexandria kernel: hid-generic 0003:28DE:1142.0020: hiddev0,hidraw3: USB HID v1.11 Device [Valve Software Steam Controller] on usb-0000:06:00.0-1.2/input3 Feb 25 21:23:15 Alexandria kernel: hid-generic 0003:28DE:1142.0021: hiddev0,hidraw4: USB HID v1.11 Device [Valve Software Steam Controller] on usb-0000:06:00.0-1.2/input4 Feb 25 21:32:36 Alexandria kernel: usb 3-1.2: USB disconnect, device number 9 For the most part, my Win10 VM has given me little trouble; especially if gaming through mouse and keyboard. It's only been while trying to use a controller for gaming (Firewatch, Bioshock series, etc.) that I can't seem to get this setup to work. Current System Info: M/B: MSI - X99A SLI Krait Edition (MS-7885) CPU: Intel® Core™ i7-5930K CPU @ 3.50GHz HVM: Enabled IOMMU: Enabled Cache: 384 kB, 1536 kB, 15360 kB Memory: 16384 MB (max. installable capacity 512 GB) Network: eth0: 1000Mb/s - Full Duplex Kernel: Linux 4.1.13-unRAID x86_64 OpenSSL: 1.0.1p Any suggestions / help definitely appreciated.