slipstream

Hawihoney, Thank you very much for your post. If I compare my initial test path I posted in my very first post at the top to the example path you posted they seem to have this much of the path text in common: "/dev/disk/by-id/ata-" Below is a side by side comparison - My PATH Tests: /dev/disk/by-id/ata-WDC_WDS100T2B0C-00PXH0_21146D802780 (nvme0n1) /dev/disk/by-id/ata-WDC_WDS100T2B0C-00PXH0_21146D802780 Your PATH Example: --> /dev/disk/by-id/ata-HGST_HUS724020ALA640_PN2181P5H1E36X I suspect the reason I got the error shown below after hitting the CREATE button in the ADD VM form is because I hit the MOUNT button on my Unassigned Devices app for the NVMe device it shows after I performed a XFS format on it. Nevertheless, it is good to know there is no need to apply a checkmark to IOMMU Group 44 shown above in a YELLOW box and I will try again on Friday and hopefully by unmounting my NVMe device from my Unassigned Devices App I will not get the error shown below. After I am done with some further testing I will update this thread with what I learn so others in the community with this same problem can learn from thread in the future.

Thank you to all for your help. TomK1412, Below is a screenshot of my System Devices IOMMU list. Inside the YELLOW box is my NVMe device. Just to confirm I understand you correctly. To successfully PassThrough my NVMe and load it with a LinuxMint.iso image I first need to apply a Checkmark and then hit the "Bind Selected to VFIO At Boot" button and reboot my server. I then need to manually add my own version of your XML code shown below so that my VM boots correctly. What numbers shown in the YELLOW box above do I paste into your XML code below so I can make it my own? <boot order='1'/> <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> Nevertheless, what is not yet clear to me is once I add my custom XML code does it cancel out the need to manually add a path to "Primary vDisk Location" parameter shown below circled in RED? In short, it's still not clear to me where in the UnRaid OS can I see the NVMe path I need to copy and paste into the "Primary vDisk Location" parameter shown below circled in RED? SimonF, I'm not adding my NVMe device via my Unassigned Devices app therefore the path: /mnt/disks does not apply. Additionally, I'm not adding my NVMe device via a pool so the path: /mnt/pool name also does not apply. The answer is I am adding my NVMe device as a passthrough to mount a LinuxMint.iso image to run as a VM. Do you know what is the path I need to paste into the RED circled parameter shown above? itimpi, Regarding the brackets found in this text string: (nvme0n1) I tried the path with and without (nvme0n1) and both versions were rejected by the UnRaid OS.

Hi All, Where in Unraid OS (v 6.9.1) do I go to so I can see the Location PATH for a NVMe drive I have installed on the PCI slot using a NVME adapter card? I need to know this because my VM setup vDisk Location parameter is set to MANUAL and now it wants me to enter a path to the NVMe drive. I entered the path shown below and the UnRaid OS rejected it: /dev/disk/by-id/ata-WDC_WDS100T2B0C-00PXH0_21146D802780 (nvme0n1) In short, I need to know where in the UnRaid OS I can see the correct NVMe Path so I can replace the incorrect portion of the path shown below: /dev/disk/by-id/ata- with the correct NVME location path. Any help will be greatly appreciated. Thank you for your time.

Jonathanm, Thank you for your post. The reason I am mounting it using my Unassigned Devices App is because SpaceInvader One In his video linked in the post above is using his Unassigned Devices app and mounting his device. So I'm confused why he is taking that approach. Nevertheless, I will follow your advice and try the following different approach. In my System Devices I 'm going to apply a VFIO checkmark to this device and then hit the BIND button. By doing this my hope is this NVMe device path problem will get fixed. Thank you to all for your time.

Ghost82, Thank you for your post. Let me break it down. SpaceInvader One says the beginning of the path needs to look like this: /dev/disk/by-id/ata- Then it needs to be followed by my NVME id which is: WDC_WDS100T2B0C-00PXH0_21146D802780 (nvme0n1) My Unassigned Devices app confirms the NVMe is MOUNTED as shown in the screen shot above. However, my Unassigned Devices app does not show me a path where my NVMe is at. Also my Unassigned Devices app generates a "(nvme0n1)" text string at the end of the ID. Can somebody please clarify if this text string needs to be included in the path to my NVMe? Lastly, can anybody in the community please clarify for me how this part of the path: /dev/disk/by-id/ata- needs to change so my Unraid OS does not reject it?

Ghost82, Thank you for your last post showing disk speed tests. My parts from Amazon arrived on Saturday which are shown in the links below: https://www.amazon.com/Adapter-advanced-solution-Controller-Expansion/dp/B07JKH5VTL/ref=pd_sbs_4?pd_rd_w=lZeD3&pf_rd_p=98101395-b70f-4a52-af63-8fac2c513e02&pf_rd_r=RFC1N4DQ7M5CCNPEJ2SB&pd_rd_r=d09706bc-d341-499f-a106-87f369a57164&pd_rd_wg=DY1q6&pd_rd_i=B07JKH5VTL&psc=1 https://www.amazon.com/Blue-SN550-1TB-NVMe-Internal/dp/B07YFFX5MD/ref=pd_bxgy_img_2/141-0873488-7450925?_encoding=UTF8&pd_rd_i=B07YFFX5MD&pd_rd_r=0d5f4af5-81a7-496e-b4e5-23f80df2f905&pd_rd_w=wXlzk&pd_rd_wg=9DKb3&pf_rd_p=fd3ebcd0-c1a2-44cf-aba2-bbf4810b3732&pf_rd_r=782K87JJMREZ3MSC8Q6T&psc=1&refRID=782K87JJMREZ3MSC8Q6T I watched the SpaceInvader One video you posted in your previous post. The screenshot below shows how my NVME app appears in my Unassigned Devices area after I click on the + button: I set my Primary vDisk Location to "Manual" and paste the path shown below which is generates the errors shown below: /dev/disk/by-id/ata-WDC_WDS100T2B0C-00PXH0_21146D802780 (nvme0n1) After I hit the "CREATE" vm button I see the error below: Additionally, removing the "(nvme0n1)" text string located at the end did not help. I still get a path error: Ghost82, can you or anybody in the community please advise what is the correct Manual vDisk Location path I need to use that the UnRaid OS will not reject? I ask because the SpaceInvader One video I watched seems to be about passing through a SSD hard drive and not passing through a NVME drive. The screen captrues below shows my System Devices for my PCI NVME card. So I don't think the problem has anything to do with hardware incompatibility because the UnRaid OS successfully recognizes this NVMe hardware. Any opinions will be greatly appreciated because I am stuck in the mud.

Thank you to all for your posts. I learned something new. I was assuming all three operating systems require being kept separately on different partitions. I never realized all 3 OS images could mingle together on the same NVME SSD partition. So my new plan is to do without setting up 3 partitions and just mount all three images onto a single partition on a new NVME SSD. Thanks for your help.

Hi All, Can the UnRaid OS handle three VMs on a single NVME SSD split as 3 partitions? My plan is to buy a 1TB Samsung 980 NVME SSD which is going to be mounted to a NVME PCI-E adapter card like the one shown in the JPG below. Addtionally, I want to install VMs for the Ubuntu OS, the Windows10 OS and the MacOS on this 1TB NVME SSD. Will the UnRaid OS support such a setup? By looking at my VM Setup Form screen capture below, I realize I may have to change the SATA option to NVME. However, I am not 100% certain how the "Primary vDisk Location" parameter needs to change so it correctly supports such a NVME setup. Mainly, what does the "AUTO" option need to change to so any one of the three operating systems correctly boots up as a VM? And what will the OS installation path look like for each one of the three Operating Systems in such a NVME setup? And will all three of my VM Operating Systems run faster by using such a NVME SSD setup? Any opinions welcome. Thank you for your time.

Thank you to all for your posts. Hopefully, what I have learned in this thread will bulletproof my UnRaid data from any possible future ransomware attack and not have to go through the same hell the poor QNap user shown in the YouTube video below has gone through:

SimonF, Thank you for your post. I have decided to follow the path of least resistance and buy a USB 3.0 PCI-E Adapter Card. It's much more easier to buy such an adapter card and then just pass it through using the VFIO Bind System Devices feature. Thanks for your help.

Hi All, The USB 3.0 ports on my SuperMicro motherboard are dead within my Ubuntu VM. If I plug in a USB stick my Ubuntu VM does not detect it. However, within my UnRaid OS my Unassigned Devices app detects any USB stick when plugged in. The screen shot below shows how I have the USB controller configured in my Ubuntu VM. Can somebody in the community please confirm to me if correctly setting up an Ubuntu VM requires I use the "3.0 Qemu XHCI" option or the "2.0 EHCI" option or the "3.0 NEC XHCI" option? Changing it from Qemu to EHCI killed my Nvidia 1030 passthrough. It no longer works. Lastly, my VFIO list in System Devices has both USB Controller ID numbers checked marked and with GREEN dots displaying. So, why is the UnRaid OS not passing through the USB ports to my Ubuntu VM? I hope somebody can advise me what is the best USB controller option I should use for an Ubuntu VM?Any help will be greatly appreciated. Thank you for your time.

Thank you to all for your post. Sorry for the confusion my bad writing caused. Correct, the UnRaid OS boots from the USB stick. However, my question is really about what order does the UnRaid OS address the PCI slots while it is booting up from the USB stick and loading itself into the RAM. Does the UnRaid OS first recognise the PCI slot closest to the CPU (#3 in my graphic above)? Or does the UnRaid OS first recognize the PCI slot farthest away from the CPU (#1 in my graphic above)? SpaceInvader One in his video only mentions "Primary Slot". So I was left confused what does the UnRaid OS see as the Primary Slot when it is going through its bootup process? Today after work I'm going to move my 710 card over to slot #3 and my hope is the UnRaid OS will recognize it as the first PCI it needs to mount. The problem is really all about how my UnRaid OS is using the wrong card to boot into GUI MODE. It is using the 1030 card and not the 710 card. My theory is because the 710 card needs to precede the 1030 card by moving it to the PCI slot right before the 1030 card PCI slot. Again thanks to all for your post.

Hi All, Below is an illustration of my Supermicro X10SRH-CF motherboard. Can anybody in the community please clarify for me if the UnRaid OS boots from a Left to Right PCI slot order or a Right to Left PCI slot order? Right now the problem is my 710 card is in PCI SLot position #1 however for some reason I don't know the UnRaid OS chooses PCI SLot position #2 as the default GPU to boot from. I do not want it to boot from the 1030 Card. I need my UnRaid OS to choose the PCI slot holding my 710 Card to run as a "Boot To GUI Mode" operation. And I need the UnRaid OS to choose the 1030 card at PCI SLot position #2 for my Ubuntu VM. Will moving my 710 card to PCI SLot position #3 make the UnRaid OS choose the 710 card as the first GPU card to boot from? I hope somebody can clarify this for me because my UnRaid OS is not choosing the correct GPU to boot from. Any advice welcom.

Hi All, I just learned QNap NAS users recently got hit with a ransomware attack. All their data got encrypted and now they have to pay in Bitcoin to get their data back. I have all of my shares set to PRIVATE. Is that safety measure strong enough to protect my data from any possible ransomware attack directed to the UnRaid OS in the future? Should I also disable the FTP and SSH features in my UnRaid OS for extra security? Any opinions welcome.

Hi All, I got a new 710 Nvidia Card and a 1030 Nvidia Card. Is the VBios dump process performed on both cards or only a single card? I'm using the 1030 card to support my Ubuntu VM and I'm using my 710 card to run my UnRaid OS in GUI mode on the same server. My thinking is I only need to perform the Vbios dump on my 1030 card due to how it is functioning as passthrough for my Ubutnu VM and my 710 card is not. However, I would appreciate it a lot if somebody in the Community can confirm if my thinking is correct or wrong. Thank you for your time.

Thank you for the post Tjb_altf4. This problem with my 1030 card dissappearing from my UnRaid OS System Devices list after I addied a 710 card seriously kicked my butt. I spent an entire day fixing this problem. Not sure which of the three approaches listed below fixed the problem: I reset my Supermicro Motherboard BIOS to factory default settings. I deleted the SpaceInvader One VBios dump script. I deleted the data found in the /config/vfio-pci.cfg file located on the Flash drive. The result is shown in the screen capture below. In short, I can now see both my 1030 card and 710 card listed in my UnRaid OS System Devices like it suppose to be. Now I have the ordeal of re-establishing my 1030 card as a passthrough card to support my Ubuntu VM. I plan to re-apply the SpaceInvader One Vbios dump scipt to make that happen. My confusion is how SpaceInvader One in the middle of his video shows he also applies his script to to his 710 Nvidia card. In my case I think I should only apply his script to the 1030 card and not my 710 card. And then after I apply his script to my 1030 card I am going to do what you mention about clicking on the BIND VFIO AT BOOT button after I select my 1030 card. Nevertheless, my question is if it is necessary to apply SpaceInvader One VBios Dump script to both my 710 and 1030 cards? Any advice will be much appreciated. Thank you for your time.

Thanks Squid for the post. You are correct. Using the lspci command gave me a list that matches the System Devices list which includes no 1030 card. As a troubleshooting test I removed the 710 card and after bootup my System Devices correctly shows my 1030 card as shown in screen capture below: However, my 1030 card does not successfully boot the UnRaid OS to GUI mode. it freezes after the last three lines of code appear shown below: overlayfs: upper fs does not support xattr, falling back to index=off and metacopy=off. overlayfs: upper fs does not support xattr, falling back to index=off and metacopy=off. vfio-pci 0000:41:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem In contrast, if I plug in my 710 card my UnRaid OS boots straight into GUI mode without freezing with the three lines shown above. Is it a good idea to delete the /config/vfio-pci.cfg file on the flashdrive? I am guessing maybe the SpaceInvader One VFIO Dump Script I applied has messed up my VFIO-PCI file and maybe if I delete this file it will magically rebuild itself to correctly show two Nvidia cards in my System Devices list. Is this a good idea or bad idea? As for the motherboard BIOS i have the parameters set in the same way they were before I introduced the 710 card. Any opinion welcome. Thank you for your time.

Can somebody in the community please post the UnRaid OS command I need to type into the terminal so I can see a list of the graphic cards I have installed on the motherboard. I need a way of confirming why my UnRaid OS is ignoring my 1030 card which is connected to the 16x PCI-E GPU slot on the motherboard. System Info: SuperMicro X10SRH-CF Motherboard 128GB ECC RAM Intel Xeon E5-2640 v3 CPU UnRaid OS v6.9.2 Nvidia GT1030 GPU passthrough for my Ubuntu VM Nvidia 710 GPU for my UnRaid OS in GUI Mode Noctua Fans Seagate 18TB Hard Drives

Hi All, My System Devices List no longer shows my Nividia 1030 card after I installed a 710 Nvidia card for the purpose of seeing my UnRaid OS in GUI mode on the same monitor connected to the UnRaid OS server machine. My 1030 card was perfectly running my Ubuntu VM after I set it up using the SpaceInvader One Vbios Dump script. The screen capture below shows the 1030 card errors I get in my VFIO PCI log. The ERROR reads: "Vendor:Device #### not found at ####. Unable to bind device." One error is for the GPU and the other error is for the Audio on the GPU. In short, the 710 card has bumped out my 1030 card from my UnRaid OS. What is the correct way to install a 710 Card when there is already a 1030 Card installed on the motherboard to support an Ubuntu VM setup as a passthrough? System Info: SuperMicro X10SRH-CF Motherboard 128GB ECC RAM Intel Xeon E5-2640 v3 CPU UnRaid OS v6.9.2 Nvidia GT1030 GPU passthrough for my Ubuntu VM Nvidia 710 GPU for my UnRaid OS in GUI Mode Noctua Fans Seagate 18TB Hard Drives

I am adding the screen capture below which shows my VFIO PCI Log. The pink errors are associated to my 1030 card which is showing up missing after I installed my 710 card. The ERROR reads: "Vendor:Device #### not found at ####. Unable to bind device." One error is for the GPU and the other error is for the Audio on the GPU. Does anybody in the community have any advice on how I could fix the error below so my 1030 card can come back as a passthrough binded device? Before adding the 710 card my 1030 card was working correctly and I was able to launch my Ubuntu VM remotely from my Windows10 client PC. However, I now seek to no longer use my Windows10 client PC and do it all within the UnRaid OS GUI mode environment which is the reason I have added the 710 card. What is the correct way to install a 710 Nvidia card to the motherboard so the 1030 card installed on the primary PCI 16x slot does not end up dissappearing in the UnRaid OS? My goal is to dedicate the 710 card to support my UnRaid OS in GUI mode and my dedicate my 1030 card to support my Ubuntu VM as a binded passthrough device. Any advice will be greatly appreciated. Thank you for your time. System Info: SuperMicro X10SRH-CF Motherboard 128GB ECC RAM Intel Xeon E5-2640 v3 CPU UnRaid OS v6.9.2 Nvidia GT1030 GPU passthrough for my Ubuntu VM Nvidia 710 GPU for my UnRaid OS in GUI Mode Noctua Fans Seagate 18TB Hard Drives

Hi all, tjb_altf4 thank you for your post. I went to my System Devices area as you advised and I have the following to report. I was not aware of this before making my last post but It looks like adding my 710 card has made my 1030 card dissappear from my System Devices area. I no longer see it listed in System Devices and when I go to my Ubuntu VM it shows the 710 card has taken the place of the 1030 card. This is bad news for me because my Ubuntu VM was working great on my 1030 card setup as a passthrough. I hate to think my Ubuntu VM no longer works due to how my 1030 card has disappeared fromt he System Devices List. The process I followed to add my 710 card is as follows. I added my 710 card by changing the VGA parameter on my Supermicro BIOS to OFFBOARD (ONBOARD is the default). I also disabled the onboard VGA connector by changing the JPG1 Jumper on the motherboard to a disabled position. Can this change I made to my motherboard BIOS and Jumper setting for the purpose of accomodating my 710 card have inadvertantly disabled my 1030 card and caused it to dissappear from my System Devices list? Or is the problem possibly associated to a parameter change I need to make on my UnRaid OS after adding my 710 card which I have yet to make? Currently I have my "PCIEe ACS override" parameter set to "MultiFunction". Is it necessary to change it to DISABLED for the purpose of running two GPUs on a single motherboard? As of right now I have not yet installed the Nvidia Driver because I would like to figure out why my 1030 card has dissapeared from my System Devices List. Any advice will be greatly appreciated. Thank you for your time. System Info: SuperMicro X10SRH-CF Motherboard 128GB ECC RAM Intel Xeon E5-2640 v3 CPU UnRaid OS v6.9.1 Nvidia GT1030 GPU passthrough for my Ubuntu VM Nvidia 710 GPU for my UnRaid OS in GUI Mode Noctua Fans Seagate 18TB Hard Drives

tjb_altf4, Thanks for the help. Just a followup question I hope you or anybody in the community can answer. I have two Nvidia cards. One is a 710 and the other is a 1030. The 1030 is designated for my Ubuntu VM and setup as a passthrough card. And the 710 is designated for my UnRaid OS to run in GUI mode. Is it possible to install this Nvidia driver plugin you mention so it only impacts the 710 card and not the 1030 card? My 1030 card is working great for my Ubuntu VM as a passthrough and I would like to know before I install this Nvidia driver plugin for my 710 card if this driver can be installed on a sever that has two different Nvidia cards without it conflicting with my 1030 card. Any information will be greatly welcome. Thank you for your time.

Hi ich777, I just created the post shown in the link below which relates to 4k resolution support when booting straight into UnRaid OS GUI mode before learning about your plugin: https://forums.unraid.net/topic/107169-boot-to-gui-mode-display-resolution-change/ In short, I have two Nvidia cards installed. My 710 card is dedicated to supporting my UnRaid OS booted into GUI mode. My second card is an Nvidia 1030 which is setup as a passthrough to support my Ubuntu VM. I hope you can clarify the following. My Ubuntu VM is working perfectly and I can see the OS in 4k resolution under my Nvidia 1030 card. However, this is not the case for my 710 card. I have no way to change my UnRaid OS GUI mode resolution to 4k. Will installing your Nviida Driver plugin allow me to see my UnRaid OS in GUI mode at a 4k resolution? And will it be conflict free with my Nvidia 1030 card which is used for my Ubuntu VM?

Hi All, I am using UnRaid OS version 6.9.1 and booting straight into GUI mode on the same stand alone machine. Additionally, I am using an LG 4k Monitor which is connected to an Nvidia 710 card via an HDMI cable and also have an Nvidia 1030 for my Ubuntu passthrough. The problem is my UnRaid OS GUI resolution makes everything on the display appear very big as shown in screen capture below: When I go to the DISPLAY SETTINGS area in the GUI I cannot find any monitor resolution setting that will allow me to see my GUI in a 4k resolution. How do I install an UnRaid OS compatible Nvidia driver that will allow me to view my UnRaid OS GUI in 4k mode? Any tips will be greatly welcome.

Squid, thank you for your post. Fortunately, my LG monitor has an HDMI 1 port and a HDMI 2 port. So it looks like it is a matter of using the SIGNAL selector button on my monitor to manaully switch between HDMI 1 and HDMI 2 source signals. Also I am going to disable the onboard VGA on my SuperMicro Motherboard. Having it enabled is most likely going to cause some kind of problem.