Detect One Hard Drive At A Time

Gateway / Performance 733
May 25, 2010 at 14:36:34
Specs: Microsoft Windows Home Server PP3, 2.19 GHz / 512 MB
Yesterday, I got two second-hand hard drives (Maxtor DiamondMax Plus 9 80GB ALA/133 HDD) and decided to toss them in an old computer and use the trial of Windows Home Server, and if I liked it, I'd buy it. The problem is, the computer will only detect one hard drive at a time, and that is the master. I have the jumper settings set correctly (No jumper is the slave) and they are both properly connected. It will detect only one hard drive at a time. Either one will be detected, but not the slave if they are both in. Desperately, they will both be detected as either the master or the slave. I have tried changing the IDE cable, resetting the BIOS with jumper and taking the CMOS battery out, and unplugging all but the hard drives (PCI, CD Drive all unplugged) so I don't think that it's the power supply. Please help, thanks!

~William
My Site: http://willstech.org/
It's a work in progress! =P


See More: Detect One Hard Drive At A Time

Report •

#1
May 25, 2010 at 16:58:40
Try each of them with a known good drive. One of them might have a circuit board with a problem that is killing the interface.

The three most important things in computing:
1. Backups, 2. Backups and 3. Backups.


Report •

#2
May 25, 2010 at 17:44:03
Try jumpering them as Cable Select (CS). When both are jumpered that way it's their position on the cable that determines master/slave priority.

Have you tried different power connections? Sometimes the contacts get flared out and don't make a good connection.

You're not really green until you're soylent green.


Report •

#3
May 25, 2010 at 19:00:37
Install one as the primary master, put the other on the 2ndary channel...makes no difference if it's master or slave.

Report •

Related Solutions

#4
May 25, 2010 at 19:00:46
Yes, better suggestions from Dave.

The three most important things in computing:
1. Backups, 2. Backups and 3. Backups.


Report •

#5
May 26, 2010 at 14:00:17
Thanks for all the responses!

First of all, I tried changing the power connectors. I tried several different configurations of the power connector but I got the same results. Primary IDE Master: Maxtor 6Y080L0; Primary IDE Slave: Not Installed

Secondly, I changed the jumper settings for them both to be cable select. Same results.

Thirdly, I paired a spare hard drive with each of the two that I'm having problems with. (The hard drive of choice is a Western Digital WD400 40GB) I tried them both as cable select, master, and slave. I got the same results.

I also went ahead and tried running them both on the secondary IDE cable (Removing the CD drive for the time being) but got the same exact results. I also tried running them both as a masters, one on the Primary IDE and one on the secondary IDE. This worked, and it sort of surprised me, but the fact that I wouldn't be able to have a CD drive in it pulls me away from this solution.

Thanks for helping me!

***(The results, by the way, is me going into the BIOS and seeing which IDE drives are detected. I figured out that if they aren't detected in the BIOS, then they won't be detected in the OS either.)***

~William
My Site: http://willstech.org/
It's a work in progress! =P


Report •

#6
May 26, 2010 at 16:20:01
Check in cmos/bios setup and see if it's possible to separately enable the second drive on the primary and secondary.

If that doesn't work you may still be able to connect a cdrom as slave to either drive. They may act differently than hard drives on the same cable.

You're not really green until you're soylent green.


Report •

#7
May 26, 2010 at 18:00:37
I knew that they wouldn't act the same. I also got the CD drive to work with it, but the only way to get it put back together with both hard drives in the case is hard to do (leave the hard drive hanging there on nothing) because the length of an IDE cable is limited.

~William
My Site: http://willstech.org/
It's a work in progress! =P


Report •

#8
May 31, 2010 at 15:04:42
Sorry that I didn't have any actual problem in the last post. The only problem that I have now is that I can't have them both on the same IDE cable, and that isn't going to work because the way the computer case is designed, I can't physically have a CD drive on the same cable as another hard drive with another hard drive on a separate cable unless I put the hard drive in the floppy drive spot, but then it's such a cramped spot that I'm afraid that it'll heat up. What settings should I look for in the BIOS to fix this problem, or is this something with the hard drives that can't be fixed?

Thanks, again!

~William
My Site: http://willstech.org/
It's a work in progress! =P


Report •

#9
May 31, 2010 at 20:53:26
All bios' have their differences. But there's probably options for 4 IDE attachments. Check if the slave on each is set to NONE or disabled. You may need to check the manual.

I imagine it's possible (although I don't know that I've checked) that an optical device attached as a slave will work when set to NONE since they're configured with OS drivers and aren't entirely dependent on the bios.

You're not really green until you're soylent green.


Report •

#10
June 2, 2010 at 09:18:08
Okay, the options for IDE Configuration are as follows:
-------------------------------------
IDE Controller [Both]
PCI IDE Bus Master [Enabled]
Hard Disk Pre-Delay [Disabled]

>Primary IDE Master [Maxtor 6Y080L0]
>Primary IDE Slave [Not Installed]
>Secondary IDE Master [HL-DT-STDVD-ROM GDR8]
>Secondary IDE Slave [FX831T]
--------------------------------
I have all of them set to auto-detect, so none of them are set to Disabled.

~William
My Site: http://willstech.org/
It's a work in progress! =P


Report •

#11
June 2, 2010 at 09:28:35
If you use Master/Slave settings you can use either connector on either drive. That makes routing the cable easier. Be sure to use an 80 wire/ 40 pin cable.

I am not sure if you are getting any of the new drives to show in the POST screens. If one is bad it may well keep the other drive on the same cable from being configured.


Report •

#12
June 2, 2010 at 09:47:39
OtheHill:
Check Response Number 5, it explains all that you asked about in your post.

Also, I tried two completely different drives and I can't get a master/slave thing to work at all. I could get it to work before (a couple years ago) but now it's just driving me up a wall!

~William
My Site: http://willstech.org/
It's a work in progress! =P


Report •

#13
June 2, 2010 at 12:17:21
If you have a Western Digital drive in the mix there are TWO different Master settings on them. One is labeled Master alone and the other Master.

You may have a bad IDE cable too.

I reread #5 and still am not clear if you have ever gotten either of these drives to be recognized. Either alone or together with another drive.

If not, then perhaps the drives themselves are NG.


Report •

#14
June 2, 2010 at 14:11:28
Okay, sorry for the confusion and let me clear a few things up, then.

I have tried two different IDE cables in addition to the one already in there, to no avail.

I have tried two COMPLETELY different drives that I had working as a master/slave relationship in another computer without changing any jumper settings and it didn't work.

I am aware of the Master alone and Master settings, I made sure that they were set properly on the WD when I tried it with the other two drives.

So, in other words, I can't get the computer to detect ANY slave drive, no matter what the drive is.

~William
My Site: http://willstech.org/
It's a work in progress! =P


Report •

#15
June 2, 2010 at 14:29:19
Are you sure you are connecting the cables correctly? It is possible to turn them end for end, which will not work. Also, CS settings will not work with older 40 wire cables.

Do you cables have three different colors on the connectors?

Most 80 wire cables have a blue board connector, with gray in the center and black on the end. See the link below.

http://www.creativecomputing.net/ca...


Report •

#16
June 2, 2010 at 19:44:22
My cable doesn't have three different colors, but the one end
says "Main Board", then "Slave" and then "Master". Then a
second cable has one connector, a long space until the next
connector, then a short space between the second and third
connectors, which are the master and slave connectors.

~William
My Site: http://willstech.org/
It's a work in progress! =P


Report •

#17
June 2, 2010 at 20:14:00
Then you are using 40 wire cables that are only good for 33MB/sec. Upgrade to newer cables.

Report •

#18
June 3, 2010 at 12:28:40
Okay, but how would that help my original problem?

~William
My Site: http://willstech.org/
It's a work in progress! =P


Report •

#19
June 3, 2010 at 12:50:06
Well, first of all, the cables may not be any good. IDE cables are fragile. Incorrect removal can result in incomplete contact of the crimped on pins. If you look at how an IDE cable is assembled there are short pins that penetrate the insulation of each wire.

Second, the extra 40 wires on an 80 wire/ 40 pin cable are grounds that act as shielding. When you don't have that shielding you can get crosstalk. Crosstalk may not allow the controllers to configure the drives.

All modern IDE/ATA drives are designed to run on 80 wire cables.

Some BIOSes have a setting to allow as much as 5 seconds for the BIOS to configure the drives. Look for such a setting and set the time longer.

To sum it up, it appears you don't even know if the drives are functional. Eliminating the possibility of a defective cable just makes good sense. At any rate running any drives on those old cables will result in a slower rig.


Report •

#20
June 3, 2010 at 15:48:11
Okay, somehow I overlooked the cable in the box and it was, in fact, an 80-wire cable/40 pin connector. I changed the wire, no luck, but then I changed the hard disk pre-delay to 6 seconds and now it seems to be working fine! Thanks for helping me get this far, but I have one simple question: Why would the pre-delay help?

Thanks a ton!

~William
My Site: http://willstech.org/
It's a work in progress! =P


Report •

#21
June 3, 2010 at 16:41:58
Just as you look for something, the longer you look the more likely you will find it. Your BIOS may not be picking up the information off the printed circuit board on the drive very readily.

Now that you can see the drives download a fitness test from the manufacturers site and run it to determine if there are issues with the drives.


Report •

#22
June 4, 2010 at 11:08:39
Okay, I downloaded Maxtor PowerMax 4.23 bootable .iso and ran it, both hard drives, the burn-in test with two passes, as well as the other tests that it offered and both hard drives passed with flying colors.

~William
My Site: http://willstech.org/
It's a work in progress! =P


Report •

#23
June 4, 2010 at 11:16:05
OK, going back to your original post. You stated you are using an old computer. Old is relative. What are the specs on the rig?

Report •

#24
June 4, 2010 at 11:21:34
Gateway Performance 733 Manufactured in 2000
-Pentium III @ 733 MHZ
-1x PC100 128 MB RAM
-1x PC133 128 MB RAM
-1x PC133 256 MB RAM
-200 Watt PSU
-2x 80 GB Hard Drives
-LG DVD-ROM
-CD-ROM

~William
My Site: http://willstech.org/
It's a work in progress! =P


Report •

#25
June 4, 2010 at 11:48:09
Possible the BIOS is having difficulty configuring the 80GB drives because of the geometry of the larger drives.

I have an 80GB drive in the drawer with a late 2003 date on it.

I am guessing that 20/30GB was the norm in 2000.

Are the properly identified in the POST screens by both model and full capacity?

One other thing to note. Maxtor came out with ATA 133 specs, which were never really standardized so that could be an issue too.

ATA 66 specs came out in 2000, so that is probably the best the controllers on your board could be.


Report •

#26
June 5, 2010 at 00:53:36
The hard disk pre delay allows the drive a little more time to spin up and be recognized by the bios. Maybe the combination of the newer drives running on the older mobo and their being on the same cable is causing a recognition problem that is fixed by allowing that extra time.

You're not really green until you're soylent green.


Report •

Ask Question