One major advantage of ddrescue is the option to restart a copy-process.
So if you keep the outputfile and the copy-log you can abort at any time.
Then reconfigure your network and restart with the same command.
Ddrescue finished today.
There are no read errors, etc..
The strange thing is that it had 3h remaining time and suddenly finished on 94,22%. What does it mean - that it was not able to rescue all?
It does not seems to be complete.
Here is the output from its log file:
# Mapfile. Created by GNU ddrescue version 1.22
# Command line: ddrescue /vmfs-in/Flawless Server/Flawless Server-flat.vmdk /vmfs-out/Flawless Server/Flawless Server-flat.vmdk /vmfs-out/Flawless Server/copy1.log
# Start time: 2018-08-30 19:31:48
# Current time: 2018-08-30 19:31:51
# current_pos current_status current_pass
0x1B495790000 + 1
# pos size status
0x00000000 0x1B495790000 +
Regardless to this I have moved the remaining portion of files, renamed the previous folder (old datastore) and registered the VM.
The problem I face now is that it refuses to start and requires me to connect another vmdk on another hard drive (another data store):
Cannot open the disk '/vmfs/volumes/5b81bebc-162ed5e6-79ce-6805ca128dcc/Flawless Server/Flawless Server.vmdk' or one of the snapshot disks it depends on.
I have not moved the other volume anywhere and its still present with the same name, so that is why I do not get what is wrong and what needs to be done to fix it.
Here is the vmware log file:
018-08-30T17:51:16.521Z| vmx| I125+ Power on failure messages: The file specified is not a virtual disk
2018-08-30T17:51:16.521Z| vmx| I125+ Cannot open the disk '/vmfs/volumes/5b81bebc-162ed5e6-79ce-6805ca128dcc/Flawless Server/Flawless Server.vmdk' or one of the snapshot disks it depends on.
2018-08-30T17:51:16.521Z| vmx| I125+ Module 'Disk' power on failed.
2018-08-30T17:51:16.521Z| vmx| I125+ Failed to start the virtual machine.
I have removed the second hard drive from the VM settings and added it again. The problem still persists.
The important part in the log file is:
2018-08-30T17:51:16.501Z| worker-2115541| I125: DISKLIB-VMFS : VmfsExtentCommonOpen: possible extent truncation (?) realSize is 3662331008, size in descriptor 3886945402.
2018-08-30T17:51:16.501Z| worker-2115541| I125: DISKLIB-VMFS : "/vmfs/volumes/5b81bebc-162ed5e6-79ce-6805ca128dcc/Flawless Server/Flawless Server-flat.vmdk" : failed to open (The file specified is not a virtual disk): Size of extent in descriptor file larger than real size. Type 3
So it seems that the copy job didn't complete, and 224,614,394 blocks (approximately 112 GB) are missing.
When I have tried to run the command again it reported "finished".
As mentioned above I also do not think that it is complete. I have decided to give up on ESXi and ddrescue, started the VM from the old datastore and will soon make a switch to another virtual and manually copy the data (rsync or cp).
Before you really decide to give up I would like to have a closer look.
Feel free to call me via skype: sanbarrow