I was finally able to get back to this project. And, I am extremely happy to report that your suggestion worked! I stopped after entering the "clean" command and went back into Macrium and everything worked as you suggested! Thanks a ton Brian!
At DSLR there is a post telling that there is a new version 5.3.7167. See thread http://www.dslreports.com/forum/r29519253-Updated-Macrium-Reflect-V.5.3.7167-Sept.-8-14 But be warned that the DSLR board itself has connection problems currently. See https://www.wilderssecurity.com/threads/dslr-down.368000/ Well, my Reflect Pro version doesn't give me an update from version 5.3.7149. And I don't see this update mentioned at http://www.macrium.com/pages/downloads.aspx So, is anybody else getting this update?
I guess I'm just curious here... if no one knows what the changes are in the new versiuon, why are you in such a hurry to get it on your system?
Well, I know some people love trying out new versions of softwares. They will love to try it out the minute the update is out. It's like an addiction, hard to cure. I myself belong to one of them. However I am not currently using Macrium Reflect so I am not in a hurry to get this update, but I can understand these ppl who rush to get it.
What's new? 5.3.7167: Additional error reporting.If a file cannot be deleted during a DSM purge then the Windows error causing the failure is now reported in the log Windows shutdown error notification when a backup is currently running.Attempting to shutdown Windows if a backup is running will now cause a notification message to be displayed to prevent or allow the shutdown. Bug Fixes: "You need to format the disk" error message when mounting an imageThe error "You need to format the disk" could incorrectly be shown when mounting an imaged partition. This has been resolved Out of Memory errorAn out of memory condition could be reported when backing up large partitions. This has been resolved.
Is anyone else having problems with this update? It is asking for my licence info even though I am valid paid user.
They have just changed the version build no. to 5.3.7170 Source: http://updates.macrium.com/reflect/v5.0/v5.3.7170/details5.3.7170.htm
This is getting annoying. What happened to their QC? Did they even test it before they release their "stable" version? This consecutive release of two versions happened a few times in the past already.
Hi, sorry to butt in on this thread but I have a problem with diskrestore when using it under Macrium Windows PE. I have Macrium Reflect Pro v5.3 build 7170 that I created a boot USB from for a windows 8.1 device, I also have an image of the device split into 4GB sections (reason will become clear later) The imaging works fine under PE when using Macrium itself, however when I try to use diskrestore I keep getting the error "Failed to update MBR on target disk" - The hard drive in question is formatted to GPT with 2 EFI partitions, one of 300MB the other 40MB, there is also a MSR (128MB) partition which is NOT part of the image. The reason for splitting the image into 4GB sections is that I also want to create a Batch file to run a set of commands to almost automate the process - hence why I am trying to use diskrestore. My batch file at the moment contains the following list of commands; Code: ECHO OFF FOR %%i IN (D E F G H I J K L M N O P Q R S T U V W X Y Z) DO IF EXIST %%i:\USBDrive.TXT SET USB=%%i:%USB% DISKPART.EXE /S %USB%WipeC.txt TIMEOUT /T 15 DISKPART.EXE /S %USB%GetID.txt > %USB%ID.TXT FOR /F "tokens=3* delims={} " %%G IN (%USB%ID.TXT) DO SET _SERIAL=%%G SET _SERIAL=%_SERIAL: =% ::ECHO %_SERIAL% %USB%\diskrestore.exe "%USB%\SB10\1992112424D067C4-00-00.mrimg" -r --targetnum 0 --targetid %_SERIAL% -e -g -u PAUSE Line 1 - Finds which drive letter has been assigned to the USB and saves it into a variable called USB in the format of C: Line 2 - Starts DISKPART and runs a separate file containing the following DISKPART commands - Code: LIST DISK SELECT DISK 0 CLEAN CONVERT GPT CREATE PARTITION EFI SIZE=300 FORMAT FS=FAT32 QUICK CREATE PARTITION EFI SIZE=40 FORMAT FS=FAT32 QUICK CREATE PARTITION MSR SIZE=128 CREATE PARTITION PRIMARY SIZE=490 FORMAT FS=NTFS QUICK CREATE PARTITION PRIMARY FORMAT FS=NTFS QUICK ASSIGN LETTER=C: EXIT Line 3 - Waits for 15 seconds to ensure that all the commands of DISKPART have completed. Line 4 - Starts DISKPART Again running another separate file containing the following commands, and saves the result in a text file called ID.TXT Code: SELECT DISK 0 UNIQUEID DISK EXIT - this performs the task of saving the unique ID of the hard drive into the file ID.TXT on the flash drive. ie Disk ID: {9043DEA1-5C9B-4096-A041-34DF41A0E531} Line 5 - Sets the variable _SERIAL to equal the parred down unique ID of the hard drive ie 9043DEA1-5C9B-4096-A041-34DF41A0E531 Line 6 - removes any preceding or trailing spaces from _SERIAL Line 7 - Runs diskrestore.exe from the USB drive (it is already part of the Macrium Windows PE) with flags as follows; %USB%\SB10\1992112424D067C4-00-00.mrimg" - This points the program to the image file to be used -r - This tells the program to restore all partitions. --targetnum 0 - This specifies the target hard drive to write the image to (in all cases 0 is the C: drive) --targetid %_SERIAL% - this specifies the unique ID of the hard drive, ie it should now not matter if the hard drive is on another machine as long as the partition sizes etc are the same. -e - Continue on any read errors -g - Display the GUI interface -u - run as unattended ie no user input required. It is during this last command with its various switches etc that I get the "Failed to update the MBR on the target disk" error. Ive asked on the Macrium Reflect forum for advice and help and all I got told was not to use diskrestore .. which seems to defeat the object of having the program, what use is it if you cannot use it? Any help or even any pointers would be appreciated. Thank you.
CJMFugazi, Can I ask the reason for this exercise? Is it for restoring the image to a new HD? Does it work if you restore the image to a blank HD? No partitions?
Brian K Originally it was just a project to see what Macrium diskrestore was fully capable of doing .. now it has turned into a bit of a crusade lol I have tried running diskrestore on a blank HD with the same issue, have also tried converting the HD to MBR, again same issue. The only time diskrestore works is when run from standard windows which goes against what Macrium state it can do.
CJMFugazi, You did better than me. After taking an image I wiped the source GPT disk with zeroes and tried to restore the image in a WinPE using diskrestore.exe. It worked from the diskrestore.exe GUI but not from the command line. "Unable to load image file" was the error.
I did find that the only way to restore an image using diskrestore from the GUI under WinPE was to ensure that the image being used was in segments of no more than 4GB. The company I work for use Macrium to do all its imaging and TBH overall it does a great job ... but, I hate it when a piece of software doesn't do as it is advertised to do ie diskrestore. what is the point in giving command line operation if it doesn't work? Anyway, have you any ideas as to where to go next in order to try and resolve the issue .. if that is possible.
I got the command line to work. On my data GPT disk I had MSR, EFI and two data partitions. A Macrium image was taken. Diskpart "clean" was then run to zero the partition table (really zeroed the first 2048 sectors) so the HD now showed as an unpartitioned MBR disk with a Disk Signature of 0x00000000. Booted into a WinPE and ran... diskrestore.exe D:\Temp\4EEF9C2656666E26-00-00.mring -r --targetnum 2 --targetid {00000000} -e -g -u All partitions were restored.
You can omit --targetid {00000000} and it still works. You can restore over the top of the previous restore (without running "clean") and it works.
You can change the image file-name. You can restore to a HD with different partitions. All partitions will be deleted before the restore commences. I used this... diskrestore.exe D:\Temp\abc.mring -r --targetnum 2 -e -g -u --reboot Edit... Out of interest HD0 was imaged. 7 GB image, not split. The image was restored to HD2. No problems. Same command line as above.
Would you like to try this restore.cmd (put it in the root of the Macrium USB flash drive) Code: ECHO OFF FOR %%i IN (D E F G H I J K L M N O P Q R S T U V W X Y Z) DO IF EXIST %%i:\restore.cmd SET USB=%%i:%USB% "X:\Program Files\Macrium\diskrestore.exe" "%USB%\SB10\1992112424D067C4-00-00.mrimg" -r --targetnum 0 -e -g -u --reboot
