2.6.0 beta 3 update failed on disk and/or memory space

I think you can improve this with journalctl maybe with

# journalctl --vacuum-size=50M

(which you might do immediately before trying an upgrade)

Interesting that the postgresql usage hasn’t gone down.

free will show you the swap usage: it’s 17% used, of some amount, probably 2G.

It’s clear that your machine is a little uncomfortably small: you need more RAM or more swap, and you can’t practically have much more swap without getting more disk.