I am not clear on the procedure you used. Trying to boot the unit alone will go nowhere correct? Are you adding an external USB hard drive then? What drive are you putting the boot cd into? internal or external? What is the boot order designated in Bios? With a little more info we can sort this out fairly easily, I hope…
I see a few things here that do not adhere to proper trouble shooting procedures. No slam on you, but using the suspected bad drive in another channel really proves nothing. As long as the drive is physically away from the case, unplug it and work the system without it. See if everything else seems to work. I would be more specific, but it is late and I have to be on time in the morning at the IT department. It is hard to tell right now, but I am guessing your HD is hosed. Ascii to Ascii, Dos to Dos. If you were to on the odd chance to be looking for a college to go to and contacted Southwest Wisconsin Technical College, you might find some more help. Wink wink.
So you mean winxp detected the drive and formatted it, but on another system?? Just because it can’t boot off of USB, doesn’t really mean anything. Can another system write and read data to it?
You really have to give much more detail.
If the BIOS does not detect it but windows does… your computer is crazy. If your drive is not detected by one computer but is usable in another (and a second drive works in both)… I once had a problem with a Western Digital drive not being detected if you enable RAID capability on the motherboard. However, that shouldn’t apply to a USB unit. Other than that… update your BIOS, of course, but I’ve got no clue.
also you have to say whether it is SATA or parallel ata. pata needs correct jumper settings, and if you choose “cable-select”, it needs a correct cable and (i think) be put in the right position. also make sure that if your cable doesn’t have a notch to orient it, you try it both ways.
if the bios does not detect the drive at all, it usually means the HDD controller is broken. (as opposed to when it can detect it, but the platters have errors.) Maybe the controller is broken in such a way that if it’s reinitialized, it works. Maybe upgrading the BIOS, or changing a settings that controls IRQ assignment (in my bios it’s called “Plug and Play OS”), or maybe enabling/disabling ACPI (doubt it) or some other weird setting will hack it to work.
Is it under warranty? If so, and since you obviously don’t have data on it, it’s a no-brainer. If not, you might be able to find a broken drive of the same model whose controller you can use (though such things are tricky). Maybe on ebay.
A drive formated on one IDE controler won’t work on another controler if the Bios for the controlers differ in how they handle interfacing with the hard drive. It was more of a problem when the Bios kept reaching new size limits on the drives. This is just to tell you why you shouldn’t just switch to a new computer without reformating on the new computer.
It could be a jumper issue.
You may have a cable wired to use C/S or cable select on the hard drive. The drive may be set to primary, but your plugging it into the secondary cable end. It would work correctly if the hard drive was set to primary and connected to the primary.
I suspect it has a bad boot sector. The Windows CD boot uses the cd to boot, and the drive was detected. The format was done and the hard drive sectors rewritten. You try to reboot and the boot sector is bad, leaving you with a non-booting drive. The drive heads would be moving around alot trying to read the boot sector, and finding nothing trying again.
The drive could have a bad power connector. It wouldn’t make a noise when you try to start. A bit of wiggling and it might work.
Much like the #3 an IDE cable could be bad. You would hear the drive running in this case.
The hd circuit board could have a crack, but I would expect that once it died to stay dead.
but if I use recovery console in xp it can see files. I can run a dir, chkdsk, and nothing seems amiss. The only indication I can find of failure is the failure to boot the machine. It would seem to me that if it can find and display the contents of the C: drive then it can read at least to some degree.
The interface still uses the IDE hardware bios on the mother board to do reads and writes. The Bios translates requests to read or write to a specific sector into a physical location on the hard drive. The computer powers up, and the Bios gets all up and running so an operating system can be loaded. The Bios looks at Sector Zero on the first data storage device, and executes the OS start up code. The Bios goes to the next and the next storage device, until a boot sector has the boot data to start the OS. The drivers in the OS add a layer that can be always accessed the same by programers to do I/O between the IDE Bios and the OS. This eleminates the need for each program to know the way to access each device. The hard drive has it’s own interface to tell it this is where the sector is on this device. So there are multiple layers to access all hard drives.
The hard drive circuits telling the heads where to go.
The Bios for the IDE controller.
The OS drivers to make all access points needed by programs the same for all devices.
A program requests data. The OS uses the driver to ask the Bios, to ask the hard drive for the data.
Bios almost always are set for LBA access for all drives now a days. Most of the Bios are the same today, and the Logical Block Addressing tables they use are identical. LBA came along to allow a greater number of sectors to used. On older computers ,when the hard drive was to large for the Bios to access all of it, you had to add in a bootup program on sector zero that handled the LBA interfacing. That was one more layer at the time to go through. Most of those motherboards were year 2000 non compliant.
CD and DVD drives interface the same way.