Closed rosskevin closed 5 months ago
As an FYI - I edited to adjust prune minimums to recommended nethermind minimums but failed because I only have 205G free:
kross@sauce:~/eth-docker$ ./ethd prune-nethermind
You do not have enough free disk space. Make sure this reads at least 250G free (Avail):
Here's total and used space on /var/lib/docker
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/ubuntu--vg-ubuntu--lv 1.9T 1.6T 205G 89% /
Aborting.
I saw:
If your Consensus Layer client takes more than 300 GiB, you can resync it with
"./ethd resync-consensus".
So I executed that, which takes everything offline but removes the 414.4GB
volume for consensus, which allowed me to execute ./ethd prune-nethermind
.
Perhaps it is unexpected for my lighthouse consensus to grow so big which is impacting nethermind auto prune success?
That Lighthouse grows that big is expected. A periodic resync of Lighthouse helps.
Most likely you didn’t have enough space for Nethermind to actually prune. It was below 350 GiB to start the prune, but not above the 270 or so it needs at a minimum. That minimum may increase with time.
This isn’t an Eth Docker issue.
In the near term both Lighthouse tree states (not ready yet) and Nethermind Path or Paprika (also not ready yet) can extend the usefulness of a 2TB drive.
In the medium term you’ll want to get a 4TB drive, see the drive gist, and CloneZilla your setup over. Remy has a good guide.
2TB should run out sometime early mid 2025.
This originally happened about three weeks ago. I ran out of space when auto-pruning had been maintaining on a 2TB drive. I accepted it, update the system and performed a resync. I enabled disk space notification on Beaconcha.in.
Fast forward to today, and I'm at 90% usage, received a notification and can't execute a prune.
Startup:
I'm going to force a resync (again) unless there is some information I can provide that would be helpful.
I'm not sure why auto prune is either not keeping up or not running.