JellyLegs

Thanks for the reply, jonnie.black. I feel better knowing they're both CMR.

I shucked EasyStore last year and turned out to be a EMAZ drive. I shucked a MyBook today (after testing) turned out to be a EZAZ drive. Both are 10TB/each and the SMART Attributes section displays, "22 Helium level 0x0023 100 100 025 Pre-fail Always Never 100," for both of them. I assume they're both Helium at this point. SMR -OR- non-SMR/CMR is the question.

Here are the issues and solutions I found to run pfSense in a docker on unRaid. First, I followed Spaceinvader One's 8 Part tutorial series below. Fair warning; I encountered a hardware problem read below. Also, in Part 3 using a Ryzen CPU solved below. Reference: FIRST, problem... The system would not recognize the Intel NIC I purchased. (eBay: Intel NIC lottery amite?:) I would stay away from the INTEL EXPI9404PTL PRO/1000 PT as it was never recognized by unRaid. Search the forums, plenty of issues with it. After additional research. I purchased a Dell Quad Port NIC part number: 0H092P for approx $25 + tax/shipping/etc.. Recognized right away! Here is a nice resource from serve-the-home to help find the right one for you. This read helps you better understand counterfeit vs real when browsing eBay using the part number for i350 cards. Obviously, it is not fool proof but some knowledge in an unfamiliar area helps! Reference: https://forums.servethehome.com/index.php?threads/comparison-intel-i350-t4-genuine-vs-fake.6917/ <<--Public service announcement!!!-->> This should be general knowledge but if you do not know here it is. 1) Make sure your IOMMU groups are separated. 2) Make sure you go into the XML and edit the controller to say multifunction='on' ..etc etc etc... Spaceinvader One talks about it in some of his other videos but here is a read if you prefer that instead. Reference: SECOND problem. Now that your hardware is playing nicely with unRaid, its the software side of things. (Ryzen Specific) For whatever reason when you run the pfSense docker it starts to hang. pfSense does not play nicely with Ryzen out of the box. Solution: XML View, Edit CPU section. Delete most of it and copy format listed below. Make sure to account for the cores & threads you have chosen to assign. <cpu><topology sockets='1' cores='2' threads='2'/></cpu> Reference: Now you should be able to follow Spaceinvader One Tutorials 3-8 no problem. --------------------------------------------------------------------------------------- Specs of my build that pertain to this guide: UnRaid Version: 6.8.3 pfSense 2.4.5 Ryzen 2600 AsRock Rack X470D4U2-2T Intel Quad Port PCIe Ethernet Server Adapter Dell PN: 0H092P Keyphrase(s): Unraid using Ryzen not working/freeze/crashing/hung/hanging in pfsense docker.

Works in VNC no problem. GT 1030 - with and without Rom Bios Machine i440fx/Q35 - All give the same error as before.

It gives me the same error. If I put the GPU back into the 2.0 x1 slot it works. I have no idea why it won't work in the 3.0 x8 slot.

Hello, So I'm having issues with my win10 VM. I had a SAS controller in the 3.0 x8 slot. I thought It would be best to use the bandwidth for my dedicated VM/GPU. So I swapped my SAS controller with my GPU onto the 2.0 x1 slot. Array came up no problem. However, with the GPU in x8 slot, when I start the VM after boot, one of my cores is pegged at 100%. Then I force stop and try it again; I receive, Unknown PCI header type 127, error. Any ideas why this would be?

I will look into it. Thanks for the reply.

Deleted zip

Any idea why this is?