Using IDE3 in non-RAID setup

Hi
I have a few questions regarding my setup which I hope some users who have or have had the same configuration can answer for me?  I know that this post may turn out to be a bit long but I really would appreciate some help and answers from users who have been down this road please.
System:
MSI 875P Neo FIS2R (no overclocking)
Intel 2.40C Ghz P4 (800Mhz)
BIOS 1.7
Nvidia FX5200 AGP 8x
LG CDRW on IDE1 (Master)
LG DVD on IDE1 (Slave)
IDE2 - Nothing installed
Maxtor 20GB ATA133 on IDE3 (Master - Non-RAID)
Maxtor 80GB ATA133 on IDE3 (Slave)
With thanks to "mdc007", I have just setup my two Maxtor drives which were previously installed on IDE1, on IDE3 as master and slave, using the following method:
Enabled Promise controller in BIOS, setup Promise IDE "as S-ATA", boot into XP, install S-ATA drivers from Device Manager and reboot.  Made sure drivers were installed.  Turned off computerm connected Maxtor hard drives to IDE3 and turn on computer.  enter BIOS and select Maxtor master drive as first boot device and then F10 to save and exit.
Everything worked just fine but I noticed on the POST screen that I had 1st IDE master/slave (CDRW/DVD), 2nd IDE master/slave (not installed), 3rd IDE master/slave (not installed), 4th IDE master/slave.
The drives on IDE3 are shown in Device Manager and I have a SCSI RAID Promise 378 S-ATA in Device Manager.  The drives also appear to be opering correctly in XP.
Q:  As my hard drives are on IDE3, why are they not shown on the POST screen?
(Note - both drives were shown on the next screen with UDMA6)
Q:  Also in the mainboard BIOS, the drives are not shown connected to IDE3.  Why?  I tried choosing "AUTO" but that made no difference.
Q:  With reference to the HDD LED, I was aware that the LED did not work with S-ATA drives on the Promise Controller at the moment but, although the HDD LED is on during POST, it shows no activity when booting into to XP or once on the desktop.  Is this correct?
Q:  With reference to the Intel IAA and IAA RAID latest software versions, I tried installing these and got a message which said something like "no compatible devices - software not supported on this chipset".  Has anyone got this software to install or am I installing the incorrect version?
Q:  I downloaded the correct version of IAA and I can't understand why it won't install so, which chipset is the message referring to?
Q:  I have seen mention of the Intel 82801EB Ultra ATA Storage Controller, which my 875P has, and also the Intel 82801ER.  Which board has the 82801ER?
Q:  With reference to the "On chip ATA(s) Operate Mode" in the BIOS, with my setup as shown above, I would appreciate advice from users who have this setup working ok, about which options are best to enable/disable in this area:
* Mode:  Legacy or Native?
* ATA Configuration:  Disabled/P-ATA only/S-ATA only/P-ATA + S-ATA/Both
* S-ATA Keep  enabled: Yes/No
* P-ATA Keep enabled:  Yes/No?
* P-ATA Channel Selection:  Primary/Secondary/Both?
* Combined Mode Option:  P-ATA 1st Channel/S-ATA st Channel?
  (this option depends on what other options you have choen above)
* S-ATA Ports Definition:  PO-1st / P1-2nd - PO-2nd / P1-1st
                                      PO-3rd / P1-4th - PO-4th / P1-3rd
  (this option also depends on what other options you have chsoen above)
Q:  With reference to PNP/PNP Configuration Option in the BIOS, with my new setup, should PCI IDE Bus Mastering be enabled?
BTW, about an hour after running my drives from IDE, I attempted to install the new drivers for the WinXP Promise SATA378 IDE Controller (from v1.00.16 to v1.00.29) and after reboot, the pc just kept rebooting and i had to choose "last known good configuration" and then once in windows, I got my first 'blue screen' with a message something like "IRQ less or equal to" etc, etc.  Don't know if that relevant or not?
Regards

To answer a few of your questions,
Reason you can't see the devices on the Promise controller in the Bios is because the Promise controller has its own separate Bios(that's the one you get into by hitting control-F. The only link the main Bios has to it is the 1 setting(disabled, SATA, Raid). Also, you'll see the Promise devices listed in the boot devices setting although with unusual prefixes like "BBS Device 0" or something like that.
Note that the 1st-4th channels listed in the standard Cmos Features are for the Intel controller only(IE: 2IDE channels + 2SATA channels)
I know that the HDD light DOES NOT work for ANY SATA devices. I haven't used my IDE3 yet but it sounds like it doesn't work for that either. As far as I know, there is no work-around for this. Unbelievable, isn't it?
For your setup:
Native Mode for WinXP
Pata Only (you're not using the SATA's)
Keep SATA enabled: Yes(only if you are overclocking and can't lock AGP/PCI frequency. Don't know why, but this has worked for many of us.)
Pata enabled should be greyed out with above settings.
Pata channels: Just primary if that's all you're using but "both" would work too.
Combined Mode: greyed out
SATA ports def: greyed out or leave default.
Not 100% sure on your other questions but I think IAA is not required on this board and IAA-Raid version will only install if you have the controller configured for Raid in the Bios. I don't think you need either with your setup. I don't have either installed atm.
I'm not sure of the difference between the 82801EB & ER but device manager lists all the 82801EB devices for me and everything seems fine.
Hope that helps out a little.
Didn't see Danny's post above when I wrote this but I pretty much agree with everything. I have Bus Mastering on but only because it sounded like a good thing   and everything seems fine with it on. (I think I read somewhere that it speed up data transfers when you're running in DOS-IE: Booting Ghost or Drive Image etc off the CD/Floppy). Never really tested though.  

Similar Messages

  • K7N2-ISLR, IDE3 for non-RAID HDD

    Hello,
    Can I use IDE3 to support a non-RAID drive? If so, how do I set this up.
    IDE1 has two 40 GB drives
    IDE2 has CD-RW and DVD
    I'd like to add a Maxtor 120 GB drive, but can't figure out how to set it up.
    Any help would be appreciated...b

    Using IDE3 requires you to set it up as a raid device, but it's not a problem. Just connect the drive, boot up, press F1 when it asks to configure for RAID, and use RAID 0. It'll work just fine there.

  • Using Disk Utility for RAID setup?

    I just purchased 2 1TB Seagate Hard Drives 32mb cache 7200prm that I want to setup a RAID 0 (striping I believe) for Final Cut Pro for rendering. Well I also have a 3rd drive that is identical, question is does more drives in that RAID setup mean faster performance? 2 drives vs 3 or 4, etc.? Also what do you think that actual difference in reading and writing would be approximately?

    You can find the max sustained, the average I/O, and minimum. From reviews and Seagate product spec details. There is some overhead for each drive as you seek and assemble the parts of a file.
    The burst rate of the drive is likely around 135MB and average of the outer half a solid 100MB/sec.
    The bandwidth in the Mac Pro totals 1GB for all drives, even though each is supposed to have 3Gbps.
    SSDs are fast catching on for speed and fast system drives, even in stripe raid.
    Don't mix 7200.12 with .11s or even different model/series/firmware. And Seagate has had its hands full with firmware issues for years, going back to the intro of SATA actually.
    If you want one large volume and if having 200MB/sec matters or helps, you might want to RAID, even partition each drive first to 3/4 level and stripe that 3/4 together to guarantee 200MB/sec range.
    But experiment for a couple weeks first.

  • Audigy 1 & Audigy 2 ZS Linked to RAID Setup Probl

    It would seem Creative's Audigy and also Audigy 2 ZS sound cards produce unwanted sound problems with RAID setu
    ps.
    Specifically, my testing was done on an onboard Promise 378 RAID 0 setup.
    The following setup was configured:
    Windows XP (Tested both Home & Pro)
    Intel Pentium 3.4C Ghz HT 800FSB
    2GB Corsair TWINX PC3200
    ASUS P4C800 Deluxe
    2xWestern Digital 60GB Caviar's Special Edition 8MB Cache in RAID 0
    Onboard Promise RAID Controller Fasttrak 378 (old and newest drivers tested)
    Creative Sound Blaster Audigy MP3+ Retail & Creative Sound Blaster Audigy 2 ZS Retail (all available drivers tested)
    The sound problems are heavily distorted sounds, cracks, cut-outs, and hissing when any type of audio is playing and is especially apparent with using the hard dri'ves.
    The standard <EM>Intel </EM>based Non-RAID configuration contains <EM>zero </EM>problems with <EM>any </EM>sound. It is only when users are using RAID that these problems occur.
    It would definitely be in Creative's best interest to investigate this issue and resolve a solution. This problem has been around for a long time, with no support from Creative.
    Please note, the onboard sound audio was tested with RAID setups and non-RAID setups and there were never any sound problems with either. All available PCI slots were tested and various PCI Latency configurations were tested within the BIOS. No solution was found.

    terror_adagio wrote:
    It would seem Creative's Audigy and also Audigy 2 ZS sound cards produce unwanted sound problems with RAID setu
    ps.
    Specifically, my testing was done on an onboard Promise 378 RAID 0 setup. The following setup was configured:Windows XP (Tested both Home & Pro)Intel Pentium 3.4C Ghz HT 800FSB2GB Corsair TWINX PC3200ASUS P4C800 Deluxe2xWestern Digital 60GB Caviar's Special Edition 8MB Cache in RAID 0Onboard Promise RAID Controller Fasttrak 378 (old and newest drivers tested)Creative Sound Blaster Audigy MP3+ Retail & Creative Sound Blaster Audigy 2 ZS Retail (all available drivers tested)The sound problems are heavily distorted sounds, cracks, cut-outs, and hissing when any type of audio is playing and is especially apparent with using the hard dri'ves.The standard <EM>Intel </EM>based Non-RAID configuration contains <EM>zero </EM>problems with <EM>any </EM>sound. It is only when users are using RAID that these problems occur. It would definitely be in Creative's best interest to investigate this issue and resolve a solution. This problem has been around for a long time, with no support from Creative.Please note, the onboard sound audio was tested with RAID setups and non-RAID setups and there were never any sound problems with either. All available PCI slots were tested and various PCI Latency configurations were tested within the BIOS. No solution was found.
    Hi, have you find a solution?
    I try to disable the Promise PDC20378 controller and the problem seems disappeared.

  • What RAID Setup do you use for your Macbook Pro Scratch Drive?

    Is there any benefit to using an Express-ESata Raid Enclosure vs a single esata drive as the scratch drive?
    If so, is there any benefit to using a 4 drive Raid 0 vs a 2 drive raid 0?
    What Raid setups are any of you all using with your MacBook Pro's? Is there a significant performance difference between using a E-Sata drive and a FW800 drive. Is RAID the right way to go?
    Sorry I'm not making a lot of sense right now, but I've searched through 20 or so pages of the forum and didn't see that anyone had addressed this question yet.

    OK, just to give you a frame of reference, I just performed the following tests -
    I hooked up my Sony AVCHD camera to my Mac Book Pro 2.4 ghz with 4 GB ram - (pretty close configuration to yours) - and imported a 26 second clip into FCP 7 with the following drive configurations:
    Capture to internal Mac Drive, no externals: 26 Second clip takes 44 seconds
    Capture to external WD USB2 drive: 26 Second clip takes 44 Seconds
    Capture to external CalDigit 2 Sata Drive Array, Raid 0, via Firewire 800: 26 Second clip takes 42 seconds
    OK, so now I move the camera over to my Mac Pro 8-Core, 2 x 3.2 Ghz Quad Core Xeon with 14 gigs of ram, and capture *to the same external CalDigit 2 Sata Drive Array,* Raid 0, via Firewire 800: 26 Second clip takes 11 seconds
    My conclusion would be the drives and drive throughput is not as consequential as the CPU horsepower in doing the conversion from AVCHD to Pro Res. However, there are many very knowledgeable people who look at these threads, and I would be interested to hear what they have to say.
    Hope this helps.
    Message was edited by: Meg The Dog to correct typo

  • Raid Setup Guide 865/875 LSR/FIS2R Rev 1.04

    On-Board Raid Setup MSI 865PE/875P
    Revision History
    Revision 1.0 (January 2004)
    -   Original Raid Article
    Revision 1.01 (February 2004)
    -   Reformatted text and fixed spelling/grammar
    Revision 1.02 (October 2004)
    -   Added warnings to temporarily disconnect ALL drives including Zip drives during formatting Raid drives for WinXP.
    Revision 1.03 (October 2005)
    -   Reformatted text and added links to download Promise/Intel Raid floppies if user is missing them.
    Revision1.04 (February 2006)
    -   Minor BB reformatting
    Intro
    Equipment List For Tests
    Description of Tests
    Pre-Raid Setup Bios Tweaks
    Raid Setup On Promise Controller
    Raid Setup On Intel Controller
    --->Intel- Migrating from single SATA to Full Raid Array
    Intro
    This guide is intended to help people configure their Bios and setup Windows for Raid using the Intel ICH5R controller  and the Promise FastTrak 378 controller. Although all the tests were done using Raid-0 the methods described should be virtually identical to setting up Raid-1 provided the user is aware of the fundamental differences between the two. It should be useful for anyone with an MSI 865PE/875P chipset on motherboards with LSR and FIS2R suffixes. Before continuing, please read the FAQ thread posted by Maesus and the Raid manual(s) that came with your motherboard. There's also some good info regarding Raid Here and Here and Here
    Keep in mind this guide is intended as a reference to help you. It is not a manual. I do not work for MSI and my equipment and time are limited. You will have different equipment and different versions of software.
    All the data below is based on tests that I ran and I tried to avoid using any theory that I did not test. If you feel I’ve missed something obvious or if you have something you feel should be added to make this guide clearer or simpler, please PM me with your thoughts. If you have a specific problem that this guide does not help you with, post a detailed thread in the forum on the main page.
    Equipment List For Tests
    MSI 875P FIS2R Motherboard
    Bios 1.8
    Enermax EG365P-VE (350w)  PSU
    P4 2.6c CPU
    Kingston KHX-3200A2 2x512MB Memory
    Radeon 9800Pro AIW Video Card
    WD 400JB 40GB/8MB cache IDE Hdd
    2-Seagate 80GB 7200.7 SATA Hdd's
    Liteon 52x32x52 CDRW
    Floppy Drive
    Tests
    Generally, tests were as follows:
    Configure 2 SATA on Promise controller(serial3&4) as Raid0 and install WindowsXP Home SP1a on Raid
    Configure 2 SATA on Promise controller(serial3&4) as Raid0 and add Raid to an existing WindowsXP installation on IDE drive(IDE1)
    Configure 2 SATA on Intel Raid controller(serial1&2) as Raid0 and install WindowsXP Home SP1a on Raid
    Configure 2 SATA on Intel Raid controller(serial1&2) as Raid0 and add Raid to an existing WindowsXP installation on IDE drive(IDE1)
    Configure 1 SATA on Intel Raid controller(serial1) and install WindowsXP Home SP1a on it. Then add 2nd SATA on Intel Raid controller(serial2) and migrate to Raid0 using Intel Application Accelerator-Raid edition.
    IDE drive used in these tests was pre-installed with a fresh copy of WinXP Home SP1a using default settings and the following drivers all from MSI setup CD and Raid Floppy Disks that came with motherboard:
    Intel INF files - version 1002
    Gigabit Lan drivers - 7.0.37.0
    SoundMax drivers - 5.12.1.3538
    Catalyst 3.7 & Multimedia Center drivers from standard ATI CD came with video card.
    Pre-Raid BIOS Tweaks
    Before I continue, I'd like to point out a few changes from the defaults that I alway make to Bios before I attempt a WinXP install or hardware change. I can't guarantee that they all apply to you but none should make things worse. If anything differs from a setting that you feel is fixing another problem you're having, by all means leave at your prefferred setting. Anything related to performance and overclocking can be raised again AFTER the Raid is all setup and everything is running smoothly.
    Standard Cmos Features
    The only thing I change here is to enable "32bit transfer mode" whenever I connect new devices to the Intel IDE controller.
    Note: Devices attached to the Promise controller and the Intel Raid(when it is enabled) will NOT appear in the standard Cmos page
    Advanced Bios Features
    Everything on defaults is usually fine except I always change the following for WinXP:
    APIC ACPI SCI IRQ - Enabled
    Boot Device select is also on this page and you'll be changing it after all the hardware is setup; more later.
    Advanced Cipset Features
    Confirm that the memory timing "by SPD" is enabled
    PNP/PCI Configurations
    Clear NVRam option I always set to "YES" before the first boot after making hardware changes. I'm not sure how important this is but I understand that's what you're supposed to do. I believe it forces the motherboard to detect hardware changes. It reverts to "NO" after the reboot.
    PCI/IDE Busmaster set to "enabled" to speed things up outside of Windows.
    Integrated Peripherals (Before Raid for most flexibilty)
    Onboard Promise IDE - Disabled if you have nothing attached to IDE3 and Serial 3&4
    ON-Chip IDE Configuration:
    Native Mode (Supported by WinXP- Allows all devices connected to IDE 1&2 and Serial 1&2 to be detected)
    SATA Only or PATA Only (select the one that you boot XP with)
    Keep SATA Active - Yes (if option available)
    Keep PATA Active - Yes (if option available)
    PATA Channel selection - Both (if option available)
    Configure SATA as Raid - No (if option available)
    Leave other settings here at default
    Note: Some older Bios versions may appear different than above
    Frequency/Voltage Control
    Dynamic Overclocking - Disabled
    Performance Mode - Slow
    Dram Frequency - Auto
    Adjust CPU Bus - 201 (for "c" type cpu's)
    DDR Voltage - 2.65 (minimum for Dual-Channel Mem stability)
    AGP Voltage - 1.55
    Note: some features above may not appear with your Bios
    Note: performance & overclocking features can be increased again AFTER the Raid array has been setup and is stable with Windows.
    Raid On Promise Controller
       This procedure should work for anyone adding a Raid array to a system already having XP installed on another drive on the Intel controller or intending to install Windows XP on the new Raid array.
    Note: IDE 3 and Serial 3&4 connectors are controlled by the Promise controller.
    Note: It is possible to setup Raid arrays using 2 IDE drives on IDE3 or even 2 SATA & 2 IDE drives. I only tested 2 SATA drives on Serial 3&4 connectors.
    Note: It is possible to setup Raid 0+1 using 2 IDE drives on IDE3 and 2 SATA drives on Serial 3&4. See HERE for a related thread.
    Note: It is possible to setup SATA or IDE drives on the Promise controller as separate drives NOT using Raid but I did not test this. See your manual.
    - Attach the SATA drives to Serial 3&4 connectors and ensure that both power and data cables are securely connected. Most SATA drives do NOT need any changes to default jumper positions if any(check Hdd installation instructions).
    - Boot into Bios
    Integrated Peripherals:
    Set Onboard Promise IDE  - As Raid
    - Save and reboot computer
    - Use control-F keys during the boot(when prompted-goes by quickly) to enter the Promise Raid Bios.
    Note: You will only be able to enter the promise Bios if you have set the Promise controller to "As Raid" AND there are devices connected and detected by the Promise Bios.
    - Use the menus to configure the Raid for your preferences.
    Note: I can't say which settings you should use for creating the Raid. It depends on many things. Do some research.
    - After saving the Raid array, reboot to Bios.(you should see the configured array for a second or two during the post and it should be "functional")
    - In Advanced bios Features>>Boot Device Select:
    Set the order you prefer to boot from
    - If you already have XP installed on another drive and are just adding the Raid for an extra drive, Ensure that the list is still appropriate and includes your XP drive.
    - If you will be installing XP on the new Raid, make sure the new Raid array is in the boot list and any other hard drives are NOT.
    Note: Typically, I put the disk with XP first and use F11 key during post to boot from another device. This is not required though.
    - Save bios
    Important!: If you are installing XP on the new Raid array, you should now shutdown and either disconnect or disable any other drives connected until AFTER XP is installed. This includes USB/Zip drives.(See "Bugs" below).
    If Installing XP On The New Raid Array(others skip to below):
    - Boot from the Windows XP Setup CD and use F6 key when prompted(at the beginning).
    - Follow prompts to load the WinXP Promise FastTrack 376/378 Controller from the floppy that came with motherboard(If Required Download Floppy Here). There are a number of different choices on the floppy. PICK THE RIGHT ONE.
    Note: if using Win2K with the floppy, you can scroll down to get more driver options on this screen. It's not readily apparent on the screen.
    - Continue setup and Windows should now show you the new Raid array as a single drive available to install to. If it shows other drives that you have connected, re-read the "important" note above and the related section on "Bugs" below.
    - When XP setup makes its first re-boot, make sure the floppy has been removed or depending on your settings it may give you a scary moment. Yes I did this(tries to boot from floppy).
    - After XP is up and running, you can re-connect/re-enable any drives you disconnected earlier. If they have been formatted, they should show up immediately and be assigned letters after your CD/DVD drives.
    - You can also install the Promise Array Manager software(from MSI CD utilities tab or download) which adds some array management settings.
    If XP Already Installed On Another Drive(and you're just adding the Raid as an extra storage disk):
    - Boot into WindowsXP.
    - As Windows starts, it should detect a new Raid device and offer to install drivers.   
    - Select Cancel. It will tell you that it was unable to install new device. If you want you can confirm the new device is present by checking Windows device Manager. It should show the new device with a yellow exclamation mark beside it since the drivers aren't installed yet.
    - Download the appropriate drivers or use the MSI CD that came with motherboard.
    Note: The MSI CD detects devices connected and shows available drivers/utilities depending on what it sees. You might not have seen the Promise drivers when using the CD before but now that you have a Raid array connected to it, the drivers will be availble from the MSI setup CD.
    - Install the drivers and re-boot
    - Device Manager should now show the Raid properly identified by XP.
    - If the Raid array was not previously formatted, you can now use Windows Disk Manager (Start > Run and type diskmgmt.msc) to Initialize and then format the Raid array.
    - The Raid array should now show in Windows Explorer with it's own drive letter.
    Bugs/Surprises
    - Trying to install WinXP on the Promise Raid while my IDE drive was connected to the Intel IDE connector resulted in Windows installing boot files to the IDE drive and the rest on the Raid drives. This was especially bad since I had another installation of XP on the IDE drive which was overwritten. The work-around was to disable the IDE drive until AFTER XP was setup on the Raid array.
    Update: There have been a few posts on the forum since I wrote this guide where people installing XP have had problems similar to the one above with USB/Zip drives connected so i am adding them to the list of drives to disconnect while installing XP.
    - When setting "Boot Device Select", if I selected "NO" for "boot from other devices", the motherboard would ignore my selection and still boot from other devices if the ones in the list were unusable.
    - Be gentle with SATA connectors on the motherboard. They can stand firm downward pressure but not a lot of side-to-side pressure.
    Raid On Intel Controller
    This procedure should work for anyone adding 2 SATA hard drives for a Raid array on a system already having XP installed on another drive or intending to install XP on the new Raid array.
    Note: IDE 1&2 and Serial 1&2 connectors are controlled by the Intel ICH5R controller. Only Serial 1&2 can be configured for Raid arrays.
    You can also install a single SATA drive and configure the system for Raid BEFORE installing XP on this drive if you intend to add another SATA drive later to form a Raid array. This method was also tested. I will refer to this for the rest of the thread as the Raid-Ready Method.
    Note: If you install WinXP on a single SATA drive without enabling Raid and loading Raid drivers, you will NOT be able to migrate the XP disk to a Raid array at a later date. Reinstalling XP would be required.
    Note: There is no performance advantage to having a single drive with Raid enabled. But doing so makes the disk Raid-ready and XP reinstall unnecessary.
    - Attach the SATA drive(s) to Serial 1&2 connectors and ensure that both power and data cables are securely connected. Most SATA drives do NOT need any changes to default jumper positions if any(check Hdd installation instructions).
    - Boot into Bios
    - In "Integrated Peripherals>>On-Chip IDE Configuration" set:
    Native Mode (Supported by WinXP- Allows all devices connected to IDE 1&2 and Serial 1&2 to be detected)
    SATA Only (Even if you will be booting XP from a PATA drive)
    Keep PATA Active - Yes
    PATA Channel selection - Both
    Configure SATA as Raid - Yes
    Leave other settings here at default
    Note: Some older Bios versions may appear different than above.
    - Save Bios and reboot computer
    - Use control-I keys during post(when prompted-goes by quickly) to enter the Intel Raid Bios Utility.
    Note: If you are using the single SATA Raid-Ready Method, you can skip the steps involving the Intel Raid utility. Go to the step for setting Boot device select in main Bios.
    Note: You will only be able to enter the Intel Raid Bios if you have set the "Configure SATA as Raid" option to "YES"  AND there are devices connected and detected by the Intel Raid Bios.
    - Use the menus to configure the Raid for your preferences.
    Note: I can't say which settings you should use for creating the Raid. It depends on many things. The Intel utility does describe the different options well though.
    - After saving the Raid array, reboot to Bios.(you should see the configured array for a second or two during the post and it should be "functional")
    - In Advanced bios Features>>Boot Device Select:
    Set the order you prefer to boot from;
    If you already have XP installed on another drive and are just adding the Raid for an extra drive, Ensure that the list is still appropriate and includes your XP drive.
    If you will be installing XP on the new Raid or using Raid-Ready Method, make sure the new Raid array or raid-ready drive is in the boot list and any other hard drives are NOT.
    Note: Typically, I put the disk with XP first and use F11 key during post to boot from another device. This is not required though.
    - Save bios
    Important!: If you are installing XP on the new Raid array or using the Raid-Ready Method, you should now shutdown and either disconnect or disable any other hard drives connected until AFTER XP is installed. This includes Zip/USB drives. (See "Bugs" below).
    If Installing XP On The New Raid Array Or Using Raid-Ready Method(others skip to below):
    - Boot from the Windows XP Setup CD and use F6 key when prompted(at the beginning).
    - Follow prompts to load the IAA Raid Driver for ICH5R (If Required Download Floppy Here) from the floppy that came with motherboard.  I only had 1 driver to choose from on my floppy but if you have more, CHOOSE THE RIGHT ONE!
    - Continue and Windows Setup should now show you the new Raid array or Raid Ready drive as a single drive available to install to. If it shows other drives that you have connected, re-read the "important" note above and the related section on "Bugs" below.
    - When XP setup makes its first re-boot, make sure the floppy has been removed or depending on your settings it may give you a scary moment. Yes I did this(tries to boot from floppy).
    - After XP is up and running and INF files and other important drivers installed, you can re-connect/re-enable any hard drives you disconnected earlier. If they have been formatted, they should show up immediately and be assigned letters after your CD/DVD drives.
    - You can also install the Intel IAA-Raid Program(from MSI CD utilities tab or download) which gives some info and adds the array management settings(Not many. Just the enable/disable cache setting and the migrate to raid option).
    If XP Already Installed On Another Drive(and you're just adding the Raid as an extra storage disk):
    - Boot into WindowsXP.
    - As Windows starts, it should detect a new Raid device and offer to install drivers. Select Cancel. It will tell you that it was unable to install new device. If you want you can confirm the new device is present by checking Windows device Manager. It should show the new device with a yellow exclamation mark beside it since the drivers aren't installed yet.
    - Download the appropriate drivers or use the MSI CD that came with motherboard.
    Note: The MSI CD detects devices connected and shows available drivers/utilities depending on what it sees. You might not have seen the IAA Raid drivers when using the CD before but now that you have a Raid array connected to it, the drivers will be availble from the MSI setup CD.
    - Install the drivers and re-boot
    Note: If the IAA Raid program detects that the Raid controller is not enabled or no device is present, it will NOT allow you to install the drivers/utility.
    - Using Windows Device Manager should now show the Raid device properly with no problems.
    - If the Raid array has not been formatted, you can now use Windows Disk Manager (Start > Run and type diskmgmt.msc) to Initialize and then format the Raid array.
    - The new drive should now appear in Windows Explorer with it's own drive letter.
    Bugs/Surprises
    - Trying to install WinXP on the Promise Raid while my IDE drive was connected to the Intel IDE connector resulted in Windows installing boot files to the IDE drive and the rest on the Raid drives. This was especially bad since I had another installation of XP on the IDE drive which was overwritten. The work-around was to disable the IDE drive until AFTER XP was setup on the Raid array. It is safe to assume this can occur with the Intel controller as well since I believe the problem occurs because of how WinXP setup addresses the hard drives.
    Update: There have been a few posts on the forum since I wrote this guide where people installing XP have had problems similar to the one above with USB/Zip drives connected so i am adding them to the list of drives to disconnect while installing XP.
    - Be gentle with SATA connectors on the motherboard. They can stand firm downward pressure but not a lot of side-to-side pressure.
    Migrating XP System Disk To Raid On Raid-Ready System
    This part describes how to use the Intel Application Accelerator-Raid edition to migrate an existing WinXP system disk (1-SATA) to a 2-SATA Raid array.
    This procedure is actually very well documented in the last part of the Intel SATA Raid manual that ships with the motherboard but I thought I’d add it to make this thread more complete.
    Please note that to use this feature of the Intel raid software the disk you are migrating FROM must have been made Raid-Ready as described above. Basically, this means that Raid should have been enabled in the Bios and the drivers installed from floppy during the WinXP install.
    Note: I tested this by migrating to a Raid0 array but Raid1 should work also if the latest Bios and version of Intel-Raid application used.
    - Open the Intel Application Accelerator Raid utility.
    - With the “Raid” tab window open, right-click on “Raid volume” and select “Create from Existing Disk” as seen below.
    - Follow the next several steps to choose the type of Raid array and the strip size.
    Note: 64kb strip size is good for general purpose and 128kb best for most desktops and work stations according to Intel. Anything smaller is for specialized purposes. You should research this a little because you can’t change it after easily.
    - After configuring the array for your preferences, you will face a couple of warnings telling you that “All data will be deleted from the Raid-controlled drive(s) and is unrecoverable” and ask if you want to continue. Obviously all data(if any) on the new drive you’re adding will be lost but the OS and other data on the disk you’re migrating FROM will be striped to the new array and will remain intact.
    Note: Any complex disk procedure such as this carries the risk of losing data. A backup of the disk is important BEFORE beginning the migration process. Don't say I didn't warn you.
    - The migration process can take a long time. You should see the window below during the operation.
    Note: With just a default WinXP installation, migrating to 2-80Gb drives took about an hour for me.
    - After the migration is complete, you will be prompted to re-boot to complete the process.
    - During the reboot, as the Intel Bios comes up for a couple of seconds(don’t blink) you will see the 2 drives configured as an array and they will be listed as “functional”.
    - After the reboot, you should have a fully functional Raid array with 2 SATA drives and all data from the single drive will have been striped or mirrored into the second one. Check Windows Disk manager(Start > Run and type diskmgmt.msc) to see the status of the new drive. See bugs/surprises below.
    Bugs/Surprises
    The only problem I had with this test came in the form of a small surprise after everything was completed and the computer had rebooted. Although the Intel Application Accelerator showed everything functioning normally, Windows explorer showed my Raid drive as 74Gb in size instead of the 150Gb or so that I expected. After checking Windows disk Manager (Start > Run and type diskmgmt.msc), I found that the missing GB’s were in fact there but were unformatted. Unfortunately, Disk Manager does not seem to allow merging or extending partitions so I ended up using Partition Magic 8 to format the empty space and merge it with the rest of the partition. This seemed to work fine and I ended up with a single 150Gb drive showing up in Windows Explorer. I also briefly tested the performance to confirm that it was operating as a Raid array.
    I know there is a utility for Win2K called DiskPart.exe that is run from command console to extend NTFS partitions but if anyone knows of an easier way or a FREE utility that will format/merge NTFS partitions that they have confirmed works, please PM me so that I can include a reference to it here.
    All the data above is based on tests that I ran and I tried to avoid using any theory that I did not test. If you feel I’ve missed something obvious or if you have something you feel should be added to make this guide clearer or simpler, please PM me with your thoughts. If you have a specific problem that this guide does not help you with, post a detailed thread in the forum on the main page.
    Vango44

    Great work vango44!
    Here are some RAID performance statistics I gathered while testing RAID on my system.  The testing software was Winbench 99.  The hard drives tested were new Seagate ST380013AS drives, formatted NTFS.  Winbench was running on a third drive that is not included in the tests and should not affect the results.
    The drives were reformatted between tests and chkdsk'ed to try and keep things "apples to apples".
    No hardware or software changes other than the RAID setup/connections were made between tests.
    Higher numbers mean better performance.
    I also ran the same tests on the newish WD Raptor 10K drives:
    I couldn't stand all the noise   the Raptors made, so I returned them.
    On my motherboard:
    SATA 1 & 2 = Intel RAID controller
    SATA 3 & 4 = Promise RAID controller
    If the test title does not include "RAID", then it was a single drive test.
    Unfortunately, I don't have a spreadsheet version of the above stats.  Otherwise I'd create nice bar charts for us and it's would be easier to deduce performance.
    Perhaps some kind reader will OCR the pictures, put them into Excel, and make some nice bar charts for us?
    Hope the info helps.

  • Udev/dmraid not picking up all partitions of a fake RAID setup! [EDIT]

    Hey all. I've been having a problem with my RAID setup in Arch.  At first Arch wasn't picking up a partition on one of my arrays, (a single large NTFS partition on a 2TB array between two 1TB drives) but after re-creating the RAID array in the Intel Storage Manager I have a different problem. Arch now find the single large partition, but now /dev/mapper isn't populated with the other two partitions on the other array that my operating systems are on (Arch and Windows), when it used to just fine!  The only thing I changed was re-creating the partition table on the other array, so I don't know what's going on.
    Upon trying to boot, GRUB  comes back with the error described on the wiki: https://wiki.archlinux.org/index.php/In … oot_device
    However I can't boot into the fallback image either!  This means that I can't apply the fix as described in the wiki.
    I'm starting to think there is a limitation in Arch where it can only handle a certain number of mapper devices (seems to be 3), or maybe it only detects the partitions on the first detected array? Now that I recreated the partition table on the larger array, it seems like that's the array that's detected first in both a GParted live session and Arch.  But in a live GParted session, /dev/mapper was fully populated with all of my disks and partitions... so why is it that Arch can only find the partitions on one of the RAID arrays?
    If you guys need any additional information just let me know... I really want to get my Arch setup up and working so I don't have to use Windows all that often (only games that don't work well in Wine).
    EDIT: Changed post and title to reflect new problem after recreating the 2TB array
    Last edited by pad76 (2011-08-11 13:15:36)

    Does anyone know if I can damage my arch install by using mkinitcpio through a Debian live-cd?  I'm going to try and use one to remake my initrd by chrooting using this guide: https://wiki.archlinux.org/index.php/In … oot_device
    Basically the commands I'm looking to execute would be this:
    # mount /dev/mapper/isw_ArchRaidPartition /mnt/
    # mount -o bind /dev /mnt/dev
    # mount -t proc none /mnt/proc
    # mount -t sysfs none /mnt/sys
    # chroot /mnt /bin/bash
    (edit mkinitcpio.conf according to wiki, inserting the "sleep" hook)
    # mkinitcpio -p 3.0-arch
    So my question is would using the commands from a debian live distro work? I have to use debain since arch live-installs don't detect my arch raid partition, like how I described above.  I also can't boot into fallback.

  • Set up Mini with 2 drives (non Raid)

    just purchased the new Mac Mini Server with 2 1TB drives. Can I set up as two (2) 1TB drives (non-Raid) one will be the main drive and the second used as Time Machine

    I was hesitant to plug the machine and and set it up. Was trying to figure out if I should do a transfer from my current machine or use migration assistant once I'd started up the new Mini.
    I finally called a local Mac Reseller and talked with their service tech. Out of the box, the new Mac Mini Server has two separate 1TB hard drives, one named "Server HD" and the other is named "Macintosh HD2". This is the exact configuration I'd hoped for. Now I can use the Server HD as my main drive, and Macintosh HD2 as my Time Machine backup drive.
    Since I'd set up an "admin" account on initial setup (which I do on all my machines) I'll now use Migration Assistant to transfer over my main account from my current computer to the Mini.
    Thank you for your help!

  • K9N2 SLI Platinum raid setup after bios flash

    Hi
    I'm building a new system based on K9N2 SLI Platinum. Apart from a new 80 GB sys. HDD everything else is reuse from another MB (MSI K9N Platinum).
    Here is what is puzling me: Before trying to install WinXP i flashed the bios to 3.2 because of the included updates to the raid bios. Flashing went well, however in my setup I want the 80 GB HDD to be non-raid and the two 320 GB HDD to be raid1. I've set this up in bios so that only channel 5 and 6 is enabled for raid and would expect that the 80 GB HDD (channel 1) would show up as a normal sata HDD when starting up. But it doesn't - it is listed as 0.0 xxxx after the "press F10 to enter raid setup" message?
    This is strange because I had the same HDD setup on my old MSI K9N Platinum and there the 80 GB sata HDD was shown as a "normal" disk and not as a "appendix" to the raid list.
    Because of this I have problems installing WinXP on the 80 GB HDD
    Any suggestions?

    Hi BOSSKILLER
    Thanks for your quick response.
    Quote from: BOSSKILLER on 12-August-08, 00:14:44
    Well, leave the 80GB only and install XP over it.
    Then connect other two HDD's and enable RAID for them.
    Unfortunately this didn't help. As soon as I installed the Windows nVidia RAID SW it prompted med that it had registered  the 80 GB disk as a new disk that wasn't a member of any RAID. This happened everytime Windows XP was started.
    The trick was to add the 80 GB disk as a Spanned disk using the nVidia RAID BIOS setup utility. Install Windows XP (again) and the Windows nVidia RAID SW and setup RAID 1 on the other two sata disk.
    I don't think this is a great setup but it works. I hope that MSI will fix this issue in a later BIOS upgrade. It would be nice if the enabled/disabled for sata RAID setting actually worked.

  • K7n2 Delta RAID Setup ----PLEASE HELP

    Can someone explain how a RAID - Striping should be setup on this MOBO?  I can not get the board to see the 2nd drive. I have duplicate Maxtor 40gb drives and it will only see one of the drives. I am using IDE3 for one of the drives and then putting the other drive on IDE1. The manual states that you can only have 1 HD on IDE3 thus the reason for setting it up this way.  I have also tried the 2 maxtor drives on IDE1 with another drive on IDE3 (dummy RAID) hoping that this config would work as well, but it did not!
    Please help!!!!!!!!!!!!!
    Thanks in advance for any and all replies.

    It does support RAID. I have been able to go into the Fastrack utility and setup a RAID consisting of one drive. The manual also states that all IDE slots support RAID. It has the promise 376 chip.

  • Extremely Unhappy with FM2-A85XA-G65 Raid setup

    I was going to setup a Raid5 array on my new FM2-A85XA-G65 but it seems to really be an unusable mess. I have updated to latest 1.7 Bios and got no improvement. I am loading Windows Server 2012 Essentials on this machine so UEFI is a must and there for Legacy Raid is out. There was supposed to be an improved way to set up an UEFI Raid 5 array in this new BIOS but I don't see squat. Setting the Legacy Raid seems to be the only way to get into the board's Raid setup but as I said that is a none starter. I had read elsewhere that the 1.7 Bios allowed UEFI Raid setup from the Bios menus (which is how it should be with a board boasting easy graphical UEFI setup) but there appears to be no such thing.
    Extremely unhappy and thinking of returning this board. I've currently setup the Raid5 array using the Windows Server 2012 and it seems to work fine but I assume the motherboard based Raid would have significantly better performance, correct?
    How much better performance should the motherboard based Raid be, and has anyone got Windows 2012 Server to load on Legacy Raid?
    Is anyone using AMD Raid Expert with this Motherboard's native Raid setup?
    Is the new Storage Spaces feature in Windows Server 2012 a better option than Raid5?

    Quote
    Is there any other way to fix it?
    Not without a Trinity cpu. Alternatively ask reseller or MSI to flash it for you.
    Quote
    For example: can I get an old FM1 CPU from a friend to test it?
    Of course not. You need a FM2 cpu. FM2 and 1 aren't compatible.
    Quote
    And what can you tell me about the memory?
    Will it work on this board?
    Those sticks are ment for Intel systems (http://www.kingston.com/datasheets/KHX21C11T2K2_8X.pdf) but they will most likely work with safe settings. Don't expect them to go anywhere near 2133. First that would be oc as your cpu's mem controller supports just up to 1866. Secondly because the ram is meant for Intel system's it might even with oc not work at the same settings/speeds it would work on Intel systems it is specified for.

  • Reformatting external drive to Mac OS Extended but maintaining RAID setup

    Hi again,
    I am considering taking the leap finance-wise and purchasing [this external drive|http://www.amazon.com/Western-Digital-WDH2Q20000N-Studio-Interface/dp/B00 16P7H3Q/ref=cmcr_pr_producttop]. It comes pre-formatted to HFS+ or something, so I guess I will need to reformat it to Mac OS Extended to use it with FCE.
    So here are the questions:
    *1. Would it make more sense to use it in RAID 0 mode for faster speed, or RAID 1 mode to keep a safer backup of my files?*
    *2. Would reformatting it to Mac OS Extended for use with FCE still allow it to use normal RAID abilities?*
    I realize this is not the right forum for posting this, but I thought someone here might be knowledgable about backup in general and how to best format an external drive for use with FCE, while maintaining the ability to have a "mirrored" RAID setup. Any thoughts?
    Thanks in advance,
    Sasha
    Message was edited by: skalicki`

    So just one more question because I'm pretty new to this whole RAID thing:
    Say I formatted the drive to RAID 1 so in theory I have 1TB of space that is "mirrored" over to the other external drive.
    *When I ingest my footage, will copies be stored to both drives, so if one fails, I will still have my media?*
    I gathered this was the idea but didn't know how it works with FCE.

  • External firewire 800 disk: Raid or non Raid?

    Hi all,
    I am currently about to by a new external firwire 800 hard disk to replace my firewire 400 200GB Maxtor. I mainly use this disk for timemachine backups and all my final cut express scratch area and work area. I am working with AVCHD video and looking to expand the storage and speed of this disk. I have narrowed my options down to two. They are both high quality options. I will be buying the enclosure and hard disks seperatly to ensure I get a good enclosure and good quality hard disk drive.
    Enclosure options:
    1. http://www.macpower.com.tw/products/hdd3/pleiades/pd_scombo.
    Pleiades Super S-Combo, FireWire 400/800, USB 2.0, and eSATA interfaces. This enclosure uses Oxford 934DSb or Oxford 924DSb chipset. This is a single drive enclosure and non Raid. I would put a 1TB disk in this enclosure.
    2. http://www.macpower.com.tw/products/hddmulti/taurus/pdd_raid2
    Taurus Raid II enclosure. FireWire 400/800, USB 2.0 and USB 1.0 interfaces. This enclosure uses Oxford 934DSb or Oxford 924DSb chipset. This is a dual drive enclosure and Raid 0 and 1. I would put a two 500GB disks in this enclosure. But will use with mirroring such that a copy of data will reside on each disk. Whilst this will reduce the overal capacity to 500GB I will have the extra redundancy should a drive fail. From which I can just replace the failed drive.
    I am aware that using Raid mirroring will slow down the data transfer to the disk enclosure but I think this should be ok for AVCHD editing for my purposes. Cost wise there is not much difference between the two options. In both options I will go for either Seagate Baracuda drive or Samsung Spinpoint.
    Would like to know what your thoughts are?
    Which options would you go for?
    Message was edited by: Just-Karma

    Hi all,
    Ok so I decided to not go done the raid mirriring route. Instead I finally made a decision and boughts a Macpower FW800 enclousre which uses the Oxford 934 chipset and a Samsung HD103UJ 1TB Serial ATA 3.0 Gbps
    buffer memory32 MB hard disk.
    The enclosure is excellent quality and the disk access is very quick via FW800. The disk itself is very quiet and also great for Final Cut with my HD editing. Only noise the disk makes is upon power up other than that it is very quiet.
    I have partitioned th disk into two 500GB's. One partition is used for time machine backups and the other is the Final Cut scratch space.
    I plan to buy another enclosure and 1TB disk and parition into two 500GB's also. I plan to use one of the 500GB's for Super Duper clone of iMac system hard disk and the second for cloning/backing up the scratch Final Cut space. This second disk and enclosure will be my offline backup system and will not be powered all the time.
    Details of the elcousre and hard disk are provided below. I purchased them in the UK. Enclosure was purchased from www.span.com and hard disk from www.ebuyer.com. Whilst span can sell disks in the enclosure you can save yourself a little money and buy seperatly from ebuyer and install yourself.
    Enclosure:
    http://www.macpower.com.tw/products/hdd3/pleiades/pd_scombo
    Hard disk:
    http://www.samsung.com/global/business/hdd/productmodel.do?group=72&type=61&subt ype=63&model_cd=249&tab=fea

  • RAID Setup

    I recently  upgraded my system and originally set up my two WD360's to the Promise RAID controller (SER-3 and SER-4) I enabled "Onboard Promise IDE" in the BIOS. However when installing the operating system (WinXP Pro),
    there was an error message saying that no hard drives could be found and to make sure they were connected
    and or powered up. I triple checked everything and it was all connected properly.
    Then I connected the drives to SATA 1 & 2 and disabled the BIOS for 'Onboard Promise IDE' and also configured
    SATA as RAID in the BIOS, and the drives are recogonized and I could install WindowsXP.
    BUT During the POST after the section about Raid Volumes etc I get the message: -
    Non Raid Disks
    None Defined
    Press (CTRL-I) to enter configuration utility.
    but the system boots normally into Windows.
    Can anyone help as it is driving me crazy.
    P4 3.00C 800FSB HT enabled
    Corsair DDR400 2 x 512
    875 Neo2-FIS2R Bios v1.60
    Raedon Gigacube 9600 Pro 128 VGA
    Antec Truepower 550W
    Western Digital Raptor 36GB x 2 @ SATA-1 and SATA-2, RAID
    BIOS - optimal settings enable USB, 1394 and ACPI.
    WinXP + SP1 + all latest Windows Updates

    Quote
    Non Raid Disks
    None Defined
    Press (CTRL-I) to enter configuration utility.
    Of course, you realise, that it isn't enough just to enable RAID from BIOS?! You also have to create RAID array by going into RAID BIOS and adding hard drives you want use in your RAID array.
    You propably can do this afterwards in windows by usin Intel Appllication Accelerator RAID edition.

  • Multiple RAID setups in one Xserve?

    Hi hope you can help me, we are a small architecture practice in the market for a new server and we are considering an Xserve and Xserve RAID system. I would quite like to set up the Xserve unit to use two of the drives in RAID 1 to mirror the operating system. My question is it possible and/or wise to have multiple RAID sets in the Xserve RAID unit? For example using four of the bays for 4x500Gb in RAID 1 (1Tb storage) for projects, and then using another 2 bays for 2x250Gb in RAID 1 as well for say Mail, maybe even another 2 bays for holding user home accounts. I understand that with share points this isn't strictly necessary but it seems to make sense to keep functions separate across hard drives for quick replacements. Or is this a lot to ask of a single RAID controller?
    Also how easy is to add storage to an existing RAID set-up without destroying the data?; say we wanted to increase the 1Tb project storage to 2Tb easily.
    Thanks for your help in advance.
      Mac OS X (10.4.8)  

    Andrew,
    I think you are over complicating you setup.
    If you do multiple RAID sets the you are really anti-optimiziung. If you asked "How can I get the least performance and lowest capacity out of a RAID?" then I would suggest three mirrored disks w/ spare per controller.
    You would have far better performance and capacity if you were to put two drives in the Xserve to mirror, then set up your RAID as RAID 5 across 6 disks with 1 spare (default config).
    With Disk Utility you can build multiple file systems on the RAID, so you could slice it up, but again that could be wasting space.
    When you get the RAID setup as one file system do not share the root. Set up sub dirs to share:
    /Volumes/Raid1 --your RAID root, aka mount point.
    /Volumes/Raid1/Mail -- mail
    /Volumes/Raid1/Users -- Home dirs
    /Volumes/Raid1/Projects -- your production storage
    /Volumes/Raid1/Backup -- Save disk images of your server and workstations here.
    And yes, changing the size of a file system means wiping it out and restoring from backup.
    Also consider the 750GB drives, it's a lot more storage for not that much more money.
    Reese

Maybe you are looking for