Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

3 Neutral

About TheSkaz

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. it was, in fact, the RTM version that was causing the issue... installed the 1909 version and it worked.
  2. so far seabios has caused the windows install to take 12 hours or so.... I also just realized that I was installing the RTM version of windows 10.... that could have been an issue.
  3. This is what I got: This device is not working properly because Windows cannot load the drivers required for this device. (Code 31) ill try seabios (as per your link)
  4. I have a virtual machine that I am trying to pass one of my GPUs to. this GPU is the main one that unraid uses when it boots. the other GPU is used for plex. I have downloaded and modified the ROM from techpowerup and am utilizing it. This is how it presents in windows: here is my relevant part of the VM Config: when attempting to install nvidia drivers through windows, I get this: and when I try through nvidia: and if I follow those instructions: Windows Version:
  5. Yep, I built everything. I have pics of the build process if anyone is interested
  6. Table with computer shelf removed Sent from my SM-N960U using Tapatalk
  7. Card Flipped upside down HDDs prior to install
  8. 1st Build Unraid 6.8.2 Pro Asus Z9PE16/2DL 2x Intel Xeon E5-2697 V2s (2.7GHz 12core) 256GB DDR3 LR-DIMM RAM 10x 2TB WD Red/WD Green/Hitachi drives 6x 240GB SSDs (ZFS raid array for VMs) 2x 120GB SSDs (for cache drive) 2x EVGA 1070s (that happened to be watercooled...) these pictures were in the original case. I took the 2080 ti out and put it my main machine, and swapped to the 2x 1070s. after that, I decided to upgrade the case. I dont have a picture of it, but I had a thermaltake tower 900 case with 2 waterlines coming over to this one to cool the 1070s. The case will become a desk PC... essentially.... the PC on the right is the UnRaid Server. OK, that was the first build. the lower processor's watercooling line worked loose as I moved this 350lb thing around and it got the cpu and mobo wet. POP!!! because all of my VMs are on there (for work) I needed to scramble and get a new motherboard that day. they dont stock those anymore lol, which leads me to server #2. Asus TRX40-Pro Prime AMD Threadripper 3990x 256GB DDR4 RAM 10x Seagate Exo Enterprise 16Tb Drives 6x 240GB SSDs (My VMs) 2x NVME 1Tb Drives for Cache. 10G ASUS NIC 2x 1070s Marvell Dual SFF-8087 controller card.......whoops I ended up swapping out that marvell card for a supermicro one which with the 8 onboard ports and 2x M.2 slots, that gives me my 18 drives again. d due to the slot spacing on the board, I had to put the HBA in upside down.
  9. thank you. I might just start over using that method. I would rather wipe everything and just start over. when I started I messed a few things up and just would like to start clean
  10. follow up question, is there a way to completely wipe everything and start over with just my product key?
  11. I upgraded my dual xeon board to a threadripper (3990x). I had to add a HBA controller and messed up and got a Marvell that has the virtualization issue. I can boot up normally but as soon as I hit the web app, the whole system freezes. I cannot even log in locally. I booted into safe mode, and got the diagnostics. virtualization is disabled until I get a new card (i need my VMs that are on the drives that are connected to that controller) tower-diagnostics-20200729-0904.zip
  12. root@Tower:~# dmesg | grep ZFS [ 61.092654] ZFS: Loaded module v0.8.0-1, ZFS pool version 5000, ZFS filesystem version 5 Thank you so much for your help and quick turnarounds.
  13. thank you so much! sorry for the headache
  14. What I did was upload the files using WinSCP: and then rebooted, once it comes back up, it shows this: it seems to be reverting. I assume I don't need to rename the files right?
  15. Thank you so much!!!!!!! [ 88.290629] ZFS: Loaded module v0.8.3-1, ZFS pool version 5000, ZFS filesystem version 5 I have it installed, and currently stress testing. Let's hope this works!