Moving SATA RAID 0 array

Any tips on how to move a SATA RAID 0 array between machines? Is it possible? Array was set up on an NF3 chipset. Can it be moved to an NF4 or 5, or even an Intel or Promise? If it includes the boot partition can you use Win XP Pro repair console to install correct Win XP drivers, asuming the array can be installed?
scott s.

sorry for not getting back sooner, but thanks for input. That makes me feel a litlle better, but with all the RAIdDproblems I see on the boards, it makes me wonder if RAID is worth the hassle.
scott s.

Similar Messages

Bootable sata raid arrays

What are the bootable hard drive RAID/SATA configurations for the MSI K7N2 Delta ILSR?
i bought an 80 gig Seagate SATA hdd and i didn't realize that the SATA ports operate only on RAID....

HI
Ive worked out that even with two SATA HD Connected you dont have to have them raided.
When u Ctrl-F got to 'Define Array', now define 2 arrays with 1 drive in each, it look like this:
1* 1+0 stripe size track functional
2 1+0 stripe size track fuctional
make sure when you build the arrays theres a option in the bottom right of the page, i think its says funationable or operational or something like that make sure thats a Y an not N
I had my 2 drives(I know but you cant bckup loads of GB's on CD's) raid 0, one crashed, lost everything, you cant see the partitions unless both drives are connected an functional so i lost everything on both as i had 2 send 1 drive back,
how is this of some use
Jason

MOVED: SATA RAID problems with 890GXM-G65 - Driver not accepted by win7 x64

This topic has been moved to Windows 64bit.
https://forum-en.msi.com/index.php?topic=139814.0

when I attempted installation I have been unplugging the current boot drive. The first screen I am given after selecting the us / english / keyboard stuff and clicking the "install now" is the screen asking for drivers.
I know that windows must be recognizing the raid drives because I could continue installation but only if I use the 32 bit drivers and corresponding os version.

PM8M2-V RAID array not recognised by WinXP Pro

Greetings,
i'm just setting up a PM8M2-V system with 2 x WD 80GB JD SATA drives. In the RAID BIOS i have configured the drives to be RAID 0 (striped) for performance and made them bootable. From a IDE DVD rom, i'm running a WinXP Pro (corp ed - no pre-installed service packs) install but the OS will not detect any drives in the system.
I have downloaded the VIA_RAID_OM74.zip file from MSI VIA PIDE-SATA RAID Drivers and Utility for creating the RAID drivers and tried to create a floppy disk with the WinXP drivers on it using the embedded (and slightly cryptic) VIA MakeDisk.txt instructions.
Containined on the floppy disk are the following files/folders:
a:\TXTSETUP.OEM
a:\PIDE\WinXP\viapdisk.cat
a:\PIDE\WinXP\viapdisk.sys
a:\PIDE\WinXP\viapide.inf
a:\RAID\WinXP\viamraid.cat
a:\RAID\WinXP\viamraid.inf
a:\RAID\WinXP\viamraid.sys
*plus the other MS operating system files in the similar directory structure*
Problem - WinXP Pro does not recognise this created floppy disk as a hardware support disk and will NOT let the OS recognise the SATA RAID array as a drive.
Complete system specs
MSI PM8M2-V VIA P4800 + 8237R (RAID)
Intel P3 3ghz HT LGA775 CPU
2 x 512 DDR-RAM PC3200
2 x WD 80GB JD SATA drives configured in a RAID 0 Striped set and bootable
1 x IDE DVD D/L Burner (Master drive on IDE Secondary Channel)
ATI Radeon 9250 128m AGP Card
Web Excel 56K software modem

Did you boot with WinXP CD 1st and then hit F6 to install the RAID controller drivers?

Access to SATA RAID-5 array without an MSI motherboard?

I have (had) an MSI K8N Diamoond Plus motherboard, and used it to create a bootable SATA RAID-5 array of three 300Gb Western Digital disks. Two years later, the motherboard developed a serious problem with the memory access, and now it won't POST beyond the memory initialization. So it's fried. I've tried multiple memory modules in multiple configs, and nothing helps.
OK, no problem, new motherboard and I'm good to go. Only this isn't an MSI motherboard, and it's an Intel chipset. So, the RAID array isn't recognized.
Are there any software tools that can reconstruct the RAID array when running on a non-nvidia chipset motherboard? Is there any other solution besides buy a new MSI motherboard?
And, if I have to get a new MSI motherboard to solve this, what's the cheapest currently available motherboard that would be compatible with the RAID established on the original K8N Diamond Plus?

Quote from: cameradv on 23-January-08, 00:07:27
Well, I'm not 100% sure which controller was doing the RAID. I'm thinking the SIL, but I beleive it was nvidia software drivers in windows that re-constructed the RAID-5 once when I replaced a drive. Can you buy a standalone nVidia RAID controller, anyway?
You were using Nvidia RAID, with Silicon can't do RAID5.

Oracle Ent. Linux drivers for HP Smart Array B110i Sata Raid Controller

Trying to install Oracle Ent. Linux (OEL) release 4 update 8 on HP DL 180 G6 server. Where we can find OEL drivers for the sata raid controller ?
(HP Smart Array B110i Sata Raid Controller)
Thanks in advance.

The HP support side shows a Linux certification matrix at: http://h18000.www1.hp.com/products/servers/linux/hplinuxcert.html
From there you can also download the necessary drivers and instructions or use HP smartstart CD which prepares the system for the OS you need to install. Oracle Enterprise Linux is binary compatible with RHEL. You will need to click on "Archive" to see support for Enterprise Linux version 4 and older.
Also interesting should be Red Hat Enterprise Linux Technical Exceptions at
http://h18000.www1.hp.com/products/servers/linux/supportmatrix/rhel/exceptions/rhel-exceptions.html

Error in SATA RAID 0 array

Did anyone had any problems with the MSI board utility that configures the sata drives in RAID arrays
I have two drives that worked fine for tree months and now when I start the system get a message from the RAID config utility telling me one of the drives has a problem.
I went through formattingand reinstalling everything and the array worked well for some time then I got the same error.
Next thing I've tried was to start the system with only the good drive connected. No surprise I got the message that the array was bad. The I connected the second drive, restarted the system and the RAID utility told that the drives were OK but the array was not, but asked if the two disks belong to the original array. I answer YES and get the array functional again and the system boots with no problems.
Next boot everything starts all over again with the RAID utility stating a bad disk.
Any ideas ???

Generally, bad sectors can be blocked off so they are ignored during a format. However, you're running a RAID which functions best with identical drives.
It's unusual to have bad sectors on drives these days which inclines me to think that "heat" is what may have led to the bad sectors.
In your case, you are better off to RMA the drives but since you have the array up again, I would recommend using it to determine if your system temps may have led to the bad sectors.
If temperature is an issue in your system, you could plug new drives back in and end up having the same results after a short time.
Then again, your situation may just be a fluke and you just got a bad drive. Either way, RMA.

Moving RAID Array from old to new workstation

I've completed building a new rig. Win10 is working. I have a RAID 0 array of 2-750GB drives in the old rig. I've installed 2-1TB drives in the new rig. Drive manager shows both old and new HD's but not as a single RAID array (RAID-OLD,
and RAID-NEW, as I have named them during the BiOS RAID naming. Could I have some guidance about this? I also have the contents backed up on a USB-3 external drive, but would like to continue with both of the RAID arrays and not go through transferring
data via USB.

Hi CWO4 Mann
For hardware, we need the driver to drive it works in Windows system. When you move your RAID to new system, ensure you have installed appropriate driver.
I suggest you download the driver in Windows 10 Technical Preview, install it in Windows 8 compatibility mode to check if it works well.
Alex Zhao
TechNet Community Support

Booting from external SATA firewire800 hardware RAID array

Just a quick post to update on a new toy and how it's being used.
Recently obtained a hardware RAID array which contains 5 drives at 250 GB each. Currenly setup as RAID 5, providing 1TB of storage.
After formating via DISk image I did a drive restore from my normal boot disk to the new array.
I changed the startup options to boot from the array.
So basically I am running my system from this new device.....I may later reconfig the array to 0+1 with a floating spare.
Cost of the box was 500. New and unused off ebay.

..

K8N DIAMOND: New Raid array and old HD... I'm going crazy!!! Please

Hi guys
First, sorry for my poor english...
My problem is:
I bought two Raptor 36 Gb for my new raid array.
I have my old HD Hitachi 250 Gb connected on sata 1.
I connected my two raptor, on sata 3 and 4, I enabled all sata port and raid config for ports 3 and 4.
I restart PC, typed F10 and set a stripe array with two raptor. All run ok...
Restarted and boot with my copy of WinXP with SP2 and NF4 raid drivers.
Installation found my array and my Hitachi;
Hitachi with 4 partitions; C (os), D (driver), E (films), F (music)
I create one partitions on my raid array, and it takes I: letter... So I formatted and start to copy os...
Errors occurs when, restarting pc and resetting the boot to Hard disk (the order of booting is 1 - nvidia array, 2 - hitachi 250 gb), just before loading installation, It shows a black screen with an error: "there is an error in your hard disk bla bla bla.. try to control your connection or connect to windows help....bla bla..."
The Raid array works properly, infact I try to disconnect my Hitachi from sata port 1 and all installation works (I'm writing from Win xp on the raid array).
I tried to connect the hitachi on port 1 of silicon image controller.... same error..!!
I'm desperate... I have all my life on my hitachi...
I think that there's a sort of conflict in drive letter assignement... I cant find a solution ..
PLEASE HELP ME!!!

Glad it worked, I had a feeling it would.
Quote
One question for you.. on G: partition, there's a directory called "Windows", do you suggest me to format this partition??
You can format it if you want to free up space, but unless you moved things around the My documents folder and everything in it is on that partition, along with anything you might of had on the old desktop during that Windows install. You might have something you want there, I usually leave mine for a few month, and figure out if I have everything I need.
Quote
What I have to do, if I need to reinstall WIn XP on first partition of raptor array??
Things should be fine now as Windows marked the Hitachi drive as G. You should be able to reinstall without issue. But if you have a lot of sensitive info on the Hitachi, I would always disconnect the Hitachi if doing a fresh install. Once windows is done installing, hook it back up. But next time you shouldn't have to reconfigure NVRAID after disconnecting and reconnecting.

WinXP-64 bit corrupts existing RAID array

I've got an MSI K8N Neo2 Platinum motherboard running Win XP Pro SP2 on two 36 gig SATA Raptors. Everything was working fine, but I wanted to try the 64 bit version of XP. Grabbed an old 80 gig PATA drive and threw that in the case. Unplugged the SATA drives so as not to risk messing with the existing working OS. Installed the latest 1218 x64 beta and it worked well.
The problem was that when I shut down and reconnected my old RAID array, windows wouldn't boot from it. I lost everything and had to rebuild Windows from scratch. So now I know to never unplug the SATA drives
Rebuilt WinXP on the RAID array and then tried rebooting with the PATA drive with the 64 bit OS. Came up with the "drive needs checking" screen, and proceeds to "fix" the RAID array while ignoring my frantic pounding on the Logitech USB keyboard to stop. Rebooted and yes, the new install was nuked. Okay, since it's gone anyway, reboot to the 64 bit OS and make sure it's got the 64 bit RAID drivers installed.
Reinstall WinXP on the RAID array, reboot to the 64 bit OS on the other drive and the same old scandisk comes and nukes it AGAIN!
So now the PATA drive is sitting on the shelf again, unless someone here can suggest what is causing this problem.
System Specs
Athlon64 3500
gig of PQI 3200 at 2-2-2-5 2.6
2x36 gig Raptors on ports 3-4
Plextor PX-716a DVD+_RW
Visiontek X800 Pro.

The first time you re-installed Win 32 on the raid that was a bit drastic. A repair ought to have done the job.
The problem was probably that you disconnected the array but that's where the boot.ini was and that file needed to be modified to add the path to the Win64 install.
Since you took out the array the Win64 install created a new boot.ini on the PATA drive. Even when you tell BIOS to boot off the array, Windows has a bad habit of looking at the IDE channels & using the boot.ini if it finds one there - but the file it found didn't point to the array of course.
So basically if you already have Win32 on the array I would leave that array connected normally when installing Win64 on the PATA drive and all should be well.
I've installed Win64 on the same array as my Win32 install and they co-exist happily. I reckon that's the most efficient way to do it. The main thing is to make separate partitions for Win32, Win64 and data files when you install Win32 in the first place. The two OSs can share the same data files, incuding stuff like email.

Raid array being seen as 2 individual drives

Hi. Here is the issue as posted in other places. Still searching for the answer to this one.
Specs:
K7n2 delta2 platinum with b50 bios
2x1gb crucial pc3200 2.5cas ram
AMD Barton 2500
2 x 160gb 7200rpm 8mb cache SATA Samsung Hdd's
Thermaltake 430w psu
Gainward fx5700 ultra graphics
OS's: original xp corp, slipstreamed xp corp sp2
raid drivers: nvraid.sys v4.27, 5.10, 5.11 (also the needed nvatabus.sys with those)
I am NOT overclocked.
fsb 166
1:1 ram/cpu
no spread spectrum or other garbage
ddr400 patch disabled
PSU gives presumably stable reading (according to what I see), with amperage ratings above the required.
checked and rechecked cables for bad ones
ran mulitple scans on drives, all come up drives OK
I HAVE installed into Raid 0 already, this is not an issue of hardware failure as far as I am concerned.
So here is the scenario
I have properly set up the array, using correct bios settings and the raid setup utility, for a raid 0 array of those 2 hdd's listed. When booting into xp, either version, I have used all 3 of the driver sets listed. I have been reinstalling to do some performance tests on different configurations.
Anyway, for the last few nights I have been trying to get the windows setup to see the raid 0 array as one 300gb drive. It does not, no matter what I try. It sees them as 2 drives, each being 160gb (or thereabouts). These drives are matched, same firmware, same lot, so that should not be an issue.
I have used numberous tools to delete the mbr on the drives, both in an array and as single drives. I have done the same as well as tried an install and formatted each drive individually, still the same effect when the raid array is recreated.
Basically, I can find no good reason why the array is seen as individuals and not as an array. It is interesting to note, that even though xp setup sees the the array as 2 drives, I can complete the text based portion of setup. However, rebooting to start the GUI portion of setup, it will not boot. Obviously becuase the bios has the controller as the nvraid controller and it is supposed to be a raid 0 array, so I expected that.
Short of rewriting the mbr, either by deleting it or by changing each drive by formatting/partitioning/installing an OS on them, I cannot think of how to fix this. I know the drives and xp cd's work because I have already installed with them.
I understand what to do in the bios portion, and in the raid setup utility portion. I know that I can boot into windows as a single drive and use the nvraid tool to set it up, but that is not the way it should be, and that is not the way I am going to learn WHY this is happening.
Roger that. First set in bios enable raid (in this bios I have to enable IDE array, then choose which controller to actually enable raid on, which happens to have been SATA 1 & 2).
Second, upon reboot, I use the F10 key to enter raid utility. Then, set to striping, set stripe size (which was one of the things I am testing), and add the drives to the array. Next step is to create it. It asks to clear disc data, and it is done.
Have deleted that array as well as just cleared it. Have deleted it and reboot and rebuild it. Have deleted it, reboot, change bios back to non-raid, reboot. Reboot. Change bios back to raid enabled. Reboot. Rebuild array in raid utility, reboot. Run setup, only see 2 hdd's, not one array.
Umm, yep, that is about it.
More to the story now.
From some other posts I tried this.
1. destroy array. reboot. disable raid in bios. reboot. verify sata's visible as singles in bios.
2. power down. pull plugs on sata's. reboot. no drives visible.
3. pull power. jumper clear cmos. wait 60 seconds. re-pin jumper. power up.
4. verify no drives. verify default bios settings. all is good
5. plug drives in. reboot. seen as singles. erase mbr on both drives. reboot
6. enable raid in bios, and choose sata 1 & 2 as "enabled". reboot.
7. use F10 key to setup raid. Here is the interesting part. Even though I deleted the array prior to all of this, and removed the drives to force an ESCD update, and cleard the cmos with the board jumper, and then before raid was enabled, cleared the mbr on the drives, when I started the raid utility, the array was already set up. That is the problem, whatever that is. I have read snippets where it is claimed that this chip or bios or whatever stores some kind of a table on this stuff, but this is a bit out of hand.
That combination, IMO, should have cleared anything out. But, the saga continues.
Thanks for you help BWM
[Edit] BTW, I have finally found a utility that will see a raid array and allow me to clear the arrays mbr. It is called SuperFdisk and is at ptdd.com. So far the only one that see's the 2 drives as 1.
Yeppers.
Started with v5.10 which came on a floppy with the mobo. Told setup to use both, nvatabus.sys and nvraid.sys. Even switched which one of the 2 I picked first, just to see.
Same thing with v4.27 and v5.11. Also tried it with just the nvraid.sys and just the nvatabus.sys (which obviously does squat for raid, lol)
Trying some new things now. Post in a little bit.
I am officially at 'Wit's End'.
Here is what I have tried now.
1.pull drive cables. pull power. jumper clear cmos. wait. power up. no drives
2.plug sata 1 in. boot. drive detected.
3.boot to command.com, run MHDD, which is a nice russian utility similar to Spinrite. Used this to clear the mbr at hardware level, and do a complete erase.
4. reboot to command.com. run superfdisk. erase mbr.
5. pull plug on sata 1, and plug in sata 2 with sata 1 cable. repeat the erasure steps listed above.
6. pull plug on sata 2, no sata plugged in. reboot
7. change bios to raid enable on sata 1 & 2. power down
8. plug in sata 1 & 2. power up.
9. inspect raid utility. no listing of any arrays. reboot
10. in raid utility, build array. did NOT clear discs. reboot
11. attempt install. single drives found again (used both drivers).reboot
12. in raid utility, optioned to CLEAR discs (funny, rebuild option is never valid).reboot
13. attempt install, both drivers, still seen as 2 individuals.
Things to note. When creating an array when presumably there are none, it assigns the raid array an ID of 2. Upon reboot, the ID is now 1. Don't know what difference that makes.
Also, tried the install listed above with APIC functionality both off and on. Also, when on, set MPS to both 1.1 and 1.4. In addition to this, each variant I tried manual HAL layers of, in this order, ACPI (the one that actually spells ACPI out), ACPI Uniprocessor, MPS Uniprocessor, and let it choose it for me.
So, here I sit in a barca-lounger at 'Wit's End', with a warm cup of java and a dinner mint.

Here is the final product on the floppy disk that I used to successfully install a stable raid 0 on the MSI K7N2 Delta 2 Ultra 400 Platinum ms-6570e motherboard.
On root of floppy, from driverset 6.70. (after much testing, I used driver pack 5.10 for my nic and smbus. I used the realtek sound drivers off the cd for audio. I have used every driver pack I could find, and while some did offer better I/O or read/write latency, this set in general provided the most stable environment. The only drivers I used were these floppy drivers for SATA, the nic and smbus just mentioned, the sound just mentioned, and updating the nvide drivers to mside drivers)
<from sataraid directory>
disk1
idecoi.dll
nvatabus.sys
nvraid.cat
nvraid.inf
nvraid.sys
nvraidco.dll
<from legacy directory>
nvata.cat
nvatabus.inf
I used the txtsetup.oem from the sataraid directory, but edited this:
[Files.scsi.RAIDCLASS]
driver = d1,nvraid.sys,RAIDCLASS
inf = d1,nvraid.inf
dll = d1,nvraidco.dll
catalog = d1,nvraid.cat
[Files.scsi.BUSDRV]
driver = d1,nvatabus.sys,BUSDRV
inf = d1, nvraid.inf
dll = d1,idecoi.dll
catalog = d1, nvraid.cat
To this:
[Files.scsi.RAIDCLASS]
driver = d1,nvraid.sys,RAIDCLASS
inf = d1,nvraid.inf
dll = d1,nvraidco.dll
catalog = d1,nvata.cat
[Files.scsi.BUSDRV]
driver = d1,nvatabus.sys,BUSDRV
inf = d1, nvatabus.inf
dll = d1,idecoi.dll
catalog = d1, nvata.cat
Now, it is important to note that I installed or attempted to install at least 50 times. Bare minimum. I noticed when I use this custom driver disc that in the GUI portion of setup, XP asks me for files from the disc. I tried lot's of different things to alleviate this, and denied some of them.
One thing that really bugged me was that the bios would see my #2 optical, slave on secondary IDE channel. A dvd/rw drive. And I could even start the setup from it. But, once I got about 3/4 through copy file stage on text setup portion, I would hang. Becuase the drive was no longer accessible. Booting from the master would get me to the desktop, but the slave optical was nowhere to be found. Updating the ATA/IDE controller to the ms ide drivers would get it visible, but I kept having issues with stability after I did that.
The most stable method I found was to use my above listing of driver files for the floppy, and when in GUI mode setup asks about NVCOI.DLL, I skipped it, ignored it, and did not let setup install it. That actually got me to the desktop, with access to the slave optical as a "removable drive". It even knew what the hardware was. It just could not access it. On a reboot however, back to not seeing it. This method however did allow me to update the nvide driver with the mside driver with no stability issues. So, for me it was a raving success.
Here are some links regarding the SATA RAID driver workaround:
http://66.102.7.104/search?q=cache:jHbX5bNfGx4J:www.msfn.org/board/lofiversion/index.php/t51140.html+nforce2+nvraid.sys+ms+ide&hl=en&client=opera
http://www.aoaforums.com/frontpage/index.php?option=content&task=view&id=292&Itemid
http://66.102.7.104/search?q=cache:J9UhG2Kd8W4J:www.short-media.com/forum/showthread.php%3Ft%3D32751+xp+2+sata+raid+0+seen+as+individual&hl=en&client=opera
Early on one problem I noticed was that in text setup mode of xp installation, there were long pauses that I have never seen before. I noticed that with both ide and sata installs. Also I noticed that when booting there was a really long pause when the xp logo is first seen in a sort of dim state till when it became bright and vivid.
Come to find out that this is a more or less typical scenario. Most instances that I read about were all pointing to the nvide driver. So, I found if I just updated the PATA controller to the standard ms ide driver, that went away and the whole system ran better.
It took awhile to figure out that if you install a driver with the nForce2 chip, you had to uninstall it or you will have issues. Herein was the main problem I encountered with the SATA RAID installs. The nvatabus.sys driver was required for an SATA RAID install. Omitting the ata driver was impossible. And for awhile I had no success updating the ms ide driver once I was to the desktop without major instability. Here are some links regarding the drivers for this chipset:
http://www.nforcershq.com/forum/latest-drivers-for-nforce-3-vt60240.html
In my browsing I came across some pretty interesting articles regarding ACPI. One thing I started playing with was the different HAL layers that xp installs on it's own, vs. me picking one manually (F5 key). I must have started the setup at least 50 times to figure out this: that this particular board does not give me the bios settings to install xp with anything but the ACPI Uniprocessor Hal. For instance, the MPS Uniprocessor HAL is much more responsive, but it lacks the IRQ's needed for setup to see the raid array. I booted to each one, some locking the system up, some booting OK. The one I found the best performance with early on was the one that spells out ACPI, not just initialized. (sorry, I don't want to look it up).
I seemed to be getting closer, but I could not find the needed bios settings to properly manage my ACPI, and since I was trying for RAID, I could not use the one that did work. Here is a link for that kind of stuff.
http://www.fceduc.umu.se/~jesruv98/info/acpi/acpi.html
Another thing that I did not like was being forced to use the dynamic overclocking feature of this board. I have a 333mhz barton core, and I have ddr400 ram. In optimized (fool proof) mode in bios, I was running asynchronous. I did not want that. So I set it down to run at 166mhz, with very slow and conservative settings on everything. Unfortunately, if I did this "manual" method, I was forced to use the dynamic overclocking. I thought I had that figured out. So I set everything to "optimized". But, as it turns out, the system had terrible stability without the dynamic overclocking set to at least Private. What this meant is that I could not rule out that my stability issues (corruptions and hangs and bsod) were from being overclocked even a tiny bit or not. And as if that were not enough, this bios has a special set of settings you must unlock to see. And one of those is paramount in achieving a stable system. It is called the DDR400 patch, and it is enabled by default. So, by pressing SHIFT+f2 AND CTRL+F3, these settings are now available. Like I said, I had to disable that DDR400 patch setting.
I also found out from the first day that my board shipped with the latest bios. I flashed the 2 prior versions with no success in more stability. After about 6 weeks of getting whipped on by this board, I found mention of some modded bios's for this board. I have used modded bios's in the past, some worked wonders, others required some serious effort to recover from. What I found out about this board is that there are 2 players who make the modded bios's. Here is the first index I found from a german website. This one actually is for the older B4 version only for the Platinum.
http://storage-raid-forum.de/viewtopic.php?t=2824
And here is an english forum for pretty much the same thing
http://www.nforcershq.com/forum/bios-mods-for-k7n-and-k8-boards-vt55014.html
These links have a bit more information, and I decided to go with these. I tried versions b61,b62 and b71. I found b71 to work the best for me. Mind you I am not into overclocking or what-have-you. Just a rig that performs as well as it was advertised to do. Try these out for the bios information:
http://forums.pcper.com/showthread.php?t=385480
https://forum-en.msi.com/index.php?topic=84715.0B62
Here is a page that had a bunch of misc stuff I found interesting:
http://66.102.7.104/search?q=cache:QkvLeKcbwjQJ:www.amdzone.com/modules.php%3Fop%3Dmodload%26name%3DPNphpBB2%26file%3Dviewtopic%26p%3D75383+nforce2+ultra+nvraid+driver+freeze&hl=en&client=opera
In the end, I have, I think, conquered this board. My findings can be summed up as follows, all in my opion only I guess.
1. There are some ACPI/APIC issues with this board or this chipset. I believe it also included drivers and some can be attributed to XP.
2. There are some major bios issues with this board.
3. There are some major driver issues concerning SATA/RAID. I am not sure who get's the boob prize, nVidia or MSI.
The only way I have found to get RAID 0 installed and stable is to modify my bios (which is a modded beta version), modify my driver disk for SATA/RAID, modify my install sequence for those drivers, modify my drivers within windows after setup, use different drivers from different driver packs for different pieces of hardware, and modify my HAL layer after everything else is done, to achieve peak performance.
If I had not spent soooo much time trying to get a stable install, I would have built up an Unattended CD, which has some possibilities for forcing non WHQL drivers. But, hey man, I am totally burn out on this board. And all it was for is a spare LAN box for when I go to a lanparty. Sheesh. Murphy's law.
Oh, and I also found out, with my own eyes, that the Soyo KT600 Dragon+ that I dumped for this wonderful board, is way faster. Faster read/writes, faster throughput on the nic, faster booting, much faster installs of xp. As a matter of fact, I could get my KT600 to get a consistent thruput on the network to my older KT266a board at 99%. That is pretty fast. 2 of these Platinum boards, on a sweet switch that is tweaked, will only go up to 91%, no matter how much I tweak them. The gigabit connects via a crossover cable at about 38% of full bore. This is tweaked stuff, but still. I listened to the hype. Dual channel memory, giglan, etc etc.
I hope this may help anyone else out there who is still fighting with these issues.
Out.
sul

Neo4 Plat SLI using SATA Raid cannot install WinXP 32

I recently purchased the neo4 platinum and was quite amazed what all comes with the board. However, I have spent quite a while trying unsuccessfully to get winxp installed. I was previously using a pci rocketraid card to run my 2 maxtor drives as a stripped raid.
Before doing the final shutdown and swap, I went into the rocketraid and deleted the array. Swapped boards (raid card did not follow), plugged in the 2 maxtors into sata ports 1 and 2. Configured nvidia raid bios settings to enable raid on sata ports 1 and 2. Entered nvidia raid bios, and created a stripped raid array with the 2 maxtors. Boot to winxp install, f6 and installed both drivers on included nvidia diskette. When I get to the partition selection, I have nothing but 'Unknown disk' listed several times. If I try to access one of these 'partitions' by either deleting or selecting, the system crashes (blue screen).
So, I deleted the nvidia array, the reinstalled my rocketraid card, and created an array on it. Went through the same install sequence, and am able to see the array as a selectable drive, and am able to install winxp on it. So, I am a bit lost on where to go from here.. I tried searching both here and google and I didnt see anyone with this particular problem. Id really love to get this bad boy running (a good upgrade for me), but it seems I am destined not to. Please, someone help!

Quote from: syar2003 on 09-July-05, 18:10:53
Inside the nvraid rom bios make sure to clear disk data and set raid bootable .
gah, sorry, I should have put that in my original post (did those).
So, a bit of an update... after a bit more futzing around, I have tried multiple times on deleting, recreating (and clearing data) arrays, trying with and without setting to boot. After the 2nd or so array creation, my problem has slightly changed. Now, windows install does not recognize any hdd's present and wont continue.
Out of curiosity, I blasted the array from the nvidia bios, then went into main bios, disabled nvidia raid, and enabled sil raid. Hooked up the drives to sil raid, and created an array. Windows install see's the array, and is currently installing to it. Now, while this may function as a work aorund (if it completes) I think I read somewhere the nvidia raid is not on the pci bus, but the sil raid is (which is why I want to use the nvraid). So, aside from any input or suggestions about resolving the problem I am having, any input on the differences between the two raid setups?
edit- windows successfully installed on the sil raid array, but I still would like a fix for the nvraid

Questions about streaming disk, firewire and SATA raids.

I have two internal drives, one for applications/system and one for audio, which had been suitable up until recently. I recently added Ivory, and some addons to the BFD drums. The BFD Deluxe has significantlly more velocity layers, and is placing a strain on computer and drives.
I moved the BFD drum data onto an external firewire 800 (because of data size) The BFD drums seem to be having a hard time keeping up, (it glitches and stutters).
I have 3 gig of ram, so I guess I'll add more ram. But I'm unsure about SATA raids. Is it better to add an external firewire RAID?... Mac Guru, has some reasonably priced kits. Has anyone had experience with them?
There is a 3 drive bay which you can put inside your G5, but I have concerns it will draw too much power and generate too much heat.
Lastly, if I buy a 4 bay external raid, can i create a 3 drive raid, and keep 1 one drive as a seperate drive (do I have to stripe all drives in one enclosure, or can they be seperate?
Any insights would be helpful.. thanx

depending on whether you use eSATA or FW, you have differnet options as to how you mount the drives as volume(s) to your computer. FW pretty much limits you to a single logical volume, although it could be RAID-0 or in some rare instances, RAID-5 with certain enclosures.
eSATA, again, depending on the specific enclosure, can mount all the drives as a single volume, but you may have the option to mount multiple logical volumes... like the 1 RAID-0 and 1 independent volume like you mentioned.
earlier tonight i recommended this drive to someone else for a laptop application...
http://www.lacie.com/products/product.htm?pid=10724
for a desktop application, you would probably go with their 3.5" solutions since buss power is not important to you.
this might not be accurate, but this is my understanding of highest read/write performance to lowest in terms of general specs (certain products may have advantages / dissadvantages depending on the implementation) all RAID-0 volumes are assumed to be 2 drive RAID, although it is technically possible to do more with certain hardware.
1) RAID-0 eSATA
2) RAID-0 FW
3) RAID-5 eSATA
4) single eSATA
5) single FW
6) RAID-0 USB2
7) RAID-5 FW
8) single USB2
9) RAID-5 USB2
RAID-5 is a real wild card here because a 3 drive image is really not the intended configuration for RAID-5... more drives is preferred before you start reaching theoretical efficiency and the actual XOR engine or lack of one can drastically affect your performance levels.

New Builder needs some info K9A Plat. RAID Array help

This is a new build AMD 64x2 6000+, K9A platinum, Lite On DVD Re Writeable SATA, 2x74Gig WD Raptors in Raid 0, Asus X1950 pro Thermaltake 700 W PSU Crossfire cert.
BIOS registered my drives, Built array PC Rebooted, Installing Win XP pro Hit F6 install drivers, Format drives, Then before Install It says that :setup cannot copy the file ahcix86.inf.
If I skip it, it will install XP but when I try to boot from the hard drive It starts to load XP but crashes to the blue screen of death
*** Stop: 0x0000007BC ( 0xF78A2524, 0xC0000034, 0x00000000, 0x00000000)
Has anyone got this error string?
First RAID array I would very much appreciate any help given.

Hi!
Looking at some info on Google and Microsoft site, I cannot find the BC error code, only the error code ending with B. It indicates an error with the boot device. It can be caused by several things.
Check that you are using the correct device drivers to install Windows
Also, check the installation CD. It could be that the disk was damaged and that you are missing a crucial file because of that
You can also try installing Windows again and choose to recover the previous installation.
If this all does not help, try installing Windows on a single HDD (no raid) to see if that will work.

Moving SATA RAID 0 array

Similar Messages

Maybe you are looking for