Jump to content

bigmac5753

Members
  • Content Count

    15
  • Joined

  • Last visited

Community Reputation

0 Neutral

About bigmac5753

  • Rank
    Member
  • Birthday December 19

Converted

  • Gender
    Male
  • Location
    UK
  1. According to previous posts, several people have successfully got it working, I just need a step by step guide as i've followed many suggestions with no success.
  2. Is there an up to date step by step guide to get this working? I've tried all the suggestions in these posts but having no luck.
  3. bigmac5753

    gtx1070 error 43

    If you were to move the monitor over to the card before a VM is started, it's highly likely to move the unRAID console to the card. Doing it after a VM is started should be OK but ideally you should use a dummy plug. Once unRAID has started, there's hardly any need to access the console but if you need to, it can be accessed from the web GUI.
  4. bigmac5753

    gtx1070 error 43

    Yes. Whichever GPU you select in BIOS as primary, unRAID will use that, as long as it has either a monitor or dummy plug.
  5. bigmac5753

    gtx1070 error 43

    Yes any GPU can be used but ideally just a basic one as all it will ever do is display the console. It can run without a monitor but you must use a dummy plug.
  6. bigmac5753

    gtx1070 error 43

    Unraid needs its own GPU for the console
  7. bigmac5753

    VM IGD passthrough

    Can anyone help me passthrough my IGD to windows 10 VM? Specs: MSI Z97 gaming i7 4790K 32GB GT710 in primary slot with dummy for console 1050ti in middle slot for VMs I was using the IGD for console and GT710 for VMs but decided to swap as the IGD is more suited for my needs. In syslinux, i've tried adding append pcie_acs_override=downstream vfio-pci.ids=8086:0c0c modprobe.blacklist=i2c_i801,i2c_smbussnd_hda_intel video=efifb:off,vesafb:off as suggested in another post, made no difference. I've also tried all combinations of seabios/OVMF & i440fx/Q35 but made no difference. Any help would be greatly appreciated.
  8. bigmac5753

    force smaller parity drive

    Shucked the drive, reported size still the same (4,000,787,030,016 bytes). It's allowing me to add it now so an 11 hour wait for parity sync. Thanks guys.
  9. bigmac5753

    Ryzen /Intel iGPU Passthrough

    If you passthrough the onboard GPU you will need a discrete card for the console.
  10. bigmac5753

    force smaller parity drive

    That is the only USB drive. Specs: M/B: MSI - Z97-G45 GAMING CPU: i7-4790K HVM: Enabled IOMMU: Enabled Memory: 32 GB (max. installable capacity 32 GB) Network: bond0: adaptive load balancing, mtu 4000 eth0: 1000 Mb/s, full duplex, mtu 4000 eth1: 1000 Mb/s, full duplex, mtu 4000 Array consists of 4TB, 3TB, 2TB, 1TB spinners. 500GB, 2x 250GB SSD's All connect to m/b or PCI-E SATA card. The only thing I can think of is move all data from 4TB array disk to new disk then use the array disk as parity instead. I'm reluctant to do this due to the wear on the drive and downtime etc... but if the sizes appear to be the same, what's stopping the current array drive being too small for parity.
  11. bigmac5753

    force smaller parity drive

    Thanks for your response, diagnostics attached. In the SMART / identity section, both drives are the exact same size (4,000,787,030,016 bytes) but it will not allow me to use it. The new drive (WD elements) is still in a USB3 enclosure and did not plan on shucking but will if it makes a difference? Thanks server-diagnostics-20181125-1707.zip
  12. bigmac5753

    force smaller parity drive

    Is there a way to force unraid to use a smaller disk as parity? I have a 4TB drive to use as parity in my array with the largest disk being 4TB but unraid says the parity drive is too small. I assume the "smaller" drive will be off by a few bytes or kilobytes or whatever which i'm not really fussed about. If the worst happens and I lose a few kilobytes it's not the end of the world.