V5.1 Reboot Error - Volume group "pve" not found

that won't help with the underlying issue that you have no idea what the raid controller did to your data (although it might help with "disaster recovery" like approaches). like I said, unless there's a vendor-backed guarantee that says otherwise, consider the disks broken the moment the controller has died.
 
End of story. I managed to clone via dd a 500 GB disk to a 1 TB disk. Copied for a long time - more than 8 hours. After that, using the gparted utility, I increased the partition from 465 GB to 550 GB. Rebooted the machine and vgchange -ay ssd worked successfully. The lvm partition was successfully copied with dd and restored on another proxmox node. At the first start, fsck was launched which successfully completed and now the virtual machine is available. Further, a similar task with a section of 5.2 TB.
 
  • Like
Reactions: _gabriel
You must log in or register to reply here.
Top Bottom