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?

Similar Messages

  • 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: 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 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 stability problems

    In the last few months I've been experiencing general stability issues with my K7T266 PRO2-RU.  In attempts to try and resolve these issues I've flashed the BIOS, updated drivers, reinstalled Windows numerous times, checked for leaking capacitors and reduced the machine to nothing more than the essential hardware (video card, memory, processor).  
    In troubleshooting I've discovered very little, except that none of these things have been very successful and some odd things that are outlined below.  
    1. The machine still randomly reboots, and programs crash inexplicably without error.
    2. WindowsXP invariably hangs during installation to the RAID controller (RAID 0).  I've tried various driver versions but all reproduce a similar result.  I suspected there may be a problem with the drives, but that doesn't appear to be the case as it does this regardless of the drives used - 2 Maxtor DiamondMax Plus D740X'(s).  It also does this when using 2 Western Digital WD300BB'(s) and new cables, so I know it is NOT my drives.  Windows will install to one drive but is as previously stated - unstable.
    3.  I've tested the machine using another video card, in addition to running the video card and the memory in my other box, of which both cards are good and run rock solid under stress testing.  
    Any ideas or suggestions are welcome.
    Here's the config:
    MSI K7T266 PRO2-RU (Bios Rev. 3.7)
    Athlon 1800+ (Not OC'd)
    256MB Corsair XMS PC2400 (x2)
    Asus GeForce 6800
    Maxtor DiamondMax Plus D740X (x2)
    Creative SB Audigy Platinum
    3Com 3C905B NIC
    Enermax EG-465P VE
    Thanks...

    Quote
    Originally posted by Rob454
    Hi,
    You sure it isn't a memory problem?
    try http://www.memtest86.com
    Thanks for the suggestion,  
    While I was waiting to see if anyone would quickly reply I read through previous posts to the forum and found a link to memtest86.  I've already tested one module to isolate bank 0 as known good and it passed.  2nd attempt I put both modules in, 1 in bank 0 and the other in bank 2.  I began receiving errors only after 5 min.  I never suspected this would be the problem as I tested the memory in another machine and previously with an obviously inferior memory test app and it passed.  No big deal though, at least now I've discovered the problem.  
    I'm now doing additional testing to the suspect module.
    (Errors in Bank 2 - Next trying it in Bank 0 which I know worked, just to rule out a possibly defective bank)
    Update:
    Errors all over the place in Bank 0,1, and 2 - Looks like the module took the dirt nap.  Time to use that lifetime warranty.
    Thanks again.

  • 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

  • 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 and Problem with a FEW DISPLAY ADAPTERS ...

    Hello ,
    I was using my mainboard with 32 MB Creative Riva TNT2 Ultra until creative's fan was damaged . I tried 16 Creative TNT2 m64 display adapter of a friend of me , but it didn't work with K7T266 PRO2-RU. Many sounds are coming from mainboard while D-LED shows Testing RTC (or boot attemp, I'm not sure about that) (Same symptoms with "no graphic adapter" - I tried again after unplugged the display adapter - )
    At the beginning I was thinking that the 16 MB creative graph adap. was broken . So , today I bought a new graphic adapter 128 MB of Creative 3d Blaster5 Radeon 9200SE . When I plugged it into mainboard , I saw the same problems with 16 MB Creative TNT2 m64 . After that , I found another 32 MB Creative TNT2 Ultra from my friend and it worked with my mainboard FINE .
    - I tried all of the old bioses of MSI K7T266 PRO2-RU
    - I tried to start the computer with no any other devices (such as HDD , sound card , tv card etc. ) . Only display adapter was plugged in the mainboard , but it didn't work . System hanged up everytime I tried .
    - I made some bios adjustments which are suggested at this forum ....
      But none of these worked ....  ?(
    What is the problem ? Why only 32 MB creative TNT2 Ultra is working with my mainboard , but 16 MB Creative TNT2 M64 and 128 MB Creative 3DBlaster5 Radeon 9200SE are not  while all of them are working FINE with an old PII mainboard . (tvout+DVI)  I'm looking forward to hear from you . , Help me please .
    Ps : Can new beta bios solve that problem ?
    XP pro
    2100+ 0.18m XP CPU with coolermaster CP5
    40 GB Seagate Barracuda IV
    300 watt Codegen Power Supply
    2*256 MB Kingston DDR 2100 Memory
    ( No floppy , no souncard , no tv card etc , no any other devices like cdrom , dvdrom , cdrw etc.)

    That's it!
    I provided a few PSU's from my friends and tried 420 watt thermaltake and 520 watt VANTEC Stealth 520A PSU  ...
    Same situation happened and 128 MB Creative ATI Radeon video card didn't work   ...
    The problem can not be about PSU ...
    I tried two different brand of fx 5200  (128 MB ) video card on my system (with 300 watt codegen PSU) . Everything is ok  .
    And I also tried the RADEON card on my friend's computer which is running with 230 watt Elan Vital PSU . It worked perfectly ...
    So what can I think about that situation?
    The Answer is : There is something about MSI mainboard ... When I wanted to contact with support center via e-mail , I got an automated e-mail answer which is not completely able to solve any of my problems.
    Besides , I saw the problems between brand new Nforce mainboard of MSI and ATI video cards ...
    SO , if we get all of these informations together , we can say "THERE IS SOMETHING ABOUT MSI" ...
    The solution is not buying expensive PSUs...
    That's really bullshit , I can buy a brand new mainboard instead of an expensive PSU.
    Finally , I bought an Asus mainboard , everthing is going ok now!
    I'll not buy products of MSI anymore because they didn't do anything to solve my problem . Goodbye MSIIIIII ....................................... ........

  • K7t266 Pro2a onboard sound problems

    Hi,
    Everything works really well on my PC except the sound.  I cannot hear anything, there is simply no sound.  My motherboard, the k7t266 Pro2a has an onboard soundcard and I can't seem to get it to work  :(
    I am running Windows XP, by the way.
    I've installed the DirectSound AC'97 Audio drivers, checked the volume, checked to see if the speakers were plugged into the right hole, and I checked to see if the jumpers were correctly fastened.  No luck :( Oh yea and I checked to see if it was enabled in the bios. Still doesn't work...
    Any help at all would be greatly appreciated, thanks so much!

    yea i have and they work just fine, apparently my computer detects that it's there, and i can run wimamp, and I can't hear the sounds.

  • K7T266 Pro2 lock up problems...frustrated...

    I have an MSI K7T266 Pro2 with latest bios and 1 512mb PC2100 ram - everything has been running fine until I started messing with bios settings.  A friend setup bios and I "thought" that the DDR was running at 133mhz, my FSB was at 133mhz (266mhz).  Since then, I can get my CPU to run at it's default speed - 1.733ghz and 266 FSB, but I can only get my RAM to run at 200mhz or 266mhz.  I'm having random freezes/lock ups in Windows XP Pro - only when I'm doing something.  Left my puter on all night last night and when I woke up, the puter did not freeze.  It doesn't make any difference if I play music in the background while messing around on the net, etc.  Any thoughts?  Is it possible to run my 2100+ (palomino) at default speed/266mhz FSB and my RAM at 133mhz?  Any help is greating appreciated...I'm going crazy!
    Bryan
    [email protected]

    Hello.
    Your CPU is a 133MHZ (266DDR) FSB CPU and you ram is also 133MHZ(266DDR).
    So all you need to do is set the FSB/MEMORY clock to 133MHZ.
    Then change the CPU multiplier to AUTO.

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

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

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

Maybe you are looking for