Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


BobPhoenix last won the day on March 3 2017

BobPhoenix had the most liked content!

Community Reputation

51 Good

1 Follower

About BobPhoenix

  • Rank
    Advanced Member


  • Gender

Recent Profile Visitors

863 profile views
  1. What does the XML look like for your NVMe device? What you are looking for is: <boot order='1'/> If that tag isn't on your NVMe device then remove it from the device it is on and add it to the NVMe device. Every time you edit the VM you may have repeat the process.
  2. BobPhoenix

    Threads posted in before sometimes not indentified

    I just saw this on a thread myself. The multiple pool feature request thread to be specific.
  3. What problems are you having that causes you to need to update? I normally only update firmware if I'm having problems. Updating can CAUSE problems so I don't update unless I have to.
  4. BobPhoenix

    Microsoft looks likely to acquire GitHub today

    According to the article GitHub was in some financial difficulty. So for the optimists in the crowd maybe this won't be too bad. I tend to be more of a pessimist though.
  5. BobPhoenix

    Passthrough hard drive to VM?

    Partitions have a -part1 at the end of the name for the first partition. I suspect partition 2 would be -part2 etc... but I've never used anything but a single partition on my drives with unRAID so I can't confirm this. So for my PNY SSDs I would use ata-PNY_CS2211_960GB_SSD_PNY381621931203001D7-part1 to get the 1st partition for the first drive: root@VMServer:/dev/disk/by-id# ls ata-PNY* ata-PNY_CS2211_960GB_SSD_PNY381621931203001D7@ ata-PNY_CS2211_960GB_SSD_PNY381621931203001D7-part1@ ata-PNY_CS2211_960GB_SSD_PNY3816219312030022C@ ata-PNY_CS2211_960GB_SSD_PNY3816219312030022C-part1@ I.E. the full path in the GUI would be: /dev/disk/by-id/ata-PNY_CS2211_960GB_SSD_PNY381621931203001D7-part1 to the first partition on the first drive above.
  6. BobPhoenix

    New with old equipment

    See if this would help - not unRAID but advice might help: https://lifehacker.com/5991848/how-to-boot-from-a-cd-or-usb-drive-on-any-pc
  7. BobPhoenix

    Need help solving random crashing.

    Two suggestions for you - first is most likely and I had nasty problems with it but I've had problems with the second before as well. Turn off in bios if on MB or remove the Marvel 88SE9123 controller card - I had my Marvel 9230 controller passed through to a VM and got dropped drives and had to reboot the server to get them back. Didn't cause unRAID crashes for me but if you are using array drives on yours this is likely your problem. I turned my MB 9230 off in the bios so I wouldn't be tempted to use it and haven't had any problems with that server any more. Turn off in bios if on MB or remove the NEC USB 3.0 controller card. Since I stopped using my Fresco USB 3.0 card in another server it has been up for 15 days and I believe it would have been longer but I had to reboot for an unRAID upgrade. Before that I got random crashes that I couldn't figure out with it installed. Really think the 1st one is most likely the cause but doing either or both of the above is where I would start to trouble shoot since you have already tried some other hardware changes.
  8. Just got the same thing on my server 6.5.3- rc1 here. Will see if a restart will help.
  9. BobPhoenix

    LSI SAS9207-8i for $99

    I've used a fan and mount like this before to put fans blowing on my PCI slots from above them: https://www.newegg.com/Product/Product.aspx?Item=N82E16835118204
  10. BobPhoenix

    SATA Controller Passthrough help

    If you are going to use your SSDs in your VM you will want to connect them to this controller and pass it through to the VM. To do that I would recommend "stub"ing the device in "syslinux.cfg" (you do that from the GUI on the unRAID flash drive). Look for the boot option you use to regularly boot unRAID (I.E. if you boot to GUI mode you will make changes to that). Most people I think use the standard default options and boot to non-GUI mode. Anyway the section in syslinux.cfg that you should be looking for: label unRAID OS menu default kernel /bzimage append initrd=/bzroot so to stub your ASMedia card you would change the above to look something like this: label unRAID OS menu default kernel /bzimage append vfio-pci.ids=1b21:0612 initrd=/bzroot if you had more devices to pass through to this or any other VMs just add it after a comma so 1b21:0612 would become 1b21:0612,xxxx:yyyy for instance Note how I got the information on your ASMedia card from the display at the top: "[1b21:0612]". Now just reboot. When you do your SSDs will no longer be visible to unRAID any more. But when you edit your VM you will now see that the ASMedia card is listed as available to pass through to the VM now. For instance on my VM server I have the following devices showing up as available to pass through to a VM most of which ARE being pass through to another VM: So your ASMedia controller would show up in the above box along with any other devices you stub'd to allow pass through. Hope that help.
  11. BobPhoenix

    Preclear plugin

    You might just want to settle on the drive manufacturers test programs to test it and then add it to your array and let unRAID clear it. Unlike in versions from 5 and before (maybe even early versions of 6) - the array is NOT offline (with current versions of unRAID) when you add a drive that has to be cleared to the array. I still use the command line script version of preclear to test my drives and you could use that as well as another option if you want.
  12. BobPhoenix

    Getting rid of vmware

    Great news! Though you would be successful.
  13. BobPhoenix

    Getting rid of vmware

    Yes but PLOP boots the unRAID OS from the unRAID flash drive. The only thing you might have to do is run make_bootable.bat from the flash drive. But if like me you prepared it to boot from the flash drive originally then you could proceed just like I advised.
  14. BobPhoenix

    Getting rid of vmware

    For me it was a easy as removing the ESXi datastore drive and USB boot flash and setting the unRAID boot flash as the boot device and booting the computer. I had all my drives connected to passed through HBAs for unRAID and they were left in the computer. I did have to setup my Windows VM from scratch on unRAID as a VM but if you only have unRAID as a VM then to get to unRAID bare metal it should be as simple as I stated.
  15. BobPhoenix

    Disabled Disk Causing Issues with unRAID share

    I see your Marvel HDD controller is enabled. I suggest you turn it off in the bios and remove any drives connected to it and use other connectors for them. When I had the Marvel controller turned on on my ASRock EP2C602-4L/D16 I would get drives dropping out randomly between 2+ times a week to every other month. The only thing that saved me was that I was passing through the Marvel controller to a VM and not using it with drives in my array. But I had to reboot my computer once too often because the Marvel controller dropped the drives and made the VM unusable. That is why I switched out my IBM M1015 8i controller to a LSI 9201-16i to gain back the 4 ports I lost from the Marvel and gain an extra 4 ports besides.