I am running diskrestore to restore an image to a new device. I can get it to restore the image from the GUI and both drives are GPT. when I try to run the diskrestore.exe from the cmd line from my script it throws the error Failed to update the MBR on the target disk.
i am calling diskrestore.exe from the cmd line in my imaging script on winpe. it is a customized GUI. built for non-IT workers to use
If your drives are GPT, it seems odd that you get an error "Failed to update the MBR". Is there any chance there could be an error in your script regarding GPT and MBR? That's the only thought I can offer, as I have no experience with Macrium Reflect.
I thought it might be because the device I am restoring to uses a UFS drive as I had some trouble booting to my WINpe because of it but I can image other devices with the same script. Yes both drives are GPT as well.I run diskpart clean before the restore as well.
just tried a simple Powershell script that calls the diskrestore.exe and points towards the restore image same result."intializing Failed to update MBR "
tried everything mentioned on that page lots of good information but no dice still failed to update the MBR on the target disk. These are all GPT disk as well..ran diskpart clean so even diskid were 00000000. I'm at a loss the GUI work perfectly well to restore
Strange message as the MBR plays no part in a UEFI system. You can zero the Disk Signature and the partition drive letters don't change. You can zero half the MBR boot code and the OS still boots.
yes indeed..I've run diskpart clean formated the drive to GPT assigned a letter so it had a specific diskID pointed diskrestore to that specific diskID still get the error.
would the issue be because the image was taken from a 4k drive and the target is 512 possibly? although it does run in the GUI perfectly fine.
You might be correct... https://superuser.com/questions/679725/how-to-correct-512-byte-sector-mbr-on-a-4096-byte-sector-disk
Update: update might have figure this one out using diskrestore.exe and the xml files for autorestore in my script. It was the sector sizes being different on the UFS drive image as related to a nvme image. 4k vs 512. In the GUI this translation I assume is run in the background..in the diskrestore.exe with xml file it needs to be implemented manually thru a script. Start with a 512 image and convert the sectors to be available to the 4k drive using the parameters in the XML file.