I run pi-hole on an iomega iconnect, it's an arm device running debian from a small external ssd and everything was working well till it stopped last night.
The webmin interface refused to connect and so did ssh.
Unfortunately this system uses systemd so I can't just read the log files. Since the boot drive is usb I can plug it into any system that can read ext4 but I can't run it.
The iconnect isn't responding to pings either. The pihole log is plain text and it appears that it is working it looks like it talked to my apple tv. Might be mistaken here as I can't find an open port running wireshark I can see traffic from 192.168.3.253 the address of pihole.
4157 359.459274 Apple_97:f9:c6 Broadcast ARP 42 Who has 192.168.3.253? Tell 192.168.3.100
4158 359.459423 Iomega_0c:d6:68 Apple_97:f9:c6 ARP 60 192.168.3.253 is at 00:d0:b8:0c:d6:68
several times, I have a sneaking suspicion that when i updated last time some changes may have occurred to the firewall running on the iconnect. I just did a reinstall of the os on the iconnect as soon as i installed pi-hole I lost comms with it after i rebooted.
As it is just the base system + Pi-hole something in the installer seems to be an issue. I would bet its the firewall rules that are broken.
Ok so now if I reboot hopefully my test install will work. and if I dd the original server image that I backed up placing these 2 files on my old image it should take in these rules on reboot and give me my server back and if anyone comes looking with the same issue they might try these rules. just rebooting now .. and yes i have a blue led pulsing red so.. yes that works. so now to restore the old image and install these 2 files.
I can't run those lines the pi-hole update locked me out but as you see in my previous post I can restore the disk and put these 2 files on the disk and with a little luck my original image will execute the new file when i put the drive back to the iconnect and restore the open rules and i will be able to login again.
hopefully ...
Need to run that one before you update (and lose connection) and make sure your network works the old way using the "/etc/network/interfaces file" before updating.
I have no connection all I can do is take the hard drive off and edit files on another system thats the problem really I can't work on the system live as i am locked out.
wireshark is showing its at the ip and talking occasionally it answers when asked who has 192.168.3.253 it replies with its mac address
You said before you had working system ?
Need to dd a working image, disable dhcpcd, make sure networking survives a reboot and then do the updates that broke your setup.
I have an initial install that installs a minimal version of jesse i then have to update it recreate all the services it was running. It would be better if i can fix the broken image.
there is a lot of work that will need to be redone if i need to start from the very beginning again.
at least systemd hasn't broken this time... so if its possible to repair it i would prefer to do so. Also what happens next time pi-hole is updated will it leave me with a broken system again?
The main thing is my archives and media theres around 10tb of storage the main thing is my mac shares. my photo's ect. it also runs print server and a couple of other things. It also was doing backups for the other systems on the lan