NF7-S v 2.0 I think I have a good one for you guys!

[Bob Troll]

Here's the system:

NF7-s v 2.0 mainboard (bios 19) with bios savior backup AMD Barton 2500xp+ Asus/Nvidia TI4200 agp 8x 256 x 2 Crucial 3200 ram. <-- tests out fine in memtest86 and Micro$shaft memtest 2 x wd 80gb se drives 8mb cache Enlight 420 or so PSU (I forgot) <--- Power rails look good and steady under load. 3 optical drives couple fans here and there (120mm up front to cool the drives)

OS Win98SE totally updated IE 6 etc and blah, blah infinitum....

Here's the issue:

I have the optical drives on the onboard ide controller and the WD's each on the S-ATA controllers using the serillel 2 adapter kits from Abit. I can see all the optical devices fine as well as the boot drive which is on the primary sata controller. I do not see the slave drive or D in the device manager. Only the C drive makes an appearance there.

I can open Windoze Explorer and root around on the drives all I want, so the OS apparently knows it is there and allows me to copy, paste and the normal things one would do with their hard drive. The correct operation of the drive is unimpeded. I have a theory that this raid controller wants to really only be a raid and doesn't want to play like I want it to.

The drives are configured with no jumpers at all which defaults to it being a single drive all by itself. I was going to try using a jumper as master for grins, but I read a message where a guy had an issue of the drive not being recognized until he pulled the jumper off and installed it in the neutral position.

HD Tach shows the drives as both being C, but yet will test each one as normal.

Any comments, barbs or witticisms to cast my direction?

Regards, Bob "hopelessly insane machine warrior" Troll

 

[ukaloo]

Bob, did you load win98se with your boot drive on SATA, if so how did you load the SATA drivers? What SATA drivers did you use? Sorry, but I helped a friend installed his OS with boot drive on PATA. I'd like to move it to SATA for him if I know how.

TIA. Ukaloo

"Bob Troll" wrote:

Here's the system:

NF7-s v 2.0 mainboard (bios 19) with bios savior backup AMD Barton 2500xp+ Asus/Nvidia TI4200 agp 8x 256 x 2 Crucial 3200 ram. <-- tests out fine in memtest86 and Micro$shaft memtest 2 x wd 80gb se drives 8mb cache Enlight 420 or so PSU (I forgot) <--- Power rails look good and steady under load. 3 optical drives couple fans here and there (120mm up front to cool the drives) ...

 

[Helinut]

Only got my NF-7 This morning, so I'm no expert. However reading through the manual if you are using the SATA to PATA interface you MUST have the drive jumpered to Master. hope this helps Helinut "Bob Troll" wrote:

Here's the system:

NF7-s v 2.0 mainboard (bios 19) with bios savior backup AMD Barton 2500xp+ Asus/Nvidia TI4200 agp 8x 256 x 2 Crucial 3200 ram. <-- tests out fine in memtest86 and Micro$shaft memtest 2 x wd 80gb se drives 8mb cache Enlight 420 or so PSU (I forgot) <--- Power rails look good and steady under load.
3 optical drives
couple fans here and there (120mm up front to cool the drives)

OS Win98SE totally updated IE 6 etc and blah, blah infinitum....

Here's the issue:

I have the optical drives on the onboard ide controller and the WD's each on the S-ATA controllers using the serillel 2 adapter kits from Abit. I can see all the optical devices fine as well as the boot drive which is on the primary sata controller. I do not see the slave drive or D in the device manager. Only the C drive makes an appearance there.

I can open Windoze Explorer and root around on the drives all I want, so

the

OS apparently knows it is there and allows me to copy, paste and the normal things one would do with their hard drive. The correct operation of the drive is unimpeded. I have a theory that this raid controller wants to really only be a raid and doesn't want to play like I want it to.

The drives are configured with no jumpers at all which defaults to it being a single drive all by itself. I was going to try using a jumper as master for grins, but I read a message where a guy had an issue of the drive not being recognized until he pulled the jumper off and installed it in the neutral position.

HD Tach shows the drives as both being C, but yet will test each one as normal.

Any comments, barbs or witticisms to cast my direction?

Regards, Bob "hopelessly insane machine warrior" Troll

 

[rms]

There is a known issue with WD drives disappearing in Windows, due to some power-saving drive feature (which can be disabled). Doesn't sound like this is your problem tho.

rms

 

[Mark H]

Bob Troll wrote:
I can see

all the optical devices fine as well as the boot drive which is on the primary sata controller. I do not see the slave drive or D in the device manager. Only the C drive makes an appearance there.

Where do you not see the slave drive? sata bios? post? The only thing I could suggest is switch the drives with cables and see if this is a controller or hd/cable issue. you should also be using the 10032 driver.

I can open Windoze Explorer and root around on the drives all I want, so the OS apparently knows it is there and allows me to copy, paste and the normal things one would do with their hard drive. The correct operation of the drive is unimpeded.

Really? try a one gigbyte zip file and transfer it from one drive to another. then unzip it and see if there are any crc errors

I have a theory that this raid controller wants to

really only be a raid and doesn't want to play like I want it to.

The drives are configured with no jumpers at all which defaults to it being a single drive all by itself.

That's correct for WD drives. read the faq at silicon image.

I was going to try using a jumper as master

for grins, but I read a message where a guy had an issue of the drive not being recognized until he pulled the jumper off and installed it in the neutral position.

HD Tach shows the drives as both being C, but yet will test each one as normal.

Any comments, barbs or witticisms to cast my direction?

Regards, Bob "hopelessly insane machine warrior" Troll

 

[Bob Troll]

Oops I see where I left out the connection point of that slave hard drive. It is the slave on the sata. I have all my optical drives on the onboard ide controllers and they are fine.

The drive is found by the sata bios at bootup as the sm drive, which is correct. The ONLY place I can not see the drive is in the device manager which seems odd since it is seen by everything on this host machine and everybody else on the lan.

Regards, Bob Troll

Bob Troll wrote:

I can see
all the optical devices fine as well as the boot drive which is on
the primary sata controller. I do not see the slave drive or D in
the device manager. Only the C drive makes an appearance there.

Where do you not see the slave drive? sata bios? post? The only thing I could suggest is switch the drives with cables and see if this is a controller or hd/cable issue. you should also be using the 10032 driver.

...