Insert Intel Matrix Storage Manager onto Cloned drive?

I'm cloning a system hard drive from old setup to another Dell system I  acquired.  I cloned from my old system and put into new, but disk not recognized.  I see that the Dell system has that crazy Intel Matrix Storage manager on it and from past experience I think it has to be on disk or it won't start up.
Windows flash screen comes up but it used to reboot instantly.  Now, after updating BIOS to A07 from A03, the splash screen comes up and system locks.
My question is this, how best to insert the needed items without having to install XP from scratch?
Many thanks
TechnecallAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

johnb6767Commented:
How to install a new motherboard without reinstalling Windows
http://arstechnica.com/hardware/news/2007/09/how-to-install-a-new-motherboard-without-reinstalling-windows.ars

I have used similar methods like this with half and half success..... Needs to be done before the drive is cloned/moved to the new hardware....

I actually have removed the devices instead of using generic MS drivers.....

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
B HCommented:
i don't think it's a driver issue as much as the wrong partition...

did you clone the entire disk, or just the partition?

thing is, if your original drive was laid out like this:
partition 1 = dell system restore
partition 2 = windows

and your new drive is now laid out like this:
partition 1 = windows
(no partition 2)

then your c:\boot.ini is now wrong.  it was correct for 2 partitions, but not one...

edit the boot.ini on the cloned drive to reflect the correct layout:
for one big parition:
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect

for dell-windows partitions it would probably be:
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect

see how many partitions it has by hooking it up and looking at disk manager (diskmgmt.msc)
TechnecallAuthor Commented:
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!
Active Protection takes the fight to cryptojacking

While there were several headline-grabbing ransomware attacks during in 2017, another big threat started appearing at the same time that didn’t get the same coverage – illicit cryptomining.

DavidPresidentCommented:
I just checked on one of my systems that has this controller, and it unfortunately uses metadata to carve out a reserved area for RAID info.   To be specific, the dump below shows the same make/model of SSD, one is behind the Intel Matrix controller, the other is behind a JBOD SAS/SATA controller.  The first number shows how many bytes are reported by the O/S  (not in the partition, but total physical bytes reported by the BIOS) for the disk in Matrix, the other is for a non-RAID.

   Total Capacity (In Bytes):           98999205888
   Total Capacity (In Bytes):           100030242816

So the path suggested by bryon just will not work.  Everything is shifted down by the # of bytes above (too lazy to do the math).   You will have to use a scratch disk to do a bit-level copy starting at the new offset.

TechnecallAuthor Commented:
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.
TechnecallAuthor Commented:
Cloned entire disk using Acronis 10
DavidPresidentCommented:
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.
DavidPresidentCommented:
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
TechnecallAuthor Commented:
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
DavidPresidentCommented:
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.
TechnecallAuthor Commented:
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?
JakeCampbellCommented:
Does it boot at all anymore? More recent Dell's have tried to make the switch to ATX compatible power supplies, still check to make sure you can replace with an ATX supply before you try. If the system powers up then you can always run Memtest and see if you have a ram problem.

Jake
TechnecallAuthor Commented:
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.
TechnecallAuthor Commented:
Motherboard bad.  Built new system.  Thanks all.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Components

From novice to tech pro — start learning today.