s1l3nce

I just found the culprit! I had to enable VT-d. Intel Virtualization Technology wasn't enough apparently.

I answer myself: Even though I had Intel Virtualization Technology enabled, that wasn't enough. I also had to enable VT-d to have my iGPU available. This is what I see after enabling VT-d:

I know this is an old post but I'm on the same boat, as you can see in my post: Did you ever solve this issue?

Hello everyone! I have moved my Unraid setup to a "newer" system (CPU i5-4690K // iGPU HD Graphics 4600 // Mobo Asrock Z87 Extreme4) and now I no longer have the option to passthrough the iGPU on my virtual machines. I only have "virtual" available. Bear in mind that I have IGPU Multi-Monitor enabled under BIOS settings (apparently, having it on disabled can sometimes be the issue but it's not in my case). On my previous system, although it was even older (i5 3000 series), I was able to passthrough the iGPU. These are my VM settings: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>VM-P2P</name> <uuid>7aea2c8b-18bf-01f9-2104-9005ee0be946</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>2</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='2'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-7.2'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi-tpm.fd</loader> <nvram>/etc/libvirt/qemu/nvram/7aea2c8b-18bf-01f9-2104-9005ee0be946_VARS-pure-efi-tpm.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv mode='custom'> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='2' threads='1'/> <cache mode='passthrough'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/vms/VM-P2P/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <serial>vdisk1</serial> <boot order='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <controller type='pci' index='0' model='pci-root'/> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </controller> <controller type='usb' index='0' model='qemu-xhci' ports='15'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:15:72:b5'/> <source bridge='br0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <tpm model='tpm-tis'> <backend type='emulator' version='2.0' persistent_state='yes'/> </tpm> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='es'> <listen type='address' address='0.0.0.0'/> </graphics> <audio id='1' type='none'/> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </memballoon> </devices> </domain>

I just found out that my board does not support bifurcation. So I will have to use a pair of sata SSDs for the time being.

I'm planing on building my Unraid temporarily with the following hardware until I can upgrade it to something better: - Mobo: Asrock Z87 Extreme4 - CPU: i5-4670K I'm going to use two NVME drives for my cache but this mobo does not have any m.2 ports. So my question is: could I use something like this? Or would it be incompatible or problematic with unraid? If you have a better recommendation, I'm all ears. PS: I'm just watching this video on bifurcation right now because I think I need my mobo to be compatible with bifurcation. I don't know if it is but I'll find out. This is in my Asrock Z87 Extreme4 manual So I guess I could use both the PCIE2 and PCIE4 slots, right?

Oh! Excellent. Thank you very much 🙏

I've tried the optimisations and they seem to work. But now I need to test a few things out and I would like to restore the system to what it was before I applied this optimisation(powertop --auto-tune &>/dev/null). How can I go back to default?

I just had a problem. I rebooted the system and when Unraid loaded back, my array was stopped. I tried to manually restart it and it gave me this error: I've just followed this advise to resolve the issue:

It worked, brother. And, curiously enough, the parity check corrected itself after that without having to do a full parity check. Thanks a lot for all the help 🙏

It's weird because I stopped it every time during this process. It happened after starting the array with only one SSD. Will try your suggestion and report back.

This is what I see on the slot of the last SSD I removed (that now shows as Not Installed) It does not seem to be possible to activate single profile from this menu now.

Hum... this looks weird. I removed the last disk, started the array and then this happened: A parity check started and it says that there is a missing (not installed) disk on the first slot.

And I just got this message on the console Should I proceed with the next disk? Btw, on the first disk removal, I clicked here where it says "balanced" and a percentage showed up. But once the first disk was removed, when I clicked on it again, it did not show any activity, although there was activity between the drives, like I showed in the console.

The array started but the cache drives are showing activity and the console is showing this

Done. You mean stop the array and remove it from the pool? Like this?

My current cache pool looks like this: I would like to convert that pool into a single drive and simply use the 250 GB Samsung SSD. Which steps do I need to follow? PS: It is mostly for the sake of learning; I know that having a redundant cache is ideal. My current Unraid setup is just a testing/learning environment. I want to familiarise myself with everything that I need to know before I move all my data to Unraid. The plan will be to use 2 NVME drives mirrored.

Oh!! Niceee! 👌

I just tried it and doubled my transfer speeds. Awesome stuff 👌

That makes sense. Thanks!

Thanks for the quick reply! So, even though my biggest drive on the array is 6 TB (besides the parity drive), the parity drive has to keep going till the end, right?

Hello! I don't really know how does it work and I have a question about a small observation. My system (currently a test build) is running a parity sync. I have 1 parity drive (10TB) and 2 other disks in the array (6TB and 2 TB). Right now, the parity sync process is at 49% and in the 'read' column, only the 6 TB drive is showing read operations. The 2TB drive is not doing anything atm. I guess this is normal? I even tried to spin it down and it stopped, so I'm guessing that the parity sync process has finished with that disk, right? PS: Where can I find detailed information about the inner workings of the parity check? I would like to have a better understanding.

It would be very helpful to have a search functionality on the WebUI. The forum is packed with posts of people asking questions to find certain options (I know because that's how I'm finding them; by searching in the forum 😂).

Sorry for resurrecting this but what does the 50 mean? Because the boot splash screen does not stay for 50 seconds by default. edit: I respond myself. "The timeout value is in tenths of a second. The default is 50, or five seconds." So a timeout 1 would mean 0.1 seconds and not 1 second. For 1 second I should write timeout 10 Sorry for my lack of linux knowledge

I've been using Virtualbox and Proxmox for a while and having snapshots is a must have for virtualisation. Not having it on Unraid is not a deal-breaker but it's a bit frustrating.