Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

2 Neutral

About WashingtonMatt

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I don't know what changed, but But I was mucking around with this again, and the agent installed on one VM. I thought I had figured out, but failed on the 2nd VM. I applied the 1903 update, and then the agent installed on the 2nd VM. First VM didn't have 1903 yet... so I dunno, but it's finally installed and working. Ymmv :shrug:
  2. I understand you don't directly support guest OSs. My hope was there was an xml modification or QEMU update that would resolve this. It's starting look like a more significant issue than that. Thank you for responding.
  3. I did read that thread previously, and I don't believe it's the same issue. I have also created a thread on the FreeBSD forum and another user is not having any issues with KVM on a Debian host. https://forums.freebsd.org/threads/freebsd-11-3-no-network-interface-after-upgrade.72931/#post-445271
  4. All currently supported versions of FreeBSD (11, 12,12.1) do not detect any emulated network interface. I discovered this after upgrading from FreeBSD 11.2 to 11.3. Rolling back restores network interface. I have reproduced the issue by downloading the installer ISO for 11.2, 11.3, 12, 12.1, and creating new VMs. ONLY the 11.2 installer is able to detect a network interface. Q35-3.1 SATA primary vdisk e1000-82545em I believe something in unRAID needs to be updated for continued compatibility with supported versions of FreeBSD. I believe this is isolated to unRAID, but I don't have a way to confirm. I am currently unable to install security patches due to not being able to upgrade to a supported version of FreeBSD. I understand FreeBSD guest on unRAID is not popular, so please at minimum take a few minutes to confirm the issue, and state whether you intend to resolve the issue in future releases so I can make a decision on how to proceed. I have posted about this on the thread below, but have not gotten any responses. unraid-diagnostics-20191119-2116.zip
  5. Can someone test FreeBSD 11.3+ on unRAID 6.8.0 RC5? FreeBSD versions 11.3, 12, 12.1 on unRAID 6.7.2 are unable to detect network interface. Hoping the latest unRAID RC version will resolve the issue.
  6. Still looking for a solution. 11.2 iso installer detects nic fine, 11.3, 12, 12.1 do not detect nic. it would be great if someone can confirm same results. Anyone willing to test FreeBSD on the latest unRAID RC?
  7. No one else uses FreeBSD? This seems to be the issue. Sounds like custom kernel might work. Prefer not to go that route, but will if that's what's necessary. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236922 cron sending nastygrams
  8. Anyone... Bueller? Someone willing to verify the issue? Any suggested workarounds? Is tomorrow eol for supported FreeBSD versions on unRAID?
  9. Downloaded FreeBSD 12 iso, new VM, installer also fails to detect network interface.
  10. Currently running FreeBSD 11.2, which is eol at the end of the month. So instead of waiting till the absolute last minute to upgrade to 11.3, I decided to knock it out 20 minutes before I was to to leave with the wife 😐. Plenty time right? wrong. After the upgrade to 11.3, the network interface is no longer detected. I rolled back successfully, and network is back. Q35-3.1 SATA primary vdisk e1000-82545em I downloaded the 11.3 ISO and created a new VM and the installer failed to detect a network interface. I believe FreeBSD 12 is affected as well, but I haven't tested yet. Is anyone aware of a fix for this?
  11. Thank you Leoyzen for all your recent input and explanations. I would love to see a guide to a get a proper base install of macOS on unRAID.
  12. https://www.backblaze.com/b2/hard-drive-test-data.html https://www.backblaze.com/blog/2018-hard-drive-failure-rates/
  13. I had the same issue. I just rolled back clover to 46xx until I had time to dig into it more.
  14. So that's showing you that your windows device is using a ipv6 dns server 2601:640... It should be your pi-hole ipv4 address .You need to check your dhcp server dns settings. Make sure it's only configured to hand out your pihole address.
  15. Your windows device should only show a single ipv4 dns address of your pi-hole. I'm not even sure what that other address is... I assume it's a valid ipv6 short format. It's probably what's doing your dns name resolution. open a command prompt and run command: nslookup www.google.com