Drivers from floppy needed for single SATA drive?

[Guest Kaos]

Just to make sure I'm not causing my own problem here... The drivers from the floppy are only needed for a RAID configuration, not for just a single SATA drive, correct?

[RGone]

That is the theory alright.

 

RGone...

[choke.]

if you get this going please let me know how you did it

[soundx98]

what's the problem Choke?

 

http://www.dfi-street.com/forum/showthread.php?t=8790

[DrNick]

No need for any drivers unless you are running a raid array:)

[Doctahg]

I could not get XP to see my Raptor without slipstreaming the sata drivers into the XP disk.

[divided]

i think pre sp2 xp cds didnt have the sata drivers, post sp2 did.

[choke.]

soundx i was unable to get my secondary sata drives to show up (anywhere) unless i set up a spanned array using the nvraidman.exe. im just wondering how others are able to just plug sata drives right on in and have them show up no problem.

[RGone]

One reason you cannot just throw drives at the board and have them work is because you are hooking them up to a raid controller that is in use monitoring the full controller. If you did not have the first raid array you could put 4 separate sata drives on the controller and not have to load any drivers at F6. That is how and why most that are not raiding are told to not use F6 for any driver during install.

 

Once you have an array everything else attached on that controller will be looked at and thought of as part of something arrayed. JBOD or Spanning is one thing the controller can see and what I use with an array and only a single other drive. But you have two drives not striped together but spanned. Not what you wanted.

 

So you should have set up the array 0 you wanted. And I think you would have done one of two things. #1option: hooked up both the other drives and you would have been given the option to "raid 0'' a single drive. It speaks of single drive striped array in the manual. That has you 3 drives hooked up and one to go. The fourth drive would then be designated as a single JBOD drive and that would be the four drives in and the last two not spanned together as they are now. #2option: would have been to hook up one of your other drives and spanned it as JBOD. Shut down and added other drive > rebooted and I am guessing it might allow you to have had drive #4 and JBOD it to itself. That is a possible scenario; since I don't think it will "force" you to change the status of what is a pre-installed and JBOD'd drive when you add the other one. Sort of like one then the other but not both inserted at once.

 

One thing that makes it such a beech is the options for a fullmeal deal stand alone raid controller are not what Nvidia has given to the user and it takes some trial and error to beat the system.

 

RGone...

[choke.]

well i didnt want to stripe these new 250s, i just want a ton of storage. my first choice was to have them show up seperately, as 2 seperate 250gb drives. when i couldnt get that to happen, i was able to span them together, and thats fine i guess. i understand the concept now about the raid controller being set up and not wanting to handle any other connections not in some sort of array and in retrospect i 'think' i wouldve got that if i had done your #2 option. i wonder what will happen if i disconnect one of them. heh, atm not in the mood to try it, maybe if i get bored next week.

to continue the discussion, the nv raid controller is set up to handle sata2 but the sil is not? i wasnt getting anything to show up in slots 4-8 and thats a seperate controller altogether. but im not sure if i ever installed drivers for that one. or do they each work off the same driver? if not, then shouldnt i have been able to just plug in to that controller and got the drive as a single?

[RGone]

then shouldnt i have been able to just plug in to that controller and got the drive as a single?

 

NO, because no SiL controller will work without at least "a" driver for it. Yes, with a driver though and then as single drive to back up onto or more storage and not arrayed. The only craziness that I have 'ever' heard of but not really tested is the SiL controller when enabled actually is in the bios boot order BEFORE the NVraid and that can make a mess sometimes. Probably would not bother me though since I do not depend on windows for 'any' formatting but ""always"" third party software and I would set any NON-boot drive to extended/logical and then it is pretty quickly 'ignored' as anything to boot and likely not mean any hardship with the NVraid coming online for use after the SiL raid controller.

 

RGone...

 

well i didnt want to stripe these new 250s, i just want a ton of storage. my first choice was to have them show up seperately, as 2 seperate 250gb drives. when i couldnt get that to happen, i was able to span them together, and thats fine i guess. i understand the concept now about the raid controller being set up and not wanting to handle any other connections not in some sort of array and in retrospect i 'think' i wouldve got that if i had done your #2 option. i wonder what will happen if i disconnect one of them. heh, atm not in the mood to try it, maybe if i get bored next week.

to continue the discussion, the nv raid controller is set up to handle sata2 but the sil is not? i wasnt getting anything to show up in slots 4-8 and thats a seperate controller altogether. but im not sure if i ever installed drivers for that one. or do they each work off the same driver? if not, then shouldnt i have been able to just plug in to that controller and got the drive as a single?