The issue has been mentioned before dated in 2024. without some real resolution.
Full error:
Error: error extracting archive - encountered unexpected error during extraction: error at entry "random": failed to extract device: failed to create device node: Operation not permitted (os error 1)
Plain select backupfile, restore button select Storage to the right one & restore on the popup
History of the container: Created as a non privileged container, running Collabora Document server. has been running for some time, so it had several apt update && apt full-upgrade seen during this period.
Reason for restore: might be infected due to php issues, unsure, so preventive restore from image of a few months old.
I did find there is an bz issue for this https://bugzilla.proxmox.com/show_bug.cgi?id=5654 that has no solution. (It has not been looked into even, state NEW since 2024).
apparently the 'random' device is forbidden in images, yet the device has been created outside of backup/restore control.
I dislike the option to have an UNprivileged container to be upgraded to privileged for this. (will attempt a privileged restore after this)
Why can such a device be created during runtime, if it disallowed?
It would be a lot better to allow restore and remove all forbidden parts later? or "fake" the restore with a warning.
On the other hand, the BACKUP software could warn for this case and NOT backup the offending items.
For now the backup (or rather restore) of unprivileged images is unreliable.
Curious to what resolution other have to this issue
Update: The privileged image never starts... Start mentions OK, it just doesn't start.
Update2: lxc -F -n 114 does not actualy show any output.
Update3: Added debug: 1 to the config file as well as unprivileged: 1 after this the container and removing ,mknod=1 DOES start with lxc -F -n 114....
Still pct start 114 & starting from WUI doesn't do anything but say OK on hastart ....
Full error:
Error: error extracting archive - encountered unexpected error during extraction: error at entry "random": failed to extract device: failed to create device node: Operation not permitted (os error 1)
Code:
recovering backed-up configuration from 'PBS1-NEXTCLOUD:backup/ct/114/2025-04-18T02:14:03Z'
Formatting '/mnt/pve/PVE/images/114/vm-114-disk-1.raw', fmt=raw size=21474836480 preallocation=off
Creating filesystem with 5242880 4k blocks and 1310720 inodes
Filesystem UUID: 8e5a4107-c090-43ff-baf8-fc6c21b7bac2
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
restoring 'PBS1-NEXTCLOUD:backup/ct/114/2025-04-18T02:14:03Z' now..
progress 2% (317.687 MiB of 10.841 GiB in 5s, 63.421 MiB/s)
progress 6% (737.661 MiB of 10.841 GiB in 15.4s, 40.325 MiB/s)
Error: error extracting archive - encountered unexpected error during extraction: error at entry "random": failed to extract device: failed to create device node: Operation not permitted (os error 1)
TASK ERROR: unable to restore CT 114 - command 'lxc-usernsexec -m u:0:100000:65536 -m g:0:100000:65536 -- /usr/bin/proxmox-backup-client restore '--crypt-mode=none' ct/114/2025-04-18T02:14:03Z root.pxar /var/lib/lxc/114/rootfs --allow-existing-dirs --repository backup@pbs@pbs.noci.lan:PBS1 --ns NEXTCLOUD' failed: exit code 255History of the container: Created as a non privileged container, running Collabora Document server. has been running for some time, so it had several apt update && apt full-upgrade seen during this period.
Reason for restore: might be infected due to php issues, unsure, so preventive restore from image of a few months old.
I did find there is an bz issue for this https://bugzilla.proxmox.com/show_bug.cgi?id=5654 that has no solution. (It has not been looked into even, state NEW since 2024).
apparently the 'random' device is forbidden in images, yet the device has been created outside of backup/restore control.
I dislike the option to have an UNprivileged container to be upgraded to privileged for this. (will attempt a privileged restore after this)
Why can such a device be created during runtime, if it disallowed?
It would be a lot better to allow restore and remove all forbidden parts later? or "fake" the restore with a warning.
On the other hand, the BACKUP software could warn for this case and NOT backup the offending items.
For now the backup (or rather restore) of unprivileged images is unreliable.
Curious to what resolution other have to this issue
Update: The privileged image never starts... Start mentions OK, it just doesn't start.
Update2: lxc -F -n 114 does not actualy show any output.
Update3: Added debug: 1 to the config file as well as unprivileged: 1 after this the container and removing ,mknod=1 DOES start with lxc -F -n 114....
Still pct start 114 & starting from WUI doesn't do anything but say OK on hastart ....
Last edited: