readelf -A /usr/bin/pihole-FTL
Attribute Section: aeabi
File Attributes
Tag_CPU_name: "7-A"
Tag_CPU_arch: v7
Tag_CPU_arch_profile: Application
Tag_ARM_ISA_use: Yes
Tag_THUMB_ISA_use: Thumb-2
Tag_FP_arch: VFPv3-D16
Tag_ABI_PCS_wchar_t: 4
Tag_ABI_FP_rounding: Needed
Tag_ABI_FP_denormal: Needed
Tag_ABI_FP_exceptions: Needed
Tag_ABI_FP_number_model: IEEE 754
Tag_ABI_align_needed: 8-byte
Tag_ABI_enum_size: int
Tag_ABI_VFP_args: VFP registers
Tag_CPU_unaligned_access: v6
That's the wrong binary. Are you just running the automated installer or are you manually downloading the FTL binary?
its first, with @jfb, we tryed automatic installer. installer bugged and stop at FTL installation. we then DL manually FTL because reinstalling we now bugged because of the nameserver. after that i finaly had access to pihole command and we started debugging more.
we made a mistake by downlaoding the wrong FTL binary but we fixed it and i try on another blank SD card with the new ftl binary and same thing happen ( right now we are on the first SD card
The output from that last readelf shows an armv7l binary. That's not what the Zero has, you have the wrong binary installed.
This is the correct output for a Raspberry Pi Zero:
readelf -A pihole-FTL-arm-linux-gnueabi
Attribute Section: aeabi
File Attributes
Tag_CPU_name: "6"
Tag_CPU_arch: v6
Tag_ARM_ISA_use: Yes
Tag_THUMB_ISA_use: Thumb-1
Tag_FP_arch: VFPv2
Tag_ABI_PCS_wchar_t: 4
Tag_ABI_FP_rounding: Needed
Tag_ABI_FP_denormal: Needed
Tag_ABI_FP_exceptions: Needed
Tag_ABI_FP_number_model: IEEE 754
Tag_ABI_align_needed: 8-byte
Tag_ABI_enum_size: int
Tag_ABI_HardFP_use: Deprecated
Tag_ABI_VFP_args: VFP registers
Tag_CPU_unaligned_access: v6
i believe you. and now you showing it. i see it. but do i reinstall it is it keep crashing with pihole -r
[✓] Detected ARM-hf architecture (armv6 or lower) Using ARM binary
[i] Checking for existing FTL binary...
[✗] Failed to retrieve latest FTL release metadata [i] Checking for user 'pihol
[✓] Checking for user 'pihole'
[✓] Installing scripts from /etc/.pihole
Get a new, blank SD Card and burn https://downloads.raspberrypi.org/raspbian_lite_latest to it. Then run the curl -sSL https://install.pi-hole.net | bash and we'll go from there.
@DanSchaper Sure, i will wipe and restart fresh with you.
i already have those files. i been freshing the SD card more then i would like to admit !
If you have a different new card, use that one.
i was a bit too quick for that. but i already try in the down time between post and did the exact same step and the new card didn't fixed anything
I'll need more details about what isn't working with output or screenshots to be able to help.
What process are you using to image the new card?
i'm using Etcher-Portable-1.5.60 to burn the image of Buster Lite.
after i manually copy ssh file in boot to gain ssh access, after that if upgrade time
So here i am with a fresh card here the step i took once in shh
1- sudo apt update
2- sudo apt upgrade -y
3- sudo raspi-config #set local as en_CA.UTF-8 and timezone as America /Montreal
4- Rebooted the Pi
5- Use the Curl url provided by DanSchaper
6- Installation crashed, differently this time but it did.
Now, pihole command doesnt work. so here a screenshot and the log i seen on where it crash.
[✗] Root user check
[i] Script called with non-root privileges
The Pi-hole requires elevated privileges to install and run
Please check the installer for any concerns regarding this requirement
Make sure to download this script from a trusted source
[✓] Sudo utility check
[✓] Root user check
.;;,.
.ccccc:,.
:cccclll:. ..,,
:ccccclll. ;ooodc
'ccll:;ll .oooodc
.;cll.;;looo:.
.. ','.
.',,,,,,'.
.',,,,,,,,,,.
.',,,,,,,,,,,,....
....''',,,,,,,'.......
......... .... .........
.......... ..........
.......... ..........
......... .... .........
........,,,,,,,'......
....',,,,,,,,,,,,.
.',,,,,,,,,'.
.',,,,,,'.
..'''.
[✓] Disk space check
[✓] Update local cache of available packages
[✓] Checking apt-get for upgraded packages... up to date!
[i] Installer Dependency checks...
[✓] Checking for apt-utils
[i] Checking for dialog (will be installed)
[✓] Checking for debconf
[✓] Checking for dhcpcd5
[i] Checking for git (will be installed)
[✓] Checking for iproute2
[✓] Checking for whiptail
[i] Using Google (ECS)
[✓] Set IP address to 192.168.2.42
You may need to restart after the install is complete
[i] Unable to find IPv6 ULA/GUA address, IPv6 adblocking will not be enabled
[i] IPv4 address: 192.168.2.42/24
[i] IPv6 address:
[i] Web Interface On
[i] Web Server On
[i] Logging On.
[✗] Check for existing repository in /etc/.pihole
[✓] Clone https://github.com/pi-hole/pi-hole.git into /etc/.pihole
[✗] Check for existing repository in /var/www/html/admin
[i] Clone https://github.com/pi-hole/AdminLTE.git into /var/www/html/admin...
Error: Could not update local repository. Contact support.
pi@Pi-Hole:~ $ pihole
-bash: pihole: command not found
pi@Pi-Hole:~ $
What does the following show:
cd /var/www/html/admin
sudo git status
cd /var/www/html/admin
-bash: cd: /var/www/html/admin: No such file or directory
sudo git status
fatal: not a git repository (or any of the parent directories): .git
Okay, how about
ls -lach /var/www/html
ls -lach /var/www
ls -lach /var/www/html
total 8.0K
drwxr-xr-x 2 root root 4.0K Dec 2 20:35 .
drwxr-xr-x 3 root root 4.0K Dec 2 20:35 ..
ls -lach /var/www
total 12K
drwxr-xr-x 3 root root 4.0K Dec 2 20:35 .
drwxr-xr-x 12 root root 4.0K Dec 2 20:35 ..
drwxr-xr-x 2 root root 4.0K Dec 2 20:35 html
Next try
sudo git clone https://github.com/pi-hole/AdminLTE /var/www/html/admin
the command itself failed as the nameserver went to 127.0.0.1.
i used the following command to temporary change it to 8.8.8.8
sudo tee /etc/resolv.conf <<< 'nameserver 8.8.8.8'
after the cloning worked
Cloning into '/var/www/html/admin'...
remote: Enumerating objects: 79, done.
remote: Counting objects: 100% (79/79), done.
remote: Compressing objects: 100% (68/68), done.
remote: Total 19709 (delta 28), reused 36 (delta 11), pack-reused 19630
Receiving objects: 100% (19709/19709), 27.08 MiB | 781.00 KiB/s, done.
Resolving deltas: 100% (10231/10231), done.
Try a pihole -r repair now.