惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

博客园 - 三生石上(FineUI控件)
月光博客
月光博客
S
SegmentFault 最新的问题
有赞技术团队
有赞技术团队
Stack Overflow Blog
Stack Overflow Blog
Engineering at Meta
Engineering at Meta
T
The Blog of Author Tim Ferriss
The GitHub Blog
The GitHub Blog
小众软件
小众软件
Hugging Face - Blog
Hugging Face - Blog
IT之家
IT之家
宝玉的分享
宝玉的分享
A
About on SuperTechFans
Vercel News
Vercel News
P
Proofpoint News Feed
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
博客园 - 【当耐特】
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
V
Visual Studio Blog
Jina AI
Jina AI
Y
Y Combinator Blog
T
Tailwind CSS Blog
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
Last Week in AI
Last Week in AI

Proxmox Support Forum

[SOLVED] - Github Auth for Mirrors-Kernel Repo? [Automation] Mass migration tool for MS Win11/Server Proxmox GUI hang - not response is it possible to reject or quarantine spam based on conditions I set ? The PVENode task list in PVE9 is partially obscured due to the terminal font being too large. About 100% error reporting due to pveproxy.service hooks Kubernetes overlay networking breaks when upgrading from PVE 9.1 to PVE 9.2.3 Zentraler Speicher No space left on device Combine datastore and direct file archival to tape Kernel panic VFS: Unable to mount root fs on unknown-block (0,0) sobald ein 7.x Kernel verwendet wird. How to migrate disk of a VM from one ZFS to another Windows Server 2025 fails to boot after PVE 9.2 / Linux 7.0 Kernel upgrade Cannot Install Proxmox on T610 Poweredge with H700 PERC card sdn Config. gateway not reachable How to safely change domain/FQDN? Welche Filterquote erreicht ihr? NFS Share status unknown on 2 of 5 nodes Can't connect to PVE9 consoles [solved] Can't connect to PVE9 consoles [solved] [SOLVED] - Use secondary network for PVE commands Created cluster, one node storage gone BUG: proxmox mail gateway FROM = null bypass spam filtering Moving existing PBS from VMWare workstation to PVE cluster Does eBGP SDN fabric support external peering? Bug: PDM 1.1 not recognizing valid license status Proxmox GUI hang - not response PVE crashes unexpectedly Proxmox Backup Server 4.2 released! Advice
Unable to restore VM
invalid@exam · 2026-06-29 · via Proxmox Support Forum

Hi Community,
First time I am trying to restore a VM from the backup, and I am getting the following error. About a year ago, I switched from RHEL KVM to Proxmox VE and also installed Proxmox Backup on a mini PC with 1 TB of storage and integrated it with Proxmox VE. Promox is still to me; I am not sure if I missed something during installation, configuration, or integration. How can I restore the VM, and how can I fix the issue so it won't happen again? Appreciate your help.

Logical volume "vm-148-disk-0" created.
new volume ID is 'local-lvm:vm-148-disk-0'
Logical volume "vm-148-disk-1" created.
new volume ID is 'local-lvm:vm-148-disk-1'
Logical volume "vm-148-disk-2" created.
new volume ID is 'local-lvm:vm-148-disk-2'
restore proxmox backup image: /usr/bin/pbs-restore --repository root@pam@192.168.50.18:backup1 vm/124/2026-05-03T08:06:30Z drive-scsi0.img.fidx /dev/pve/vm-148-disk-0 --verbose --format raw --skip-zero
connecting to repository 'root@pam@192.168.50.18:backup1'
using up to 4 threads
open block backend for target '/dev/pve/vm-148-disk-0'
starting to restore snapshot 'vm/124/2026-05-03T08:06:30Z'
download and verify backup index
fetching up to 16 chunks in parallel
progress 1% (read 268435456 bytes, zeroes = 0% (0 bytes), duration 2 sec)
progress 2% (read 536870912 bytes, zeroes = 1% (8388608 bytes), duration 5 sec)
restore failed: reading file "/mnt/datastore/backup1/.chunks/aabe/aabec9020cadc776a9ab4169df2133a5ecdcad77d6777210d2aab5037a02bc07" failed: No such file or directory (os error 2)
Logical volume "vm-148-disk-2" successfully removed.
temporary volume 'local-lvm:vm-148-disk-2' successfully removed
Logical volume "vm-148-disk-1" successfully removed.
temporary volume 'local-lvm:vm-148-disk-1' successfully removed
Logical volume "vm-148-disk-0" successfully removed.
temporary volume 'local-lvm:vm-148-disk-0' successfully removed
error before or during data restore, some or all disks were not completely restored. VM 148 state is NOT cleaned up.
TASK ERROR: command '/usr/bin/pbs-restore --repository root@pam@192.168.50.18:backup1 vm/124/2026-05-03T08:06:30Z drive-scsi0.img.fidx /dev/pve/vm-148-disk-0 --verbose --format raw --skip-zero' failed: exit code 255