NF7-S Sata RAID Problems.

sins55sins55
edited March 2004 in Hardware
hi there, ive been browsing the forums to see if anyone has posted my problem but it seems that it hasnt been posted before (used search and Faq sticky) and to be honest im completly out of idea's on why im getting the problem, either way on with the issue im trying to resolve.

right, im using a abit nf7-s v2.0 to raid my 2 seagate barracuda 120gb 7200rpm drives, using the sata channels and PATA>SATA adapters that came with my board and one borrowed from a friend. (drives are both set to master and sata>pata controllers are idential)

im using the latest bios and sata controller drivers from abit.com.tw, and have tried evey bios/driver under the sun to try and fix this.

when i install winxp (using f6 to install the sata driver :D ) it formats the drives, and starts to copy files, the problem begins after reboot, when setup reboots the machine it just hangs at where it would continue setup (just a black screen)

ive tried everything i can think of and everything that ive come across on the net so far, disabled acpi, diffrent drivers, different copy of winxp/2k/2k3server, downclocking my machine, installing on a different hdd on the pata channel, EVERYTHING!! :confused2

any help would be appreciated beyond belief

/edit, Drives are detected in a win2k install on another drive and i can read/write to them, im using standard winxp pro (no SP1)

Comments

  • drasnordrasnor Starship Operator Hawthorne, CA Icrontian
    edited February 2004
    If you have this problem with an install on your PATA hard drive without installing the RAID drivers at all, I'm inclined to believe you have something other than a RAID problem.

    -drasnor :fold:
  • sins55sins55
    edited February 2004
    no no, the install works fine on my pata, config, setup installs fine, im using it right now, its only the sata raid that doesnt boot.
  • Park_7677Park_7677 Missouri Member
    edited February 2004
    In your motherboard BIOS, find P2P Discard and change it to "1 ms" (should be "30 us" default).

    Make sure SATA Boot is the 1st Boot Device, and in the BIOS where SATA is turned on and off, make sure Boot Rom is ON.
  • sins55sins55
    edited February 2004
    changed ext p2p discard to 1ms, still no go, and sata boot rom is always enabled, changed between acpi modes and still nothing.

    thanks tho!!

    edit/ sata is the only boot device, and allow othe boot device is disabled.
  • amorphismamorphism
    edited March 2004
    Hey sins55,
    u fix your problem cuz i got the same one.
    could really use some help.

    thanx,
    amorphism
  • Park_7677Park_7677 Missouri Member
    edited March 2004
    Below is part of a PM
    sins55 wrote:
    think i just found the source of my problem on nforcers forums, something to do with the sata raid bios that im using (bios 23) and apparently people have been having the same issue as i have, thanks for all your help. i hadn't even considered what u said to do, so thanks.

    about to flash to a modified bios now, will post in the thread if it solves the issue.

    I don't know if it fixed it or not, as he didn't post in the thread. However, you may want to try it anyway.

    Good luck :)
  • EQuitoEQuito SoCal, USA
    edited March 2004
    http://forum.abit-usa.com/showthread.php?s=&threadid=33981
  • Mt_GoatMt_Goat Head Cheezy Knob Pflugerville (north of Austin) Icrontian
    edited March 2004
    I know this is obvious but did you change your boot order in the bios to include the Silicon Image controller? Did you go into the RAID bios and either set up an array or designate one of the drives as the "Boot" drive? You need to do those prior to trying to install an O/S.
  • MissilemanMissileman Orlando, Florida Icrontian
    edited March 2004
    I agree with Equito. It's the SATA bios. I had a perfectly working system flashed to the 21 and it hung everytime. Used Equito's modded bios with the old SATA bios in it and back to working perfectly.

    Other people reported the same thing you are getting during install with that one particular bios.


    Worth a shot since it's an easy fix.
Sign In or Register to comment.