I did a full image backup and successful image restore of a windows dynamic drive.
I had to update the mbr and dynamic (LDM) disk database manually because urbackup doesn’t save this info. Is this correct? The raw.mbr is too small to have the LDM info. My restore was interrupted and I resumed with ddrescue so I may be wrong about urbackup - perhaps it saves the LDM somewhere else?
Windows dynamic disks have hidden LDM info in the MBR and at the last 2048 sectors of the drive.
ldminfo --copy /dev/sda saves the first 4KB of the mbr and the last 1MB of the drive into separate files (sda.part and sda.data) - these can be used to recover the dynamic disk privhead/tockblock if you are very careful with dd.
I fixed some bugs with large disks and compiled for Windows/Cygwin
ldmutil will also copy/restore the MBR and LDM at the end of the disk as well as printing some info. It uses a different format than ldminfo
ldmutil /dev/sda c backup - save mbr+ldm in a single file (1052160 bytes)
ldmutil backup c /dev/sdb - restore backup mbr+ldm to device.
I have fixed some issues in ldmutil but there still may be problems with it so be careful.
If you are restoring make sure the last 2048 sectors are free - this does not show up as a partition at least with MBR disks so you may overwrite the LDM database, or ldmutil may overwrite filesystem info
Be careful with low level disk utils. Double check partitions after manipulating LDM/MBR info. In my case, Linux ldm messes up the partition order because it doesn’t handle OEM partitions properly. My /dev/sda3 moves to /dev/sda1 unless I have a patched ldmtool.