BasementGamer

Members
  • Posts

    8
  • Joined

  • Last visited

About BasementGamer

  • Birthday February 4

Converted

  • Gender
    Male
  • Location
    Mexico

Recent Profile Visitors

545 profile views

BasementGamer's Achievements

Noob

Noob (1/14)

1

Reputation

  1. I opened my dashboard this morning to find out that the Flash drive was corrupted somehow. I followed the instructions on the troubleshooting page and was able to repair the flash drive, and it seems to have fixed the issue. However, fearing it was maybe a bug in 6.11.3, i decided to update to 6.11.5, and now my pihole container is, once again, broken. You see, I was able to make it work before even though libvirt sets up a dnsmasq server on 192.168.122.1 by adding the "bind-interface" setting to it. But now the problem seems to be different. I don't see port 53 being used, or any port that the pihole container uses (after changing port 80 and 443 to unused ones), yet I still get "address already in use" error when trying to start the container. The main change I see in Unraid happening is that IPVLAN is now being used for new configurations. However, I have an old one and I see that I'm still configure to use MACVLAN, but my thinking is that maybe I need to switch to ipvlan or create an ipvlan network for pihole? I'm starting to think maybe using pihole on Unraid is not worth it, I'll have to look at actually getting a Raspberry Pi for it.
  2. Did you figure out what's wrong? My server rebooted this morning due to a power outage, and now I can't start pihole with the same issue (docker: Error response from daemon: Address already in use.) For some reason, when trying to find out what address might be in conflict, I found out that the unraid server is using port 53 with a strange IP (192.168.122.1), which isn't dhcp assigned, or even accessible outside of unraid.
  3. Well, I took a leap of faith and upgraded my Unraid install from 6.9.2 to 6.11.0, and so far everything seems to be working fine. Great job!
  4. Have you tried upgrading to 6.11.0 to see if the corruption issue was fixed?
  5. I found the instructions on this thread. The short version, you need to manually download the packages from Slackware 15, then put them in /boot/extra, and the packages will be automatically installed on reboot. Or, if you don't want to reboot, you can manually install them with installpkg <pkgname>
  6. I am currently running Unraid 6.9.2. Can I make the upgrade directly to 6.11.0, or do I need to go to 6.10.3 first? I was holding the upgrade to 6.10.3 because I saw there were some issues with SQLite and PLEX/Sonarr/Radarr/etc, are these fixed?
  7. I am in the same situation. I have an old GT 710, which is not supported by the latest drivers. Is there a way to manually go back to the latest legacy version (470.129.06)? I don't see it in the list of available drivers, and there is no "legacy" option available for the plugin. Thanks
  8. There's a new vulnerability that affects Secure Boot and GRUB2: https://www.eclypsium.com/2020/07/29/theres-a-hole-in-the-boot/ Is Unraid affected by this, and if so, is there a way to mitigate/patch the problem?