Skip to content
View in the app

A better way to browse. Learn more.
Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Unraid Summer Sale in live: 20% off Starter and Unleashed + buy one, get one 50% off

[Support] binhex - UrBackup

binhex
in Docker Containers

Featured Replies

I have noticed from binhex repo he has several versions he updated in 24hrs ago.

Hopefully he can let us know

  • Quote
    • Replies 529
    • Views 128.9k
    • Created
    • Last Reply

    Top Posters In This Topic

    Popular Days

    Most Popular Posts

    • KluthR
      KluthR

      Basically you remove UMASK, PUID and PGID variables and change the the variable for the backup to point to "/backups" (container path) and the appdata to "/var/urbackup" (container path).  

    • JonathanM
      JonathanM

      @betaman@Elmojo, I know this is an 18 page thread right now, but I really, really recommend reading it all. Keep in mind the first few pages are teething issues with older versions of the software and

    • binhex
      binhex

      just got some time to try a full system backup of my daily driver vm, then created a new vm, booted off the urbackup recovery media and restored, and voila it worked a treat!, restored vm booted up an

    Posted Images

    I went and pulled version 2.5.33-2-01, which is admittedly an old version, and it's running now. I'll keep an eye on the repository and see if a new update rolls out that may fix this issue.

  • Quote

    FWIW I updated and everything works fine for me.

  • Quote
    • Author
    2 hours ago, Kilrah said:

    FWIW I updated and everything works fine for me.

    Same for me, i use this, no issues here. I will investigate further, i have a feeling its a compilation issue affecting only certain processors. for now anyone affected please roll back to the previous tag.

  • Quote

    Like I said, it doesn't work for me.

    unraid.PNG

    This is the server hardware.

    I'm still running unRAID v6.12.14

    PS: I also pulled 2.5.33-2-01, this version works for me.

    Edited by Wimpie

  • Quote

    this my setup, I will wait for an update

    image.png

  • Quote

    Mounting images is not working (I swear it worked before).

    urbackupsrv mount-vhd --file Image_C_251106-1627.vhdz --mountpoint contents0

    Loading FUSE kernel module...

    modprobe: FATAL: Module fuse not found in directory /lib/modules/6.12.24-Unraid

    Starting VHD background process...

    Waiting for background process to become available...

    Mounting...

    fuse: failed to access mountpoint contents0: No such file or directory

    Mounting failed.

    I am on unraid 7.1.4, so why is it looking for fuse in a location mentioning 6.12.24?

  • Quote
    10 hours ago, SemiNormal said:

    I am on unraid 7.1.4, so why is it looking for fuse in a location mentioning 6.12.24?

    That's the linux kernel version, not unraid version

    I'm not aware of it ever been possible to mount images within the container.

    Edited by Kilrah

  • Quote
    • Thanks 1
    • Author
    1 hour ago, Kilrah said:

    I'm not aware of it ever been possible to mount images within the container.

    Same, this has never worked for me.

  • Quote
    • Thanks 1

    So if I want to pull files from an image backup, do I need to restore to a VM?

  • Quote
    • Author
    2 hours ago, SemiNormal said:

    So if I want to pull files from an image backup, do I need to restore to a VM?

    Yes, which is why if you want to restore individual files i would always recommend performing a file level backup (restore files) as well as a image level backup (restore machine).

  • Quote
    • Thanks 1
    • Upvote 1
    4 hours ago, SemiNormal said:

    So if I want to pull files from an image backup, do I need to restore to a VM?

    Should be able to assemble/export the image, then you can mount that wherever you want (obviously you need temp storage big enough to store the full uncompressed image)

    https://www.urbackup.org/administration_manual.html#x1-9400010.7

    But yeah the point of image backups is to restore an existing machine as is easily and fully, not give easy access to individual files.

    Edited by Kilrah

  • Quote
    On 11/12/2025 at 7:40 AM, ijuarez said:

    this my setup, I will wait for an update

    image.png

    Also using S2600CP and same issue. I think it might be an issue with the onboard NIC?

    How do we roll back versions again?

    Edited by betaman

  • Quote
    On 11/17/2025 at 12:29 PM, betaman said:

    Also using S2600CP and same issue. I think it might be an issue with the onboard NIC?

    How do we roll back versions again?

    I'm using binhex/arch-urbackup:2.5.33-2-01

  • Quote
    54 minutes ago, phreeq said:

    I'm using binhex/arch-urbackup:2.5.33-2-01

    Thanks. How do I install this version?

  • Quote

    Put that in the template's Repository line.

  • Quote
    1 hour ago, Kilrah said:

    Put that in the template's Repository line.

    Thanks…I knew it was simple. 🤦🏼‍♂️

  • Quote

    That worked for me, (putting binhex/arch-urbackup:2.5.33-2-01 in the repository line) its back up and running :-) Thanks Guys

  • Quote
    On 11/17/2025 at 12:29 PM, betaman said:

    Also using S2600CP and same issue. I think it might be an issue with the onboard NIC?

    How do we roll back versions again?

    I don't use the onboard nic i use a intel quad nic,

    Rolled back to the binhex/arch-urbackup:2.5.33-2-01 and it operational

  • Quote
    1 hour ago, ijuarez said:

    I don't use the onboard nic i use a intel quad nic,

    Rolled back to the binhex/arch-urbackup:2.5.33-2-01 and it operational

    Ok, I rolled back as well and it's working.

  • Quote
    • Author

    Hi all, i have pushed a new image which i hope fixes the issue with the image for certain people (does not affect me), please update and let me know.

  • Quote

    Hoi @binhex,

    Saw your message just now.

    I tried the new image (latest and then update), but it doesn't work for me.

    Hope the log helps, if you need anything else, let me know...

    In the mean time, going back to binhex/arch-urbackup:2.5.33-2-01...

    Created by...
___.   .__       .__
\_ |__ |__| ____ |  |__   ____ ___  ___
 | __ \|  |/    \|  |  \_/ __ \\  \/  /
 | \_\ \  |   |  \   Y  \  ___/ >    <
 |___  /__|___|  /___|  /\___  >__/\_ \
     \/        \/     \/     \/      \/
   https://hub.docker.com/u/binhex/

2025-11-25 13:05:37.885781 [info] Host is running unRAID
2025-11-25 13:05:37.916972 [info] System information: Linux TV-Tower-2 6.1.118-Unraid #1 SMP PREEMPT_DYNAMIC Thu Nov 21 15:54:38 PST 2024 x86_64 GNU/Linux
2025-11-25 13:05:37.955825 [info] Image architecture: 'amd64'
2025-11-25 13:05:38.002941 [info] Application name: 'urbackup'
2025-11-25 13:05:38.052286 [info] Base image release tag: '2025112201'
2025-11-25 13:05:38.088084 [info] Application image release tag: '2.5.34-1-02'
2025-11-25 13:05:38.125530 [info] PUID defined as '99'
2025-11-25 13:05:38.170413 [info] Executing usermod for PUID '99'...
2025-11-25 13:05:38.278140 [info] usermod completed successfully
2025-11-25 13:05:38.317381 [info] PGID defined as '100'
2025-11-25 13:05:38.350618 [info] Executing groupmod for PGID '100'...
2025-11-25 13:05:38.459368 [info] groupmod completed successfully
2025-11-25 13:05:38.489439 [info] UMASK defined as '000'
2025-11-25 13:05:38.520521 [info] Permissions file '/config/perms.txt' exists, skipping setting ownership and permissions on '/config' and '/data'
2025-11-25 13:05:38.553278 [info] Deleting files in /tmp (non recursive)...
[info] Creating soft link from /config/urbackup to /var/urbackup...
2025-11-25 13:05:41.854716 [info] Starting Supervisor...
2025-11-25 13:05:41,997 INFO Included extra file "/etc/supervisor/conf.d/urbackup.conf" during parsing
2025-11-25 13:05:41,997 INFO Set uid to user 0 succeeded
2025-11-25 13:05:42,001 INFO RPC interface 'supervisor' initialized
2025-11-25 13:05:42,002 INFO supervisord started with pid 7
2025-11-25 13:05:43,004 INFO spawned: 'urbackup' with pid 74
2025-11-25 13:05:43,004 INFO reaped unknown pid 8 (exit status 0)
2025-11-25 13:05:43,040 DEBG 'urbackup' stderr output:
/home/nobody/start.sh: line 20:    80 Illegal instruction        /usr/bin/urbackupsrv run --config '/config/urbackup/config/urbackupsrv' --no-consoletime

2025-11-25 13:05:43,040 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 23114002800928 for <Subprocess at 23114002792864 with name urbackup in state STARTING> (stdout)>
2025-11-25 13:05:43,040 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23114002441360 for <Subprocess at 23114002792864 with name urbackup in state STARTING> (stderr)>
2025-11-25 13:05:43,041 WARN exited: urbackup (exit status 132; not expected)
2025-11-25 13:05:43,041 DEBG received SIGCHLD indicating a child quit
2025-11-25 13:05:44,043 INFO spawned: 'urbackup' with pid 81
2025-11-25 13:05:44,058 DEBG 'urbackup' stderr output:
/home/nobody/start.sh: line 20:    87 Illegal instruction        /usr/bin/urbackupsrv run --config '/config/urbackup/config/urbackupsrv' --no-consoletime

2025-11-25 13:05:44,058 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 23114002441360 for <Subprocess at 23114002792864 with name urbackup in state STARTING> (stdout)>
2025-11-25 13:05:44,059 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23114002296480 for <Subprocess at 23114002792864 with name urbackup in state STARTING> (stderr)>
2025-11-25 13:05:44,059 WARN exited: urbackup (exit status 132; not expected)
2025-11-25 13:05:44,059 DEBG received SIGCHLD indicating a child quit
2025-11-25 13:05:46,062 INFO spawned: 'urbackup' with pid 88
2025-11-25 13:05:46,079 DEBG 'urbackup' stderr output:
/home/nobody/start.sh: line 20:    94 Illegal instruction        /usr/bin/urbackupsrv run --config '/config/urbackup/config/urbackupsrv' --no-consoletime

2025-11-25 13:05:46,080 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 23114002296480 for <Subprocess at 23114002792864 with name urbackup in state STARTING> (stdout)>
2025-11-25 13:05:46,080 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23114002717232 for <Subprocess at 23114002792864 with name urbackup in state STARTING> (stderr)>
2025-11-25 13:05:46,080 WARN exited: urbackup (exit status 132; not expected)
2025-11-25 13:05:46,080 DEBG received SIGCHLD indicating a child quit
2025-11-25 13:05:49,084 INFO spawned: 'urbackup' with pid 95
2025-11-25 13:05:49,098 DEBG 'urbackup' stderr output:
/home/nobody/start.sh: line 20:   101 Illegal instruction        /usr/bin/urbackupsrv run --config '/config/urbackup/config/urbackupsrv' --no-consoletime

2025-11-25 13:05:49,099 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 23114002923872 for <Subprocess at 23114002792864 with name urbackup in state STARTING> (stdout)>
2025-11-25 13:05:49,099 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23114002926320 for <Subprocess at 23114002792864 with name urbackup in state STARTING> (stderr)>
2025-11-25 13:05:49,099 WARN exited: urbackup (exit status 132; not expected)
2025-11-25 13:05:49,099 DEBG received SIGCHLD indicating a child quit
2025-11-25 13:05:50,100 INFO gave up: urbackup entered FATAL state, too many start retries too quickly

    Edited by Wimpie

  • Quote
    • Author
    1 hour ago, Wimpie said:

    Hoi @binhex,

    Saw your message just now.

    I tried the new image (latest and then update), but it doesn't work for me.

    Hope the log helps, if you need anything else, let me know...

    In the mean time, going back to binhex/arch-urbackup:2.5.33-2-01...

    Created by...
___.   .__       .__
\_ |__ |__| ____ |  |__   ____ ___  ___
 | __ \|  |/    \|  |  \_/ __ \\  \/  /
 | \_\ \  |   |  \   Y  \  ___/ >    <
 |___  /__|___|  /___|  /\___  >__/\_ \
     \/        \/     \/     \/      \/
   https://hub.docker.com/u/binhex/

2025-11-25 13:05:37.885781 [info] Host is running unRAID
2025-11-25 13:05:37.916972 [info] System information: Linux TV-Tower-2 6.1.118-Unraid #1 SMP PREEMPT_DYNAMIC Thu Nov 21 15:54:38 PST 2024 x86_64 GNU/Linux
2025-11-25 13:05:37.955825 [info] Image architecture: 'amd64'
2025-11-25 13:05:38.002941 [info] Application name: 'urbackup'
2025-11-25 13:05:38.052286 [info] Base image release tag: '2025112201'
2025-11-25 13:05:38.088084 [info] Application image release tag: '2.5.34-1-02'
2025-11-25 13:05:38.125530 [info] PUID defined as '99'
2025-11-25 13:05:38.170413 [info] Executing usermod for PUID '99'...
2025-11-25 13:05:38.278140 [info] usermod completed successfully
2025-11-25 13:05:38.317381 [info] PGID defined as '100'
2025-11-25 13:05:38.350618 [info] Executing groupmod for PGID '100'...
2025-11-25 13:05:38.459368 [info] groupmod completed successfully
2025-11-25 13:05:38.489439 [info] UMASK defined as '000'
2025-11-25 13:05:38.520521 [info] Permissions file '/config/perms.txt' exists, skipping setting ownership and permissions on '/config' and '/data'
2025-11-25 13:05:38.553278 [info] Deleting files in /tmp (non recursive)...
[info] Creating soft link from /config/urbackup to /var/urbackup...
2025-11-25 13:05:41.854716 [info] Starting Supervisor...
2025-11-25 13:05:41,997 INFO Included extra file "/etc/supervisor/conf.d/urbackup.conf" during parsing
2025-11-25 13:05:41,997 INFO Set uid to user 0 succeeded
2025-11-25 13:05:42,001 INFO RPC interface 'supervisor' initialized
2025-11-25 13:05:42,002 INFO supervisord started with pid 7
2025-11-25 13:05:43,004 INFO spawned: 'urbackup' with pid 74
2025-11-25 13:05:43,004 INFO reaped unknown pid 8 (exit status 0)
2025-11-25 13:05:43,040 DEBG 'urbackup' stderr output:
/home/nobody/start.sh: line 20:    80 Illegal instruction        /usr/bin/urbackupsrv run --config '/config/urbackup/config/urbackupsrv' --no-consoletime

2025-11-25 13:05:43,040 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 23114002800928 for <Subprocess at 23114002792864 with name urbackup in state STARTING> (stdout)>
2025-11-25 13:05:43,040 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23114002441360 for <Subprocess at 23114002792864 with name urbackup in state STARTING> (stderr)>
2025-11-25 13:05:43,041 WARN exited: urbackup (exit status 132; not expected)
2025-11-25 13:05:43,041 DEBG received SIGCHLD indicating a child quit
2025-11-25 13:05:44,043 INFO spawned: 'urbackup' with pid 81
2025-11-25 13:05:44,058 DEBG 'urbackup' stderr output:
/home/nobody/start.sh: line 20:    87 Illegal instruction        /usr/bin/urbackupsrv run --config '/config/urbackup/config/urbackupsrv' --no-consoletime

2025-11-25 13:05:44,058 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 23114002441360 for <Subprocess at 23114002792864 with name urbackup in state STARTING> (stdout)>
2025-11-25 13:05:44,059 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23114002296480 for <Subprocess at 23114002792864 with name urbackup in state STARTING> (stderr)>
2025-11-25 13:05:44,059 WARN exited: urbackup (exit status 132; not expected)
2025-11-25 13:05:44,059 DEBG received SIGCHLD indicating a child quit
2025-11-25 13:05:46,062 INFO spawned: 'urbackup' with pid 88
2025-11-25 13:05:46,079 DEBG 'urbackup' stderr output:
/home/nobody/start.sh: line 20:    94 Illegal instruction        /usr/bin/urbackupsrv run --config '/config/urbackup/config/urbackupsrv' --no-consoletime

2025-11-25 13:05:46,080 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 23114002296480 for <Subprocess at 23114002792864 with name urbackup in state STARTING> (stdout)>
2025-11-25 13:05:46,080 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23114002717232 for <Subprocess at 23114002792864 with name urbackup in state STARTING> (stderr)>
2025-11-25 13:05:46,080 WARN exited: urbackup (exit status 132; not expected)
2025-11-25 13:05:46,080 DEBG received SIGCHLD indicating a child quit
2025-11-25 13:05:49,084 INFO spawned: 'urbackup' with pid 95
2025-11-25 13:05:49,098 DEBG 'urbackup' stderr output:
/home/nobody/start.sh: line 20:   101 Illegal instruction        /usr/bin/urbackupsrv run --config '/config/urbackup/config/urbackupsrv' --no-consoletime

2025-11-25 13:05:49,099 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 23114002923872 for <Subprocess at 23114002792864 with name urbackup in state STARTING> (stdout)>
2025-11-25 13:05:49,099 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23114002926320 for <Subprocess at 23114002792864 with name urbackup in state STARTING> (stderr)>
2025-11-25 13:05:49,099 WARN exited: urbackup (exit status 132; not expected)
2025-11-25 13:05:49,099 DEBG received SIGCHLD indicating a child quit
2025-11-25 13:05:50,100 INFO gave up: urbackup entered FATAL state, too many start retries too quickly

    Thanks for trying, could you try pulling down the latest image again (just tweaked it some more) and let me know the result.

  • Quote

    We might have a winner...

    First I got:

    unraid_urbackup.JPG

    Then the website worked.

    unraid_urbackup3.JPG

    This is the log:

    Created by...
___.   .__       .__
\_ |__ |__| ____ |  |__   ____ ___  ___
 | __ \|  |/    \|  |  \_/ __ \\  \/  /
 | \_\ \  |   |  \   Y  \  ___/ >    <
 |___  /__|___|  /___|  /\___  >__/\_ \
     \/        \/     \/     \/      \/
   https://hub.docker.com/u/binhex/

2025-11-25 20:14:39.769416 [info] Host is running unRAID
2025-11-25 20:14:39.804091 [info] System information: Linux TV-Tower-2 6.1.118-Unraid #1 SMP PREEMPT_DYNAMIC Thu Nov 21 15:54:38 PST 2024 x86_64 GNU/Linux
2025-11-25 20:14:39.834078 [info] Image architecture: 'amd64'
2025-11-25 20:14:39.878105 [info] Application name: 'urbackup'
2025-11-25 20:14:39.907256 [info] Base image release tag: '2025112201'
2025-11-25 20:14:39.936647 [info] Application image release tag: '2.5.34-1-04'
2025-11-25 20:14:39.968364 [info] PUID defined as '99'
2025-11-25 20:14:39.999452 [info] Executing usermod for PUID '99'...
2025-11-25 20:14:40.086781 [info] usermod completed successfully
2025-11-25 20:14:40.120999 [info] PGID defined as '100'
2025-11-25 20:14:40.172512 [info] Executing groupmod for PGID '100'...
2025-11-25 20:14:40.288056 [info] groupmod completed successfully
2025-11-25 20:14:40.317654 [info] UMASK defined as '000'
2025-11-25 20:14:40.348670 [info] Permissions file '/config/perms.txt' exists, skipping setting ownership and permissions on '/config' and '/data'
2025-11-25 20:14:40.382920 [info] Deleting files in /tmp (non recursive)...
[info] Creating soft link from /config/urbackup to /var/urbackup...
2025-11-25 20:14:43.634811 [info] Starting Supervisor...
2025-11-25 20:14:43,775 INFO Included extra file "/etc/supervisor/conf.d/urbackup.conf" during parsing
2025-11-25 20:14:43,775 INFO Set uid to user 0 succeeded
2025-11-25 20:14:43,779 INFO RPC interface 'supervisor' initialized
2025-11-25 20:14:43,780 INFO supervisord started with pid 7
2025-11-25 20:14:44,782 INFO spawned: 'urbackup' with pid 74
2025-11-25 20:14:44,783 INFO reaped unknown pid 8 (exit status 0)
2025-11-25 20:14:44,808 DEBG 'urbackup' stderr output:
Raising maximum file descriptor to 65535 failed. This may cause problems with many clients. (errno=1)
Raising nice-ceiling to 35 failed. (errno=1)

2025-11-25 20:14:45,809 INFO success: urbackup entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-11-25 20:14:51,441 DEBG 'urbackup' stdout output:
MOUNT TEST OK

2025-11-25 20:14:51,445 DEBG 'urbackup' stdout output:
Testing for btrfs...

2025-11-25 20:14:51,450 DEBG 'urbackup' stderr output:
ERROR: Could not create subvolume: Inappropriate ioctl for device

2025-11-25 20:14:51,451 DEBG 'urbackup' stdout output:
TEST FAILED: Creating test btrfs subvolume failed

2025-11-25 20:14:51,451 DEBG 'urbackup' stdout output:
Testing for zfs...
TEST FAILED: Dataset is not set via /etc/urbackup/dataset

    I don't have a ZFS drive, and also no BTRFS drive that is backed up by urbackup (it's a XFS drive). Don't know what the "Could not create subvolume: Inappropriate ioctl for device" means (test for BTRFS drives ?).

    Don't know if these are important:

    Raising maximum file descriptor to 65535 failed. This may cause problems with many clients. (errno=1)
Raising nice-ceiling to 35 failed. (errno=1)

    Haven't tried a restore or anything else, just a startup of the docker.

    One strange thing: I used to have 2 port mappings, they are gone. The website works though...

    unraid_urbackup2.JPG

    Thanks for looking into this...

    Edited by Wimpie

  • Quote

    I had tonight a few backups working, didn't find any errors in the urbackup error log. So I think it is solved.

    Thanks Binhex!

  • Quote

    • Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Reply to this topic...
    Go to topic listing

    Account

    Navigation

    Search

    Search

    Configure browser push notifications
    Chrome (Android)
    1. Tap the lock icon next to the address bar.
    2. Tap Permissions → Notifications.
    3. Adjust your preference.
    Chrome (Desktop)
    1. Click the padlock icon in the address bar.
    2. Select Site settings.
    3. Find Notifications and adjust your preference.