Moving system installed on RAID0 to the new motherboard

[Konrad Klar]

Currently I don't have such problem, but I consider possibility of moving my WindowsXP installed on RAID0 (Intel controller integrated in i965 chipset) to the new motherboard, based on quite different chipset.
I have two questions:
1. Is there a tool than can convert RAID0 metadata between formats used in different (incompatible) RAID controllers?
2. Is there a method of installing drivers for hardware, that is not present in system (e.g. tool that can create fake hardware ID [sorry, maybe such concept is totally stupid... I don't know])? To boot on new MoBo I'll need to install on my current system drivers for RAID controller integrated in new motherboard.

Thanks in advance.

[Blue_MiSfit]

fuhgettaboutit...

Move the data, and wipe the array. Move it to the new box, rebuild it, and restore the data. Only way to do it right, since you have an integrated controller.

~MiSfit

[blizard]

fuhgettaboutit...

Move the data, and wipe the array. Move it to the new box, rebuild it, and restore the data. Only way to do it right, since you have an integrated controller.

~MiSfit

That is also the only way to avoid conflicting hardware drivers as you will need to update hardware driver to support your new motherboards chipset and hardware. Windows XP should also be replaced with a fresh install to avoid problems.

[Wolfman]

The only raid worth using at home is mirroring.. everything else simply gives you these sort of problems. A lot of people think raid is a backup solution, or alternative to one. Use raid only on temporary files that you need higher performance on.

[Konrad Klar]

I understand difference between RAID0 and RAID1. Thanks.

I want higher transfers, not more safety of datas. I don't want spending money for securing my single HDD datas, if for the same money I may have 2x more capacity and 2x more sustained transfers. RAID0 in my home computer is not worth using from my limited home budget's point of view.
Even on my home computer in home applications I see huge difference between one disk and RAID0 in areas, where sustained transfer is important factor - making VOBs from MPEG2 files, unpacking large archives etc.

If there is no method (or nobody knows method) of converting raid metadatas between formats used by different incompatible controllers then looks like I'm tied to the Intel's chipset family.

P.S.
I have heard recently that at least second stage of process of moving WindowsXP installation on RAID0 to the incompatible controller is (potentially) possible. This method is repairing system using installation CD and providing (via F6) drivers for new controller. That drivers will by installed in system during process of repairing.
Of course it would make sense (if actually working) only if raid metadatas would be earlier converted to the new format.

[Dr.Khron]

Just becuase there might be a way to do it, doesn't make it a good idea. Especially if you have your system disk on RAID.

I have to second Blue Misfits advice, its the ONLY SAFE way to do it.

[foxyshadis]

There's nothing wrong with RAID0 system if you're a believer in regular backup.

The best thing to do would be to hook up the new motherboard and see if it recognizes the raid set; it'll tell you during initialization. If it doesn't, you can go into raid setup and see if it can detect it, or else you might have to break and recreate it. It should always be compatible for the same chipset and may be compatible with upgrades (like nforce3->4 or 965->P35), chances are very good that if it's a totally different chipset it won't work at all because of striping differences. This is at the hardware level, before the windows drivers get involved at all.

You can make an ISO of the RAID drive by booting from another drive or BartPE, break and recreate it, reapply the ISO, and at that point you will need to have the new drivers. You can save yourself a repair installation by just installing them before you change the RAID, windows won't care if you have multiple unused drivers.

[Konrad Klar]

chances are very good that if it's a totally different chipset it won't work at all because of striping differences.

So you are suggesting that difference is way in which actual datas are physically organized on disks, not just/only metadatas describing array?
If so, then indeed no other way of transferring array than backup/restore...

You can save yourself a repair installation by just installing them before you change the RAID, windows won't care if you have multiple unused drivers.

Maybe I don't get your idea :confused: . Problem is rather such that I cannot install (under WindowsXP at least) drivers for hardware that is not present. Before changing RAID new controller is not present in system and installer refuse to install drivers for it.

[foxyshadis]

The installation should come with a .inf file along with all the system files, so you can install it the old fashioned way. It might have to be extracted or even copied out of the temp folder after starting the installation. Nforce drivers are all like that, at least.

[would_like_to_know]

He-he, if you are using RAID0, you surely must be doing regular backups, since the risk of losing it all is pretty high! Right ?!?

If you do have a good backup system, just copy all your stuff there, and do a clean reinstall. This will be faster time wise, and a lot less "exciting" (as in adrenaline from having to start from scratch once you screwed up). Note that a "boring" reinstall is a good thing, much less potential pain.

Note that Windows (XP included) is pretty evil with respect to moving an HD to a new system. If new hardware causes reboots upon booting up, you are very much stuck. Bill G is so afraid that you will move his precious license to a new machine, that there is not way to tell a booting Windows machine to load no drivers except the most basic ones, and re-detect them all from scratch. One can mess around with hardware profiles and removal of all the old drivers manually (search the web) to make it workable, but why is not there an automatic option for that in Windows ?!?

Suppose your motherboard died, you cannot remove the old drivers anymore, and the new system just reboots. Thank you, MS and Bill G!

With a Raid0, potential pain is bigger. Back up your stuff, and try to see if the new system finds Windows when you start with a Windows install. It usually says "found Windows on such an such drive" (after loading whatever drivers, including Raid ones).

If it does, it will offer repair/upgrade options to you on top of the old system. Choose "upgrade", it keeps more of the old stuff intact. I chose "repair" due to lack of knowledge, and regretted it, WinXP played it safe, and nuked a lot of my desktop icons, although the applications themselves worked just fine.

[Konrad Klar]

@foxyshadis
If I understand you correctly, it would be sufficient to copy .inf and related .dll .sys files to the appropriate %SystemRoot% subdirectories and driver will be accessible when needed. Right?

He-he, if you are using RAID0, you surely must be doing regular backups, since the risk of losing it all is pretty high! Right ?!?

No... :) If risk of failure for one disk is (for example) 1% for year, then for two disk RAID0 it is 1-0.99^2.
1.99% - I don't care/fear too much. I can live with it.

[would_like_to_know]

No... :) If risk of failure for one disk is (for example) 1% for year, then for two disk RAID0 it is 1-0.99^2.
1.99% - I don't care/fear too much. I can live with it.

Well, the only time I tried Raid0 with your attitude, the disks started failing on me within ~1 month, Murphy law or such ... :devil: So, the 2% probability suddenly became 100% for me, not a nice situation to be in! Fortunately, I recovered most of the stuff.

But do try Windows XP boot from a CD, see if it recognizes your new Raid and the previous Windows on Raid disks, and offers to upgrade it. This would be the least likely to fail scenario (for data), and if it did not find your older Windows - you can abort at any time, and scratch your head on what to do next :rolleyes:

[foxyshadis]

@foxyshadis
If I understand you correctly, it would be sufficient to copy .inf and related .dll .sys files to the appropriate %SystemRoot% subdirectories and driver will be accessible when needed. Right?
Not copy, right click and install the inf and it'll make all the required copies & registry keys.

[Konrad Klar]

Thanks foxyshadis!