Jump to content

testdasi

Members
  • Posts

    2,812
  • Joined

  • Last visited

  • Days Won

    17

Everything posted by testdasi

  1. Are you able to consistently boot and hard reboot (i.e. shutdown VM and then start VM) your Windows 10 VM with the GPU fine? "Yesterday" when it worked, was Ubuntu the first VM you ran after Unraid boot? To help with troubleshooting on your own, you can turn on Ubuntu built-in screen sharing functionality which is just VNC server. Alternatively, use a 3rd party solution like NoMachine. Also, use Ubuntu 18.04 i.e. LTS release. 19.10 is not LTS and a lot of things have not been optimised.
  2. 9p poor performance has been known for a while now since it requires a lot of tuning and the right workflow to maximise its benefits. Given the availability of alternatives (e.g. SMB, NFS, even vdisk etc.), if performance is what you are after, just simply don't use 9p.
  3. Yes you can. I have changed my cache and Unassigned Devices config (e.g. VM-dedicated stuff) too many times to count.
  4. The Dell H200E looks to be a LSI clone so you should be able to access your JBOD enclosure in Unraid just like it's directly connected internally. I still recommend you read up on flashing HBA controllers to IT mode since it's generally recommended on the forum. You can run a Windows VM and access via RDP (that is a pretty common use case). Ripping your physical media should be done in docker (e.g. ripper or makemkv dockers - I have used both and they are both good) - it's a lot simpler to set up. Passing through an optical drive to the VM is complicated and writing optical discs does not work - at least I have never managed to make it work. If you can run something in Windows baremetal, it's 99.99% sure to run in a Windows VM. The only 2 exceptions are: nested virtualisation (i.e. a VM under another VM - it needs hardware support) and software that is purposely coded to NOT work in a virtualised envi (e.g. *cough* nvidia *cough*) But just as ripping physical media, anything that has an Unraid docker should be run as a docker. It's safer and more efficient. A docker for Unraid is like an app on your Android phone. There are many dockers on Community Apps so I'm sure you will find something useful. For example, there are dockers that allow Transmission or Deluge to run through a VPN (any VPN that supports OpenVPN should work but PIA is easier to setup). The dockers also have Privoxy setup so you can use the Privoxy proxy for jDownloader docker, which allows it to run through the same VPN.
  5. One thing you like most about Unraid: The integration of docker + VM + storage into a simple user-friendly GUI. Have not seen any product out there that makes things that easy. One thing you'd like to see added to the OS in 2020 Official SSD array support
  6. No that has never worked. You set up the fan profiles in BIOS and that's all the control you have.
  7. Are you sure you downloaded the correct vbios file specific to your exact GPU? The vbios file has to be specific to the exact same card (brand + model + revision). It's not uncommon for certain cards to not have the vbios available on Techpowerup, and no, the vbios files typically canNOT be cross-used. If you are not sure, start with no vbios instead (and if all else fails, dump your own vbios). No vbios is better than wrong vbios. Now if you are sure the vbios is correct (or start from a no-vbios state) then try this. Make sure you do not skip / workaround anything because you think it doesn't matter / didn't work / whatever. Boot Unraid in legacy mode. Start a new VM template, set everything up just like the old template but have Hyper-V = Yes. Do NOT tick start VM box. Save template (the VM should not start automatically after saving since you did not tick the start VM box!) Now edit the template in xml mode, replace everything between <hyperv> and </hyperv> with this <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vpindex state='on'/> <synic state='on'/> <stimer state='on'/> <reset state='on'/> <vendor_id state='on' value='0123456789ab'/> <frequencies state='on'/> </hyperv> <kvm> <hidden state='on'/> </kvm> Start the VM and keep your fingers crossed. If it still doesn't work then you probably need to borrow a cheap GPU to boot Unraid and dump your own vbios. It's even better if you can buy a cheap GPU for Unraid to boot with.
  8. Option A is cheaper. Option B is theoretically faster (but not perceivable in practice) and is better if you have games that don't support network storage. (note you won't be able to run 250GB + 1TB in cache. You should use the existing 1TB in cache and mount the 250GB as unassigned e.g. for temp download spaces).
  9. You can have route the cable UNDERNEATH your PSU (and even your mobo) for better cable management. I ran 2 SATA power cables, 1 from left to right and 1 from right to left. That works well with how the HDDs are mounted in the cages. Also cable-tie your excess cable as high as you can (preferably to the cable-tie slots along the case frame). Last but not least, to save the HDD cage for HDD, remember velcro is an excellent mounting mechanism for 2.5" SSD. 😅
  10. A 2-legged-chair is more stable than 12i. What with it?
  11. If you are planning to run game out of the array then you probably will benefit from 7200rpm drives (but only a bit). 100MB/s bottleneck is only if you access the array through gigabit network. Your virtio network card in your VM runs at 10Gbps which maxes out at 1.25GB/s so you will not be gigabit-limited. Of course there is network latency but that would usually only be a big problem with games that have zillion tiny files (unlikely with modern titles). There is a guide by SpaceInvaderOne on how to set up a hybrid cache + array storage for games. In that case then you will benefit from a large (e.g. 1TB+) SATA SSD for cache. Take note though that certain game services do NOT allow you to move game storage to a network drive (I think Blizzard is one). In that case, you will need to create a vdisk file, which make things rather complicated albeit doable.
  12. From what you have described so far, you have 2 set of uses: "backing up my PC (time machine backup type), my phone's and using it as home automation and Plex server." <-- this is typically done by Unraid Windows PC <-- obviously Windows So for your normal uses, are you looking to do BOTH (1) and (2) at the same time? e.g. will you be working on a Word doc on your Windows PC while another member of the household watches a movie via Plex? If the answer is "yes" then you will be looking to run Windows as a VM and your hardware will have to support virtualisation for it to work (i.e. you might want to clarify what other hardware you have before proceeding). If the answer is "no" then you can choose between dual boot (dual boot = booting either Win OR Unraid any one time - yes confusing terms) or use VM. What you have described in your reply is a dual boot AND VM scenario which is OK. Just be mindful that repeated booting between VM and baremetal MAY cause Windows to ask you to reactivate. It's hard to say if x GB is enough for cache without knowing what exactly will be stored on the cache. 250GB is generally sufficient as cache if all you do is docker, appdata, libvirt and light write activities. If you are downing multiple 50GB+ Linux iso's simultaneously then obviously 250GB isn't enough. For Windows, 1TB NVMe is generally enough for most uses. Ask yourself if you actually need 1.25TB instead of 1TB? "Certified Frustration-Free Packaging" = cardboard envelope. Padding is entirely optional. You don't need 3 drives to have a parity. You have 2 drives with 1 parity and 1 data.
  13. What you are asking for is a DOS era implementation. Modern HDDs firmware has been effectively doing with this for quite some time now (e.g. reallocate bad sectors to good spare ones and thus preventing uses of these bad sectors). If your HDD has bad sectors, it is usually an indication that it is failing though. So you will want to watch the count and if it's steadily increasing, replace your HDD (with urgency). I personally replace a HDD as soon as any bad sector is detected.
  14. @Can0nfan: You probably want to post in the Feature Request instead. Based on a recent what new feature do users want poll though, I don't think >2 parity is on the LT new feature roadmap. (multiple array is on the roadmap).
  15. Are you planning to run Windows VM or Windows barebone (i.e. dual-booting i.e. EITHER Win or Unraid at any time)? If you are running Windows VM, then you can use the 250GB SSD as cache and pass through the NVMe as a PCIe device (i.e. similar to passing through a GPU) for best performance. Save you having to buy another drive for cache and the 250GB is better off used for Unraid purposes (e.g. appdata, docker, libvirt, temp storage etc.). For most users with modern HDDs, there's really no need for a cache drive to enhance write speed (e.g. you can use reconstruct drive aka "Turbo Write" to write to you array at close to the max write speed of your HDDs). IF you still want to buy another SSD for cache then get SATA unless you are out of SATA ports (obviously). Outside of extremely niche uses (e.g. massive db webserver), I have not seen any perceivable diff between SATA and NVMe for Unraid cache. In terms of HDD choices, buy the cheapest you can get from a reputable dealer who are familiar with shipping HDDs (e.g. Amazon is a reputable dealer BUT they are NOT familiar with shipping HDDs e.g. they sent me a HDD in a cardboard envelope without padding recently). Brands / models don't matter with consumer home uses. To use as backup server, 7200rpm is only necessary if you have a ton of tiny files. 5400rpm is generally good enough (and will be less noisy and should consume a tiny bit less power). Also, you are better off getting 2x8TB instead of 3x4TB. (a) fewer points of failure, (b) based on Backblaze data, newer large capacity drives e.g. 8TB+ seem to have better reliability than old low-capacity drives and (c) relatively easier future expansion of the array.
  16. Yes both will run at x8 No it will not affect gaming performance with your GPUs.
  17. 2-games-1-PC is relatively easy to do with Ryzen. You might want to make your life easier with Threadripper for a 3-gamers-1-PC build. X570 motherboards have at most 3 PCIe x16 slots and the bottom most one will cover up the internal IO (you just need to have a look at a X570 motherboard picture to understand what I mean). So assuming you can pass through all 3 (the bottom one will certainly need ACS Override), case choice and PC building finesse will be important. 4-gamers-1-PC = definitely need Threadripper. You need to leave core 0 free for Unraid so whatever the core counts of your CPU, what is practically available for VM is n-1. You then also need to take into account Ryzen architecture idiosyncrasy with CCX and CCD and latency penalty when crossing CCX / CCD. So the TL;DR: with the 3900X, the best config for gaming is to have 1 full CCX per VM = 3 cores per VM. Something you have not considered for practicality is USB hot-plug-ability. You will not be able to have USB hot plugs for all VM without additional USB cards (even Threadripper only has 2 passthrough-able onboard USB controllers). For some, that may be a show stopper right off the bat.
  18. Marvell controller? The issue came up with 6.7 so you missed all the discussion. Maybe start with reading this:
  19. This is very strange. First time I see this problem. If you think it worked 2 years ago then perhaps give older versions of Unraid a try to hopefully identify when things changed. It can still be downloaded directly from Unraid using the URL e.g. For 6.5.3 it's https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.5.3-x86_64.zip i.e. you just need to replace the version number. 2 years ago, probably is around 6.3.0 - 6.4.0 I highly recommend you backup your current USB stick + config before doing anything. Just in case. (or alternatively use a different USB stick). And don't set the array to auto start. You can check IOMMU without needing to start the array (i.e. to avoid unexpected issues).
  20. Someone asked me for the 12e BIOS for the Gigabyte X399 Designare EX, which has been replaced on Gigabyte website with the buggy 12i version. So here it is attached - original zip file from Gigabyte. mb_bios_x399-designare-ex_f12e.zip
  21. Yes indeed. (don't forget the hyperthreading sisters of the cores).
  22. It's not really a problem in itself. 1909 is generally not (yet) automatically rolled out to the general public. You either have to purposely look for it (e.g. my / your case) or are part of the Windows Insider programme (i.e. early adopters / testers). Due to the bugginess of recent Windows major releases (which even had a major bug causing data loss to some users), some have said it's like Microsoft is experimenting on the brave ones who choose to have an early dip. So 1909 may very well be fine (I personally haven't seen any issue) but the PR damage has been done, so to speak.
×
×
  • Create New...