Clarification: Installing ARCH to RAID setup in BIOS

So I've been looking in to setting up ARCH on my laptop that has a RAID that's set up in the BIOS. I've been researching on the wiki as well as on the internet but it's only partially answered my question:
With a BIOS enabled RAID do I still need to use tools like MDADM to set up the raid inside of arch, or should arch see its own drive like windows does?
I'm sure I will have other questions as I delve in to installing on a RAID so I will ask what I have now as well:
Reading threads about doing this it seems like I will need a third drive something outside of the RAID to store the RAID configuration if I opt to use GRUB, however syslinux supports RAID during boot, does this still hold true and if so what do I need to do while installing syslinux to have it know that there's a RAID there and configure correctly?
Any other tips on this topic are very welcome.

So, is rEFIT able to boot GRUB but GRUB is not able to find Arch? Or is rEFIT not able to find GRUB?
For what it's worth, I recently installed Arch on my Macbook 5,1. I also used rEFIT (installed using OS X). My drive partitioning was
/dev/sda1: EFI/OS X boot partition
/dev/sda2: OS X
/dev/sda3: Linux Swap
/dev/sda4: Arch
As you mentioned, the new Arch installer doesn't give you the option of selecting primary partitions to install GRUB (the old installer did). So, when I reached the last stage of the installer (installation of the bootloader), I exited the installer, launched GRUB in interactive mode, and installed GRUB to my 4th partition (where /boot is). (It sounds like you did something similar.) When I rebooted rEFIT discovered that my 4th partition was bootable and displayed a Tux logo. Clicking on the Tux logo launched grub. From there I am able to launch Arch.
Some thoughts:
1. Did you make sure your partition tables are synced? I didn't need to do this, but I've heard of other needing to do this.
2. Did you make sure that the grub was configured properly; e.g. you've specified the correct path to the kernel, etc.
3. Did you try prayer and/or other forms of divinity?

Similar Messages

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

  • Installing Arch in Raid 0?

    As my motherboard does not have RAID functionality, my only hope here is software RAID. I found a bit of info here, but nothing on RAID 0. Is RAID 0 possible only using software RAID? and if so how do I go about setting it up during the install process? I have two 74GB Western Digital Raptors, so I'm excited to see how fast they'll be in RAID 0. I do need to RMA one of them before I can start the install, however, so I'm starting this topic to get an idea of how hard this will be. I've never done more than a run of the mill Arch install and setup.

    when you are partitioning your drives during setup, just create 100MB (or w/e) partition for booting....
    e.g.
    /dev/sda1 --> 100MB
    /dev/sda2 --> rest
    /dev/sdb1 -->100MB
    /dev/sdb2 --> rest
    you can create a software RAID0 from the /dev/sdx2 partitions and just boot from one of the /dev/sdx1 partitions.
    hope that helps

  • Installing Arch on a RAID (for dummies)

    Playing with RAID's is fun for all the family, and makes things go faster.
    this is how I (re)installed Arch Linux, in a simple RAID configuration.
    Ingredients
    ===========
    1. Two 160GB drives
    2. Arch Linux CD (Dont Panic)
    Planning
    ========
    1. root partition on a RAID 1 setup (mirroring)
    2. home partition on a RAID 0 setup (striping)
    3. swap partition on a RAID 0 setup (striping)
    in this kinda setup, one disk can fry, but the system will still boot and function normally.
    home will be lost for ever, but I always back it up anyway (and so should you).
    *Important* - make sure your two IDE drives are not connected to the same cable, setup one as a primary master and the second as a secondary master.
    The works
    =========
    1. Boot the machine using the setup CD.
    2. Using cfdisk, partition the two drives exactly the same:
       Device Boot      Start         End      Blocks   Id  System
    /dev/sda1   *           1        4863    39062016   83  Linux
    /dev/sda2            4864       17021    97659135   83  Linux
    /dev/sda3           17022       17083      498015   82  Linux swap / Solaris
    I chose 40GB for root, 100GB for home (results in 200GB), and 1GB for swap.
    Do exactly the same on the second drive /dev/sdb
    3. create the RAIDs using mdadm:
    modprob raid1
    modprob raid0
    mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/sda1 /dev/sdb1
    mdadm --create /dev/md1 --level=0 --raid-devices=2 /dev/sda2 /dev/sdb2
    mdadm --create /dev/md2 --level=0 --raid-devices=2 /dev/sda3 /dev/sdb3
    4. create filesystems on the partitions:
    mkfs.xfs /dev/md0
    mkfs.xfs /dev/md1
    mkswap /dev/md2
    5. mount the root partition on /mnt
    mount /dev/md0 /mnt
    6. start the setup program
    /arch/setup
    7. select all base packages
    8. install packages
    9. configure:
    choose configure system and then, edit mkinitcpio.conf modules section:
    MODULES="ata_generic ata_piix raid1 raid0 xfs"
    In this line, I only added "raid1 raid0 xfs" to the modules.
    then, edit mkinitcpio.conf hooks section, and add the RAID stuff after that:
    HOOKS="base udev raid autodetect pata scsi sata usbinput keymap filesystems"
    md=0,/dev/sda1,/dev/sdb1
    md=1,/dev/sda2,/dev/sdb2
    md=2,/dev/sda3,/dev/sdb3
    In the hooks line, I have added the raid hook before autodetect
    10. install the kernel
    choose install kernel from the menu.
    11. Install grub
    choose install bootloader then grub
    edit the grub entry to:
    # (0) Arch Linux
    title  Arch Linux  [/boot/vmlinuz26]
    root   (hd0,0)
    kernel /boot/vmlinuz26 root=/dev/md0 ro md=0,/dev/sda1,/dev/sdb1
    initrd /boot/kernel26.img
    install grub to /dev/sda
    when prompted about root partition choose /dev/sda1
    when prompted about RAID stuff choose no
    do exactly the same on /dev/sdb
    12. exit the setup program
    13. fix mdadm.conf
    mdadm -D --scan >>/mnt/etc/mdadm.conf
    14. fix fstab
    add this to /mnt/etc/fstab:
    /dev/md0                /       xfs     defaults                0       0
    /dev/md1                /home   xfs     defaults                0       0
    /dev/md2                swap    swap    defaults                0       0
    15. reboot and install the rest of the system
    16. make sure all is well:
    cat /proc/mdstat
    Personalities : [raid1] [raid0] [linear] [multipath] [raid6] [raid5] [raid4] [raid10]
    md2 : active raid0 sda3[0] sdb3[1]
          995840 blocks 64k chunks
    md1 : active raid0 sda2[0] sdb2[1]
          195318016 blocks 64k chunks
    md0 : active raid1 sdb1[1] sda1[0]
          39061952 blocks [2/2] [UU]
    mount
    /dev/md0 on / type xfs (rw)
    /dev/md1 on /home type xfs (rw)
    make sure swap is on:
    cat /proc/swaps
    Filename                                Type            Size    Used    Priority
    /dev/md2                                partition       995832  0       -1
    17. If things go wrong, you can reassemble the RAIDs after booting from the setup CD, dont recreate them:
    mdadm --reassemble /dev/md0 /dev/sda1 /dev/sdb1
    for more reading, consult the WIKI: http://wiki.archlinux.org/index.php/Ins … AID_or_LVM
    Last edited by daf666 (2008-03-08 20:36:42)

    Sorry for the late reply clickit, I guess you might have fixed it already.
    There is a mistake in the guide, I will correct it now, the types in these lines should be --level=0
    mdadm --create /dev/md1 --level=1 --raid-devices=2 /dev/sda2 /dev/sdb2
    mdadm --create /dev/md2 --level=1 --raid-devices=2 /dev/sda3 /dev/sdb3
    Very sorry about that, but that does not cause your problem, because it would have created a mirror RAID instaed of a stripe.
    Your BIOS has nothing to do with the Linux software RAID, the RAID settings you see in BIOS are probably to enable the on-board RAID controller you have.
    The grub part is tricky, you have to make sure whats in the configuration file is according to the setup that you have (not just copy from the guide).
    Also keep in mind that if you have SATA, things might look different and the setup might need to be different.
    PS - regarding swap, since I wrote the guide I removed the swap space and instead I use a swap file on the RAID0.. I guess it the same because my system  rarely uses swap anyway
    Last edited by daf666 (2007-10-17 21:31:59)

  • [SOLVED] BIOS not detecting USB Drives after i installed Arch

    SOLVED: In BIOS under 'Advanced' disable 'Fast BIOS Mode'.
    Original post:
    Hi there!
    I'm fairly new to the arch (and linux) scene and just setup my Samsung 530U3B with a brand new installation of arch. Everything went fine and the system is running flawlessly. Almost.
    I just happend to notice that BIOS is not checking for USB drives anymore, it just somehow skips that part. If enter the boot selection, the bootable USB drive won't show up. Neither does it show up in BIOS setup. I tried to boot with the same USB drive that i used to install arch just yesterday, the live media does not boot - the drive doesn't even blink. The boot priority is set to usb drive first, the boot selection screen (hammering f10 during boot) doesn't give me any other option than to boot from the normal SSD. Also, prior to the arch installation (came with w7 installed) the BIOS screen would stay for about 2seconds and then proceed to boot - this doesn't happen anymore. When i press the power button greeted by the grub bootloader in about 1s.
    I tried 2 different usb drives, both with the arch iso (same that i used to install the currently running OS, downloaded yesterday). The drives also show up once my arch is booted (starting to blink just after i hit enter in grub). Also, both drives boot without a problem on my desktop computer.
    Anyone got any ideas?
    I don't really now what kinda of information would be helpful so i'm just dumping stuff i know:
    BIOS: Phoenix SecureCore Tiano Version 04XK
    Machine: Samsung 530U3B
    SSD: Samsung MZ7PC128HAFU-000
    ISO used to install (checksum ok): archlinux-2012.07.15-netinstall-dual.iso
    Last edited by araex (2012-07-26 16:57:47)

    DSpider wrote:
    The boot priority is set to usb drive first
    Welcome to the forum.
    If you just set the USB stick to be first in the boot order, the next option (from the list) takes its place the moment you unplug it. You need to set the BIOS to boot from your equivalent of "Removable Devices" first, "Internal Drives" second and "Optical Drives" third.
    The USB stick doesn't show up at all. I set the priority as follows:
    1. USB HDD
    2. USB FDD
    3. USB CD
    4. SATA CD
    5. SATA HDD
    6. NETWORK
    I used that same configuration to install arch. USB doesn't seem to initialize at all. Also, if i enter "usb" in the grub commandline, no devices are listed.
    Thanks!
    UPDATE:
    I just figured it out. In my BIOS under 'Advanced' the 'Fast BIOS Mode' was enabled, once i disabled it, everything went fine. I don't remember changing that option. Silly me.
    Sorry for your time
    Last edited by araex (2012-07-26 16:56:30)

  • Help with installing Arch x64 to Silicon Image SiI 0680 raid card

    I am having one heck of a time trying to find information on installing Arch on a Silicon Image SiI 0680 raid card. I have searched both the wiki and the forums and I cannot find any information about this card. I am trying to install a raid 0 setup on Arch x64 Could someone point me in the right direction, any help is appreciated. Thank you.
    Information about the card: http://www.newegg.com/Product/Product.a … 6816132004

    My memory has slipped a bit:  the following is more to the point than my reference to md=0!
    Member
    Registered: 2009-09-02
    Posts: 17
    E-mail
    Re: [SOLVED] usb /boot, RAID5 /root, mkinitcpio.conf help request
    The array stabalized and I was able to reboot with the following entry in my menu.lst:
    # (0) Arch Linux
    title  Arch Linux
    root   (hd0,0)
    kernel /vmlinuz26 root=/dev/md0 ro
    initrd /kernel26.img
    $ cat /proc/mdstat
    Personalities : [raid6] [raid5] [raid4]
    md2 : active raid5 sdi1[0] sdg1[3] sdh1[2] sdk1[1]
          2197715712 blocks level 5, 64k chunk, algorithm 2 [4/4] [UUUU]
    md1 : active raid5 sda3[0] sdf3[5] sde3[4] sdc3[3] sdd3[2] sdb3[1]
          7252222400 blocks level 5, 64k chunk, algorithm 2 [6/6] [UUUUUU]
    md0 : active raid5 sda2[0] sde2[5] sdf2[4] sdd2[3] sdc2[2] sdb2[1]
          52451840 blocks level 5, 64k chunk, algorithm 2 [6/6] [UUUUUU]
    Thank you very much to everyone in this thread.  I really appreciate the help. 
    Offline

  • Bios and SATA Raid setup nightmares

    Three manuals with this mobo and I just can't get it set up.
    I have the 865PE Neo2-FIS2R, an Intel 3.0GHZ Northwood processor, a pair of 256 memory chips configured as dual channel. A pair of SATA drives are on the Intel ports. The IDE has four devices connected, a HDD, Zip drive, and a pair of CDs. All of the hardware, jumpers, cables seem to be working fine.
    My goal was to have a SATA Raid 0 setup, with the spare drive for backup and misc storage. CD's and Zip for input, burning, etc.
    After everything was connected I booted Win XP Pro from the CD, did the F6 thing and installed the drivers for both Intel and Promise (Fastrack and drivers). Setting up the bios "Integrated Peripherals" was a real problem and the book very little help, but I finally got the system to recognize things so I could format and boot and install the OS. I did the Control-I thing and configured the Raid drives (at least I think). So far, so good.
    After the OS was installed, SP1 added, etc. I got ready to configure the Raid. The CD does not come up with the screen shown in the manual. But I did find the Intel IAA RAID Edition in a folder. Running it results in an error message saying that the software does not support this chipset. Downloading similar drivers for both Promise and Intel always dead-ends the same way.
    What I'm leaving out are the--literally--hours of time I've spent trying to get the devices configured right in the Bios' "Integrated Peripherals." I have no idea what I'm doing and the book is no help. But the devices are all there now and the OS runs fine (but not as a Raid 0 set up).
    The book says I can migrate this configuration to a Raid volume. How, when I get that error message?
    And another thing. Can I use the Promise IDE (PATA) port for a single drive? It's the only place on the mobo where ATA 133 is supported.
    I think I'm in a world of trouble here. Don't know squat about these complex bios setups. Sorry this is so long.
    ardi

    OK, I actually went down to the basement and dug out the ICH5R Raid Manual. Basically it says in order to take advantage of the ability to migrate later on, you have to set Raid in Bios B4 loading Windows and install Raid driver with Windows setup. If you've already got Windows installed on 1 disk and had Bios set to"SATA as Raid- NO", you're out of luck.
    Here's the exerpt from the manual:
    Quote
    The Intel Application Accelerator RAID Edition offers the flexibility to
    upgrade from a single Serial ATA (SATA) hard drive to a two drive RAID 0
    configuration when an additional SATA hard drive is added to the system.
    This process will create a new RAID volume from an existing disk. However,
    several important steps must be followed at the time the system is first
    configured in order to take advantage of RAID when upgrading to a second
    SATA hard drive:
    1. BIOS must be configured for RAID before installing Windows* XP
    on the single SATA hard drive.
    2. Install the Intel Application Accelerator RAID driver during Windows
    Setup.
    3. Install the Intel Application Accelerator RAID Edition after the
    operating system is installed.
    Maybe someone knows a work-around?  

  • Setting up encryption on an already installed Arch setup?

    Recently I have been thinking about setting up encryption on my already installed Arch setup. I would reinstall and encrypt it that way, however I do not have an external HDD big enough to back up everything, so I was wondering if it is possible to encrypt a hard disk on an already installed Arch setup. I have two partitions, /dev/sda1 and /dev/sda2, and would like to encrypt both while not having to reinstall.
    Can anyone help? Thanks!
    Edit:
    Alternatively, could I reinstall it and use encryption in the install in such a way that it retains my file contents?
    Last edited by ThatPerson (2013-07-30 12:41:13)

    I use rsync rather than tar to do what Stebalien is suggesting here.  I use btrfs, and my root filesystem is actually a subvolume.  So I mount the entire btrfs filesystem (from subvolid=0) at /var/lib/btrfs-root.  By doing this, it makes it much easier to simply rsync (or tar) from that mountpoint to the backup mountpoint.  This makes it so that I can actually backup the system I am running off of without explicitly excluding all the volatile directories (like /sys, /tmp, /proc, etc.)  Though I think a more sane approach, since I use btrfs, would be to snapshot each subvol and rsync those instead. 
    I guess what I am trying to get at, is that if you were to create something like /mnt/system and /mnt/backup.  If you mounted your rootfs to /mnt/system (and then possibly your home partition to /mnt/system/home), then mount the backup destination to /mnt/backup, you could simply do something like:
    # rsync -aAXv /mnt/system/* /mnt/backup
    Then of course you would have to put it all back after you set up Luks/dmcrypt.
    This installation I use has been through a few different drives and trying and removing Luks/dmcrypt.  I have also changed filesystems, switched to LVM2, tried mdadm RAID0, mdadm RAID1, and eventually went back to btrfs.  So as mentioned above, there is really no need to reinstall just to change the underlying layout of the HDD/SSD.  Of course this assumes that you have a spare drive with the space to copy your entire filesystem to... but then you should have backups anyway, right?

  • Uncertainty with grub-bios, grub-install when installing Arch

    Hi guys.
    I decided to reeinstall Arch on my T400 laptop since I threw in a new SSD and some 8GB of RAM and given the fact the old install (which btw is running just fine) was on GRUB legacy.
    There is one thing I'm not sure of and I hope somebody could clarify on this matter. The GRUB(2) wiki page has three ways of configuring the MBR (https://wiki.archlinux.org/index.php/GR … ode_region). It seems that neither the official installation guide, nor in the beginners guide seem to clarify if this step is mandatory during the installation via pacstrap. Maybe even pacstrap deals with this during the installation process? I really don't get it. I watched some Arch install vids on youtube, and nobody seems to pay this step any attention...
    Before I forget here comes my partitioning scheme:
    gdisk-configured GPD
    1 partition --> 2 MiB partition --> no file-system
    2 partition --> rest of the disk -->ext4 (discard, noatime, that kinda stuff in /etc/fstab)
    So, what is the deal with that three steps described in the GRUB wiki post?
    Many thanks in advance
    ralle

    illusionist wrote:
    ralle wrote:
    ...when you click on the link I added in my original post and scroll up just a few lines, you see this:
    Install grub-bios boot files
    There are 3 ways to install GRUB(2) boot files in BIOS booting:
    #Install_to_440-byte_MBR_boot_code_region (recommended) ,
    #Install_to_Partition_or_Partitionless_Disk (not recommended),
    #Generate_core.img_alone (safest method, but requires another BIOS bootloader like grub-legacy or syslinux to be installed to chainload /boot/grub/i386-pc/core.img).
    This is the part I don't quite understand. Do I need to perform one of these steps when I do a fresh install as I did? Is this step somewhere implicitly performed during the installation (by pacstrap perhaps)?
    Hope I was able to clarify...
    Thanks
    It is little tricky to understand. Install to 440 byte MBR boot code region means that you need the first 2048 sectors to store grub's information. It does not mean you need to make a 2 MB partition . For example if your hard disk have 100000 sectors then you need to make the partitions from 2048th sector[leaving first 2048 sectors(0-2047) alone] which means you have 97952 sectors left. By default when you partition using "fdisk" it automatically leaves the first 2MB and start form 2048th sector.
    Edit reason: typo
    ...well I don't quite know about the last statement. From where I'm standing I understand that post [https://wiki.archlinux.org/index.php/GR … structions] as to create a dedicated partition with a EF02 flag. That leaves you with a minimum of 2 partitions (1 filesystemless + 1 root) plus the 2 MiB gap in the very front of the drive.
    I think zero_one's first reply kinda confirms that. But then again, I might be wrong all along...
    Cheers
    ralle

  • Installing Arch on a Intel P55 raid

    Hello, i would like to install Arch on a stripped raid made with the Intel P55 chipset, while it works without problems on Windows, it seems i'll have to do some work to make it work on Arch.
    I didn't found anything about installing the system on intel's raid in the begginer's guide, and from what i've found, i will need dmraid to install ArchLinux on the raid but it seems dmraid isn't  included in Arch's linux iso
    "Warning: Command "dmraid -ay" could fail after boot to Arch linux Release: 2011.08.19 as image file with initial ramdisk environment does not support dmraid. You could use an older Release: 2010.05. Note that you must correct your kernel name and initrd name in grubs menu.lst after installing as these releases use different naming"
    from the wiki
    Means i have to use an "outdated" Archlinux to install it on a raid, and upgrade afterward if i'm correct. Isn't there a way for me to create an iso that include rmdisk ?
    Can i, from way or an other, use the latest ArchLinux iso, and put the rmdisk in a usbkey, and use it from there for ArchLinux install ?
    Is the intel P55 chipset supported at all ?
    Note that this raid doesn't contain Windows system, only data, and can be formated entierly if required without problems.
    Thanks for your time.
    Best regards, Magissia

    Magissia wrote: Isn't there a way for me to create an iso that include rmdisk ?
    Can i, from way or an other, use the latest ArchLinux iso, and put the rmdisk in a usbkey, and use it from there for ArchLinux install ?
    Create an ISO:
    https://wiki.archlinux.org/index.php/Archiso (you can add the packages you need, such as "rmdisk", build the archiso, and boot it)
    https://wiki.archlinux.org/index.php/Archboot i think this one is similar (I did not try yet)
    Install on USB:
    https://wiki.archlinux.org/index.php/Usb_install
    An arch-installation can be done with all 3 ways I mentioned. (you can even grab an existing arch, copy the files over, chroot, configure, and boot)
    Good luck.

  • How can I install Arch Linux on a software raid?

    Hi Guys, I've been at this for 3 days now and I can't get it to work. Basically I have 2 500GB SATA HDDs and I want them both on a raid1 array. I had it working on Ubuntu with no issues but the installer did all the work for me. I have attempted to follow the instructions on the wiki for Raid and LVM but I quickly get lost and I don't understand the LVM stuff. I managed to get 2 arrays up (md0 for /boot and md1 for /) but I was contently running into errors trying to install grub. In my last attempt I somehow managed to get grub installed on /dev/sda and /dev/sdb but then when I reboot the system it fails to mount /dev/md0 or /dev/md1 these raid devices don't appear in the /dev/ directory and I cannot bring them up manually. I have been all over Google and I can't find a comprehensive guide to setting up a raid 1 array and installing Arch. If anyone can direct me to useful instructions or layout the procedure for me I would really appreciate it.
    Thank You.

    This is genius, sheer brilliance. When I wanted to raid my Ubuntu install I specifically wanted to install a new HDD and just raid it with my existing disk but I had to download and alternate install CD and re-install the OS. I searched all over the net for an alternative and could not find anything. It's baffling that I had to start a thread to find such an insanely useful utility. Unless I'm taking the wrong approach. I mean, doesn't everybody raid if they can? Is there a better way to backup your disk? Why is it so difficult to find any useful information about raiding your disks? ... but I digress. Despite the fact that nobody else seems to know about this tool I know about it now and it seems to be the key to solving my problem. But I still have one problem. I have installed Arch on /dev/sda1. I downloaded (with wget), compiled, installed, and ran raider. I followed the on-screen instructions to the letter. When I swapped the disks and rebooted. I get pass the grub screen and get this error during boot.
    Waiting 10 seconds for device /dev/md1 ...
    Root device '/dev/md1' doesn't exist. attempting to creat it.
    ERROR: Unable to determine major/minor number of root device '/dev/md1'.
    You are being dropped to a recovery shell.
    Type 'exit' to try and continue booting
    /bin/sh: can't access tty; job control turned off
    [ramfs /]#
    I cannot type anything at this prompt. No response from the keyboard. I'm so close to getting this to finally work. Dose anyone know what might be going wrong.
    Thank you guys for all your help.

  • Bios not install error and Raid Configuration not showing physcial HDD in Lenovo

    Is this a SATA hard drive by any chance?  Sounds like you have an Adaptec SCSI controller, but no hard drive attached to it.  Are you booting an install DVD of some sort?

    Bios not install error and Raid Configuration not showing physcial HDD in Lenovo RD 120 Server (New)
    updated bios still same error
    and at array configuration it is not showing any hard disk
    hard disk utility it is showing hard disk 
    we are trying to install OS with single hard disk in Lenovo RD 120 Server
    This topic first appeared in the Spiceworks Community

  • K9NU RAID setup

    I'm trying to install XP Pro x64 on a newly formed RAID 0 array, but XP setup isn't seeing my array.
    I've turned on RAID for the SATA drives (2x 200GB WD Caviar).
    I've setup RAID 0 array through ctrl+A during POST (subsequent reboots show 400GB up and healthy).
    During XP setup, I've hit F6 to install SATA drivers with prepared floppy (more on that in a minute).
    After I accept the EULA, I'm given a choice of partitions to install XP on, none of which are my new RAID array.
       - my only options are my x32 OS & program partitions that are keeping me connected through this process (I re-installed an old WD 120 GB PATA drive for this)
    I've tried disconnecting the PATA drive during one of the install attempts, and there's been no drives at all available.
    I've tried setting the RAID array as the first boot device in the BIOS... no dice.
    I think my problem is the driver floppy.
    I don't have the original disc that came with the board, so I've been trying different sources for the files:
     - manually choose from the board drivers page on MSI site (Uli_SATA-RAID_AP003.zip)
     - original install CD that came with the MoBo
     - nVidia site (Uli_Integrated220.zip) although this is an .exe and not useful at all
    I've figured out that I need the M1697 driver on the floppy as well (m5288.sys, found it on the orig CD), but I cant figure out how to have it there with the m5287.sys.
    During the F6 install of the RAID drivers, only the m5287 is installing.
    If I have both m5288 & m5287 in the same folder (xp_64), only the m5287 installs.
    If I try to have both uli>floppy folder structures copy on to the same floppy, there's not enough room (and I'm asked to over-write files).
    If I try to use two separate floppys (one with m5287, one with m5288, and their associated files and folders), I get a notification that m5287 isn't on the (m5288) disc.
    The options I'm given during the F6 driver install are all just OS choices (xp_32, xp_64, etc).  I'm choosing the x64 option, but there's no further option for individual .sys files, as all the walkthroughs specify.
    Is there anyone out there who can give me a detailed breakdown of the directory/folder/file tree from the install floppy?  I could work with an .iso of the floppy also (if that's even possible with floppys).
    Thanks
    All the hair on my head is gone, I'm starting to pull it from much more painful areas

    Here's what I've learned/gathered... for posterity.
    Pardon the length of this post, but I want to be as detailed as possible in case anyone else comes along with the same issue.
    Feel free to skip to the credits at the end...
    The Basics:
    The two drivers that Windows installation is looking for at the F6 screen (for the K9NU Neo-V board, at least), are for M1575 & M1697 (southbridge & northbridge, respectively) chipsets.  Both are necessary for proper SATA function during Win install, and are covered by the M5287.sys & M5288.sys files, respectively.  These must be on the F6 floppy disc if there is to be any hope of Win install seeing drives in a RAID array.  Also on the disc is M5289.sys, which Uli describes as a RAID driver.
    When the floppy is inserted after F6 screen, options for the desired OS version (2000, XP, Server, x64, etc) are given, and after a choice is made the drivers are loaded.  From my experience with this process, (if the floppy is configured right), both are loaded at once, without having to select them individually.  I mention this because all the online tutorials for this process indicate that you must repeat the hit "s" key/insert floppy routine for the second (M5288.sys) driver.  In any case, once you have loaded the driver, Win install will tell you what it has loaded for use.  If both M1575 and M1687 are not mentioned (either in the same line, or as two), installation of drivers has not been completed and Win won't install correctly on RAID!  In fact, without the M1697 driver (at least), Win won't even "see" your SATA drives (if RAID is enabled in BIOS).
    Continuing on to install Windows, and after accepting the EULA, install finds the drives on the system an you choose the target drive (in RAID 0, this is the size of both drives in the array combined; 200GB + 200GB = 400GB, or thereabouts; 372.62MB in my case).
    Voila... Done.  Follow the yellow brick promts.
    My issues (as I see them):
    My first problem was that misplaced the RAID install floppy that came with the board.  (Just as likely, if not likelier, is that my board didn't come with one.  The MSI site mentions that its inclusion was optional.  Given that my current floppy disc collection contains one for a CAD program that I've had since my days with an IBM 386, I'm inclined to believe this was the case.  But whatever; no harm, no foul)  Regardless, much heartache could have been avoided if I had the original floppy!
    My second problem was in my confusion over the process for making a new one.  I had the original install CD for the MoBo, so I had all the files I needed, but the makedisk.txt instructions in the floppy folder were clear as mud (in hindsight I ended up following them, but there was no clarification about over-writing folders, which would have been very helpful).  I think my original fault when making the floppy was to copy the folders in the reverse order ie, M1687>FLOPPY instead of FLOPPY>M1697.  Someone with more knowledge about the specifics can correct me, but I think the way the files over-write makes this order relevant.  In any case, the way I originally copied the files gave me a problem in the F6 install, namely the M5288.sys (northbridge chipset driver) wasn't loading into Win install.  The result:  my SATA drives were invisible, only the IDE drive on my system was there (since it had my working WinXP x32 OS on it, I was hesitant to install there, lest I have to communicate with this forum via iPhone).
    Note to Svet:  The file you posted for me to make my floppy from, despite containing M5287.sys/M5288.sys/M5289.sys, only loaded M5287.sys in the F6 screen.  This may have been a problem on my end, but I managed to duplicate it by extracting the M5287 folder from the nVidia.com>download drivers>Uli>Integrated220.zip referenced in above post.  I think either the ulisata.cat, disk1, or txtsetup.oem files didn't contain the necessary directions for install to utilize M5288.sys, but I'm not a coder, so I can't say for certain.
    At no point (even with the proper floppy configuration) did the F6 screen appear to load M5289.sys, so I made a separate floppy with just that (from the files in nVidia.com>download drivers>Uli>Integrated220.zip), that loaded successfully as a second instance of hit "s"/insert floppy, and showed a second line below "M1575/M1697 INSTALLED", reading "RAID DRIVER INSTALLED" (or similar).  Whether this was a needed operation I don't know, since there was no more mention of it from Win install.  It did, however prompt me to re-insert the disk with M5288.sys on it.
    My final problem, to which I have no understanding of why, but is fixed so I don't care.  Maybe someone else will.
    Once I finally had a floppy disk with drivers that would "see" my SATA drives (including a 500GB data drive), I had the option of installing onto an unallocated space.  Great, except that the size was about 1.1TB!  I don't know how Windows came up with 200 + 200 = 1100, but there you have it.  I tried to install there, as there were no ~375GB spaces in view, and I was exuberant at just being able to recognize the drives that Win install had been hiding.  Each attempt to install onto this phantom TB of unallocated space resulted in an error that Win could not write onto a SCSI drive, and that I should turn it off.  (This is what sent me on my hunt for the "missing" M5289.sys that was present in the floppy disks, yet not installing through F6).
    Still no luck until I went into Disk Management in Windows (on the functioning IDE drive) and saw that it did see the RAID array as a single volume, but that it was at 1.1TB, unformatted, and uninitialized.
    Back to the BIOS, delete the RAID 0 array, rebuild it (all through CTRL+A), Windows sees it as a proper 372GB volume, initialize it, format it (probably didn't need to do this, but better than having to log back into Win x32 if I'm wrong), then back to try the XP Pro install again.
    Both M1575 & M1697 drivers load fine, I throw in the second floppy with M8289.sys on it just to make sure, and I'm blessed with a 372GB RAID 0 array to install onto.  Onward to Oz.
    Because, because, because, because, becaaaaause...
    Because of the wonderful things he does!
    Thanks to Svet, Fredrik, Wonkanoby, Stu, and anyone else who's had input or helped me through this mess.
    It's a sure thing my next MoBo will be MSI, so I may stop back and say Hi.
    Peace

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

  • Can't install Win7 with Raid 0 on a K9A2 CF

    Motherboard:    MSI K9A2 CF
    DDR:            8GB (4*2GB)
    Proc:      AMD Athlon 620
    HDD's:      2*Hitachi 640GB (same drive models)
    So the problem i'm having is that i can't get Windows7 to get installed in raid 0. I bought this set of hardware to do some experimenting with small business server 2008. I've installed SBS2008 in Raid 1, and seemed to work (but i've never crashed a disk to test it). The tests went fine, and since a month or two this PC/Server is doing nothing.
    Now i've been trying to get Windows7 installed but can't get it going with a Raid 0 setting (that's why i'm doubting if the RAID 1 with sbs was working correctly).
    First problem i'd run into was that my DVD wasn't accepted (missing device driver). I've created a bootable USB disk and seem to work.
    The problem starts when i should select the disk.
    First, i've setup the following in the RAID-Bios:
    I've done it with 1 array, or with 2 array's it doesn't change anything.
    In the normal bios (updated last night to the latest version, which actually slows the systems down during the install). I've selected RAID in this screen
    RAID (i've selected RAID)
    When i get the option to select a drive, it doesn't display any drives so I select the option to add a driver.
    These are the drivers i've downloaded:
    But when selecting these drivers I've get a negative response
    (with or without "Hide drivers that are not compatible......"
    When i download other drivers (I actually tried them all) i get some response:
    But when i select this driver, it takes several minutes to proces:
    But it comes back blank:
    When i select in the bios other options (like IDE)
    It comes default with a disk:
    But this is half of the array (1 drive). When i try to partition it, it fails. So it isn't accessible.
    Last thing: i've tested with all 3 available Bios options (IDE, RAID and AHCI) in combination with all (Win7, Vista and WinXP) drivers. But there are no differences.
    I understand i made a long post, but normally i just figure it out myself with researching on the web. I have tried everything i can think of. But it seems that:
    1. I made an error configuring the raid-arrays (with one big array, the results are the same).
    2. I made an error in the bios? (setting should be raid, other settings i should think of?)
    3. I'm working with the wrong drivers? I think i'm doing something wrong driver related but can't pin the problem.
    4. Or... ?
    I'm open to suggestions,  i've run out of option. :(
    Thank you.

    Quote from: Fredrik on 28-March-10, 23:42:10
    'Mostly aimed at galmoer. 
    If you don't mind the cat's response, this is perhaps useful:
    http://forums.amd.com/game/messageview.cfm?catid=261&threadid=117185
    Great link, seems to work. So after trying everything it was just a simple driver error.
    I've tried the drivers from 1337 but they didn't work. But the chinese drivers did work:
    http://www.rayfile.com/files/edf377e1-ec6f-11de-aad5-0014221b798a/
    I don't know how or what. But the RAID console seemed to get 2 disks (2 raid arrays) and installed and formatted correctly from there on.
    Installed Win7, booted and all the hardware was accepted.
    If anyone has a line to MSI or someone from MSI is reading this: If needed i'm willing to run some kind of debugger if it helps. But otherwise I would suggest checking the drivers offered on the website because the drivers on the MSI website are faulty for some of your users. On the K9A2 they will not work with RAID with Windows 7 64-bit (the official drivers I mean).
    Bas to answer your question: I have no particular interest in running a 64-bit operating system. But when it failed to work it became a challenge to get it working. I could have switched to 32bit immediatly but I don't like to give up the first moment something doesn't go as planned, and in the end I had so much time invested I just wanted it to work under 64bit .
    Frederik, thanks again for the link, really helpfull. Thank you all for helping and  giving suggestions.

Maybe you are looking for