Macrium Reflect being stupid?

[Mark Kaine]

idk last few times i tried it, on several systems it always throws some cryptic errors , on one machine it outright refused to make a backup whatsoever...

 

So today i made a backup of my pc's os drive... of course also got a weird error (forgot something about it cant read something... doesn't make any sense... and then continues on anyway...) and it placed a "G:(recovery drive)" on the target disk besides the MRIMG file its actually supposed to make... 

 

So what do i do with this folder now and i hope that isnt my actual recovery partition i kinda need that on my pc and not a random backup drive... 

 

pretty sure i will not use this software again but yeah... how do i remove this recovery partition now and how do i make sure its actually intact on both my os drive and the backup image?

 

 

also note: it put this recovery partition on the target drive on another attempt where i canceled it because it threw several nonsensical errors... so this shouldn't have to do anything with the current backup...its still confusing why its even there  

[Mark Kaine]

ok maybe I'll remember this next time... deleted the partition,  yada yada, of course it wouldn't let me "extend"...

 

So i had to move the backup somewhere else, delete both partitions on the drive, then

diskpart -> clean

 

lol, its so simple... it would be even more simple if windows let you extend any unallocated partitions, but apparently thats a bit too much to ask...

 

why macrium copied the recovery partition separately I'll never know... 

[wseaton]

If you do a full logical disk copy / restore Macrium will just copy all those stupid Windows utility partitions as is. You really should be working at logical disk level, and not trying to manipulate or restore specific partitions, especially of they are OS related. That is, unless you like fiddling with diskpart

[Mark Kaine]

53 minutes ago, wseaton said:

If you do a full logical disk copy / restore Macrium will just copy all those stupid Windows utility partitions as is. You really should be working at logical disk level, and not trying to manipulate or restore specific partitions, especially of they are OS related. That is, unless you like fiddling with diskpart

well i wanted a MRIMG file... 

 

what I got is "error i don't know what im doing" and a "recovery partition".

 

i don't really think thats my fault in this case... i just wanted a full backup, no shenanigans. 

 

It did it on second try as said, but not without throwing an error first *again* so my trust in the resulting MRIMG is exactly 0...

 

 

Oh yes, i had fun with diskpart trying to delete this stupid recovery "partition"... tyvm! 

 

i still don't understand why it did that... tbh i think it simply doesn't work with nvmes... it *never* ever just copied a recovery partition in clear sight before.

 

 

i know it would probably be helpful if i knew the error messages,  but it honestly boiled down to "cannot read something" ... shouldn't it just stop at this point instead of continuing?