OT...adding a 3rd HDD trouble

Stiffler wrote on 9/8/2003, 12:02 AM
Bear with me as I try to explain my trouble.

I have a 30GB system drive, and a WD 80GB drive for my video (and storage) set up as a slave drive. These drives are on one IDE cable, and I don't have another slot on my motherboard for another cable.

To add a 3rd drive, the computer store sold me an Ultra ATA/133 PCI raid controller card along with the new 120GB WD hard drive.

The trouble is that my computer does not 'see' this drive. It does show up (as a spare drive) when I boot-up, but windows does not see it.

There are no conflicts. The PCI card shows it is working properly in 'Device Manager', but does not show the new drive.

Before I bring it in, I thought I'd try here. (I'm sure it's something simple).

Any ideas?

BioStar motherboard
Athlon 2100
XP Home
640 DDR

Thanks, Jon

Comments

kentwolf wrote on 9/8/2003, 12:06 AM
(It's good at least that the drive is showing up at boot time.)

Be sure you have formatted the drive. I do not believe it will show up in your drive list until you do that.

Even though it's not showing up as a system drive...

Right-click on My Computer
Select Manage
Select Disk Management

You should see the new drive there.

Right-click on the new drive, then format.

That should do it...
Stiffler wrote on 9/8/2003, 12:42 AM
Ok, I checked the Disk management, but it was not there. The only thing there was my 2 hard drives and my CD-ROM drive.

(In Device manager I look under SCSI and RAID controllers. It says it is fine.)

I have been trying to set it as a master or slave, but that does not help.

I did format it, but not from the current location. I hooked it up as a slave drive off the master (system drive). These drives have the cable coming off the motherboard, and the new cable for the new drive is coming off the Ultra ATA/133 raid controller. Does that make sense?

Thanks.
kentwolf wrote on 9/8/2003, 2:49 AM
>>...Does that make sense?...

Yes. I also have a Maxtor ATA-133 card; running 8 drives.

>>(In Device manager I look under SCSI and RAID controllers. It says it is fine.)

That would be the *controller* that's fine, not the drive.

I am assuming that...

1.) You are running NTFS.
2.) Your drive does not require the less common "cable select" setting.
3.) Your cable is good. I have actually had a bad cable once, as well as a bad drive.

You say that you formatted it, the new drive, once in another location.

That proves that all *could* be OK with that new drive.

I have also noticed regarding Drive Image, WinXP NTFS is very particular where you can restore what partition/drive. With Drive Image, I cannot create say, my main C drive, then restore it all to D:. It seems to "freak out" NTFS. NTFS seems to want to keep everything in the same location in which it was created.

What I would do is wipe your new drive clean with the utilities disk that came with it, then try to format it from scrath *in its' current physical position*.

Have the nw drive plugged into channel 1 of your ATA card.
Set the new drive for Master.
Boot to your utilities disk.
Wipe the drive clean, then reboot to Windows.
Then try to format via Manage, like I mentioned before. (Powerquest's Partition Magic is also helpful as a future consideration...)

Often, it easier to work with a clean slate than to try to fix one.
Maverick wrote on 9/8/2003, 3:06 AM
Just a quick thought.

You said you formatted it as a slave - have you reset it to Master. easily overlooked.
Zulqar-Cheema wrote on 9/8/2003, 9:40 AM
Something not quite right here, you said you only had ONE ide connector for the two IDE drives, yet you say you also have a CDROM, then surely this would require an addtional IDE connector. In which case a cable change and set the new drive to master and the CD to slave to et t in to the system.

Also I have never heard of formatting for Slave, just formatting.
filmy wrote on 9/8/2003, 10:50 AM
I recently added a new drive and an Ultra 133 controler. I had somewhat of the same issue at at first. First thing to look for, formated or not, is as you are booting - the controler should pop up and look for drives attached and if it finds any it will list them. If you do not see this as you turn on your computer and before it enters windows there is a problem. (You may have to go into your bios and look for a setting called "Silent Boot" and turn it to "off" or "no" in order to see what is happening during boot up)

Next - While the drive showed up on the controler during boot fine in windows the drive was not anywhere to be found. So I opened disk managment and the drive sort of showed up - it was there but not "mounted" (And I wa ssuddenly reminded of the good ole Amiga and having to mount drives - seems so long ago) so I did that and than was told it needed to be assigned so I did that and than I could format it. Thing is that this drive is listed as a 'dynamic drive' - the only one mared as such. And I do have another drive hooked up the same controler, but that is not marked as a 'dynamic drive' but it does give me the option for coverting it to one. So I dunno if that is making a differance on your system - choosing dynamic or not.

As for the jumper settings for slave or master - many, if not all, of the newer systems auto detect thiese settings and you don't need to deal with the jumpers. I just pulled mine off.
JJKizak wrote on 9/8/2003, 11:05 AM
Another thing to consider is once you are feeding your IDE buss from the ata card go into your CMOS and select "Primary IDE buss only" since you are not using the secondary IDE connector on the motherboard.

JJK
BillyBoy wrote on 9/8/2003, 2:27 PM
Remember that the extra 133 controller cards are SEPERATE from you regular BIOS setup. a brief page should flash by at boot indicating which drives or devices are connected to the extra controller card. Such drives can NOT be adjusted through normal means typically hiting the delete key or another key to bring you to your computer's setup screen.

Obviously if you installed a new 133 controller card, then the drives need to be plugged into the card NOT the secondary IDE controller on the motherboard.
Stiffler wrote on 9/10/2003, 1:48 AM
Thanks for all the help, I got it going. Vegas users are the best!

I printed out this post, and tried everything that was posted here.

kentwolf, Maverick, zcheema, filmy, JJKizak, and BB...I tried all the possibilities.

It seems it was a BIOS issue, not my computer BIOS, like BB said, but the BIOS for the controller card, as filmy mentioned in the first part of his message.

I had the BIOS set up as a spare drive, when it should have been set as Master, or something, (during boot-up, not jumpers).

Thanks again for the help!

Jon