• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

transferring a RAID array to a new mobo

F

Fraggable

Platinum Member
I recently sold my old AGP video card to upgrade to a new PCI-E mobo + video card. My system is set up with RAID 0 across 2 SATA 150 Seagate 80GB drives. On my old motherboard it ran beautifully, I never had a single problem with it.

It just ocurred to me that I might have issues transferring the array to my new mobo. Are RAID 0 arrays usually easily transferred to new mobos or are there problems if the new board has a different RAID controller?
 
It's quite UNLIKELY that you'll be able to directly move a RAID 0 array from one motherboard to another. Different RAID controller chips use different ways of managing the RAID array and are often incompatible. The safe way to do it is to have current backups of your array on another drive, to create a NEW RAID 0 array on your new PC, and then transfer the backups to the new array.

Disk arrays CAN be moved, but, typically, only if you are using a separate RAID controller card, such as a PCI card. Those can be moved, along with the drives, and wlll instantly function on the new motherboard.
 
Darnit, that's gonna be a pain. I have my data backed up on my laptop and on DVD but I hate the idea of installing all my stuff again.
 
Here's a twist to this problem: If I set up a RAID 0 array using an NF4 board, then move to a different NF4 board, will it work?
 
Originally posted by: Fraggable
Here's a twist to this problem: If I set up a RAID 0 array using an NF4 board, then move to a different NF4 board, will it work?
Click to expand...

I did it with a RAID 1 array, and it worked. Just create the RAID the same way in the BIOS menu and it should recognize it.
 
My new DFI mobo was giving me fits, I had to flash the BIOS 4 times to get it to reboot once. If it acts up again I'm gonna RMA it for a Fatal1ty board. I wanted to make sure it would transfer easily.
 
Originally posted by: dwcal
Originally posted by: Fraggable
Here's a twist to this problem: If I set up a RAID 0 array using an NF4 board, then move to a different NF4 board, will it work?
Click to expand...

I did it with a RAID 1 array, and it worked. Just create the RAID the same way in the BIOS menu and it should recognize it.
Click to expand...

Backup everything you can before you do so, just in case. Beyond that, there isn't much more you can do, other than just seeing what happens.
 
Generally speaking, moving among identical controllers shouldn't be a problem. The real problem here will come from Windows itself, since the other hardware in the machine is likely to be different. If it's just data, there should be no problem moving among the same RAID chipset controller type.

\Dan
 
As suggested above, about all you can do now is try it and see. Since you are using the same RAID controller, that'll likely not be a problem. As mentioned, it's possible, but not likely, that Windows itself could complain, forcing either a complete re-install or else a "Repair Install".

If you run into issues, you might consider if this is a good time to buy an inexpensive PCI RAID card. There are low-end, software-based RAID PATA and SATA cards for around $50 at Newegg. If you use these, you'll be free in the future to move your array to any new motherboard that has a PCI slot and has drivers for your RAID card. I consider this freedom to be worth the fifty bucks.
 
You almost always will have to reinstall windows, not matter what. Moving between the same controller usually works fine for the data, but windows can't handle a change in motherboards. If it's the same manufacturer you might have a 50% chance of it working, and between manufacturers is totally up in the air and unlikely. I'm pretty sure nforce3 to nforce4 works for instance.
 
If you have a third drive with enough capacity, you can create an image of your array using software like Acronis.

You can then move your currently RAIDed drives to your new motherboard, create your array and restore from your image.

Then, you will have to do a repair install using the steps here to ensure you can boot off your RAIDed drives attached to your new motherboard.

The most important thing is to have yourself covered in case of problems. It sounds as if you do.

Acronis can also span your image across DVD's if that's how you need to do it. Read up and know what you have to do if you go that route.
 
Originally posted by: obeseotron
You almost always will have to reinstall windows, not matter what. Moving between the same controller usually works fine for the data, but windows can't handle a change in motherboards. If it's the same manufacturer you might have a 50% chance of it working, and between manufacturers is totally up in the air and unlikely. I'm pretty sure nforce3 to nforce4 works for instance.
Click to expand...
The motherboard chipset is more important than the manufacturer. I moved a RAID 1 between two different brand NF4 boards, and it worked fine, but remember that a RAID 1 is simpler than a RAID 0. One drive will boot by itself. I was using Forceware drivers downloaded from Nvidia, not from the MB CD.
 
I'm afraid it's reformat time. It's not even a RAID thing. It is a chipset thing. As long as you are going from one mommaboard to another that uses exactly the same chipset, you'll be fine. If not, it's time to do the right thing and you already know what that is!
 
I'm staying away from the RAID thing, but the comments about having to re-install windows are false.

You can move a Windows installation from different motherboards provided the chipset/drive controller that's registered as a boot device is on both machines. Given that Nforce and VIA controllers have universal drivers that span many chipset revisions, it's not that hard. I have a common Windows image built on an Asus Nforce 1 board that boots fine when Ghosted to a MSI Nforce 2 board. A lot of other drivers have to be re-installed, but that's easy. Just remember to to obliterate ATI card drivers if you are moving to a box that won't be running the same or never version card. I believe you can move a machine that's booting off a VIA chipset to an Nforce, but not the other way around.

Recently moved a very complex production Windows Citrix server from a Dual Xeon IBM server running integrated RAID SCSI to an Asus based dual core X2, which is about as radical a hardware move as you can get. I just used a 3Ware IDE RAID card as the common device in both machines.
 
Even if you can slap multiple driver packages in, in the end, it will hobble performance from not just my experiences, but many other reports as well. So this brings up the question...

Why did you upgrade anyways?!
 
Originally posted by: Luckyboy1
Even if you can slap multiple driver packages in, in the end, it will hobble performance from not just my experiences, but many other reports as well. So this brings up the question...

Why did you upgrade anyways?!
Click to expand...

It was my AGP>PCI-E jump. I went from an X800XT AIW to a X1800XT. Had to be done eventually.
 
Originally posted by: Fraggable
Originally posted by: Luckyboy1
Even if you can slap multiple driver packages in, in the end, it will hobble performance from not just my experiences, but many other reports as well. So this brings up the question...

Why did you upgrade anyways?!
Click to expand...

It was my AGP>PCI-E jump. I went from an X800XT AIW to a X1800XT. Had to be done eventually.
Click to expand...


So, there you go! You've answered your own question then and know what's the right thing to do. Am I 100% fer sure right? Maybe not in this case, but I'm close enough to 100% as to make it simply not worth bothering with.
 
Originally posted by: Luckyboy1
Originally posted by: Fraggable
Originally posted by: Luckyboy1
Even if you can slap multiple driver packages in, in the end, it will hobble performance from not just my experiences, but many other reports as well. So this brings up the question...

Why did you upgrade anyways?!
Click to expand...

It was my AGP>PCI-E jump. I went from an X800XT AIW to a X1800XT. Had to be done eventually.
Click to expand...


So, there you go! You've answered your own question then and know what's the right thing to do. Am I 100% fer sure right? Maybe not in this case, but I'm close enough to 100% as to make it simply not worth bothering with.
Click to expand...

You lost me. I've already formatted and reinstalled based on this NF4 Ultra chipset.

What are you right about?
 
Well, if that's the case and alls well, then you landed by dumb luck more than anything else into the 1.8% or so of those builds that can do it without "a problem". but there's the question...


How do you know it is doing as well as it can without going the reformat route?

Only one way to find out, so it's entirely up to you!
 
Originally posted by: Luckyboy1
Well, if that's the case and alls well, then you landed by dumb luck more than anything else into the 1.8% or so of those builds that can do it without "a problem". but there's the question...


How do you know it is doing as well as it can without going the reformat route?

Only one way to find out, so it's entirely up to you!
Click to expand...

Ok now i'm pretty sure you either don't understand english or aren't really reading my replies...
 
I got a Abit AT8 Crossfire board, installed Windows again, flashed the BIOS, and all is well, including the X-Fi.

I noticed though, before I flashed the BIOS it said 'Engineering Smaple' above ther memory test line...
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top