After Critical breakdown - can not see my Backups

[Udbytossen]

I've damaged my Intern m2sata storeage, had a new disc and reinstalled my PVE
Inside the PVE - I have a virtual Machine for the backup Server - and no Can't remember the direct path of the Datastorage here on my PBS Server

I've added the disc again in my PBS Server - and can see my Backups in my namespaces on the disc which is mounted at /mnt/Internal :


I've googled about this error and found this and tried changing the owner from this link:

chmod backup:backup -R /mnt/datastore/Intern
chmod -R 700 /mnt/datastore/Intern
systemctl restart proxmox-backup

but listing the disc with df -lah - I'm seeing the disc is almost filled - is normally been pruned through time.

/dev/sdb1    2.0T 2,0T    53G    98% /mnt/datastore/Intern

But when adding the storage through the GUI - I'm getting this error:



So what Can I do since my settings are correct - the permissions for the share are added - but saying there the wrong persmissions.
The backup user and group is 34 - so what goes wrong here

Looking in /etc/proxmox-backup - I do not see the datastore.cfg only seeing .datastore.lck vand the journalctl -f shows only this:



So what can I do - to add this datastorage correctly and beeing able to restore my machines from there

But I can not get or understand why the persmission is the error here.....

 

[Onslow]

chmod backup:backup -R /mnt/datastore/Intern

Must be chown instead of chmod

 

[mfederanko]

The permissions and owner should be configured like this:

Post in thread '.chunks folder completely removed from system and can't find it'

Jan 28, 2026

The permissions or user/group ownership of you directory structure are not correct, which gets verified by the proxmox-backup-api when adding the datastore.
Your permissions of the datastore have to be set as follows:

755 /mnt/qnap_backup
750 /mnt/qnap_backup/.chunks
750 /mnt/qnap_backup/.chunks/0000 - ffff
644 /mnt/qnap_backup/.lock

additionally the user and group owning all the files and directories in /mnt/qnap_backup must be owned by 34/backup:34/backup.

Maybe double-check the owning user/group of all files?

which can be found in the source at [1].

[1]...

• mfederanko

 

[Udbytossen]

Hmmm - off carse that was a spelling mistake - the command are surely chown - insted of chmod
Have tried running the command

chown backup:backup -R /mnt/internal
chmod 700 -R /mnt/internal
systemctl restart proxmox-backup

The Backup user and group have number 34 as expected


But still getting the error


Tried to change the permissions to as requestet from @mfederanko -

but still same error

 

[Udbytossen]

A Reinstall of both my PVE and PBS for retrying this from scratch - imported the harddisk sets the permission as described with

chown backup:backup -R /mnt/internal
chmod 700 -R /mnt/internal
systemctl restart proxmox-backup

but the same error occours - will this mean that I can not recover the disk

 

[Alban24x7]

Your backups are fine, this is just a registration issue.

chmod -R 700 is probably why the check keeps failing. PBS wants the layout Manuel posted (755 root, 750 .chunks, 644 .lock), not 700 everywhere.

Then when adding in the GUI, tick "Reuse existing datastore", otherwise PBS tries to create a new one in a non-empty dir and fails. Or just create /etc/proxmox-backup/datastore.cfg by hand (it's normal it doesn't exist after reinstall):

datastore: Intern
    path /mnt/datastore/Intern

then systemctl restart proxmox-backup proxmox-backup-proxy.

If it still fails, post the error as text plus output of ls -lan on the datastore root.