• Content count

  • Joined

  • Last visited

  • Days Won


1812 last won the day on April 25

1812 had the most liked content!

Community Reputation

61 Good

1 Follower

About 1812

  • Rank
    ¯\_(ツ)_/¯ Member


  • Gender

Recent Profile Visitors

533 profile views
  1. Search for the Ryzen build theads. I believe your issue is covered there. good luck!
  2. Link in my sig would solve your problems, or at least, let you know the problem isn't the card. The bios needs to be rolled back. You can thank Linux and HP. Sorry I didn't have all the info on HP peculiarities gathered in one place sooner! But it's info you'll need going forward with unraid on a proliant.
  3. I've never done what you're trying to do. I instead use a 4 port nic and send that to pfsense. BUT This is how you change your xml to the the other virtual adapter: click on the red square button on the pfsense vm icon when it is stopped. On the dropdown menu, select edit xml. scroll down to the section that looks similar to this: <interface type='bridge'> <mac address='52:54:00:82:25:11'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/> </interface> note: your mac address and address will be different. where it lists "model type=" change to <model type='e1000-82545em'/> make sure source birdge is "br0" scroll down further, click save. NOTE: you can no longer edit your vm using the vm manager as custom edits will then be discarded and you will lose the e1000. Don't be surprised that when you attempt to boot the server, and it is looking for the pfsense vm for network connectivity, that it can take a while. Docker runs an update check at boot. And if there is no network detected, each docker has to go through a preset timeout which is somewhere between 100 and 300 seconds if I remember correctly. This is on every autostart docker in order. This is before the vm's are autostarted. PRO TIP: set your unRaid server on a static ip. it's easier to find it after setting up pfsense and running the firewall on the same box. Good luck.
  4. But seriously, if it requires a driver, I bet LT would consider adding?
  5. You so crazy. buy one and let me know how it goes.
  6. Not a problem. I remember when I was new to all this. I couldn't have gotten up and going if it weren't for others in this great community.
  7. These diagnostics are probably from your GUI boot since the unsafe interrupts line is missing from them. Please either add the line to GUI boot or boot normally and try to start the vm. If it doesn't work, then post diagnostics from that.
  8. Only works when added to first append/top level boot. If you want it enabled on GUI mode, it has to be there as well ( as I have understood it.)
  9. Group 22 has a sata controller and pci bridge trying to be passed to the vm. vm's don't like pci bridges. group 18 has a pci bridge and the gpu with it's audio component. Your logs also contain this message: vfio_iommu_type1_attach_group: No interrupt remapping support. Use the module param "allow_unsafe_interrupts" to enable VFIO IOMMU support on this platform To do this, click on the link to the hp prolaint thread in my signature, follow the directions in Step 3 of the vm problems section to allow unsafe interrupts. Then reboot, try again. if it doesn't work, post new diagnostics.
  10. cold be faulty psu.. in the duration while contemplating that, install the fix common problems plug in and put it in troubleshooting mode. next time it happens, get the logs from that shutdown.
  11. More reasons why I shouldn't be on the internet right after getting up in the am...
  12. https://wiki.lime-technology.com/UnRAID_Manual_6#Enable_MSI_for_Interrupts_to_Fix_HDMI_Audio_Support
  13. Pci bridges are never fun to work around. I have never directly had the issue but a couple folks on here have. First, turn acs override off. then go to syslinux.cfg and try adding the device id of the pci bridge to the two from the video card and reboot. it probably won't fix it, but worth trying. When that doesn't work, Look in your bios for an SR-IOV function. if disabled, enable and recheck iommu groupings. If that doesn't do it, then re-read the HP solution posted above and see if that is applicable to your server. And if none of that works, we may get creative and try something else. What version of unRaid are you on and what bios and date are you on?
Copyright © 2005-2017 Lime Technology, Inc. unRAID® is a registered trademark of Lime Technology, Inc.