[Backup Plugin] dd full disk backup failed - zstd: error while loading shared libraries

1st Official Post
    • New

    Dear OMV Community,


    I am running OMV 7 on a Raspberry Pi 5 8 GB. OMV is installed on an SD card (only OS, no user data), the data drive is an NVMe SSD connected via PCIe. Following the recommendations in this thread, I am trying to configure the backup plugin to create a dd full disk backup to have an image I can easily restore by writing it back to the SD card.


    When I run the backup I get one of the following errors (it is inconsistent, which):


    Case 1:

    [2024-09-22 16:21:02+0200] [backup] Starting dd full disk ...

    zstd: error while loading shared libraries: LZ4_versionString: cannot open shared object file: No such file or directory

    [2024-09-22 16:21:02+0200] [backup] ERROR: zstd exit code = 0

    [2024-09-22 16:21:02+0200] [backup] ERROR: dd full disk backup failed!


    Case 2:

    [2024-09-22 17:23:33+0200] [backup] Starting dd full disk ...

    zstd: error while loading shared libraries: ead_cond_signal: cannot open shared object file: No such file or directory

    [2024-09-22 17:23:33+0200] [backup] ERROR: zstd exit code = 0

    [2024-09-22 17:23:33+0200] [backup] ERROR: dd full disk backup failed!


    The LZ4 library seems to be installed fine:


    Otherwise OMV seems to work fine. Do you have any ideas, how I could resolve this?


    Thank you in advance.

    • New
    • Official Post

    What is the output of: dpkg -l | grep lz4

    omv 7.4.8-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.14 | compose 7.2.5 | k8s 7.3.1-1 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.9


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • New

    Thanks for the fast response!


    I installed the package:

    However, I am still getting the same error:

    Tried sudo ldconfig and rebooting, did not make a difference.

    • New
    • Official Post

    How old is the SD card?

    omv 7.4.8-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.14 | compose 7.2.5 | k8s 7.3.1-1 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.9


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • New
    • Official Post
    Quote from FDanee

    I installed the package:

    I was wrong about that and deleted that post. It doesn't hurt to install the package though.

    omv 7.4.8-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.14 | compose 7.2.5 | k8s 7.3.1-1 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.9


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • New
    • Official Post

    These errors are sometimes a sign the card is going bad.


    What about:


    dpkg -l | grep libc6

    dpkg -l | grep -v ^ii

    omv 7.4.8-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.14 | compose 7.2.5 | k8s 7.3.1-1 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.9


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • New

    Here you go:

    • New
    • Official Post

    I would guess the SD card is going bad. What brand and model?

    omv 7.4.8-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.14 | compose 7.2.5 | k8s 7.3.1-1 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.9


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • New
    • Official Post

    that is a good card. Did you buy from a reputable place? I would test it with f3.

    omv 7.4.8-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.14 | compose 7.2.5 | k8s 7.3.1-1 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.9


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • New

    sudo apt-get reinstall zstd fixed the issue, I was able to complete a dd full disk backup successfully.


    I am still curious about the SD card. What is the best way to check the integrity of the file system while running? Also, I am planning to switch to a smaller card anyway, the OS does not need 128 GB and imaging the complete device takes forever.

  • FDanee

    Added the Label resolved
    • New
    • Official Post
    Quote from FDanee

    What is the best way to check the integrity of the file system while running?

    I would start with f3 to check the card. fsck can check the filesystem but that will most likely not find storage level corruption.

    Quote from FDanee

    sudo apt-get reinstall zstd fixed the issue, I was able to complete a dd full disk backup successfully.

    That almost confirms that you have storage level corruption.


    Quote from FDanee

    Also, I am planning to switch to a smaller card anyway, the OS does not need 128 GB and imaging the complete device takes forever.

    If you clone the current system to a new card, you will most likely clone the corruption to the new card. I would look at omv-regen.

    omv 7.4.8-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.14 | compose 7.2.5 | k8s 7.3.1-1 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.9


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • New

    Well, this is awkward...


    I transferred the system with the omv-regen method to a brand new 32 GB SanDisk Max Endurance card I tested before with h2testw. Did everything according to the omv-regen guide: install Bookworm Lite image to SD card, install fresh OMV, run omv-regen, etc.


    Then I tried to run a dd full disk backup again, and got the exact same error:

    Ran sudo apt-get reinstall zstd again, now it is working.


    At this point I am ready to classify this as something else than storage corruption. Nevertheless, as I wanted to move to a smaller SD card anyway, it was ultimately a useful exercise and good learning opportunity. Also, it was amazing to experience, how seamlessly a major surgery like this went thanks to the tooling, kudos to everyone involved.

    • New
    • Official Post

    Not sure what the issue could be. I just tried it on an RPi4 and my dev VM. No issues. I wonder if zstd is install on the RPI image by default and it was installed incorrectly. I would have to flash a new image.

    omv 7.4.8-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.14 | compose 7.2.5 | k8s 7.3.1-1 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.9


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • New

    I am experiencing this same issue, and did all the troubleshooting steps above.


    After testing the brand-new 32 GB microSD card w/ F3 (passed perfectly), I reflashed with most recent version of RPI-OS using the official tool on Ubuntu Linux. Then reinstalled OMV 7 via bash script. Same problem.


    When I reinstall zstd and liblz4-1 via apt, the backup will then work ONCE. If I try it again immediately after, it will return a segmentation fault. Reboot, same problem. Reinstall zstd and liblz4-1 and it will work again ONCE.

    OMV 7.4.8-1 (Sandworm)


    Hardware

    Raspberry Pi 5 Model B Rev 1.0, 8 GB RAM

    32 GB SanDisk micro SD card

    4 x 1 TB HDD in RAID5 (EXT)


    Kernel

    Linux 6.6.47+rpt-rpi-2712

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login