cow - qcow2
Posted: 16 Oct 2016, 10:22
Good day,
it has been asked before. But I don't get the answer.
I need to recover qcow2 files that hold my VMs created with qemu-img. Photorec (tested different versions) does find *.cow files but many more than I originally had and of very small size. The ones I am looking for are about 80GB.
Is it possible to 'recreate' my original qcow2 files?
For your information, this is how I got into this mess:
My server had two 3TB disks in software raid (Debian jessie). On disk failed and was replaced. In order to reassamble my raid, I had to copy the partition table from the still working to the new disk. I used sgdisk. I assumed wrongly sgdisk would copy from <source> to <target>. But no. It is the other way round. The manpage is not a big help either. Whatever.
This is all that happened. No corruption or other failures on the good drive.
After this I used ddrescue to copy all data from the good drive to the new one in order to protect the original data. Also used testdisk to search for the lost partitions. It finds them and recognizes them as software raid. But when I used these to write a new partition table and rebooted, I couldn't mount them. Neither directly nor via assembly through mdadm. So I tried to recover the imported files.
it has been asked before. But I don't get the answer.
I need to recover qcow2 files that hold my VMs created with qemu-img. Photorec (tested different versions) does find *.cow files but many more than I originally had and of very small size. The ones I am looking for are about 80GB.
Is it possible to 'recreate' my original qcow2 files?
For your information, this is how I got into this mess:
My server had two 3TB disks in software raid (Debian jessie). On disk failed and was replaced. In order to reassamble my raid, I had to copy the partition table from the still working to the new disk. I used sgdisk. I assumed wrongly sgdisk would copy from <source> to <target>. But no. It is the other way round. The manpage is not a big help either. Whatever.
This is all that happened. No corruption or other failures on the good drive.
After this I used ddrescue to copy all data from the good drive to the new one in order to protect the original data. Also used testdisk to search for the lost partitions. It finds them and recognizes them as software raid. But when I used these to write a new partition table and rebooted, I couldn't mount them. Neither directly nor via assembly through mdadm. So I tried to recover the imported files.