• Content Count

  • Joined

  • Last visited

Everything posted by slipstream

  1. 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
  2. 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: Connect New SATA drive to SATA cable and Power cable. Preclear Drive. Format Drive. Assign new disk to Movie Share 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 t
  3. 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 compl
  4. 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: I can't make heads or tails of the Description for the ERROR. It is not clear to m
  5. 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 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
  6. 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.
  7. 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: Additionally, the drop down menu below shows "SCSI" as one of the parameter options to pick
  8. 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." The SATA Controller card I am using has a Marvell 9512 chip. It also has a Marvell_SATA_V1.2.0.1049 - Windows
  9. 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. Regarding the PASSED THROUGH slider button shown below circled in YELLOW. Is it necess
  10. 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 bac
  11. 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 (nvme
  12. 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. 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:
  13. 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. I unmounted my NVMe drive from my Unassigned Devices app. In short, my UD app now shows a "MOUNT" button for my NVMe drive. I opened my UnRaid Terminal and entered this command: ls -lisa /dev/disk/by-id/ 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
  14. 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 CREA
  15. 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
  16. 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:
  17. 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.
  18. 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 in
  19. 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:
  20. 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.
  21. 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 c
  22. 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:
  23. 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.
  24. 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 wor
  25. 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 th