Nobody told me you couldn't reboot this thing

[DaHai]

Please follow the below template, it will help us to help you!

I had Pi-Hole Installed on my Raspberry Pi 3B+ and everything was working fine (well, except local DNS names and Total queries counting local queries as well, but that was another unsolved thread).
I went to reboot it as a final check and now its dead, dead, uber-dead:

sudo shutdown -r now

Expected Behaviour:

It should have come back after the reboot. Right??

Actual Behaviour:

It went down, then apparently attempted to reboot, as I saw the activity light blink and the Eth0 lights blink, but nothing beyond that. No access via SSH anymore, no Web Interface anymore, is not Ping-able, does not show up in Fing.

Unplugged power, waited 30 seconds, plugged back in - still dead. Rinsed and repeated - still dead.

I had OpenVPN client running on it as a network gateway and using CloudFlare DoH. All that had been working great for many months, with reboots, until I added Pi-Hole and turned it into a Black-Hole.

Debug Token:

Sorry, no Debug Token - its dead Jim, you take his wallet and I'll get the tricorder.

Pi-hole Version v4.3 Web Interface Version v4.3 FTL Version v4.3.1

Any suggestions?

[technicalpyro]

remove the SD card and check the image if its corrupted it wont boot. also check and make sure you're using a proper power supply NOT a spare phone adapter or something like that

[DaHai]

It's a good power supply: no blinking red lights
How do I check if the image is corrupted?

[DaHai]

More Info:
I booted with an HDMI monitor and USB keyboard and found it was booting fine, but not on the network.
Then I discovered it had assigned itself an IP address from one of my tun adapters, instead of the proper static IP address it was previously set to. Not sure if I did that or what.
This is what it set in dhcpcd.conf:

interface eth0
        static ip_address=10.9.0.6
        static routers=10.9.0.5
        static domain_name_servers=127.0.0.1

And this is what it was before installing Pi-Hole:

interface eth0
static ip_address=172.27.3.3/24
static routers=172.27.3.1
static domain_name_servers=8.8.8.8 8.8.4.4

Now it kinda works again with the original dhcpcd.conf settings above. At least it boots and get the right IP address and gateway, but...

It's really slow to find new domain names and fails for the first few tries before finding it:

# This site can’t be reached

**www.netflix.com** ’s server IP address could not be found.

So, apparently something is still screwed up.
I tried the following for static domain_name_servers=

127.0.0.1
127.0.0.1#5053
8.8.8.8 8.8.4.4

But nothing helped.

Ideas?

[mibere]

Interesting to read this. In daily usage my Pi 3B runs without any problems, hangs or crashes. But I would say that 30-40% a 'sudo shutdown -r now' ends in a "dead" device; the Pi never comes back, I have to pull the power cable.

[DaHai]

Here's my current entry in dhcpcd.conf, and it seems to work better/faster, but heck if I know which DNS server its actually using now:
static domain_name_servers=127.0.0.1#5053 127.0.0.1 8.8.8.8 8.8.4.4

[mibere]

My /etc/dhcpcd.conf contains

interface eth0
static ip_address=192.168.5.220/24
static routers=192.168.5.1
static domain_name_servers=192.168.5.1

192.168.5.1 is the router. And 192.168.5.220 is out of the routers DHCP range.

[technicalpyro]

@DaHai

static domain_name_servers=127.0.0.1#5053 127.0.0.1 8.8.8.8 8.8.4.4

will ignore Pi-hole

should be set to 127.0.0.1 ONLY.

having things like what i assume is an unbound instance in that line allows things to leak around the Pi-hole.

[DaHai]

Oddly, as I said earlier, I tried that and regularly got 'Server's IP address could not be found' on any new site I visited. It also appeared to happen with the cache expired.

I'll try it again just to be sure.

P.S. [Update]: @technicalpyro , I think you're right. I was chasing a ghost. Seems to work fine with just 127.0.0.1

Thank you!