Unable to build gravity tree in /etc/pihole/gravity.db_temp

Just noticed, whilst updating, this in the terminal:

As far as I can see, it's working ok, just reporting.
Anything I should do/check?

[i] Building tree...
[✗] Unable to build gravity tree in /etc/pihole/gravity.db_temp
Error: stepping, disk I/O error (10)
[i] Number of gravity domains: 118256 (117937 unique domains)
[i] Number of exact denied domains: 0
[i] Number of regex denied filters: 0
[i] Number of exact allowed domains: 0
[i] Number of regex allowed filters: 0
[✓] Optimizing database
[✓] Swapping databases
[✓] The old database remains available
[✓] Cleaning up stray matter

[✓] Done.

[i] The install log is located at: /etc/pihole/install.log
[✓] Update complete!

Core
Version is v5.18.4-621-g0f31802 (Latest: null)
Branch is development
Hash is 0f318027 (Latest: 0f318027)
Web
Version is v5.21-959-g7acf464 (Latest: null)
Branch is devel
Hash is 7acf4647 (Latest: 7acf4647)
FTL
Version is vDev-817aad9 (Latest: null)
Branch is development
Hash is 817aad91 (Latest: 817aad91)

Please upload a debug log and post just the token URL that is generated after the log is uploaded by running the following command from the Pi-hole host terminal:

pihole -d

Thanks. Just for completeness, I've noticed one of my block lists, Smart TV, was no longer available/moved URL, that was updated/corrected since my post, before the debug,

[✓] Your debug token is: https://tricorder.pi-hole.net/oW2kjiC8/

Looks like gravity update was executed correctly, even with the error message.

The error points to a disk issue, but I'm not sure what was the issue exactly.

Do you see the same error if you try to repeat gravity update (pihole -g)?


Note:

There is an older issue with exactly the same title, but in German:

In that case, apparently it was a SD card issue.

thanks again.
I've never noticed earlier any such issues - though, I don't always review everything...

I tried fsck, not sure at this point how to proceed...

~ $ sudo pihole -g
[✓] DNS resolution is available

[i] Neutrino emissions detected...
[✓] Pulling blocklist source list into range

[✓] Preparing new gravity database
[✓] Creating new gravity databases
[i] Using libz compression

[i] Target: https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
[✓] Status: Retrieval successful
[✓] Parsed 117214 exact domains and 0 ABP-style domains (blocking, ignored 0 non-domain entries)
[i] List stayed unchanged

[i] Target: https://raw.githubusercontent.com/Perflyst/PiHoleBlocklist/master/SmartTV.txt
[✓] Status: Retrieval successful
[✓] Parsed 242 exact domains and 0 ABP-style domains (blocking, ignored 0 non-domain entries)
[i] List stayed unchanged

[i] Target: https://v.firebog.net/hosts/static/w3kbl.txt
[✓] Status: No changes detected
[✓] Parsed 351 exact domains and 0 ABP-style domains (blocking, ignored 0 non-domain entries)

[i] Target: https://raw.githubusercontent.com/d3ward/toolz/master/src/d3host.txt
[✓] Status: Retrieval successful
[✓] Parsed 131 exact domains and 0 ABP-style domains (blocking, ignored 0 non-domain entries)
[i] List stayed unchanged

[i] Target: https://raw.githubusercontent.com/MajkiIT/polish-ads-filter/master/polish-pihole-filters/hostfile.txt
[✓] Status: Retrieval successful
[✓] Parsed 318 exact domains and 0 ABP-style domains (blocking, ignored 0 non-domain entries)
[i] List stayed unchanged

[i] Target: https://raw.githubusercontent.com/hkamran80/blocklists/main/smart-tv.txt
[✓] Status: Retrieval successful
[✓] Parsed 290 exact domains and 0 ABP-style domains (blocking, ignored 0 non-domain entries)
[i] List stayed unchanged

[✓] Building tree
[i] Number of gravity domains: 118546 (118007 unique domains)
[i] Number of exact denied domains: 0
[i] Number of regex denied filters: 0
[i] Number of exact allowed domains: 0
[i] Number of regex allowed filters: 0
[✓] Optimizing database
[✓] Swapping databases
[✓] The old database remains available
[✓] Cleaning up stray matter

[✓] Done.
~ $ df -H
Filesystem Size Used Avail Use% Mounted on
udev 1.8G 0 1.8G 0% /dev
tmpfs 398M 55M 344M 14% /run
/dev/mmcblk0p2 16G 8.1G 6.2G 57% /
tmpfs 2.0G 2.2M 2.0G 1% /dev/shm
tmpfs 5.3M 17k 5.3M 1% /run/lock
/dev/mmcblk0p1 535M 80M 456M 15% /boot/firmware
tmpfs 33M 447k 33M 2% /var/cache/fontconfig
tmpfs 398M 46k 398M 1% /run/user/1000

:~ $ sudo fsck /dev/mmcblk0p1
fsck from util-linux 2.38.1
fsck.fat 4.2 (2021-01-31)
There are differences between boot sector and its backup.
This is mostly harmless. Differences: (offset:original/backup)
65:01/00

  1. Copy original to backup
  2. Copy backup to original
  3. No action
    [123?q]? q

~ $ sudo fsck /dev/mmcblk0p1
fsck from util-linux 2.38.1
fsck.fat 4.2 (2021-01-31)
There are differences between boot sector and its backup.
This is mostly harmless. Differences: (offset:original/backup)
65:01/00

  1. Copy original to backup
  2. Copy backup to original
  3. No action
    [123?q]? 1
    Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
  4. Remove dirty bit
  5. No action
    [12?q]? 1

*** Filesystem was changed ***
The changes have not yet been written, you can still choose to leave the
filesystem unmodified:

  1. Write changes
  2. Leave filesystem unchanged
    [12?q]? 1
    /dev/mmcblk0p1: 395 files, 38795/261115 clusters

Gravity update was executed without issues.

If you aren't seeing more error messages, I don't think you need to do anything. Pay attention to any other filesystem errors, but maybe it was a temporary issue.

1 Like