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

Similar Messages

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

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

  • 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

  • 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

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

  • [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!

  • K7T266 Pro2 RU repaired but...

    Hello.
    Long time no see, I'm back now ^^
    Since the glorious times of my first Socket A system, much water have flowed on rivers so to say that many things happened, to me and in the world.
    Well, ok, to make long story short here's the thing.
    Some time ago (iirc some years) I were trying some spare hardware I have and when I was trying my old K7T266 Pro2 RU motherboard, after some tests, I did a mistake: I didn't installed properly a stick of ram, being partially inserted on one side and not fixed properly in its slot, so, forgetting and/or not noticing it, I switched on the motherboard and the poor board "poofed" out dead. The component that burned was nearby the ram slots, named D7 on the board and it was an SS12, a schottky diode: I thought so that replacing it would have sufficed to bring the board back to life, so I went to a tech assistance shop and they gave me an SS14 diode, claiming that it have the same characteristics of the SS12 being it just stronger than the earlier and that it can stand some more voltage, so I bought it for a few euro.
    After that I left all the mess apart since I lost interest to it, until now that I decided to try to fix the motherboard with the new component and see it I were right about it, but here came the first problem: when I were trying to unsolder the old burnt diode, it was really difficult, first off because it was too near the ram slots (so I were fearing to melt the plastics of the retention system), second off because the pin on the opposite side of the ram slots wasn't wanting to let go the track it was soldered! I struggled much to make it let go and after I succeeded, luckily, the track under was lifted from the board and I found it even cut!
    After swearing all of my calendar (don't mind about this, it's something we do much in italy, not always tho :P), I then tried to solder the new diode: it wasn't so difficult, and luckily i managed to sold back the cut track rejoining it and, because the whole thing wasn't so fix, I put even a drop of Superattak glue (cyanoacrylate): the result was very good, even tho couldn't be as if it nothing happened, but acceptable in general.
    I tried then to reinstall it on one of my old case desktop ATX lying around, throwed my old Athlon XP 1800+ Palomino and a stick of 256 MB DDR266 from an old Intel celeron 1.7GHz Willamette rig I got recently, and powered it up again: first attempt didn't do anything, after some cable checking (I don't remember now but maybe I reversed the reset and power on switches plugs ^^) it finally run... and *drum roll* it even did the POST! I was happy, then, and was thinking that everything were going the good way. But Murphy is always hiding somewhere, so my happiness wasn't lasting long.
    Ok, then, I decided to try to test it again to see if the hardware is still going, so I tried to install windows XP on a spare maxtor 80gib I had lying around, but with no much luck: firsts attempts hanged many times always on the same step (still on the early blue text-only screens), so I decided to try to run a memtest first, to check it before everything, and here comes the new main issue.
    I've installed memtest86+ v4.20 on an old 256 mb usb pendrive, successfully, because I needed to test the ram on some other computers, so I had the thing already ready for the task: I inserted it on one of the onboard usb plug (the v1.1 ones: naturally on the usb 2.0 it's not even detected) and tried to boot the board from it. Failing.
    I then tried it again on other computers: first my notebook, then some other rigs and all of them run the test correctly. To be sure I reinstalled the memtest on the pendrive, to no avail.
    I've tried to change the ram stick, I've plugged a 512 MB DDR400 one (not the one of the incident, but surely a working one, since I tried it successfully on other rigs), and change the slot too, still to no avail.
    The pendrive "boots", but it hangs prompting me:
    Quote
    SYSLINUX 3.86 2010-04-01 CBIOS Copyright (C) 1994-2010 H. Peter Anvin et al
    No DEFAULT or UI configuration directive found!
    Boot:
    What should I do?
    Is it because of the USB 1.1?
    Or maybe a BIOS issue?
    Or is it really my motherboard that's still TFU? I really hope not, I want to make it work again :(
    Anyway, of anybody of you that still have this glorious motherboard, can you please tell me if you can run memtest86+ from one of the ONBOARD USB (1.1) plugs?
    I take it from here, btw: http://www.memtest.org/ (http://www.memtest.org/download/4.20/memtest86+-4.20.usb.installer.zip to be correct).
    Please answer me, thank you in advance!!
    Edit: I forgot to say that I did the c37 removal mod for making the board compatible with 0.13 µ cpus, successfully, natuarlly :P

    Quote from: Bas on 06-February-12, 19:38:58
    Looks like the harddisk is broken.
    As it complains about the partitions just like XP does.
    No, I tried to boot the memtest from usb disconnecting everything else, so no hdd and no cd/dvd. I also tried to disable every integrated periferal and device: fdc, serials and parallel, midi, game, ide, raid, audio, modem and usb (1.1 naturally).
    Btw when I said that it complains about the partitions? :o
    Quote from: eagle3 on 06-February-12, 20:58:32
    Try memtest on a cd and boot from that; or use a linux live cd. Or the marvellous Ultimate Boot cd. http://www.ultimatebootcd.com/
    Also that board was built around the time of the bad cap debacle..
    I think I would have binned it..
    I followed your suggestion (but I thought it by myself too) and tried with the cd version of memtest86+, burning the iso onto a brand new cd (sigh, so much space wasted :p), and tried it: it finally worked, and I found that the 256 Mib ddr266 stick isn't compatible with the board, since the test didn't even started, another stick of 512 Mib ddr333 got errors (even 1 is too much to me, but it didn't have only 1 error), and finally the 512 Mib ddr400 tested fine for about 2 hours! That's a relieve ^^
    Unluckily even using the good working ram, it still don't want to boot memtest86+ from the usb pendrive.
    I still ask to anyone with my same board if they can do the same test, just to be sure that's just the board that can't boot properly from usb, or maybe a little incompatibility with my old pendrive.
    Thanks for now.

  • K7T266 PRO2 (MS6380 Ver 3.0) FDD Controler Problems

    I just purchased a new boxed OEM MSI K7T266 PRO2 (MS6380 - Ver 3.0) motherboard from JUST DEALS on E-bay which seems to have very sparce (or none) documentation for download on this site.  This is a non-raid board which has the AGP Pro video card socket (with the white lock and release lever at the end of the AGP female connector).  The board can also be identified with the following rather unique component/connector layout at the bottom end of the board:
    1.  In place of where RAID connectors attach to most of these model boards, this board has three aux USB connectors above the connector where the case front panel connectors usually plug in.
    2.  There are 3 CDROM audio connectors at the lower left below the last PCI slot.
    3.  To the left of the case front panel connector, there are two rows of connectors and jumpers which appear to be for  use with a case which has front panel audio connectors.  I believe the jumpers are for the purpose of selecting which audio output to use  (front or the standard rear sound output jacks.
    4.  The area between the last PCI slot and the USB and front panel audio connectors described above, the motherboard is rather blank with no components or even places where optional components have not been installed.
    5.  This motherboard has a Phoenix bios whereas most other K7T motherboards made by MSI seem to be AMI bios.
    6.  Finally, when doing a search for MS6380 Ver3.0 on Google, all the hits seem to be in Russian, German or French.   I suspect that this MB may have been manufactured for the European market.   BIOS display is in English, however.
    PROBLEM
    I have installed an AMD Athlon TBird 1.2 ghz cpu with 40mb WD hard drive which already had Windows Me and lots of other SW installed.  The system boots just fine from the hard drive and all works well except for the Floppy drive.   When I try to access the FDD with a know good disk installed with valid data, it comes on and spins up, the front light blinks and after about 30 seconds of continuous running, a message comes up "floppy disk not formated, format now: (Y/N)"  If I try to format the disk, it will not format and the system will ask to check to see if a disk is installed.   Changing floppy disks does not help, whether this is a disk which has verified data installed or just a formated blank disk.  I have tried two different FDD cables and 3 different Floppy drives and always get the same result.   I have checked for bent or broken pins in the connectors and found they are all good.  The FDD is a 1.44 MB and is connected to the end of the two-drive cable.  No other FDD is installed.  When I go into the BIOS setup, I verify that Drive A is installed as a 1.44BM 3.5" Floppy and None is selected for Drive B.
    I am currently at a loss to know how to proceed here.  I am wondering if this could be a BIOS problem but I am not sure if I can find BIOS update on the MSI Web site when they do not even list a MS6380 Ver 3.0 motherboard at all.
    I am considering installing a PCI FDD controller card but not sure that these are even manufactured.
    Please help.

    To Toenne:
    Thanks for the reply.  This has to be a BIOS problem since the FDD has to be accessed by the BIOS before any software or installed chipset drivers on the HD are ever used.  With my problem, I cannot even boot the system from the FDD.
    I tried resetting CMOS and that did not help.  I wonder if there is some kind of multi-mode floppy disk drive which this BIOS expects to see other that you standard old fashion IBM 3.5" 1.44gb drive.  The solution is likely to reflash the BIOS except with this odd MB serial number, I am not sure if I can find the latest BIOS software for this Phoenix chip.
    Does anyone know if there are any PCI FDD controller cards on the market where I could disable the on-board controller and use a plug-in card?
    Thanks

  • K7T266 Pro2-RU Hard drive size limit

    What is the maximum size hard drive that the BIOS can handle for the K7T266 Pro2-RU board? The official web site and BIOS updates are sort of vague... I know that the regular limit is 137 GB, and Windows XP Service Pack 1 has some kind of workaround. Will there be problems with installing big hard drives on this board? I'm not planning on using the RAID controller...
    Thanks  

    well that works for drives over 32gb and under 137gb on boards whos bios cannot see drives over 32 gb
    but ive never seen it proved to work with drives over 137 gb in a board cannot cope thith drives that big
    bios indicates the raid has 48 bit lba support so usde your big drives on that
    https://forum-en.msi.com/index.php?threadid=292&sid=

  • K7T266 Pro2 RU: Boot problem, wrong CMOS setting

    Hi All,
    I have had the Pro2 RU MB for a year now with very few problems. Over Christmas I was cleaning up my computer and was going to do a format :C and reload windows. When I went to start the computer after cleaning it up (remove all cards, clean up dust) I got 4 red leds on d-led. Tried everything (different memory, reset bios, unplug everything except video, ect) always 4 reds. Bought a duron 1.3 GHz put it in started the computer it start to post, went through fastrack raid screen and then I got "CMOS settings wrong" "press F1 to setup", "F2 load defaults" ...... screen I go F1 into setup make ajustments and everytime I save and I get 4 red leds on reboot. If I go F2 load defaults and continue it will try and boot, my hard drives are in a raid 0 array and it will check floppy, ide 0, cdrom by default so it can't boot. If I reboot at this point it will go 4 red leds. I can't flash the bios which is ver 3.2 because the bios protection is enabled and I can't change any settings. I could use some help this one has my stumped.
    I have tried 3 different power supplies, and that is not the problem.
    K7T266 Pro2 RU
    Duron 1.3GHZ, retail box HSF
    256MB Cruical pc2100 ram
    300w AMD approved PSU
    Geforce2 GTS 32MB
    2 60GB Quantum HD in raid 0 array
    Win 2k pro
    Cheers Rugger

    I have reset the cmos with pc unplugged...yes.
    I have read the FAQ at this site, I have used the search feature at this forum I have googled my problem searched a few other sites and I am stuck. I have been building computers and troubleshooting problems for 3 years now. If it was a new board I would RMA it at my wholesaler.
    It seems like there is a problem with the cmos chip because it will not accept any changes to the settings. As soon as you save the changes in the cmos the computer reboots and I get 4 red leds in d-led.
    Cheers Rugger

  • K7T266 Pro2 RU problem and question

    Hello
    I recently upgraded my CPU from an Athlon Thunderbird 1.400 to a AthlonXP 1700+ on my MSI K7T266 Pro2 -RU (MSI 6380 v2.0). The problem is that when i have the option Fast Command enabled in the bios, windows (Windows XP Professional) will crash and reboot after a couple of minutes (this happens even while i am browsing the net). With my previous CPU the fast command option didn't cause any problems. I wanted to ask if there is a way to solve the problem as the Fast Command increases the performance of my PC by 6-7%.
    Also while the mobo won't support the tb2200+  will it support a lower clocked tb cpu (like 2000+)? And will i have a problem if i take an AXP2000+ and o/c it to 2200+ or 2300+?
    Sorry if the above questions are already answered but its 02:40 in the morning and i don't have the courage to search the forum
    Thank you for your replies
    Palpatine
    AMD AthlonXP 1700+ @1600MHz
    Globalwin WBK68 HSFAN
    MSI K7T266 Pro2 - RU (3.6 bios, Via 4in1 v4.00)
    2 x 256 mb Corsair XMS 2400
    2 x WD400BB 7200rpm in RAID 0
    Leadtek Geforce 3 (with DetonatorXP 40.41)
    Soundblaster Live! Player 1024 (latest creative winxp drivers)
    Compex NIC 10/100 PCI
    Teac W540E CDRW 40x/12x/48x
    Pioneer DVD 106S 16x/40x
    Herolchi 350W PSU

    I had the fast command problem with the 512 mb generic ram (2x256) which i replaced later with the corsair XMS 2400, so i don't think that the cause of the problem is the memory. The memory now runs at 145 at CAS2 stable.
    I will try tomorrow flashing the mobo with the 3.3 bios and see if it solves it (i had the 3.6 before i installed the new cpu).
    Also i read in another forum that a mobo supports up to a specific cpu because higher clocked cpus require higher current and might destroy the circuitry in the mobo. If this is not true and its just a bios support issue then i will buy a XP2000+ and will try to o/c it to FSB 145-150 (2200+ to 2300+).
    Do you have the fast command enabled? I see we have the same mobo, memory and (almost) the same cpu.

  • Using K7T266 Pro2, Cannot find BIOS Protection function.

    I am using K7T266 Pro2 (MS-6380 v2.0) with BIOS update 3.70. I was reading the manual and suddenly I found a interesting function “BIOS Protection”, quote from manual:
    Quote
    This function protects the BIOS from accidental corruption by unauthorized users or computer viruses. When enabled, the BIOS’ data cannot be changed when attempting to update the BIOS with a Flash utility. To successfully update the BIOS, you’ll need to disable this Flash BIOS
    This is a really useful function but the problem is that I cannot find it! According to the manual it should be in the Advanced Chipset Features section, below the “PCI Delay Transaction” function. But when I go to my BIOS setup there is nothing below the “PCI Delay Transaction” function. And so I ask my self “where is the BIOS Protection function?”, I checked threw all the other sections but I could not find it… please help me, where is this function? Doesn't it include in the new BIOS update 3.70? Is anyone experiencing the same thing?

    Quote
    Originally posted by elpcmaster
    Downgrade to 3.3. It is the best and supports Linux and Norton Ghost, unlike 3.7.
    I'm assuming that by this you mean it does not support a network boot?  
    The reason why I say this is that I recently restored my K7T266 PRO2-RU BIOS Rev. 3.7 using Symantec Ghost Corp. Edition (MultiCast Server).  The Ghost image was stored on a remote machine, all that was needed was a floppy disk which was simple enough to configure using the wizard.  I had no problems -  BUT that doesn't mean the thing (my motherboard) isn't flakey as hell though.

Maybe you are looking for

  • Error while running AD User Target Recon

    Hi, We are getting the below error while running AD User Target Recon: [2012-09-04T10:07:32.262-04:00] [oim_server2] [NOTIFICATION] [] [oracle.iam.features.scheduler.agentry.operations] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.De

  • I just updated my iPhone to the 5.0 OS and now all of my calander events are gone. How do I get them back??

    I just updated my iPhone to the 5.0 OS and now all of my calander events are gone. How do I get them back?? Any help/advice is welcome!

  • Multiple HTML objects not aligning

    In the footer of my muse site, I have two HTML objects that should appear side-by-side. One is a live feed from a ratings website, the other is a Facebook like box. Both are pulling approved code, both appear great in Muse, Muse has previously publis

  • Rights to the apache server?

    Running Apache 2.0.59 on NW 6.5 SP 7. I gave my new web master rights to my httpdocs directory so he can handle all the web changes. Here's the fun part...every time he makes a change to a PHP file and saves it. Apache will display an error saying it

  • Memory or lack there of

    How can I tell how much memory I have and how much is used up? I have an iMac G5 (late 2006) I think it is 1GB. When I go into utilities I'm not sure what I am looking for.