11/12/2023 0 Comments Nxfilter raspberry piIf you still want to go the Ubuntu route, the good luck and I hope you get it working.Ģx120GB Crucial BX500 SSD (Mirror) for bootĨx8TB WD80E(Z/M)AZ (RAIDZ2) (1 RMA'ed after 12 months)Ģx1TB Samsung 860 EVO SSD (Mirror) running the following jails and VMs:Ĭalibre 4.7.0 and replaced with Calibre-Web 0.6.19 running in a Docker container So if you want to try these steps and see if you get any further, I would love to hear back from you. So I'm not sure if somehow they were getting into a race condition which caused the high network traffic.Īnyway, I think I'm close, but just haven't figured out the steps need to get to the finish line. It's network interface is statically defined with address, default gateway and uses the gateway's DNS so no problem there, but all my clients use the Pi-Hole for both their DNS and DHCP. My server does not used either the DNS or DHCP from the Pi-Hole. When I got the system stabilized by unplugging the network cable, I restarted the VM and then everything worked great again. I've read as much documentation as I could find, but nothing stood out. I have yet to figure out what caused this, but I think it might have something to do with the way my network devices are configured. So, at a quiet time, I rebooted my server and then all hell broke loose! That network interface started pumping out huge amounts of data and the server became unresponsive. But I wanted to make sure it would restart after a system reboot. Plugged a network cable into the interface and into a switch and everything worked great while the system was up. That's what's supposed to happenįirst, during the setup, I chose to use an unused network interface on my server. This should allow the VM to start up without intervention should your server go down. You should now have a fully running Pi-Hole running in a VM on your TrueNAS server.Īs a last step, you will want to make sure that your VM is set to autostart when the server reboots and also make sure that the VNC device is set to "NOT delay VM boot till VNC connects". When the install and setup has been completed, reboot your new Pi-Hole server to make sure everything starts correctly. When finished installing, use your browser to connect to Pi-Holes admin console and do any further setup that you require. If you use "unbound", then that can be added later. Now install the Pi-Hole software as usual using the standard "curl -sSL | bash" and go through the normal Pi-hole scripts. You should now install sudo and create the pi account (if you didn't do it during the install process) and any other software you may want to use. This is a bhyve problem and not a Debian problem. Doing this will now allow your new Debian VM to boot normally every time, but the same steps may be required anytime you update the Grub boot loader. " and finally "cp grub圆4.efi boot圆4.efi". Once the system has booted, you must login as root then "cd /boot/efi/EFI", "mkdir BOOT", "cd BOOT", "cp. At the "Shell>" prompt, type "exit" to start the Boot Manager then select "Boot Maintenance Manager", the "Boot from File" and select the first item listed, then select "" then "" and finally "grub圆4.efi". When the boot fails, let it time out (about 90 seconds) and then the UEFI Shell appears. And Debian wouldn't boot after the install but this was a known problem with bhyve which required a simple fix. I had to make sure that the VNC device was set to 800圆00 during the install, otherwise the screen ended up garbled. I installed Debian with only a couple of small problems. As the Raspberry Pi I was trying to replace had 4 cores, I thought 2 cores and 2 threads each should be enough. The amount of memory and disk are no-brainers, but I just guessed at the number of cores and threads to throw at it. I created a virtual machine with 1gb memory, 10gb disk and 2 cores with 2 threads. However, I think I did it a little different than you.įirst, instead of Ubuntu, I used Debian 10.9.0 as that is what the current version of Raspian is based upon. GT2416, I too have been working hard to try and get Pi-Hole working in a VM under TrueNAS 12.0-U4.1 with mixed results.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |