Ok...last night I was trying to set up my XP machine with the OS and App drive(Western Digital 20GB) on the IDE 1 position as master and two Maxtor 40GB drives on IDE 2 as a striped RAID 0 array...now, if I disconnect the two Maxtor drives and do the XP setup it sees the WD drive..if I try it WITH the two Maxtors setup as a RAID or as independent disks XP won't see any hard drives. huh? What gives? When setting up XP I did the Standard PC and loaded the third party drivers for the RAID card..so it "should" be ok...but it's not...
If I install the OS off of the primary than move it to the RAID card it works...I'm confused :confused:
Anyone? Beuler?
Opus
Topic Tags
Comments
Here's something I noticed...when installing WIn2k and doing the
Here's something I noticed...when installing WIn2k and doing the F6 thang...it pops up with the ATA PCI RAID...doing the same thing on XP it shows up as a SCSI card!!! I think it's driver related that I'm coming across....I'm going to try and download the newest drivers and try it that way...BUT..my main system is leaving to replace a
The Supermicro(Supermacro it should be called) is dual PIII 1Ghz....wont even recognize SCSI drives properly!! This is the onboard SCSI dual channel controller...sad sad sad sad...anyhue..dont know when I'll get my system back again...geez!! When and IF I do..the person may just buy my system from me I'll build another one with a different rack mount case and a couple of other different features I havent decided on..same mobo and processor(well, maybe the 1.8a!!)
Peace
Opus
All RAID cards, SCSI or IDE show up as SCSI devices to Windoz(al
All RAID cards, SCSI or IDE show up as SCSI devices to Windoz(always gets listed in device manager as such).
Maybe you should not have loaded the third party drivers for the RAID card during the install of the OS to the single IDE1 drive, because when windows starts up, it is now looking to boot from the RAID drives, which have no OS installed on them. When you remove the RAID drives the OS boots from the IDE1 channel because the loading of RAID drivers failed to in initialize, and it defaults.
I could be right, but Im not sure ;)
Try loading the RAID drivers later, after the new install on the single drive.
Okay , Maybe you should try loading the OS drive first without
Okay ,
Maybe you should try loading the OS drive first without the RAID card in , then reboot add the RAID. Also I had a question about partitioning
removable drives(such as those in a RAID-because at some point you may replace them or drives in a removable caddy). Do you usually format these as extended partitions ?
Sorry this post does not have to do with RAID but I would also like to know the answer to the OPUS
Q.
First time I messed with my Promise TX2(non RAID) and the drives(2 WD 40 gig 7200), this very thing happened to me. I wanted to load standard PC and apparently on boot these cards have some sort of priority and I don't why they get checked first for OS and other stuff but they do, and obviously I didn't want to F6 to load the drivers because unlike XP , it would have put everything on same IRQ(9) without giving me the extra IRQ's like in ACPI XP mode. At that time, just like I told you Opus, I did the same thing and loaded the OS(WIN2000 SP2 BTW) off of the
onboard primary, then moved the OS drive over to the controller on my next boot and it worked like a charm. Now I remember that you told me it might cause conflict because my system might think it should still be on the mainboard controller but, it ran very smooth just like yours. I may try this again with a Win2000sp2 load to be able to access some of the better drivers and stuff we already talked about.