• Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About inva_zimm

  • Rank


  • Gender
  1. 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!
  2. 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 ab
  3. 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
  4. 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 p
  5. 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
  6. [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 t