ELF load command alignment not page-aligned

[dajiahao]

Hi,

I have an very old box (armv7l) which I destroyed by mistake my running borgbackup.
Entware is sucessfully installed but the package coming with entware always gives an error about an unsupported msgpack.

So I tried installing via pip

Successfully built borgbackup msgpack
Installing collected packages: msgpack, borgbackup
Successfully installed borgbackup-1.2.7 msgpack-1.0.7

but running borg I get this error:

borg
Traceback (most recent call last):
File "/opt/lib/python3.11/site-packages/borg/archiver.py", line 37, in
from . import helpers
File "/opt/lib/python3.11/site-packages/borg/helpers/init.py", line 9, in
from .checks import * # NOQA
^^^^^^^^^^^^^^^^^^^^^
File "/opt/lib/python3.11/site-packages/borg/helpers/checks.py", line 4, in
from .errors import Error
File "/opt/lib/python3.11/site-packages/borg/helpers/errors.py", line 3, in
import borg.crypto.low_level
ImportError: /opt/lib/python3.11/site-packages/borg/crypto/low_level.cpython-311-arm-linux-gnueabi.so: ELF load command alignment not page-aligned

Appreciate any suggestion on how to fix this.

[ThomasWaldmann]

About the entware package giving "unsupported msgpack": you have to contact the package maintainer about that. They should be careful and provide a msgpack as required by borgbackup.

About the "ELF load command alignment not page aligned": not sure where that comes from, never seen that before. Maybe an OpenSSL issue?

As a general note: you maybe don't want to run borg on too old / too small hardware. Borg needs some RAM to load the indexes into memory and older SBCs tend to not have a lot of RAM. Of course it also depends on the repository size.

[dajiahao]

about entware I asked there already

this machine only receives backup jobs, and usually small ones (less than 1TB), so far this was no problem until I thought I should update entware ... and now backing up to this machine fails - (never touch a running system - learned the hard way ;)

[ThomasWaldmann]

Closing this as outdated: it has seen no activity for a long time and predates the current borg releases.

If this still affects you on a current version - borg 1.4.x (stable) or the borg 2.0.0 beta - please open a new discussion with up-to-date details.