[SOLVED] Restore VMs and CTs without the original Drive

Jan 29, 2021
4
0
1
22
Hello,

my main Hard Disk Drive has gone and all of my CTs / VMs on it. But I have several backups on my Proxmox Backup Server, but can't restore it because my main drive is broken. And if I try it it will delete the vm / ct after the error.


/etc/pve/storage.conf (Server-HDD-400GB is broken and ServerHDD-1TB_1/2 are my new drives)
dir: local
path /var/lib/vz
content vztmpl,iso,backup

lvmthin: Server-HDD-400GB
thinpool Server-HDD-400GB
vgname Server-HDD-400GB
content images,rootdir
nodes pve

pbs: ProxmoxBackupServer
datastore HDD-700GB
server 192.168.178.99
content backup
encryption-key 1
fingerprint 0f:9b:d1:f0:c3:00:d4:f7:38:68:6c:36:78:a3:b8:c3:5c:0d:46:94:5b:48:91:03:78:42:9a:73:de:91:72:91
prune-backups keep-all=1
username root@pam

lvmthin: Server-Hdd-8000GB
thinpool Server-Hdd-8000GB
vgname Server-Hdd-8000GB
content images,rootdir
nodes pve

lvmthin: ServerHDD-1TB_1
thinpool ServerHDD-1TB_1
vgname ServerHDD-1TB_1
content rootdir,images
nodes pve

lvmthin: ServerHDD-1TB_2
thinpool ServerHDD-1TB_2
vgname ServerHDD-1TB_2
content images,rootdir
nodes pve

My Drive Error:
Incorrect checksum in metadata area header on /dev/sdc at 4096
Failed to read mda header from /dev/sdc
Failed to scan VG from /dev/sdc

My fsck.ext4:
root@pve:~# fsck.ext4 -nf /dev/sdb
e2fsck 1.44.5 (15-Dec-2018)
Warning! /dev/sdb is in use.
ext2fs_open2: Bad magic number in super-block
fsck.ext4: Superblock invalid, trying backup blocks...
fsck.ext4: Bad magic number in super-block while trying to open /dev/sdb

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>


Thanks ins advance!

- Theo
 
Last edited: