Menu
▾
▴
#44 image aborted during recovery g4l 0.55a
Hello Michael and Frank,
yesterday i tested g4l the first time, and i found some strange behaviour of this software:
i wrote an image from a nvme m.2 drive with a windows 10 uefi installation on it. i backed it up on a wd 3.5" hdd, connected over a sata2-icybox. filesystem of the wd hdd is ext4. now when i try to revover the image, the process jumpes from something around 33% to 100% immediately and then goes back into the last menu. i restarted the pc and checked the m.2 drive - no data has been restored. how can this happen?
greetings, Wursti
The only time I've heard it jump like that is when dd gets an error writing to the disk/partition. Usually, it is a bad sector, or that the disk/partition is smaller than the original. g4l impages can be restored to teh same size or larger disk/partitions. It is a bit level backup, so that is what I've seen. Don't have NVME disks to test it on, so have only used the virtual box disks, and seemed to work just like the normal disks.