in the template, 
please show me your setting for the mounting part (pbs_etc,  pbs_logs,  pbs_lib, Backup Dir)
and also 
the permision of those dir on the array 
thanks

2 hours ago, ZappyZap said:

in the template, 
please show me your setting for the mounting part (pbs_etc,  pbs_logs,  pbs_lib, Backup Dir)
and also 
the permision of those dir on the array 
thanks

I left everything with default values.

 

drop in a shell and provide output of :
 

ls -al /mnt/user/appdata/pbs
ls -la /mnt/user/pbs_backup

 

Thanks

On 2/10/2025 at 3:59 PM, ZappyZap said:

drop in a shell and provide output of :
 

ls -al /mnt/user/appdata/pbs
ls -la /mnt/user/pbs_backup

 

Thanks

root@*********:~# ls -al /mnt/user/appdata/pbs
total 0
drwxr-xr-x 1 root   root   20 Feb 10 09:09 ./
drwxrwxrwx 1 nobody users 648 Jan 14 15:34 ../
drwx------ 1     34    34 302 Feb 10 13:40 etc/
drwx------ 1     34    34  88 Feb 11 01:28 lib/
drwx------ 1     34    34  16 Feb 10 09:11 logs/
root@*********:~# ls -la /mnt/user/pbs_backup
total 4
drwxr-xr-x 1 nobody users    0 Feb 10 09:09 ./
drwxrwxrwx 1 nobody users 4096 Feb 11 04:41 ../
root@*********:~# 

 

Thank you for following up

Edited February 15, 20251 yr by Sickdove
Solved

I've started having problems with my PVE nodes crashing when the backup process runs. I suspect this is a recent update to PVE that I ran, which then quickly had a follow up set of patches for the kernel and the backup services on PVE. Makes me think there was a problem on the initial 8.4 patches. I ran those quick updates this week, but had another node crash last night during the backup. At least I suspect it was when the backup started, because the only node that crashed last night was the one node that had a backup scheduled. 

 

I'm now looking at what the possible causes might be. There are no additional patches available on the no-sub repo for PVE as of this morning. I might just have to wait for that to make it's way down from the Ent repo. As part of the recent patches I did update to PVE 8.4 and all of the PVE backup components were updated to the same release.

 

I noticed that PBS has been updated to 3.4. Estimate on when we'll get that updated to this container for Unraid? I have no idea if that will help, but I'm trying to rule out whatever I can.

 

Thanks for building this container!

i will look at this , 
i ask the maintainer of the docker image to update it.

Do we backup to a share on the array, or does it need to be a disk/share (not array).

 

I had a VM setup to run pbs, but wondering if this docker is as good (id sooner pbs in docker)

Edited May 3, 20251 yr by greygoose1

i'm running into issues OS error 39 when backing up to a specific storage, but not with other ones.

pbs error:

2025-08-24T12:55:21-07:00: starting new backup on datastore 'array' from ::ffff:192.168.200.50: "ct/104/2025-08-24T19:55:16Z"
2025-08-24T12:55:21-07:00: protocol upgrade done
2025-08-24T12:55:21-07:00: GET /previous_backup_time
2025-08-24T12:55:21-07:00: GET /previous
2025-08-24T12:55:21-07:00: download 'index.json.blob' from previous backup 'ct/104/2025-08-22T10:01:19Z'.
2025-08-24T12:55:21-07:00: POST /blob
2025-08-24T12:55:21-07:00: add blob "/backup/array/ct/104/2025-08-24T19:55:16Z/pct.conf.blob" (242 bytes, comp: 242)
2025-08-24T12:55:21-07:00: POST /dynamic_index
2025-08-24T12:55:21-07:00: created new dynamic index 1 ("ct/104/2025-08-24T19:55:16Z/catalog.pcat1.didx")
2025-08-24T12:55:21-07:00: GET /previous
2025-08-24T12:55:21-07:00: register chunks in 'root.pxar.didx' from previous backup 'ct/104/2025-08-22T10:01:19Z'.
2025-08-24T12:55:21-07:00: download 'root.pxar.didx' from previous backup 'ct/104/2025-08-22T10:01:19Z'.
2025-08-24T12:55:21-07:00: POST /dynamic_index
2025-08-24T12:55:21-07:00: created new dynamic index 2 ("ct/104/2025-08-24T19:55:16Z/root.pxar.didx")
2025-08-24T12:55:25-07:00: POST /dynamic_chunk
2025-08-24T12:55:25-07:00: POST /dynamic_chunk: 400 Bad Request: inserting chunk on store 'array' failed for ce3d65000809b05d69c97a86bb878b6153dcd1909b946448683ea177547c17c8 - mkstemp "/backup/array/.chunks/ce3d/ce3d65000809b05d69c97a86bb878b6153dcd1909b946448683ea177547c17c8.tmp_XXXXXX" failed: ENOENT: No such file or directory
2025-08-24T12:55:38-07:00: backup ended and finish failed: backup ended but finished flag is not set.
2025-08-24T12:55:38-07:00: removing unfinished backup
2025-08-24T12:55:38-07:00: removing backup snapshot "/backup/array/ct/104/2025-08-24T19:55:16Z"
2025-08-24T12:55:38-07:00: TASK ERROR: removing backup snapshot "/backup/array/ct/104/2025-08-24T19:55:16Z" failed - Directory not empty (os error 39)

I have verified that the referred folder is indeed empty:

# ls -al /backup/array/ct/104/2025-08-24T19:55:16Z
total 0

Also not all backup to this storage fails, many do go through without a problem:

2025-08-24T12:55:59-07:00: starting new backup on datastore 'array' from ::ffff:192.168.200.50: "ct/105/2025-08-24T19:55:54Z"
2025-08-24T12:55:59-07:00: protocol upgrade done
2025-08-24T12:55:59-07:00: GET /previous_backup_time
2025-08-24T12:55:59-07:00: GET /previous
2025-08-24T12:55:59-07:00: download 'index.json.blob' from previous backup 'ct/105/2025-08-24T10:05:39Z'.
2025-08-24T12:55:59-07:00: POST /blob
2025-08-24T12:55:59-07:00: add blob "/backup/array/ct/105/2025-08-24T19:55:54Z/pct.conf.blob" (242 bytes, comp: 242)
2025-08-24T12:55:59-07:00: POST /dynamic_index
2025-08-24T12:55:59-07:00: created new dynamic index 1 ("ct/105/2025-08-24T19:55:54Z/catalog.pcat1.didx")
2025-08-24T12:55:59-07:00: GET /previous
2025-08-24T12:55:59-07:00: register chunks in 'root.pxar.didx' from previous backup 'ct/105/2025-08-24T10:05:39Z'.
2025-08-24T12:55:59-07:00: download 'root.pxar.didx' from previous backup 'ct/105/2025-08-24T10:05:39Z'.
2025-08-24T12:55:59-07:00: POST /dynamic_index
2025-08-24T12:55:59-07:00: created new dynamic index 2 ("ct/105/2025-08-24T19:55:54Z/root.pxar.didx")
2025-08-24T12:58:28-07:00: PUT /dynamic_index
2025-08-24T12:58:28-07:00: dynamic_append 128 chunks
2025-08-24T12:58:28-07:00: successfully added chunk 69747f61d204bfd2d40847db5cb24e98bea087734b8b41ac33f1f4443df1564a to dynamic index 2 (offset 0, size 3040670)
2025-08-24T12:58:28-07:00: successfully added chunk 3d0a06dc713c329e9c6cfc9dece971cbf3b81cf57a093fbd1a2aa1e0a00e6fec to 
...
...
...
2025-08-24T12:58:38-07:00: successfully added chunk 09fddc974d7ab2457cd92ce23609a82ffd4f57aae2a29c0d1aabe36ecdbdf63d to dynamic index 2 (offset 534114720, size 613221)
2025-08-24T12:58:38-07:00: POST /dynamic_close
2025-08-24T12:58:38-07:00: Upload statistics for 'root.pxar.didx'
2025-08-24T12:58:38-07:00: UUID: 41b02de881094f06b318e87ca0daea46
2025-08-24T12:58:38-07:00: Checksum: 4bddaab6629b0eb216e7e687424b1e3a579221a4f9824821cfb14e95642aae12
2025-08-24T12:58:38-07:00: Size: 534727941
2025-08-24T12:58:38-07:00: Chunk count: 147
2025-08-24T12:58:38-07:00: Upload size: 0 (0%)
2025-08-24T12:58:38-07:00: Duplicates: 147+0 (100%)
2025-08-24T12:58:38-07:00: successfully closed dynamic index 2
2025-08-24T12:58:38-07:00: POST /dynamic_chunk
2025-08-24T12:58:38-07:00: upload_chunk done: 433529 bytes, a480f82fa6dd2053316fa7cf938dad1672b112e3c31402e982b7dd16857f9353
2025-08-24T12:58:38-07:00: PUT /dynamic_index
2025-08-24T12:58:38-07:00: dynamic_append 1 chunks
2025-08-24T12:58:38-07:00: successfully added chunk a480f82fa6dd2053316fa7cf938dad1672b112e3c31402e982b7dd16857f9353 to dynamic index 1 (offset 0, size 433529)
2025-08-24T12:58:38-07:00: POST /dynamic_close
2025-08-24T12:58:38-07:00: Upload statistics for 'catalog.pcat1.didx'
2025-08-24T12:58:38-07:00: UUID: 82ac4294d1da48e5b9fdc7bf38ffa022
2025-08-24T12:58:38-07:00: Checksum: 27ad341c7a863baea72bd01f1d17fc2d9834463cc7cd2bd2eabc536dfdb124f9
2025-08-24T12:58:38-07:00: Size: 433529
2025-08-24T12:58:38-07:00: Chunk count: 1
2025-08-24T12:58:38-07:00: Upload size: 433529 (100%)
2025-08-24T12:58:38-07:00: Duplicates: 0+1 (100%)
2025-08-24T12:58:38-07:00: Compression: 42%
2025-08-24T12:58:38-07:00: successfully closed dynamic index 1
2025-08-24T12:58:38-07:00: POST /blob
2025-08-24T12:58:38-07:00: add blob "/backup/array/ct/105/2025-08-24T19:55:54Z/index.json.blob" (480 bytes, comp: 480)
2025-08-24T12:58:38-07:00: POST /finish
2025-08-24T12:58:38-07:00: syncing filesystem
2025-08-24T12:58:38-07:00: successfully finished backup
2025-08-24T12:58:38-07:00: backup finished successfully
2025-08-24T12:58:38-07:00: TASK OK

Thanks!

1 hour ago, myusername said:

it seems to be that no matter the settings on this update, PBS is using the docker vDISK for backup storage regardless of the settings when setting up the docker container on unraid, and/or configuring the datastore within PBS itself

Is this in reply to the issue I posted?

My configuration should be pretty normal, any clue why it would behave this way?

Hello, I installed this for the first time and nothing comes up from the webui. Took all the defaults, only changed the Timezone.. Any idea what the issue is? Here is what the log says

2 hours ago, Dro said:

Hello, I installed this for the first time and nothing comes up from the webui. Took all the defaults, only changed the Timezone.. Any idea what the issue is? Here is what the log says

check the permission of your mount point in the Host.

19 hours ago, ZappyZap said:

check the permission of your mount point in the Host.

Its just the standard appdata path /mnt/user/appdata where all my other docker containers reside, all permissions are ok there. Is there something specific i need to do for this that i missed somewhere? Everything i left default.

please post the permission

10 hours ago, ZappyZap said:

please post the permission

Is this what you want?

can you put the perm of.
/mnt/user/appdata/pbs

Seem like your directory are not correctly set
for /etc/proxmox-backup. you have set /mnt/user/appdata/pbs/etc
but the etc. directory seems to be in /mnt/user/pbs_backup

Edited November 6, 2025Nov 6 by ZappyZap

Hmm, like i said above i did not change anything. I just took the defaults of the container.. so that is strange..

here are the default for this template :

and your SS match it
but your FS seems to say otherwise

Edited November 6, 2025Nov 6 by ZappyZap

maybe i am being dense but can you explain to me how the FS says otherwise? Your screenshot matches mine exactly and above you said i have mine set to this below, but the template is set that way as well? I don't get what I am missing.

Seem like your directory are not correctly set
for /etc/proxmox-backup. you have set /mnt/user/appdata/pbs/etc
but the etc. directory seems to be in /mnt/user/pbs_backup

on you ss , of /mnt/user/pbs_backup , i see you have etc, logs and lib directory
they should be in /mnt/user/appdata/pbs

unless i am mistaken

can you please share :
ls -alh /mnt/user/appdata/pbs/

Thanks

here you go

that's lokk good
`ls -alh /mnt/user/appdata/pbs/etc`

Thanks

if you do not have anything backed up yet i would say , delete all dir and start from scratch ....
because i cant reproduce this issue

i have many times =(

I can try it again.

also just an FYI i loaded the PDM as well, same issue, cannot get to web interface.. Something is strange with these two. Only happens with these. All other containers have installed with zero issues. Have been running this server for 10+ years.. on 7.2 now if that makes any difference..

EDIT: Same issue, deleted, cleared everything, no luck.. Appreciate the help but i dont know what is wrong. I did notice this on install.

Edited November 7, 2025Nov 7 by Dro

Hmmmm
interesting....
which version or the unraid kernel ?

Edited November 7, 2025Nov 7 by ZappyZap

10 hours ago, ZappyZap said:

LHmmmm
interesting....
which version or the unraid kernel ?

6.12.54 it’s the latest version of Unraid 7.2 full release

Is it possible something has change and your containers aren’t updated for it?

Possible,
and to be clear, not my container, it is my template but not container.
I will update my unraid and get back to you.