Reinstall Windows on raid array

Hello all,
I have 2 arrays running a 0+1 which windows in installed on and a raid 1 which my games are installed on.
I originally built the array after windows was installed so I didnt have this issue....
I want to reinstall windows on the same array and to do so would be boot from the cd like normal and F6 and install the raid drivers and windows should then see the arrays.  Pick my array to install to and away I go...
Second question I assume running my games/programs from a 0+1 array would work better than the raid 1?
Tell me if I'm missing something.  TIA
K9N platinum sli

Tiresmoke, I think you missed the part where he said RAID0_1 and RAID1.  He has two arrays, the first is RAID0_1 which mirrors stripe sets (see here: http://www.acnc.com/04_01_0_1.html), and the other is RAID1 which is simply a mirror.
That being said, I'm about to try the same thing.  I just bought 3 additional WD Raptor 74GB 10K SATA drives and am doing some basic IOMeter performance testing now before creating a 0+1 set.  Wanted to quantify the performance gain, I'll post it in a new thread when I'm done.
As for your first question, yes, you'd want the latest nVidia RAID drivers on floppy to inject into the install with the F6 key.
For the second question, the performance of a stripe set is superior to that of a mirror set, and a mirrored stripe set beats them both.
Let me explain:
Normal access (non-RAID) would write to one disk.  When reading, it would read from one disk.
On a stripe set (RAID0), you write to multiple disks (doubling, tripling or quadrupling your write performance depending on how many disks 2, 3, or 4), and the same with reads.  But you gain performance, but no redundancy, and in fact increase your risk of failure (any drive dies and you effectively lose all of them).
On a mirror set (RAID1), you write to two disks simultaneously (no performance gain, but failure protection), but you can read from both disks simutaneously thereby doubling your read performance!
On mirrored stripe sets (RAID0_1) you gain the performance gain of the stripe, with the added redundancy of the mirror.  You get 2-factor read performance improvement along with redundancy.  If it were possible to add more disks to it, you could realize even better read performance, but alas you can't use the two Silicon ports in the nVidia RAID set.
That make sense?

Similar Messages

  • Problem Installing 817 on Windows 2000 with RAID Array

    I am having a problem installing Oracle under windows 2000 which has 2 x 60 GB discs configured in RAID array. When I run the setup program the cursor goes busy for about 10 seconds and returns back to normal and nothing happens !. No errors nothing.
    However when I run the Object Manager in the ods_preinstall directory it starts but in the log file I get the following error message:-
    02/14/02 09:46:18 : (892) : Error in IO Control call for disk PhysicalDrive0 (Error 21)
    02/14/02 09:46:19 : (892) : The count = 28
    02/14/02 09:46:19 : (892) : The signature is 0x443aa035
    02/14/02 09:46:19 : (892) : Error: First Partition of the disk must be an extended disk
    02/14/02 09:46:19 : (892) : Found the partition: 7
    Any idea whats happening....? Has anyone seen this before. Do I need to do something special in teh RAID..?
    TIA
    Martin

    Here are some possible solutions:
    1. The installation notes state that you must be logged on as Administrator to be able to install 9i. Are you logged on as the Administrator? Being logged on as user01 with Administrator priviledges isn't the same as Administrator.
    2. Is the disk full? If I remember my installation correctly, I needed 3 times the size of the files. The documentation will tell you how much space you need.
    Hope these two questions help
    Regards,
    Michael

  • [VIA] K7T266 PRO- RU motherboard: Windows XP on a RAID ARRAY (fasttrak100 LITE)

    Hi All!
    I have a
    MSI  K7T266 PRO- RU motherboard, BIOS is the latest, official from MSI website,
    Problem short description: Windows XP (sp1 or sp2 english, I tried both)
    will not install when I set 2 x 40 Gig = ~80 Gig Stripe Array.
    detailed description:
    motherboard K7T266 PRO- RU  BIOS 1.9 AMI BIOS.
    AMD ATHLON XP 1700 + "Palomino" microprocessor, at default speeds.
    one piece of 512 PC 3200 RAM, can tell details later.
    Power supply: 400 W CODEGEN model : 300X.
    HDD-s : one IBM deskstar, fully functional, and a SEAGATE barracuda. seagate SEATOOLS, IBM DFT 32 no errors both.
    I set in the FASTTRAK 100 LITE "PDC20276R" (written on the chip) bios a STRIPE array. Powerquest drive magic , or the Windows XP CD handles it fine , as a 80 gig disk.
    I downloaded ALL available versions of the FASTTAK 100 LITE driver from the MSI website.
    (only tried: MSI driver FASTTRAK 100 lite, the only available driver on the MSI website, and various drivers from www.promise.com) ( http://www.promise.com/support/download/download2_eng.asp?productId=15&category=driver&os=0&go=GO ) (but I guess they WONT support my raid controller on the motherboard)
    Windows XP CD , booting, Press F6 for additional RAID /SCSI drivers, I put in the floppy, choose WinXP fasttrak lite driver, windows continues, even formatting the 80 GIG disk, copy files- access the FASTTRAK.SYS driver, EITHER it says: no fixed disk present, press F3 to exit windows setup, or windows setup continues, copies files, reboots, and then STOP ERROR
    http://www.martin555.dyndns.org/stop.jpg
    please, help me with the following:
    how to install XP on a raid array.
    is it worth, will it be little bit faster disk load times etc?
    is it secure if I trust the HDD-s?
    any clue, how to overclock the AMD 1700+ athlon XP palomino to its maximum, but still stability?
    AND : I read a lot about some MOD-ded BIOS called " KUNIBERT"  , which makes the LITE raid to a FULL RAID and some other extras? where to get it and what to do?
    email me if you can    martin5   "at"   freemail.hu
    THANKS !

    pardon me, dump? my english is not very perfect.. you mean to trow away, replace to something better, more stable power supply, more powerful?
    you must see... first I would like to resolve the "installing XP on a raid array" problem,( how is it possible, is it worth, will it speed up hard disk access and load times... etc... ) and after that maybe I  will OC the machine...
    it is now , with a 8 cm ventillator and a large aluminium cooler 39 Celsius IDLE and goes to 45 Celsius during EVEREST benchmarking test. (temperatures on 1700+ default setting and OC-'d to 1900+. just experiencing with it. ) (I saw the toms hardware guide movie , smoking processors..)
    cheers, Marton.

  • RAID arrays and Windows

    Not sure where to post this one.  You have been very helpful before so I’ll try again.
    The machine is the Media Centre in my signature.
    Installed two new Maxtor SATA drives, set up as RAID 0, clean install of XP MCE. Boots on the RAID array.  Not a single problem. Installed MSI drivers, XFS video card drivers and KCorp PCI network adaptor for wireless link.  Download and install all Windows updates. All OK.
    On a later start up it spends long time trying to detect RAID array, then RAID error. Automatically reboots and detects a healthy raid array. Tries to open Windows but screen goes almost black but faint Windows loading page with the short activity bar showing no activity.  If left it eventually springs to life. Tried starting in safe mode, no problem.  Restore to an earlier restore point, no better.
    The RAID problem is intermittent. The Windows problem looks as if it stalls for a variable length of time before it gets going.
    Don’t know where to go next.  Any suggestions?   

    fafner: I wanted a large disk to hold recorded TV progs, videos, CDs etc and 160GB is the max for this mainboard.  I went for 2x160GB Maxtor drives.  As I was using two drives I reasoned I might as well use RAID 0 to get a single volume and a faster machine.  In particular I read somewhere that RAID 0 halved, or nearly so, the start up time.  Who wants to wait a couple of minutes for the TV to fire up?
    Fredrik:  The XFX video card drivers are in fact nVidia drivers which are the latest.
    Doctor Stu:  I have subsequently installed XP on both drives individually.  On one it worked well, on the other same old problem: either the drive not found in the BIOS after the heading ‘Detect IDE drives’ or the screen fades as Windows starts up.  Checked both drives with Maxtor’s Powermax disk checking utility.  Provided the drive was connected to the SATA1 socket and the other drive not connected both passed the Full Test.  I could not get Powermax to recognise SATA2 even though both were detected correctly in the BIOS.  My conclusion is that the problem was a dodgy connection which I hope has been rectified with all the swapping around.
    Is there disk testing utility that puts the disc under load similar to Mem86 for memory?
    Will I try RAID again?  I doubt it even though it did start up in far less time.
    My thanks to all.   

  • Grub not detecting Windows on RAID 0 array.

    I'm having some trouble with my RAID array. I have tried to research this, but all I can find is how to install Arch Linux ONTO an array, not how to detect Windows on one, and configure grub for it. I have two SSDs in a RAID 0 configuration, which holds my Windows 7 installation. I then have two HDDs in JBOD. One of those HDDs is my mass storage drive for Windows and Linux, the other is my Arch Linux install.
    The problem is that--with os-prober installed--Grub isn't detecting my Windows install. I was trying Fedora when I converted my Windows install to RAID 0, and Fedora picked up on it when I ran grub-mkconfig with os-prober installed. Grub at that point was pointing at /dev/mapper/<some random-seeming string> for Windows, and it worked.
    Now that I'm back "home" to Arch Linux, I am trying to get grub to see Windows, but it never detects it. /dev/mapper/ is empty except for 'control', and /dev contains sda and sdb, which are the drives that are supposed to be in the array. At this point, I'm completely lost.  I'm not even sure if this is software or hardware raid. I thought it to be hardware, because my motherboard has a RAID option rom on it, which is what I used to build the array, but the /dev/mapper stuff makes me think it's software.
    Can anyone at least get me pointed in the right direction?
    Thank you,
    KD0BPV
    Last edited by kd0bpv (2012-12-08 10:25:12)

    Well, I did add ntfs to my initramfs, but it still dropped into an emergency mode terminal. I checked to make sure that it was successful, and the ntfs kernel module was loaded. Any ideas?
    # lsmod | grep ntfs run in emergency shell:
    ntfs 191626 0
    /etc/mkinitcpio.conf:
    # vim:set ft=sh
    # MODULES
    # The following modules are loaded before any boot hooks are
    # run. Advanced users may wish to specify all system modules
    # in this array. For instance:
    # MODULES="piix ide_disk reiserfs"
    MODULES="ext4 ntfs"
    # BINARIES
    # This setting includes any additional binaries a given user may
    # wish into the CPIO image. This is run last, so it may be used to
    # override the actual binaries included by a given hook
    # BINARIES are dependency parsed, so you may safely ignore libraries
    BINARIES=""
    # FILES
    # This setting is similar to BINARIES above, however, files are added
    # as-is and are not parsed in any way. This is useful for config files.
    # Some users may wish to include modprobe.conf for custom module options
    # like so:
    # FILES="/etc/modprobe.d/modprobe.conf"
    FILES=""
    # HOOKS
    # This is the most important setting in this file. The HOOKS control the
    # modules and scripts added to the image, and what happens at boot time.
    # Order is important, and it is recommended that you do not change the
    # order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
    # help on a given hook.
    # 'base' is _required_ unless you know precisely what you are doing.
    # 'udev' is _required_ in order to automatically load modules
    # 'filesystems' is _required_ unless you specify your fs modules in MODULES
    # Examples:
    ## This setup specifies all modules in the MODULES setting above.
    ## No raid, lvm2, or encrypted root is needed.
    # HOOKS="base"
    ## This setup will autodetect all modules for your system and should
    ## work as a sane default
    # HOOKS="base udev autodetect pata scsi sata filesystems"
    ## This is identical to the above, except the old ide subsystem is
    ## used for IDE devices instead of the new pata subsystem.
    # HOOKS="base udev autodetect ide scsi sata filesystems"
    ## This setup will generate a 'full' image which supports most systems.
    ## No autodetection is done.
    # HOOKS="base udev pata scsi sata usb filesystems"
    ## This setup assembles a pata mdadm array with an encrypted root FS.
    ## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
    # HOOKS="base udev pata mdadm encrypt filesystems"
    ## This setup loads an lvm2 volume group on a usb device.
    # HOOKS="base udev usb lvm2 filesystems"
    ## NOTE: If you have /usr on a separate partition, you MUST include the
    # usr, fsck and shutdown hooks.
    HOOKS="base udev autodetect pata scsi sata dmraid filesystems usbinput fsck"
    # COMPRESSION
    # Use this to compress the initramfs image. By default, gzip compression
    # is used. Use 'cat' to create an uncompressed image.
    #COMPRESSION="gzip"
    #COMPRESSION="bzip2"
    #COMPRESSION="lzma"
    #COMPRESSION="xz"
    #COMPRESSION="lzop"
    # COMPRESSION_OPTIONS
    # Additional options for the compressor
    #COMPRESSION_OPTIONS=""
    The systemd journal is still showing the same errors I posted earlier.

  • Windows Vista + nVidia i680 MB + RAID5 + iTunes 7.3.2 = RAID array trouble

    Dunno if any of you can help out with this but I'm at witt's end over this issue.
    I have a Windows Vista box running an Abit In9-32MAX motherboard (nVidia i680 chipset), four drives in a RAID 5 array and using iTunes 7.3.2
    Drivers for the motherboard are the most recent ones from the nVidia site. BIOS for motherboard is also current.
    Practically ANY time I import any audio or video file over 50 MB into iTunes the entire RAID array will degrade. I'm also having issues transcoding video into Quicktime using Videora which seems to be related to this issue. The video simply refuses to play.
    For what it's worth the video/audio content is legit. I own the DVD's that I'm transcoding so I can watch them when I travel.
    Any thoughts, ideas, suggestions, etc appreciated. I'd love to go a whole week without iTunes/Quicktime forcing me to rebuild the RAID array.

    Well, whatever Itunes/quicktime does, it's definitely causing some sort of RAID compatibility. I've had this problem since I got my new rig a month ago. Nvidia 680i SLI board with a RAID 1, and I have it working fine (I've done 3 system restores now) and then I install itunes, and kablooie, there goes the RAID. I can also tell you that even if you disable the mediashield program (NVRAID.exe), it will still happen (this was my last experiment in trying to make it work) and the raid will show up degraded in the BIOS.
    Basically, Apple and Nvidia need to exchange a freaking phone call and try and figure out what is causing it to go bad. from reading around, it's not just apple (though they are the biggest culprit). I've seen people mention bittorrent and some other program whose name escapes me at the moment cause this as well (digital imaging program I think).

  • 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

  • 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.
     

  • RAID array became drive F: instead of C:

    Hm... when installing Win XP new on my new system, the RAID array (which is bootable and has the op.system) became drive F: and my ZIP drive is now drive C:  8o
    It wouldn't bother me too much, but some software insists on being de-compressed to C: during installation - good thing that not one of my CD-ROMs became drive C: , lol
    Any way to change the drive assignment so that the array would become C: ?
    On my earlier K7T266Pro2-RU, I had no such phenomenon  ?(

    changing it is childs play, however you cant do it.
    first ill tell you how, then ill tell you why you can't.
    ok, goto control panel, then administrator options, then computer management, then select Disk Management
    Down on the left hand side at the bottom you should see your disks and Cd drives etc with there current letters, right click and slect new letter, but you can use a letter already in use, so the one on C or D you want to use, change first to H or whatever, then change the one thats wrong to what it should be and then change back your drive to C or D or what you want it to be.
    But, why can't you change it?
    Because all the root paths for windows will be pointing to F:\ and if you change to C:\ you may well find gods unholy mess on boot up. Thats if it even boots up.
    Way to do this is boot PC with only CD and hard disk on, when XP is all happy make sure letters are ok, and then start adding devices and changing letters.
    When all service packs and updates installed and win XP totally happy, at that point i suggest doing the activation, not before, incase something goes wrong and you need to reinstall.
    hope that helped..

  • K9A Platinum - Not seeing RAID Array on restart...

    Hello again guys...
    Here's the deal...
    The computer will not recognize the RAID array when I choose to restart from inside Windows. If I press the reset on the computer or I do a shutdown then reboot, it works fine. Also, this morning I finished a clean install of Vista 64 and forgot to turn off sleep mode like I normally do, and when I came back home I got a tasty blue screen. When I tired to restart I got a message stating that the RAID driver was corrupt or missing. I reloaded Vista again, but I still have the issue of the machine not seeing the RAID array upon restart, and I have tried this about 10 times with the same results.
    Restart = No Recognized RAID Array.
    Cold Boot, Reset Switch or CTRL+ALT+DEL = No problems.
    My system specs are in my sig below.
    There was one other tidbit, I had a problem with this motherboard failing to load Windows with 4GB of RAM installed when I first got her, and thru this forum and the MSI help center, it was suggested I update my BIOS to a beta version that was out at the time. I see now that the version is now a standard release v1.6, should I go to the release BIOS or just stay with the current one?
    Thanks for your time! 

    Yes I can.  I first installed XP Pro since I was testing system stability with my new 6000+.  Every soft reboot results in the array being undefined.  I have to wait until the controller scans and says there is no array, then I can reset it to make it see the arrays.  If I reset before the controller scans, it still shows no arrays.
    Vista 64 Ultimate will only install on my K9A platinum if the following is true:
    1) The SATA controller is in RAID mode, I have 4 SATA HD's, none are striped, and my DVD is external
    2) The desired HD/array must be the first boot device, if the DVD is first it will refuse to recognize the partition as valid to use
    If I use Native IDE or AHCI mode, Vista doesn't see any partitions.  If I use Legacy IDE mode, Vista will start the install, but on reboot the motherboard pauses for 5 minutes and tells me the HD has an error and I have to hit F1 to continue.
    I only recently got  Vista 64 Ultimate stable again.  I was having a problem where the system would power off instantly when it reached the desktop.  I replaced the power supply.  I then had trouble getting the drivers installed without crashing the OS.  One thing I noticed while reinstalling Vista is that Microsoft automatically updates the driver for the RAID Controller. The driver version is 2.5.1540.41 and the version that the ATI 7.6. and 7.7 want to install in 2.5.1540.36. That would put it out of sync with the ATI RAID Console driver.  The next reboot would result in crashing.  Can't prove that is why though.

  • Boot problems from RAID Array

    I have recently reinstalled my system (K7N2G-ILSR).
    It was working fine with a RAID array to boot (set to boot from SCSI in Bios).
    The RAID array is 1 SATA drive with 1 IDE on IDE3.
    I have 2 additional IDE HDDs and 2 Optical Drives (On IDE1&2).
    I also have a SCSI controller with one external drive.
    While reinstalling I had problems in the windows installer - after partitioning and copying files it would try to reboot, and would then come up NTLDR missing.
    I initially thought it must be some confusion with my external SCSI drive trying to boot, but removing made no odds.
    I ultimately had to unplug all my non raid HDDs, and it would then boot no problem at all.  Unfortunately having got it working, every time I try to plug any IDE HDD back in, it goes back to NTLDR Missing on boot (this is despite boot being set to SCSI in bios, IDE isnt even later in the boot sequence!)
    I need to be able to reconnect my drives, but cant find anything comparable in the forum.
    Why does it matter if I connect an IDE drive at all when it is set to boot from SCSI (RAID)?  Is my bios corrupt or something?
    Thanks for any help!
    Martyn

    Thanks Noby and Richard for the advice, and sorry I have been slow to read it - I've been away.
    I'm not sure I didn't do my last installation in exactly the way you describe anyway.  Still, it's probably worth another go.  
    I was hoping for an easy solution without reinstalling yet again, since the system is working albeit with only the RAID array connected.
    Assuming the other drives do now have an MBR written to them, even if I reinstall windows without them connected, will they not still cause problems when reconnected?  
    Am I looking at having to wipe the drives and start again with them too?  
    Even if I do this, does formatting a drive wipe any MBR on it?  
    Is there not some way to directly edit the boot record on each drive when windows installer doesn't figure it out right?
    Sorry for the multitude of questions but I have had this problem time and time again and never found a reliable solution - last time it seemed simple chance that I ever got the board working!
    Thanks again
    Martyn

  • Is It Possible to Clone RAID Array in a Safe and Easy Way?

    Why do computer users need to clone RAID array, especially Windows Server users need to do RAID cloning? Generally speaking, they need to clone RAID array regularly in order to upgrade disk or migrate data from small disk to a larger one. A typical
    example is that when the partitions on the hardware RAID runs out of space, you may prefer to rebuild the hardware RAID with larger hard disks. Then, you need to backup the data to another place, rebuild the hardware RAID and restore data again.
    What a time-consuming task!
    Is it possible to clone RAID array in a safe and easy way? The answer is yes and this article will introduce a RAID cloning software.

    Hi jiangchunli,
    Were you looking to post this question in some other forum? This looks like related to RAID and Disk upgrades.
    This forum is meant for
    http://www.windowsazure.com/en-us/services/recovery-manager/
    Please let us know if this is indeed Hyper-V Recovery Manager related so we can help better.
    Thanks
    Praveen
    Praveen/ www.PraveenKumar.in

  • Raid array removed, hard drives now wont work?? help

    Hi all,
    I had a KT266 pro2RU motherobard with 2 ibm 40gig hard drives that were in raid mode 0,
    I took the 2 drives out of the computer and wanted to use one of them in another computer on a standard drive controller (single drive not raid) and i cant seem to access the disk to format it or install windows xp on it?, it keeps saying write access denied?,
    I am thinking that i should have unmounted? the raid array before taking the drives out to put them back to normal but dont have the raid system any more, is there any way i can make these 2 40 gig drives work now?, or has it overwritten the HD bios or something?
    If anyone can help i'd appreciate it
    Cheers

    i would try fdisk on it or partition magic if you have that
    http://www.bootdisk.com will get you an me boot disk has f disk

  • RAID Arrays and WinXP Home

    OK... I tried upgrading to Win XP 64-bit, but found there were games and applications that were screwy there and some items without 64-bit drivers, etc.  So, I rolled back to a clean install of XP Home (32-bit).
    After much effort, I was told today at a local techie-store that XP Home "doesn't allow for RAID arrays."
    True?
    I have 2 Hitachi 160GB drives I got last week at the afore-mentioned store for $112 US total!  So, I am trying to make it all work, but am having no luck.
    Any thoughts?
    Scott in Los Angeles

    There is a way to make some versions of windows do a software RAID, but the MSI board has a VIA and a Promise hardware array. Don't worry about what the 'techie' said.
    Enable Promise controller in BIOS and set it for RAID.
    Press Ctrl & F when prompted to set up your RAID array.
    Boot to Windows CD
    Press F6 when prompted and insert your Promise RAID disk.
    Enjoy!

Maybe you are looking for

  • How do I randomize a playlist order in iTunes 11.0.1.12?

    I recently updated my computer software (iTunes included, obviously) and have come to realize that this new version does not give me the abilities that the previous versions have.  I wiped my iPod clean to start from scratch, as it was full and I was

  • Material download issue

    Hello Experts, I am facing typical material download issue, please help me out to overcome this: - material number in ERP has lot of speical characters say e.g. - : = - DNL_CUST_PROD0 / PROD1 / PROD 3 / TAX all has bee done - Materials are already do

  • Authorizations: restrictions for InfoObjects and InfoProvider

    Hi Gurus, I am trying to define authorizations via RSECADMIN in 7.0 for a specific InfoObject and specific InfoProviders. The situation is: I want user USER1 to see only Company 4360 on Cube 'XXXXX', but he must be able to see all the Companies in al

  • How can I activate my apple ID without credit card?

    how can I activate my apple ID without credit card? the "none" option is not shown for me in billing info part

  • Installing Latest 10.5.1 Update doesn't work.

    When I try to install the latest update for Leopard, it won't go through with the installation. It says: The installer could not validate the contents of the MacOSXUpd10.5.1 package. When I download the package and try to mount the disk, it gives me