Insert Intel Matrix Storage Manager onto Cloned drive?

I need to clarify here.  The drive from the Dell system has been removed.  I cloned my custom built system onto a new SATA HDD and put into Dell system.  I am used to doing this.  Sometimes I have to run Recovery process to fix boot or mbr.  But this time, during Windows Recovery process it doesn't "See" the HDD, although the system BIOS does.  So, I cannot fix boot order.  I think this is an Intel Matrix Storage manager issue.  I've seen this before but cannot remember how I fixed it.  I hope that IMSM goes completely away.  I remember the bad old F6 install days!

So, I'm trying to take my cloned drive from completey different system, with diff hardware, etc. and transplant it into a used but nice Dell Dimension 9150.  I expected the system to boot up so I could remove all software and drivers from old sys set up and install all the Dell drivers.  System won't even boot into Safe Mode now.  Nor does Windows see the disk in Recovery Console so I can perform a fixboot or fixmbr.

Cloned entire disk using Acronis 10

Don't know if you read my post 31748942 before you posted 31743900, but to clarify, what you are trying to do will not work without doing a binary copy of the HD contents.   Block #0 in the matrix is physical byte # ( 100030242816 - 98999205888)

So problem is that your windows system is trying to boot the metadata information reserved at the beginning of the disk. It won't work.   Download a LINUX live CD, put in a scratch drive, then use dd command, or you could probably use some partition management software and clone the windows partition that starts at the offset, and move it to block#0.

I would think Acronis 10 could handle this for you, but don't know since I don't have it.  But in any event, you now know root cause, the exact byte where your windows partition starts, and what you have to do.  Hopefully acronis can copy data at a starting offset.   Try contacting their support if you are not sure.   If you are a UNIX person, then you can easily do this by using dd and telling it the starting offset, but you will need a scratch disk.    Perhaps some partition management software will let you put a bogus partition at beginning of the disk drive where the metadata is, and can then turn the whole-disk image into the 2nd partition, but the better solution is just to binary move the data from the offset to byte #0

dlethe, thanks.  Sounds like you really know your stuff.
Can I do this by hooking the drive up to another system and using something like Acronis Disk Director or ?? (suggestions) to fix?  You've got us on the Binary Copy thing. ??  Thanks much

I don't know Acronis well enough to know. I'm too spoiled, as  I'm a storage architect, (heck, I have NDA with Intel and the API for their controller so that is why I was able to answer it so quickly, as I happened to be logged onto a LINUX box that has this controller at the time).  So anyway, after doing this for 25 years, I have a bag-o-tricks worth of code I have developed myself or gotten from manufacturers that can do pretty much anything you can imagine, so I just don't need Acronis.

I've got in-house code that I wrote years ago to migrate raw disk images into a partition, but it isn't anything I can give you due to intellectual property restrictions.  This is a rather simple thing to do, and I would be surprised if any decent image backup solution couldn't handle what you need to do.   Of course, the safe thing is to migrate with an offset to a scratch disk, rather than doing it in-place.  Never know when you will have a power failure or a memory parity error that would lock up a PC and destroy the data.

That's interesting.  So coincidentlly enough, the Dell system stopped working after a recent power outage although it was already unstable.  Sometimes not able to boot up. etc.  I wonder if this is not infact a RAM problem or power supply issue?

Thanks all.  Turns out motherboard was just bad.  PS tested well and so did memory.  System worked long enough to install new OS, but then restarted on it's own and other weird behaviors.  Just built new system and relegated this one to parts bin.  Thanks again for responses.

Motherboard bad.  Built new system.  Thanks all.