How do I move my operating system to a SSD.

Word Man said:

Cliff - see my private message about setting up a disk check from within Windows
to run on a restart (chkdsk /f c: from an elevated cmd prompt).

I just did that, and yes it did finish the cleaning and here I am on it again...

Should I use Macrium again now, and try making the IMAGE again now ?
thanks Cliff M.

Word Man said:

You could but here's the thing - you should repeat the chkdsk procedure AGAIN and make sure it comes back clean "no errors found" this time. IF IT DOESN'T, stop and feel free to phone me. We don't want your C: drive going too far south and getting where it can't even boot. We can try a different kind of option for imaging in Macrium if need be to at least make sure you don't lose any of your data.

Another thing - I'm operating under the assumption that the read errors and abort of your Macrium image occurred while it was still imaging Partition 4 (the OS) - is that correct?

When I do the chkdsk /f C:
then restart, the system does does the restart and you do not get to see it doing the chkdsk command...
you only get to see the note at the bottom that say "scanning and repairing 0 through 60, and then later 100%
and it re-inits after that bck to a Microsoft login screen. So I just did it again before starting this email.
I am not sure what partition it was in when Macrium was see a read-error.
Your comments ???
Cliff

Word Man said:

Another thing - I'm operating under the assumption that the read errors and abort of your Macrium image occurred while it was still imaging Partition 4 (the OS) - is that correct?

Should I try to do the Marcrium Image copy again to try to see where the error is in the data...????

I have run those chkdsk and sfc/scannow commands while in "safe mode" , sometimes you get different results , sfc/scannow found corruption and successfully repaired them on my system , the same command run without safe boot found nothing .

Word Man said:

At this point, since you've run chkdsk /f C: two times, it should have repaired the problem (if that WAS the problem and it wasn't very serious) and it's probably worth the effort to go ahead and boot into rescue CD and try again. This time, keep an eye on it and let's see if it completes - if not, WHERE it aborts - watch your operations screen and note which partition (1 through 7) it is performing operations on - partition 4 is definitely where it will sit most of the time.

Some other things after you try above, that we can discuss offline if need be:
A) You can attempt the image by running Macrium inside Windows and you have more logging available to look at and see exactly where it aborts and more precisely why.
B) You can run chkdsk again but redirect that text that scrolls so quickly into a file for you to look at and see what it says. Chkdsk can also be run on your D: drive but let's see if we know which drive Macrium is aborting on first - if it keeps aborting.

Ok, and I will try all that again tomorrow after about 4pm CST... if it aborts, and I will note that..
,yes, OK, and I have read you said above..
after I try all that tomorrow, I will give you a call. thanks so much.. Ballgame time now.. be safe Cliff M.

Word Man said:

OK, Cliff.

Actually, we'll be able to check on your chkdsk results in your event viewer in Windows if need be but I'll wait to see how your next try at imaging with Macrium goes first.

Thanks for all your help. We can do anything with it later. At least the Dallas Cowboys finally got their act together last night and took the W with them. You and I can check anything you wish during this week. I am really not in a hurry to get it changed over to my SSD except that it will be faster.
Thanks, be safe.. cliff M.