K7T266 Pro2 RU - RAID controller as standard IDE port?

Hello,
I have an old MSI K7T266 Pro2 RU board, which includes a RAID controller.
Currently it is set up with a stripe RAID array comprising of 2 X 40 GB hard
discs as a single 80 GB array. I wish to replace this with a single 200 GB
drive, and am wondering can the RAID controller on the board be used in this
fashion - as a standard IDE controller, suitable for running a single IDE
hard disc? Or would I need to use some unofficial BIOS on the RAID
controller to convert it to a pair of standard normal IDE controllers? Currently
the RAID array is nearly full with files, and thus I want to know for sure
this will work before backing up the data, erasing the RAID array, and buying a single new 200 GB drive.
Thank you,
Simon Howson

Hi,
I don't want to run a stripe aray, I just want to replace one of the 40 GB drives for a 200 GB drive, and then just have 2 individual IDE drives on the RAID controller oprating as 2 seperate hard discs. Will this work?
It has been ages since I set up the RAID array, and can't remember if it is possible to just format and have them running as single drives, or if the RAID controller can only run in RAID modes such as stripe, or mirror, or mirror + stripe etc.

Similar Messages

  • K7T266 Pro2 RU, Raid-0 & Linux

    When I try to install either Red Hat 8.0 or Mandrake 9.0 on my K7T266 Pro2 RU, which has 2 x 40GB drives configured as RAID-0 (ie 1 x 80GB), both versions of Linux see the two physical drives and not the one logical stripe array. Why? It almost seems that the Linux drivers for the Promise 20265R are treating the raid channels and normal IDE channels. I want to install Linux onto the RAID-0 stripe!
    I have searched for guides/tutorials on installing Linux on RAID, but all the ones I found only talked about RAID-1 (Mirroring).
    Windows 2000/XP only sees the one logical drive.
    Any help would be appreciated!  
    Chris.

    The installer is wrecking the /etc/raidtab file when trying to detect existing raid arrays.
    Solution: Format a floppy disk with a DOS filesystem (in Linux, you can use the command "mkdosfs /dev/fd0"). Copy
    use detect_devices;
    package detect_devices;
    log::l("PATCHING");
    *raidAutoStartRaidtab = sub {
        my (@parts) = @_;
        log::l("patched raidAutoStartRaidtab");
        $::isInstall or return;
        require raid;
        #- faking a raidtab, it seems to be working )
        #- (choosing any inactive md)
        raid::inactivate_all();
        foreach (@parts) {
       my ($nb) = grep { !raid::is_active("md$_") } 0..7;
       output("/tmp/raidtab", "raiddev /dev/md$nb\n  device " . devices::make($_->{device}) . "\n");
       run_program::run('raidstart', '-c', "/tmp/raidtab", devices::make("md$nb"));
        unlink "/tmp/raidtab";
    use raid;
    package raid;
    *prepare_prefixed = sub {
        my ($raids, $prefix) = @_;
        log::l("patched prepare_prefixed");
        $raids or return;
        &write($raids, "/etc/raidtab") if ! -e "/etc/raidtab";
        eval { cp_af("/etc/raidtab", "$prefix/etc/raidtab") };
        foreach (grep { $_ } @$raids) {
       devices::make("$prefix/dev/$_->{device}") foreach @{$_->{disks}};
     to the floppy disk. Remove the floppy and reboot using the Mandrake Linux 9.0 CD1 to do a CD-ROM installation. During boot, press F1 at the splash screen, then place your floppy disk that contains patch.pl in the floppy drive. At the prompt, type "patch", then follow the installation as usual.
    Hope that helps

  • Use 694D Pro-AR Raid Controller as standard

    I am currently runnign windows 2000 on this system, and i was wondering if it was poossible to use the Fastrak 100 Raid Controller that is built in as a standard IDE without having to use raid?

    You can build a 'fake' RAID array on 1 drive and use it this way.

  • K7T266 Pro2-RU raid crash

    I have had this system up for about 8 months. One day when converting mp3 to wav the system crashed. When rebooting I would get a black screen or it would hang during the boot process. I was using XP and W2K server - never had an issue until this crash, and now problems when booting with either.
    I attempted to do update the raid drive (got the grand message re: stop what the heck your doing or face certian death or Continue and prepair to die - when updating the driver in xp). Nothing worked. So I fdisked the drive (20gb ibm) drive that was my c: and reinstalled W2k Server...still seeing the same issue.
    Raid array says it is functional, but that is about it. System hangs durning boot, and if ide 3 and or 4 is unplugged, I can then boot up and work off of the 20gb drive.
    Anyone, anyone?
    System:
    2000 server on a 20gb ibm
    1.5gb of Ram
    2- 40gb ibm darkstar hard drives in array
    Promise raid lite 1.13
    K7T266 Pro2-RU
    tried new cables,
    changing around the jumper,
    latest raid drivers from our friends at msi,
    but today I am thinking hammer may do the trick...

    Still no luck, today I went out and downloaded
    File Scavenger 2.0.
    It could see the array, and for 40 dollars I can buy a license to repair the drives...or so they say.
    Does MSI have any raid repair utilities, or does anyone know of any good raid repair programs

  • K7T266 Pro2 RU (Raid Problem)

    I have 2 HDD (WesterDigital 40gb)
    My bios is 3.6 hacked (Raid bios V2.00.24)
    I run cpu 1.7ghz
    Everything works except my drivers on raid.
    i try use ide 3 for 1 hdd and ide 4 for 2 hdd
    (When my system boots up and it's doing some raid detecting/testing) it simply freez up and my raid activity light is on forever.
    I did try change settings like on raid make 1hdd master othr slave... but endup in same situation.
    I noticed when my settings like this.
    IDE3 or IDE4 (1 HDD Master other Slave) some times it's go through.
    If I run just 1 HDD raid have no problem but as soon i try use 2nd 1 it's just start doing that freezing stuff.
    I did test both hdd on regular IDE 1 and they work fine (atleast quick test ~5minute)
    If any of you have and idea please let me know.
    PS it's sux to be on 70mhz Computer (my backup pc )

    I did try following settings.
    setting 1:
    IDE 3 (HDD 1) No Jampres
    IDE 4 (HDD 2) No Jampres
    Freeze at RAID checking/Detecting
    Setting 2:
    IDE 3 (HDD 1) Cable select
    IDE 4 (HDD 2) Cable select
    Freeze at RAID checking/Detecting
    Setting 3:
    IDE 3 (HDD 1) Slave
    IDE 4 (HDD 2) Slave
    Freeze at RAID checking/Detecting
    Setting 4:
    IDE 3 (HDD 1) Cable select/Slave/No Jampres
    IDE 4 (HDD 2) Disabeld (No Power to HDD)
    Works fine
    Setting 5:
    IDE 3 (HDD 1) Disabeld (No Power to HDD)
    IDE 4 (HDD 2) Cable select/Slave/No Jampres
    Works fine
    Setting 6:
    IDE 3 (HDD 1) Master
    IDE 3 (HDD 2) Slave
    Did work cuple times but usualy Freeze
    Setting 7:
    IDE 4 (HDD 1) Master
    IDE 4 (HDD 2) Slave
    Did work cuple times but usualy Freeze
    Setting (Regular IDE 1) 8:
    IDE 1 (HDD 1) Master
    IDE 1 (HDD 2) Slave
    Detect both HDD and works fine.
    PS I used another hacked bios with (Raid Bios 1.31 (B22)) It some what detect HDDs but for some reason when I try Install Win XP (Trying to format 20GB) it basicly formating really slow (After 2-3 hours it was done on 50%)
    IS there anyw ay to test RAID under dos some how?

  • K7t266 pro2 ru raid problems after bios update

    i updated my bios to most resent ver. as of 12/20/03 and i was going to raid two 120 gig maxter ata 133 hdd.  so i enable onboard raid in bios and save n exit. but it act's like there is no raid the scanning screen is not there nor the screen to access the raid setup. so i go back to the bios to verify the bios settings and raid is still enabled and to find out there is no fastrak 100 boot option there any more just cdrom floppy hdd-0 and disable thats it...any help out there? could use a little. need any more info let me know.  oh! i rolled back my bios to ver. 3.0 to see if it would fix it ....nope :(

    ok got it, flashed bios back to 3.7 and solved my problem woohoo!!

  • K7T266 Pro2-RU hard drive size..

    Hi !
    I tried to find a solution by searching the forums but this exact question
    nodoby asked.
    I bought new HDD (Seagate ST3160023A) 160 G / ultra ATA and
    i cant get it working.
    Board is K7T266 Pro2-RU and it seems that BIOS is recognise new
    HDD but i cant made any partitions and/or format it.
    I tried it many different ways, with other HDD:s
    Master, Slave, Cable Select.
    Seagate's own disk utility hangs, Windows xp (SP1) Disk management hangs and so on.
    Is this some known issue or is it so that the HDD is broken ? if
    i understood correctly, mainboard should support HDD:s up to 160Gb ?
    Thank you !

    Quote
    i understood correctly, mainboard should support HDD:s up to 160Gb ?
    Correct for the onboard raid controller, but the ide controller can only manage drives up to 137GB as far as I remember.
    Btw: Moved this thread to the via section, maybe anyone there else has some idea.

  • Xserve 2006 RAID Controller

    Hi Everyone,
    I have an Intel Xserve 2006. Recently the RAID controller card failed so I popped back in the regular SATA controller (that it originally came with) and ordered a new RAID controller.
    I am pretty sure I have the correct one for the 2006 model but it does not seem to work. I have no battery on it (thought one would come with it) the original expanded and I am pretty sure broke the other RAID controller.
    Any ideas why this new one is not working also? Is it the battery?
    Many thanks for any suggestions.
    David Lee

    Hi David,
    Have you got the new RAID card in there now or the SATA backplane? I'm in London as well so will try and help you out as much as I can if you need it.
    Contact details on my profile.
    Thanks
    Beatle

  • MSI K7T266 Pro2-RU - problem with the lite-raid - would like to use it as a normal ide

    Hi!
    I tried to install a single drive on the raid-controller and create a single array for it.
    For some reason the disk management in Windows XP does not see it, even though
    I have updated the related drivers. However, the Disk management showed it the first time after I had installed the HD onto the raid, but as I could not do anything intelligent with Disk management in regard of the HD, I removed the drive from Disk management with that effect that the disk management does not recognize the drive at all, even though I have now re-created the array on the risk, disabled and enabled raid on the Bios.
    I read that there exists modified bios for MSI KT3 Ultra ARU BIOS, which will turn the Raid into regular IDE. That would be something that would most probably be the best way to proceed for me. However, do such bioses exist for MSI K7T266 Pro2-RU? Any other suggestions on how to get the disk management to succeed in recornizing the IDE on the raid-controller would be good to hear as well.
    Yours sincerely,
    Tero

    Ok, I tried updating with the hacked 3.7 Full Raid Bios. Now I seem to have another problem: even though the hacked bios recognizes my HD, it thinks it's about 130 GB, when it in reality would be 250 GB. The hacked bios seems to work ok with Disk Management in Windows XP too, so it's a shame that the hacked bios doesn't seem to have a support for large disks. On the other hand the link at Lumberjacker was dead for the hacked bios v3.6, I would have tried it, if it would have provided me with a good solution to my problem.
    I then went back and installed the official v3.7 bios and the lite raid does now recognize the HD being 250 GB, but the Disk Management just states "Missing" in regard of the HD and does not let me do anything fruitful with it. I looked the HD's properties and the Device Manager just states "Hardware device not connected code 45".
    How in earth could I manage to make this work now (I do not want to move my other HD:s as they are full of stuff and don't want to risk losing any content)?
    General specs of the computer: IDE 1: 60 GB and 120 GB Matrox, IDE 2: Nec2500 and Sony DVD-Rom, Athlon 1800+ XP, 512 MB memory, Ati 9700 np, Network adapter card. The new HD to be added is a 250 GB WD (have removed the jumper)
    Thank you for any tips,
    Tero

  • Raid 0 Failure! XP Pro won't read array on MSI k7T266 pro2 *URGE

    Before anything else, thanks for reading and I hope you can help:
    I have an MSI k7T266 Pro2A-RU motherboard with 512MB of Mushkin RAM, AMD XP 1600+, a Geforce2 MX400, Audigy Soundcard and a cheap PCI NIC card.  I consider myself an above average technician and I've come up on a problem I can't figure out.  There is about 80GB of data at stake here:
    I have 2 IBM Deskstar 40GB 7200 RPM drives that were configured in a RAID 0 (stripe) configuration over a year and a half ago.  This gave me a total of 80GB online.  Windows XP Professional was installed and the drives have been running fine every since...
    The system was practically bulletproof and it was very rare it ever locked up for any reason.  A few days ago, however, the system locked up about 4 or five times.  There was no software or hardware that had been added or installed and system use hadn't really changed up or down. I run up to date antivirus software (Command Anti-Virus), run behind a secure firewall and watch what I open.  The lock ups were random, but happened when I was away from the computer. ( I leave my system on all the time).
    Being a bit paranoid, on 1/28/03, I acquired an 80GB Maxtor drive to install to back up my datafiles.  Before the install, I notice the system had locked up at least once that day, so I figured I would hurry up and get the drive in to back up.  I installed the 80, booted, configured it in XP and made it active and transfered a few test files over.  No problem.  I made the decision to back up my data files before bed and continued to work for the next two hours.  The system ended up locking up with a windows blue screen STOP error message: KERNEL_FAULT_INPAGE_ERROR when I tried to run a program.  Thinking little of it, I rebooted the computer to find I could no longer access the data on the RAID.  
    I've tried nearly EVERYTHING I can think of.  (You can already assume I've done the basics (check/replace the cables, etc).  Here's a list and the results:
    ---- Reboot in all available modes (Safe,  Safe with NW, Normal, Last known, etc).  They all FAIL.  In safe modes, you can see where the system actually tries to boot off the array (runs through driver files and stops on MUP.SYS) and hangs. Same result with all other drives removed except the RAID.
    ---- Installed another drive, loaded XP with the raid controller files (By the way, it's a Promise ATA 100 "lite" controller), plugged the RAID back in and it hangs on boot up.  Safe mode gives the same results.  Tried the same thing with Windows 2000 (so I could access the NTFS partition) and Windows 2000 won't load when the array is plugged in, but loads ok when it isn't (used the 2000 driver for the RAID controller for this attempt).   Safe mode gives the same results.
    ---- Removed all drives except the Array and tried to reload XP (with the array drivers downloaded again from the site.) No effect.  System hangs.
    ---- In a last ditch effort, I have access to Winternals Administration Pack 2002 of all of their tools.  ERC Commander, designed for this type of problem, Disk Commander, and the other tools all do the same thing:  Any time the system attempts to read from or access the arry, the OS will hang.  It won't even check for NTFS compatibility in the ERC commander program booting from a boot CD, and for those that are familiar with it, the Disk Commander program blue screens with a STOP: 0x000007B (0xF896963C, 0xC0000034, 0x0, 0x0) error. Research has told me this is an INACCESSABLE BOOT DEVICE message.
    These are the main highlight major attempt things and there's a few things in between I've tried (like using Norton Ghost to try and mirror the array to the 80GB.  Norton ghost said there is an error reading the partition and can't go any further (Returns an Internal error))
    I'm at the point where I have run out of available options and don't know what else to try.  I have since purchased the exact same motherboard off e-bay to see if it just so happens to be the controller and to see if my RAID will come back so I can at least read the data off of it.  It should be here in a few days.  If that doesn't work, I'm toasted.  Could I be fighting a hardware (drive or board or controller) problem.  Is the array THAT corrupt the OS can't read it???  
    If anyone has any other bright ideas, I'm willing to try about anything short of damaging the array. Any help is greatly appreciated.  Please post here, or e-mail to [email protected].
    BTW, the Promise BIOS is Fasttrak 100 "Lite" v 1.31.1(Build 30)
    Thanks.
    - Chuck! ?(  ;(  ;(  ;(  ;(  ?(  

    got one but its lightley used for storage but amd forum storage is full of tales of woe with them
    type deskstar and problems in goggle for a laugh

  • K7T266 Pro2-RU and Promise FastTrak100 RAID Drivers

    Hello
    I am trying install my 2 new Seagate HardDisk in the IDE RAID on my K7T266 Pro2-RU motherboard without success.
    MotherBoard's IDE RAID BIOS can see the two 160GB HDD that I have installed and Windows XP can not see it with the lastest BIOS v3.7 and the lastest Promise FastTrack IDE RAID Controller ( v2.0.90 Build 10 ). Both HDD are not detected by Windows XP by using F6 key, However my 2 40GB HDD are detected by Windows XP without problems.
    I have 2 K7T266 Pro2-RU motherboards and they have the same problem, I think that the really the problem is the fasttrack.sys driver  Could be it updated ?
    Does anyone have new Promise Drivers for Windows XP ?
    Cheers.

    Yes I do, I have used that drivers for many time and they are very old in this moment because Seagate Barracuda 7200.9 160GB are not visible, only my IBM DeskStar 40GB works fine with that drivers.
    I have tryed to use the last fastrtrack.sys v2.00.0.25 from Promise Technology without success which has support to large HDD above 137GB and needs BIOS update to my motherboard v2.00.0.24 in FastTrack (tm) "Lite" BIOS v2.00.1030.23.
    http://www.promise.com/support/download/download2_eng.asp?productId=15&category=driver&os=0&go=GO
    I have installed Windows XP SP1 in my IBM DeskStar 40GB on IDE3-RAID and works fine, later I have installed another HDD Seagate 160GB on IDE4-RAID and Windows XP can not see it.
    Later and I have put the new fasttrack.sys (v2.00.0.25) driver in Windows XP and with a reboot machine, Windows XP can see my new HDD160GB HDD like a 149.05GB unpartitioned drive ( which is corret ). When I put the old fasttrack.sys driver Windows again can not see the 160GB HDD 
    Later I going to install the Windows XP SP1 in the new Seagate Barracuda 7200.9 160GB and the IBM DeskStar 40GB by using F6 key and neither HDD were visibles. So I can not continue with the installion 
    Later I going to install WinXP again with the old drivers and once again only IBM 40GB is visible.
    I need your HELP MSI Support Team.
    Thanks in Advanced.

  • More than 4 IDE devices using the Raid controller on the MSI-6567 645E Max2-LRU ?

    Here is the specs page of the board
    http://www.msi.com.tw/program/products/mainboard/mbd/pro_mbd_detail.php?UID=79
    I have a HD and a CD-ROM drive on the first IDE controller, and an HD and a CD-writer on he second IDE controller
    Since the specs say the board only supports 4 IDE devices I was wondering-
    1) Can I connect another HD to one of the onboard Raid controllers, and work with it in addition to all the other IDE devices currently plugged in, without RAID?
    i.e. CD-writer, CD-ROM, and 3 HD's working together ?
    2) Can I connect 2 more HD's, one to each onboard RAID controller and have them work in raid in addition to all existing IDE deviced?
    i.e. CD-writer, CD-ROM, 2 HD's and 2 more HD's in RAID format working together ?
    Thanks in advance..  

    But like I said, I do not intend to connect CD-ROMS to the RAID controllers, only HD's - the CD-ROM and CD-Writer are currently connected to the normal IDE controllers and I don't plan on changing that in any case
    My question was whether or not i can add more HD's to my current system by adding them to the RAID IDE's
    simply put, to be 100% clear my question is this -
    will the current configuration work:
    IDE 1 = CD-ROM + HD1
    IDE2 = CD-WRITER + HD2
    RAID IDE1 = HD3
    and will this one work:
    IDE 1 = CD-ROM + HD1
    IDE2 = CD-WRITER + HD2
    RAID IDE1 = HD3
    RAID IDE2 = HD4
    when HD3&4 work in RAID mode
    Thanks again for you help
    RE your suggestion - why not put a CD-ROM and an HD on the same IDE ? that way my HD's are connected to different IDE controllers for better performance

  • [VIA] RAID 0 Data Recovery with MSI K7T266 Pro2

    Well my Motherboard has seem to have gone TU on me, and it is well beyond it's warranty. 
    I have two 60gb HD running in Striped mode using the on-board raid.  If I were to get the same motherboard, would this allow me to see the striped array and recover my data, or am I at a loss?  I have some of the data backed up, but since most of it isnt, because I have nearly filled my 120GB of space and I don't have a good backup solution. 
    Thanks.
    Current Config:
    AMD XP 1900+
    MSI K7T266 Pro2
    GeForce 4400Ti
    Two WD 60gb @ RAID 0.

    Quote from: Richard on 29-November-05, 06:33:47
    SporkLover,
    My current RAID Array is on its 6th or 7th mobo (Multiple different mobo chipsets and different controllers) and I have not lost either the Array, Partition, or any Data.
    You just have to make sure that you make the primary HD the same on the new RAID and it is Crucial that you use the same Stripe Size, if you do not, then all data will be lost!
    Take Care,
    Richard
    Rich,
    Thats comforting to know!  This setup has been the best, and most reliable, so when I bought all of the components years ago, I set it up and forgot most of the parameters. 
    I completely used up all of the available space so I think that should make guessing that stripe size easy.
    osnavi, not entirely sure what happened.  It started to lock up on me randomly, and after much trouble shooting and frustration, I gave up.  Eventually I saw the problem, a few of the capacitors on the motherboard started to peak, and eventually busted.  Not sure what caused it, maybe it was my power supply.  Its an Enermax 400W, and when I bought it, it was within the required specs for the processor and Mobo.  There was plenty of case cooling, as well as CPU Cooling... so it is a great mystery to me.
    Thanks again!

  • Second IDE Raid controller

    I have  MSI K7T 266 Pro 2 RU board, onboard raid,  i want to install second raid controller card.  I cant get into a bios of second card.  Second card is CMD PCI - 0649 Ultra 100 Raid controller.
    If the a problems when running two raid controllers in one system?
    And how can i get into the bios of second raid card.
    P.S.  card is installed in Windows XP fine.  i can see two hard drives connected to it.  Right after raid bios on onboard raid it looks windows.
    Please help
    Thanks

    Quote
    Originally posted by pcman12345
    My pc boots of onboard raid. (2) 40gig drives.  What do new drivers have to do with getting into bios of pci raid card.  I have all the latest drivers anyway.
    Any other ideas?
    Thanks for your help.
    It sounds like you are booting from the promise RAID controller.  If so, you are well familiar with the way in which it dominates the bootup process for the first 30 seconds or so.........(dots look familiar?...)
    I wonder if the second RAID card is also initiating its bios sequence at the same time underneath the Promise boot screen (underneath, so to speak) so that when the Promise routine is finished, so is the CMD routine, and you proceed from that point with both RAID controllers initialized (but can only see one of them at a time from the bios screen.)
    Do you you have "boot from other device" enabled in the bios?  If so you might try disabling that to see if it will sequence the RAID controllers initialization so that the CMD bios appears after the Promise bios is done (I assume you have the onboard Promise array selected as the boot device.)
    A bit more trouble would be to reboot to main bios,  disable the onboard RAID controller in the bios, save and reboot.  At this point the Promise bios will not display and you should see a CMD bios display which you could manipulate--then reenable the Promise controller to boot, etc.  If you disable the Promise controller and you still don't see a bios for the CMD RAID device you need to look elsewhere.  Also, it might be that the CMD bios access requires a certain key sequence pressed during post to display?....Just some random thoughts...

  • K7T266 Pro2-RU Promise FastTrak100 RAID Drivers

    Hello dudes,
    In November of the year 2005 I had big problems with the detection of the hard disk installed in the promise raid controller when I was installing Windows XP SP2, then, MSI did not know how to solve the problem for me...   
    Now I have decided to share my experience with you because was very hard to solve it... 
    From 11/22/2005 until 09/24/2008 I have been tested a modified/hacked Promise FastTrack100 Series Windows Drivers without problems, it was and is the lastest one Windows XP Promise driver ( FastTrak100 Windows Drivers v2.00.0.34 ) wich is working fine with Windows XP SP3
    I have gotten to fix the Windows XP HDD detection ( Seagate's Barracuda 7200.9 160GB HDD ) by using above drivers.
    Only put drivers on floppy disk and remember pulse F6 with modified drivers because original do not works
    FastTrak100 Windows Drivers v2.00.0.34 Original Drivers
    Code: [Select]
    http://rapidshare.com/files/147873298/FastTrak100_Windows_Drivers_v2.00.0.34.zip.html
    FastTrak100 Windows Drivers v2.00.0.34 Modified Drivers
    Code: [Select]
    http://rapidshare.com/files/147873238/FastTrak100_Windows_Drivers_v2.00.0.34_Full.zip.html
    I am sorry for my bad english :(
    Cheers.

    Yes I do, I have used that drivers for many time and they are very old in this moment because Seagate Barracuda 7200.9 160GB are not visible, only my IBM DeskStar 40GB works fine with that drivers.
    I have tryed to use the last fastrtrack.sys v2.00.0.25 from Promise Technology without success which has support to large HDD above 137GB and needs BIOS update to my motherboard v2.00.0.24 in FastTrack (tm) "Lite" BIOS v2.00.1030.23.
    http://www.promise.com/support/download/download2_eng.asp?productId=15&category=driver&os=0&go=GO
    I have installed Windows XP SP1 in my IBM DeskStar 40GB on IDE3-RAID and works fine, later I have installed another HDD Seagate 160GB on IDE4-RAID and Windows XP can not see it.
    Later and I have put the new fasttrack.sys (v2.00.0.25) driver in Windows XP and with a reboot machine, Windows XP can see my new HDD160GB HDD like a 149.05GB unpartitioned drive ( which is corret ). When I put the old fasttrack.sys driver Windows again can not see the 160GB HDD 
    Later I going to install the Windows XP SP1 in the new Seagate Barracuda 7200.9 160GB and the IBM DeskStar 40GB by using F6 key and neither HDD were visibles. So I can not continue with the installion 
    Later I going to install WinXP again with the old drivers and once again only IBM 40GB is visible.
    I need your HELP MSI Support Team.
    Thanks in Advanced.

Maybe you are looking for