CountMike :
While cloning specially when something goes wrong it's not uncommon to loose data from the original. With full disk backup you can keep backup file .mrimg (that MR makes) to make a new boot disk any time and as many times as needed.
Mike:
I can relate only my experience re disk-cloning operations over a period of about 20 years. During that period I've personally performed and/or participated in thousands of disk-cloning operations involving a multitude of PC systems. Up to about 10 years ago I used a variety of d-c programs, however, for about the last 10 years or so I use (nearly exclusively) the Casper d-c program, although I have experimented as well with a variety of other programs.
During all that time involving thousands of d-c operations I can recall only a single case where the source drive became corrupted as a direct result of the d-c operation. And even here, as I recall, there was some question as to whether it was due to some deficiency inherent in the program or the result of some electrical power malfunction in the system that occurred during the d-c operation.
In a number of cases that were brought to my attention by PC users complaining about a problem they experienced re a corrupted source drive during a d-c operation, we found that in EVERY case the problem was a result of user error in that the user misidentified the source & destination drives during the d-c operation.
Having said all this...if a user would ask me to give him or her 100% assurance that carrying out a d-c operation will never, under any circumstances, result in their source drive being corrupted as a result of that operation, it's obvious I could not do that as I'm sure you would agree.
However, we routinely strongly recommend d-c as a viable, safe operation for a PC user to perform when circumstances are present for a transfer of data from one drive to another as they seem to be in the OP's case. I say "seem to be" because he indicates there are "some problems" with the source drive. Depending upon the extent & severity of these "problems" the d-c program may balk at carrying out the d-c operation. But in any event even if the d-c operation cannot be successfully performed it should have no negative impact on the source drive's data.