slipstream

Members
  • Posts

    130
  • Joined

  • Last visited

Posts posted by slipstream

  1. Hi All,

    I updated my OS to the latest 6.11 version and now my CA Fix Common Problems plugin app is prompting a Jumbo Frames Warning shown in the screen capture below.  What makes no sense to me is I do not have a "eth2" interface.  I only have the two ethernet interfaces shown below which are "eth0" and "eth1" (no "eth2" to be found).  And I only use "eth0" and the "eth1" interface is disabled.  Additionally, my "eth0" "Desired MTU" parameter is set to 1500 and not 9000.  So why do I get this error?  Before I click on the IGNORE WARNING button I  would like to know what is causing this warning to appear.  Any info welcome.

     

    Warning.png

     

     

     

     

    Desired MPU.png

     

  2. Squid,
    Thank you for your post.  Your advice pointed me in the right direction to where I eventually was able to solve this problem.  

     

    I looked at the Unassigned Devices GUI located in the MAIN tab.  I clicked on the GEAR icon and found no mount parameter to where I could change the path. I also clicked on various other Unassigned Devices icons and the result was the same. I couldn't find any parameter where one is allowed to change the NVME path.  

     

    So my focus changed to UnRaid's VM tab where it is possible to edit the Ubuntu template. In the Ubuntu template there is a parameter where I was able to make the change shown below:


    OLD PATH:
    /mnt/disks/WDC_WDS100T2B0C-0...._21146D8...../lnxdsk.img


    NEW PATH:
    /mnt/disks/21146D8...../lnxdsk.img

     

    After making this change my Linux Mint VM now fires up perfectly without any errors.


    Now the million dollar question I have is why did Unassigned Devices autonomously change the path to my NVME drive?  I never got any notification of this change and I would have appreciated such a notification because it was a big head ache to fix this problem. Is there anything I could do that will lock my Unassigned Devices configuration to prevent such changes from being done in the future without my knowing about it?  

     

    Any tips welcome and thank you for your time. 

     

     

  3. Hi All,

    The Execution Error started appearing out of no where.  This error pops up anytime I try to launch either my Linux Mint VM or my Win10 VM which are mounted to a 1TB NVME stick as shown in the screen captures below.

     

    My NVME Win10 VM was successfully working for the longest time configured to the path below:

    /mnt/disks/WDC_WDS100T2B....._2114...../win10disk.img

     

    And my NVME Linux Mint VM was successfully working for the longest time configured to the path below:

    /mnt/disks/WDC_WDS100T2B....._2114...../lnxdsk.img

     

    In my Libvirt.txt Log Diagnostics file I downloaded it mentions a "virStorageFileReportBrokenChain:5178".  I suspect it is a clue as to why I lost access to my VMs. Does anybody know what does a "virStorageFileReportBrokenChain:5178" mean?

     

    More Disk Log Information is shown in the screen capture below as well.  I don't understand why it shows the word "DISCARD" in this line of code: 

     

    discard '/dev/nvme0n1p1' 

     

    Should I interpret this to mean my Unraid OS  for some crazy reason has discarded my the NVME drive which contains the img files for both of my VMs? How can I confirm if this is really the case? Is there a logical troubleshooting work flow I can follow that will help get to the bottom of this problem?

     

    Any help will be tremendously appreciated.  I would really like to know if this problem is fixable.  I would hate to erase the NVME stick and start from scratch all over again building my two VMs.   Thank you for your time.

     

     

     

     

     

     

     

     

  4. On 12/31/2021 at 6:34 PM, Squid said:

    Can you still reach the webGUI from another system?  Post your diagnostics

     

     

    Squid,

    Thank you for the tip.  I have my UnRaid box setup to bootup using the "UnRaid OS GUI Mode".  Therefore, it did not cross my mind to reach the UnRaid webGUI from another system connected to my home network. In short, I was able to get access to the Plugins tab and the screen capture below shows the Nvidia plugin prompting a problem I have boxed in YELLOW:

     

    image.thumb.png.8026e934d58fe737e3214375c317710f.png

     

    It has auto-upgraded itself to v495.46.  So I changed it to Production Branch v470.94 and then rebooted the machine. That fixed the problem! Thank God everything got back to the way it was working 3-4 months ago which was the last time I fired up the machine. 

     

    The lesson I learned here is to not have the Nvidia driver set to the LATEST option.  I need to figure out how I can LOCK my Nvidia driver to the Production Branch option so it no longer auto updates.  This way one can avoid such Nvidia driver headaches.

     

    Again, thanks a lot for your help.

  5. Hi All,

    I powered up my UnRaid box after 3-4 months of having it powered down.  While bootup I noticed plugins were updated.  In short, the bootup process came to a dead stop after the error below appeared:

     

    Modprobe: Error: could not insert 'nvidia': no such device

     

    This is the first time I see this error.  My theory is the Nvidia Plugin shown in the link below got updated during the bootup process to a new version which has caused this error to appear.

     

    https://forums.unraid.net/topic/98978-plugin-nvidia-driver/?tab=comments#comment-913250

     

    Is my theory correct?  Or incorrect?  If correct, I would be grateful if somebody in the community helps me with any information that will help me fix this Nvidia Modprobe Error. RIght now I am unable to boot to the UnRaid GUI screen.

     

    I'm able to successfully login into the "Root@Tower:~#"  prompt and type in UnRaid commands.  What is the best UnRaid command I can type into the "Root@Tower:~#"  prompt for the purpose of diagnosing this problem and ultimately fixing it? I'm using a 1030 Nvidia Graphics Card for VMs and a 710 NVidia Graphics Card for the UnRaid OS.  What troubleshooting can I perform to determine which of the two Nvidia cards is causing this error to appear? 

     

    Any advice or opinions welcome because my UnRaid box has essentially become bricked.  Thank you for your time.

     

    Below is my configuration:

    UnRaid OS = v6.9.2

    Supermicro X10SRH-CF Motherboard /  XEON CPU

    1030 Nvidia Graphics Card (VM Pass Through and dumped Vbios using SpaceInvaderOne dump script)

    710 NVidia Graphics Card (For UnRAID OS)  - It shows me the boot process but fails to show UnRaid GUI because Modprobe error appears.

    NVMe PCI-E Card with a 1TB stick to house Linux Mint OS and Windows10 OS VMs. 

    USB Controller Card (Pass Through for VMs)

    Marvell SATA Controller Card (Pass Through for VMs)

     

     

  6. Hi All,

    My UnRaid array stores thousands of video titles and it is setup with both a Linux Mint VM and a Windows10 VM.  I need advice on which Video Manager app meets my needs on either a Linux Mint or Win10 platform?  I need an app that will allow me to tag video titles to multiple custom categories of my choosing.  For example, I got a 60 minute training video called "Keto Dieting".  For this video I would like to assign tags to it such as "Diets", "Diabetes", "Cooking Recipes", "Health", and "Smoothies".  What is the best app that allows you to assign such categories to a video using the most user friendly approach and not some complicated approach that takes a lot of time?  In short, I want to spend the least amount of time possible assigning video titles to custom categories of my choosing.   Any advice welcome.

  7. 12 hours ago, tjb_altf4 said:

    The VM editor hides hardware no longer connected, but this is a PITA when you try and remove missing hardware from the config as you found out, the VM will fail to start if configured hardware is not available.

    You need to go into the XML view and remove that section yourself to clear it, save, then try adding the mouse after.

    Thanks to all for your postings. tjb_alt4 can you please clarify what you mean with PITA?  Not familiar with this acronym.  I will try what you advise. I'm going to go into the XML for the Windows10 VM and manually remove the 222:3061  then SAVE the change. Then disconnect the Vertical 2 mouse and plugin the Vertical 5 mouse followed by rebooting the Windows10 VM.  Hopefully, this will fix my problem.  Thanks again.

  8. Hi All,

    I am using an old Evoluent Vertical 2 mouse in my Windows VM and it's identification number is: 2222:3061 as shown below. I now purchased a new Evoluent Vertical 5 Mouse and I honestly thought changing something as basic as a mouse in my Windows VM was going to be as easy as unplugging the old mouse and plugging in the new one. Nevertheless, UnRaid gives me an error message that reads "Can't find USB device 2222:3061 when I plug in the new Evoluent Vertical 5 Mouse.

     

    What is the correct way to perform a Mouse upgrade to my Windows VM so the 2222:3061 ID number changes to the correct new Mouse ID number? I have gone to my Windows 10 VM template and I do not see a place where I could update the Mouse identification number. I hope such a hardware change does not mean I have to reinstall my entire Windows 10 VM all over again from scratch because that would be a lot of work.  Any advice will be greatly appreciated.

     

    image.thumb.png.605238a4e90f8f57183a02ee40b3dbff.png

  9. Hi All,

    I have a lot of folder names to change in my MOVIE share. Below is a change example of what I am contemplating:

     

    FOLDER NAME BEFORE CHANGE:   Close_Encounters_Of_The_Third_Kind

     

    FOLDER NAME AFTER CHANGE:   CLOSE ENCOUNTERS OF THE THIRD KIND

     

    Is there an UnRaid Rename App Plugin that is easy to use that can batch rename a bunch of folders as shown in example above?

     

    If no, what is the best open source easy to use Windows 10 Rename App I can install onto my Windows VM and make the batch folder name changes from my Windows VM to my MOVIES share? 

     

    Lastly, does PLEX prefer I replace all folder name underscore "_" symbols with blank spaces? Or does PLEX prefer I leave the underscore "_" symbols as is?  Or is it better to use periods "." between all words that make up a folder name? 

     

    Any advice welcome. Thank you for your time.

     

  10.  

     

    Hi All,

    After watching the SpaceInvader One video in the YouTube link below:

    https://www.youtube.com/watch?v=jjkaidlZmgs

     

    I orderered from Amazon the exact same Samsung 32GB flash drive he recommends in his YouTube video.

     

    I then followed the steps shown in the SpaceInvader One YouTube video in the link below to mount the ZIP backup to my new Samsung 32GB flash drive:

     

    https://www.youtube.com/watch?v=NEkgAhFI_GM

     

    Unfortunately, I hit a brick wall with the Unraid USB FLash Creator getting stuck at "Syncing file system" as shown in JPG below:

     

    image.png.05983545c7735a6bb6d3835eb02a56aa.png

     

    Long story short, I had to spend a lot more time completing this simple task due to SpaceInvader One making no mention of this stuck on "Syncing file system" problem on any of his two YouTube videos shown in the two links above.  I find such erroneous information from SpaceInvader One to be totally counter productive. Doesn't he test his videos?

     

    Fortunately, what ended up working for me is shown in the YouTube Video link below:

    https://www.youtube.com/watch?v=NEkgAhFI_GM

     

    Lastly, I wish LimeTech would update their USB Flash Creator app so it supports the 32GB USB Flash drive SpaceInvader One recommends upgrading to.  

     

    Just my two cents.

     

     

     

     

  11. Hi All,

    I am running Linux Mint as a VM and have encountered a problem with my mouse and keyboard going dead. The fix is to disconnect the Mouse and Keyboard from the USB ports dedicated to the UnRaid OS and connect these two devices to the PCI USB controller card pass through I have setup for my Linux Mint VM.  After I do this my mouse and keyboard come alive within my VM.

     

    Can anybody in the community please clarify if the following assumption is correct or incorrect.  Am I correct to assume a Mouse and Keyboard can be shared across both the host UnRaid OS and a Linux Mint VM?  Or do I need to have one Mouse/Keyboard set for the host UnRaid OS and a separate Mouse/Keyboard set for my Linux Mint VM?

     

    In other words, does a VM by default designed to use the same Mouse/Keyboard the host Unraid OS system uses or does it require it's own Mouse/Keyboard devices ?   ANy opinion welcom and thank you for your time.

     

     

  12. Hi All,

    My VM mouse and keyboard locks up after I connect an external MyBook Hard Drive to a USB port that is part of a USB controller PCI card I added as a pass through. I have to FORCE STOP the VM so that I can work around the LOCKED VM and shut it down. 

     

    Does such a problem mean I have a defective PCI USB Controller card?  This card was working nicely and now it is not.  My plan is to move the USB Controller card to a different PCI slot but I just wanted to know if such a LOCKED VM problem is a strong indicator of a commonly known problem relating to passing through a PCI USB Controller Card. Thank you for your time.

  13. Jonathanm,

    THank you for your post. I am following the 11 steps under the "Data DIsks" section. The clearing process is going to take around 12 hours. After that is done I will format the disk  and then add it to my Movies Share.

     

    Lastly, my Movie Share three drives were originally set to HIGH WATER and each drive indicates 80% full.  Is it too late to change it from HIGH WATER over to FILL DISK after I add the new drive to the MOVIE Share?  I kind of regret having chosen HIGH WATER and not FILL DISK from the beginning. Now I'm wondering if making such a change will cause data corruption.  Any opinion welcome.  Thank you for your time.

     

     

  14. Hi All,

    I need to add more hard disk space to my Unraid Movie Share. So I purchased a new 10TB hard drive which matches the size of my parity drive.  Listed below are the steps to adding a new hard drive to a SHARE as I understand them in my mind:

     

    1. Connect New SATA drive to SATA cable and Power cable.
    2. Preclear Drive.
    3. Format Drive.
    4. Assign new disk to Movie Share
    5. Run Parity Check so new drive gets added to parity drive.

     

    Regarding STEP 5.  Is it necessary to perform a Parity Check?  I ask because performing a parity check takes a very long time. Some where close to 2 whole last time I ran a Parity Check.  I hope somebody in the community can look at my five steps and let me know what I am leaving out.   Any opinions welcom. Thank you for your time.

     

     

  15. Ghost82,

    Thank you for your post.  It blows my mind the rabbit hole the error I got can take me down into.  I saw your link and my hat is off to you because that is some seriously complicated stuff.  🙂  At a basic level, I used the Windows 10 Template to build my Windows 10 VM.   And this template has i440fx as a default. 

     

    Do you think it is possible the UnRaid Developers could offer a Q35-5.1 version of the Windows10 template at some point in the future? 

     

    I honestly think a  Q35-5.1. Windows 10 template would have probably supported my Optical Drives with no complications in the beginning.

  16. Ghost82,

    Thank you for your two posts.  I very much liked your suggestion relating to changing my Windows 10 VM from i440fx to Q35-5.1.  The reason is because my Linux Mint VM is setup with Q35-5.1 and as I mentioned earlier all four Optical Drives work perfectly in my Linux Mint VM.  So I thought it was worth a shot to make this change to my Windows 10 VM.  However, when I clicked on the "UPDATE" button to save my change to Q35-5.1 I got the error shown below:

     

     

     

    image.png.14e841d7a792e9223767e9e26e58ba62.png

     

     

    I can't make heads or tails of the Description for the ERROR.  It is not clear to me if the PCI controller mentioned in the ERROR is actually my Marvell SATA Controller Card. Nevertheless, I clicked on the OK button and by doing this it prevents me from saving the Q35-5.1 change I made to my Windows10 VM.  That was a dissapointment.

     

    However, I decided to try out a different strategy which was to re-arrange how the Optical Drives connect to the Marvell SATA Controller card.  This card has a total of 8 SATA ports.  So I disconnected and reconnected 4 of the SATA cables to different SATA ports on the Marvell card.  After rebooting the server and firing up my Windows 10 VM I was pleasantly surprised to learn all four of my Optical Drives now work correctly.  My guess is the Marvell driver update I made to the latest version required I disconnect and reconnect the SATA cables to different SATA ports on the card.

     

    In short, I'm glad the solution to this problem did not involve buying a different SATA controller card as I was close to doing.  Again, thank you very much for your help with this matter.  I hope this thread helps an UnRaid Community member in the future experiencing a similar problem with Optical Drives and PCI-e SATA Controller Cards. 

     

     

     

     

     

     

     

     

  17. Ghost82,

    Thank you for your post.  To answer your question. Yes, I already installed various versions of the Marvell drivers. In fact, I already visited the TenForums.com link you provided yesterday evening.  I downloaded the Marvell_SATA_V1.2.0.1047 - Windows 10. ZIP file and it did not fix the problem. After more research I found a Marvell_SATA_V1.2.0.1049  version and this did not fix the problem either.  The tsstcorp drive you mention also does not work. It is a Samsung Optical Drive and even though it is missing a YELLOW triangle it does not recognize a DVD disk when I put one in the tray. 

     

    I think the problem is the three Marvell drivers I have tested are too old. The newest one I think goes back to 2013.  This is why I was asking in my original post if anybody in the community knows what is the best SATA controller card chipset I can use that will work in both Linux and Windows10 VMs? I have tried cards with Marvell and AsMedia Chipsets and they work for Linux but not for my Windows VM.  The only device connected to the Marvell SATA controller card that actually works in my Windows VM is my Samsung SSD drive. 

     

    I don't understand why my Windows 10 VM recognizes my Samsung SSD drive but blocks all four physical Optical Drives.  The reason I need all four Optical Drives is because I have several hundred DVD titles I want to archive onto my UnRaid array.  This task will go a lot faster if I used 4 Optical drives compared to a single Optical Drive.  My plan was to dump all of the DVD disk data to the Samsung SSD and then move it over to the Array.

     

    Good to learn the IDE / SATA / SCSI parameter settings I mentioned in my second post only impacts the Virtio drive and not the physical Optical Drives I have installed.  That information you provided allows me to remove these parameter settings from my troubleshooting list.  I honestly thought it was the probable cause to my problem. 

     

    To answer your other question, the Marvell controller draws power from the PCI slot. I have not noticed any power port connector on the card.  And swapping the the TSSTCORP Samsung Optical drive with the ASUS Optical Drive is something I have not done.  I will try it out even though the SAMSUNG Optical drive is not working either.

     

    I have confirmed the Marvell Driver is present but I need to do further poking around to see if Windows10 driver is over writing it. 

     

    For right now I'm going to buy my third SATA controller card. However, this one is going to have a JMB585 Chipset.  Hopefully, this will fix the problem.   Thank you for your help.

     

     

  18. Just a follow-up.   I learned a new UnRaid Terminal Command which is "lsscsi". This command is suppose to list all of the SCSI devices installed in the server.  Below is the output and from what I see it's a list of all my ARRAY hard drives plus my VM NVMe stick ( WDC WDS100T2B0C-00PXH0__1 ).  Is it possible my NVMe stick is causing my Windows 10 to mistakenly see my Optical Drives as SCSI devices? 

     

    Additionally, do you think using a Blacklisting approach targeted to my Marvell SATA Controller could enable Windows 10 to see the Optical Drives correctly?   Thank you for your time.

     

     

    root@tower:~# lsscsi
    [0:0:0:0]    disk    Lexar    USB Flash Drive  1100  /dev/sda 
    [1:0:0:0]    disk    ATA      WDC WD101KRYZ-01 1H01  /dev/sdb 
    [2:0:0:0]    disk    ATA      WDC WD101KRYZ-01 1H01  /dev/sdc 
    [3:0:0:0]    disk    ATA      ST14000NM0008-2H SN02  /dev/sdd 
    [4:0:0:0]    disk    ATA      ST14000NM0008-2H SN02  /dev/sde 
    [5:0:0:0]    disk    ATA      ST14000NM0008-2H SN02  /dev/sdf 
    [6:0:0:0]    disk    ATA      ST14000NM0008-2H SN02  /dev/sdg 
    [7:0:0:0]    disk    ATA      ST14000NM0008-2H SN02  /dev/sdh 
    [8:0:0:0]    disk    ATA      ST14000NM0008-2H SN02  /dev/sdi 
    [9:0:0:0]    disk    ATA      ST14000NM0008-2H SN02  /dev/sdj 
    [10:0:0:0]   disk    ATA      ST14000NM0008-2H SN02  /dev/sdk 
    [11:0:0:0]   disk    ATA      ST14000NM0008-2H SN02  /dev/sdl 
    [11:0:1:0]   disk    ATA      ST14000NM0008-2H SN02  /dev/sdm 
    [11:0:2:0]   disk    ATA      ZA960NM10001     2147  /dev/sdn 
    [N:0:1:1]    disk    WDC WDS100T2B0C-00PXH0__1                  /dev/nvme0n1

     

  19.  

    Ghost82,

    Thank you for your email.  To answer your question I have not added a SCSI controller neither as hardware or software. Also it is news to me that Windows only sees SCSI drives. If that is the case shouldn't the Driver for my Marvell SATA controller card take care of this?  In short, I don't understand why my Windows 10 Device Manager window shows theses Optical Drives as SCSI CdROM devices if in the CDRom Bus parameters shown below show I selected the "IDE" option:

     

    image.png.dedefe57be69c065c9e57b139a296a1f.png

     

    Additionally, the drop down menu below shows "SCSI" as one of the parameter options to pick from but I selected "IDE" instead. Do you think these parameters are associated to the reason why my Optical Drives show as SCSI CdROM devices in my Windows 10 VM?

     

    image.png.d0e778f2608cc356eea572d645aad8dd.png

     

     

    Below is my Windows VM XML you requested.  I hope this XML reveals what the problem could be:

     

    <?xml version='1.0' encoding='UTF-8'?>
    <domain type='kvm'>
      <name>Windows 10</name>
      <uuid>8a6af88a-6985-45fd-2154-b44ce6ace238</uuid>
      <description>Win10</description>
      <metadata>
        <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/>
      </metadata>
      <memory unit='KiB'>33554432</memory>
      <currentMemory unit='KiB'>33554432</currentMemory>
      <memoryBacking>
        <nosharepages/>
      </memoryBacking>
      <vcpu placement='static'>16</vcpu>
      <cputune>
        <vcpupin vcpu='0' cpuset='4'/>
        <vcpupin vcpu='1' cpuset='16'/>
        <vcpupin vcpu='2' cpuset='5'/>
        <vcpupin vcpu='3' cpuset='17'/>
        <vcpupin vcpu='4' cpuset='6'/>
        <vcpupin vcpu='5' cpuset='18'/>
        <vcpupin vcpu='6' cpuset='7'/>
        <vcpupin vcpu='7' cpuset='19'/>
        <vcpupin vcpu='8' cpuset='8'/>
        <vcpupin vcpu='9' cpuset='20'/>
        <vcpupin vcpu='10' cpuset='9'/>
        <vcpupin vcpu='11' cpuset='21'/>
        <vcpupin vcpu='12' cpuset='10'/>
        <vcpupin vcpu='13' cpuset='22'/>
        <vcpupin vcpu='14' cpuset='11'/>
        <vcpupin vcpu='15' cpuset='23'/>
      </cputune>
      <os>
        <type arch='x86_64' machine='pc-i440fx-5.1'>hvm</type>
        <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
        <nvram>/etc/libvirt/qemu/nvram/8a6af88a-6985-45fd-2154-b44ce6ace238_VARS-pure-efi.fd</nvram>
      </os>
      <features>
        <acpi/>
        <apic/>
        <hyperv>
          <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='8' threads='2'/>
        <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/disks/WDC_WDS100T2B0C-00PXH0_21146D875690/win10disk.img'/>
          <target dev='hdc' bus='virtio'/>
          <boot order='1'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
        </disk>
        <disk type='file' device='cdrom'>
          <driver name='qemu' type='raw'/>
          <source file='/mnt/user/isos/Windows 10/Win10_21H1_English_x64.iso'/>
          <target dev='hda' bus='ide'/>
          <readonly/>
          <boot order='2'/>
          <address type='drive' controller='0' bus='0' target='0' unit='0'/>
        </disk>
        <disk type='file' device='cdrom'>
          <driver name='qemu' type='raw'/>
          <source file='/mnt/user/isos/virtio-win-0.1.190-1.iso'/>
          <target dev='hdb' bus='ide'/>
          <readonly/>
          <address type='drive' controller='0' bus='0' target='0' unit='1'/>
        </disk>
        <controller type='usb' index='0' model='qemu-xhci' ports='15'>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
        </controller>
        <controller type='virtio-serial' index='0'>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
        </controller>
        <controller type='pci' index='0' model='pci-root'/>
        <controller type='ide' index='0'>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
        </controller>
        <interface type='bridge'>
          <mac address='75:67:00:45:8a:50'/>
          <source bridge='br0'/>
          <model type='virtio-net'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x02' 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='mouse' bus='ps2'/>
        <input type='keyboard' bus='ps2'/>
        <hostdev mode='subsystem' type='pci' managed='yes'>
          <driver name='vfio'/>
          <source>
            <address domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
          </source>
          <rom file='/mnt/user/isos/vbios/1030vm1.rom'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
        </hostdev>
        <hostdev mode='subsystem' type='pci' managed='yes'>
          <driver name='vfio'/>
          <source>
            <address domain='0x0000' bus='0x03' slot='0x00' function='0x1'/>
          </source>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
        </hostdev>
        <hostdev mode='subsystem' type='pci' managed='yes'>
          <driver name='vfio'/>
          <source>
            <address domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>
          </source>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>
        </hostdev>
        <hostdev mode='subsystem' type='pci' managed='yes'>
          <driver name='vfio'/>
          <source>
            <address domain='0x0000' bus='0x07' slot='0x00' function='0x0'/>
          </source>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/>
        </hostdev>
        <hostdev mode='subsystem' type='usb' managed='no'>
          <source>
            <vendor id='0x03f0'/>
            <product id='0x164a'/>
          </source>
          <address type='usb' bus='0' port='1'/>
        </hostdev>
        <hostdev mode='subsystem' type='usb' managed='no'>
          <source>
            <vendor id='0x2222'/>
            <product id='0x3061'/>
          </source>
          <address type='usb' bus='0' port='2'/>
        </hostdev>
        <memballoon model='none'/>
      </devices>
    </domain>

     

     

    Below is a list of the cards I have installed onto my SuperMIcro Motherboard:

    1. A NVMe PCI-E Card with a 1TB stick I have partitioned with your help to install three operating systems. 
    2. A 710 NVidia Graphics Card (For UnRAID OS)
    3. A 1030 Nvidia Graphics Card (Pass Through for VMs)
    4. A USB Controller Card (Pass Through for VMs)
    5. A Marvell SATA Controller Card (Pass Through for VMs)

     

    I don't think any of these cards can be considered SCSI Controller cards.

     

    The screen shots below show how my Marvell card appears in the Systems Devices area. 

     

    Below is how my Marvell SATA controller appears without a Checkmark applied. With no checkmark applied it does not appear in neither of my VMs:

    image.thumb.png.9f6a4e5ecd706a1613c345cd7db7d959.png

     

     

    However, after I apply a Checkmark then hit the BIND button and reboot the server the Optical drives work for my Linux VM but not for my Windows 10 VM due to how Windows 10 sees them as SCSI CDRom devices:

     

    image.thumb.png.785aa87c78b677f6e5b91d85e421ae22.png

     

    Again, thank you for your help and I hope this is the last brick wall I encounter in setting up my VMs.  

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

  20. Hi All,

    I am running the latest Unraid version and have both a Linux Mint VM and a Windows 10 VM configured. The problem is my Optical Drives work perfectly in my Linux Mint VM.  However, in my Windows 10 VM the Optical drives fail to work. As shown below my Device Manager window shows the Optical drives with yellow triangle warnings.  And the  PROPERTIES window for one of the drives reads: " The device cannot start (Code 10) STATUS DEVICE POWER FAILURE."

     

    image.thumb.png.efb1771f2403f0d9c08b760a3b91cffb.png

     

    The SATA Controller card I am using has a Marvell 9512 chip. It also has a Marvell_SATA_V1.2.0.1049 - Windows 10. driver installed.

     

    My WIndows 10 VM  Setup Form has IDE selected for both CDRom Bus parameters shown in graphic below:

     

    image.png.87e2da379c0eae97dad70ff295c4f43a.png

     

    Can anybody in the community please recommend a SATA controller Chipset that is compatible with both Windows 10 and Linux Mint that supports ATAPI devices such as Optical drives?  The chipsets below are the ones I have heard about for SATA controllers. 

    • AsMedia Chipset
    • JMB585 Chipset
    • Marvell Chipset

     

    Is the JMB585 Chipset compatible with Windows10 and Linux Mint?  Below is the link to the JMB585 Chipset SATA controller card I'm considering to buy:

     

    https://www.amazon.com/CREST-Internal-Non-Raid-Controller-Bracket/dp/B07ST9CPND

     

     

    Any opinions welcome.  Thank you for your time.

  21. Ghost82,

    Just wondering if you can clarify the following. Currently I have to manually click on the Unassigned Devices "MOUNT" button before I start my VM. If I don't do this my VM gives me a path error message and fails to start.  So I looked into how I could configure my NVMe settings so it auto mounts itself.  By clicking on the blue button circled below in YELLOW the UnRaid OS shows you a DISK EDIT Settings window where I discovered  some settings I hope you can comment on.

     

    image.thumb.png.d98d9dda1f5968326df6e3f3732f8807.png

     

    Regarding the PASSED THROUGH slider button shown below circled in YELLOW.  Is it necessary to activate this PASS THROUGH button?   Hawihoney in his post above advises to activate this PASS THROUGH button but not sure if I should because his NVMe Install approach differs from your NVMe install approach. 

     

    Regarding the AUTOMOUNT and SHARE buttons. I am planning on activating the AUTOMOUNT button because I want the NVMe drive to automatically mount itself after my UnRaid system powers up.  And as for the SHARE button I don't plan to activate this button out of security concerns.  I look forward to reading any opinion you may have regarding these buttons shown in the screen capture below. 

     

     

    image.png.b691f439155ae2d3cabf1556b4d2cf4e.png

     

    Lastly, the screen capture below shows my 1TB NVME correctly partitioned to 322GB.  This differs from the DISKS screen shot shown in my previous post that shows the entire 1TB drive space occupied by my Linux Mint OS.  Thanks again for your help which got me past this NVMe partition sizing problem.  I plan to repeat this partitioning process for the  Windows10 and MAC OS installs with a few changes.    Thank you for your time.

     

    image.png.20f036860e6086d87afa72a9c52b3dde.png

     

     

  22. Ghost82,

    Thank you for your two posts. Great news! I got successful results following your instructions. The only problem I encountered came up after executing the command below in my UnRaid terminal:

     

    qemu-img create -f raw /mnt/disks/WDC_WDS100T2B0C-00PXH0_21146D802780/lnxdisk.img 300G

     

    The  "Formatting" message shown in the terminal never disappeared. So I was not sure if the formatting was successfully completed or not.  After 10 minutes of waiting I entered the command shown below:

    ls /mnt/disks/ WDC_WDS100T2B0C-00PXH0_21146D802780/

     

    And it replied back with:

    lnxdisk.img

     

    So, I guess the "Formatting" message not dissappearing from the Terminal is by design.

     

    Creating the Linux Mint VM itself went smoothly.  I selected Virtio and not SATA.   Do you know if both options offer the same performance?

     

    I will post some screen captures tomorrow because it is getting late and I have to get up early in the morning tomorrow.

     

    Again, thank you for your help. I'm sure this thread will help others in the community wanting to do the same thing in the future.

     

  23. Ghost82,

    Thank you for your three recent posts. I deleted my NVMe's two partitions and then formatted and mounted my NVMe using my Unassigned devices app. 

     

    Below is the terminal text I got after running the "ls /mnt/disks/" command inside my UnRaid terminal:

    root@tower:~# ls /mnt/disks/
    WDC_WDS100T2B0C-00PXH0_21146D802780/
    root@tower:~#

     

    Below is the LOG file my Unassigned Devices app generated. It summarizes how my NVMe is now newly formatted:

    May 25 21:44:26 tower kernel: nvme0n1: p1 p2
    May 25 21:45:15 tower emhttpd: WDC_WDS100T2B0C-00PXH0_21146D802780 (nvme0n1) 512 1953525168
    May 25 21:45:15 tower emhttpd: read SMART /dev/nvme0n1
    May 25 21:57:54 tower unassigned.devices: Removing partition '2' from disk '/dev/nvme0n1'.
    May 25 21:58:26 tower unassigned.devices: Removing partition '1' from disk '/dev/nvme0n1'.
    May 25 21:58:31 tower kernel: nvme0n1:
    May 25 21:59:49 tower unassigned.devices: Device '/dev/nvme0n1' block size: 1953525168.
    May 25 21:59:49 tower unassigned.devices: Clearing partition table of disk '/dev/nvme0n1'.
    May 25 21:59:49 tower unassigned.devices: Reloading disk '/dev/nvme0n1' partition table.
    May 25 21:59:49 tower unassigned.devices: Reload partition table result: /dev/nvme0n1: re-reading partition table
    May 25 21:59:49 tower unassigned.devices: Creating Unraid compatible mbr partition on disk '/dev/nvme0n1'.
    May 25 21:59:49 tower kernel: nvme0n1: p1
    May 25 21:59:49 tower unassigned.devices: Reloading disk '/dev/nvme0n1' partition table.
    May 25 21:59:49 tower unassigned.devices: Reload partition table result: /dev/nvme0n1: re-reading partition table
    May 25 21:59:49 tower unassigned.devices: Formatting disk '/dev/nvme0n1' with 'xfs' filesystem.
    May 25 21:59:54 tower unassigned.devices: Format disk '/dev/nvme0n1' with 'xfs' filesystem: meta-data=/dev/nvme0n1p1 isize=512 agcount=4, agsize=61047598 blks = sectsz=512 attr=2, projid32bit=1 = crc=1 finobt=1, sparse=1, rmapbt=0 = reflink=1 data = bsize=4096 blocks=244190390, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0, ftype=1 log =internal log bsize=4096 blocks=119233, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 Discarding blocks...Done.
    May 25 21:59:57 tower unassigned.devices: Reloading disk '/dev/nvme0n1' partition table.
    May 25 21:59:57 tower kernel: nvme0n1: p1
    May 25 21:59:57 tower unassigned.devices: Reload partition table result: /dev/nvme0n1: re-reading partition table
    May 25 22:02:14 tower unassigned.devices: Adding disk '/dev/nvme0n1p1'...
    May 25 22:02:14 tower unassigned.devices: Mount drive command: /sbin/mount -t xfs -o rw,noatime,nodiratime,discard '/dev/nvme0n1p1' '/mnt/disks/WDC_WDS100T2B0C-00PXH0_21146D802780'
    May 25 22:02:14 tower kernel: XFS (nvme0n1p1): Mounting V5 Filesystem
    May 25 22:02:14 tower kernel: XFS (nvme0n1p1): Ending clean mount
    May 25 22:02:14 tower unassigned.devices: Successfully mounted '/dev/nvme0n1p1' on '/mnt/disks/WDC_WDS100T2B0C-00PXH0_21146D802780'.

     

    Lastly, the screen capture below shows how my NVMe disk looks iike after mounting it to my Unassigned Devices app:

     

    image.thumb.png.7f99e1da9ca77575eec33e55d99d5fce.png

     

    Just to confirm.  You explain 4 different ways to passthrough a "disk" to a virtual machine in your post above. Is your #4 description the approach you are using for my NVMe setup?

    Again, thank you for your time.

     

     

  24. Ghost82,

    Thank you for your post.  You are correct, my goal is to have my NVMe split into three partitions so I can install Linux Mint, Windows 10 and Mac IOS to each partition. However, due to my lack of experience I think I messed it all up.  Below is a screen capture of my Linux Mint "DISKS" window which shows how my 1TB NVMe drive is currently situated with the Linux Mint OS.

     

    image.png.5779cf9772b12c8b5d840ece3095667c.png

     

    I do not understand why it shows FAT 32 being that my LinuxMint ISO image I downloaded is 64bit?

     

    If I understand you correctly Ghost82 I need to make the following fixes:

    1. Passthrough my NVMe PCI card by applying a Checkmark and hitting the BIND button. Currently my NVMe PCI Controller card looks like what is shown in the screen capture below:

      image.thumb.png.48cb55b272763827f6a074abe1f02971.png
       
    2. Using MiniTool Partition Wizard on my Win10 PC I need to split the NVMe into 3 partitions.  Here is where I am confused and will appreciate some help. Should all three partitions be formatted in the UnRaid OS  XFS standard or should each partition conform to the partition standards listed below?
    • EXT4 (Linux Mint OS) 333GB partition size
    • NTFS (Windows10 0S) 333GB partition size
    • APFS (MAC OS) 334GB partition size

    3.  Listed below are the NVMe install paths I am assuming I need to use:

    /dev/disk/by-id/nvme-WDC_WDS100T2B0C-00PXH0_21146D87862-part1     (For LinuxMint OS)

    /dev/disk/by-id/nvme-WDC_WDS100T2B0C-00PXH0_21146D87862-part2     (For Windows10 OS)

    /dev/disk/by-id/nvme-WDC_WDS100T2B0C-00PXH0_21146D87862-part3     (For Mac OS)

     

    Below is something you say I hope you can clarify because I do not understand what parameters in the Create VM form are impacted by what you say below:

    "you did not install linux on a virtio image, you installed it on your nvme drive attached to a virtio controller."

     

    As shown below I selected "VirtIO" in the Create VM Form. Does that look correct to you?  How do I avoid the problem of not installing Linux Mint on a Virtio Image? 

    image.png.99e4ce127004b85c41ed835fff240813.png

     

    In short, please share any info you may have you think will help me perform this configuration the best way possible.  Thank you for your time.

     

     

     

  25. Hi all,

    I have carried on with my troubleshooting regarding this matter and I am glad to say this problem has been solved.  Below are the steps I performed. Again, thank you to Hawihoney and everyone else who contributed to this thread.

    1. I unmounted my NVMe drive from my Unassigned Devices app. In short, my UD app now shows a "MOUNT" button for my NVMe drive.
    2. I opened my UnRaid Terminal and entered this command:  ls -lisa /dev/disk/by-id/
    3. From the list shown in the terminal I tracked down my NVMe info and then concatenated this path text string: /dev/disk/by-id/nvme-WDC_WDS100T2B0C-00PXH0_21146D87862
    4. I created a new Linux Mint VM and changed the vDisk Location parameter to "MANUAL" and pasted this path: /dev/disk/by-id/nvme-WDC_WDS100T2B0C-00PXH0_21146D87862
    5. I hit the "CREATE" button and the result was my Linux Mint OS installed onto my NVMe drive as a Virtio image. 
    6. Glad to say my Linux Mint OS operates a lot faster compared to the previous configuration I was using.

    That was it. No need to BIND my NVMe device in the System Devices VFIO list or make any XML edits.  

     

    Again, thank you to all for your help and I hope this thread helps out somebody in the future with a similar problem.