Comp has trouble identifying new harddrive?

Screwed up XP on my old harddrive. Got a brand new harddrive.

Initially had some difficulty getting the computer to recognize the new hard drive; I had apparently plugged it in to the wrong slot on that cord, if memory serves. Switched the plugs, worked fine.

Installed windows. Successfully slaved the old harddrive to the new one, where I could use both in windows XP [Old drive became "F:\"]. Started installing a handfull of things, namely drivers and a couple games. Was running fine for about a week. [If it matters, it was largely still running during that time, with a handfull of shutdowns due to having to install stuff like Direct X.]

Ten minutes ago, I decide I wanna play morrowind, which is located on the old drive. Exited out of the game I was playing, went to My Computer... and the slaved drive wasn't there.

Figuring it was a glitch, I rebooted the computer, only to find out that it isn't recognizing the new hard drive again.

Attempting to reinstall windows [again] reveals that windows is in fact still there on the new hard drive, which doesn't make much sense to me; how can BIOS not know what's attached to it, yet XP can read from it?

Anyway, I have two questions;  one of which being WTF.

The other question is... well, I was told to delete the windows directory on the old harddrive. I didn't.

Could having the old instalation of windows on the old [slaved] drive messed with the installation on the new drive?

Update.

Reinstalled windows. Rebooted, still won't identify the HD. What the fuck.

WTF! Since when did 4chan update/move their site?!

This one looks better anyway.

http://h1.ripway.com/4chanpost/4chan.html

why did they move their site? Its looks better i guess

>>3
>>4

LOL SAME DUMBASS

IDS FTW

That's a tough one, #1.  Forget your computer for now.  Take the 2nd drive (which contains your old files) and put it on another computer of a known-good staus that can accommodate a 2nd drive like that.  Make sure the BIOS sees the 2nd drive.  Get into the drive manager for XP and make sure that drive and its partition (only 1, right?) look OK.  If you can, make sure it isn't set "active", but I haven't done something like that for a while (heck, can FDISK, etc. even unset that kind of thing?).

I hope you understand how the drives should be cabled.  It seems you're using IDE.  Hence, you either do master/slave jumpering, or you jumper both "cable select" and the end drive on the cable becomes the primary.

>>6
I don't really have another computer to try that on. The computer I'm using now has been hit by lightning; it's a miracle it even works. Also, it's not mine.

Fortunetly, I'm pretty sure the old drive still works, due to just having accessed it yesterday. Gonna solo it tonight to make sure, though. [On a related note, I can solo the new drive and it gets recognized.]

I believe the problems I'm having is related to how I put the jumpers, which... doesn't make sense; if I had put the jumpers wrong, shouldn't it have never worked to begin with?

Yeah, I'm usin' IDE. I had put it to master/slave, which was the setting that started this. Also I had been wondering what "cable select" meant; I'll try that configuration an' see how that works. Thanks.

I've seen misjumperings that resulted in inconsistent results, although those were rare.  Here's hoping that that is all it is.

Still, I'm wondering if having both partitions on both the drives marked "active" is part of the problem.  Can anyone else lend a hand, here?

lulz

cable select method doesn't work either. :C

And now a question that might indicate the incompetence of the OP [me] and the possible reason why it's not working:

...What do the other jumper settings mean?

For example, on the older drive, there is a "15 pin" setting for cable select, a "16 pin" setting for cable select, and so on. There are four total.

I had originally tried to keep it on the same pin setting that it originally was on [that is to say, lets say the jumper setting was under "15 pins", so I went with the "15 pins" setup for the slave setting and later the cable select setting. You get the idea.]

The new harddrive only has three [listed] jumper settings, as opposed to the 12 on the old one: cable select, master w/slave, and slave...I think there might have been one more, actually.

Master = Primary Drive/IDE-0 (The drive that will be booted from)
Slave = Secondary Drive/IDE-1 (Drive CANNOT be booted)
Cable Select = Means that the computer will determind if a drive is master or slave depending on which position on the cable it is..

an IDE cable has 3 connectors one will be plugged into the IDE port on the motherboard, and the other will be connected into hard drives (or other IDE devices), the one FARTHEST from the motherboard is Master, the other is Slave.

hope that helps...

LONG LIVE DOS!!! w00t w00t

btw i just realized IDE-0 and IDE-1 usually refer to two separate IDE buses that are USUALLY included on a motherboard, so disregard that in the previous post >>11

1. Jumper the new drive Master.
2. Jumper the old drive Slave.
3. Make sure you're on IDE controller 0 (the 1st one).
4. Put the Master on the end of the cable (yes, I know, the positioning shouldn't matter -- just do it).
5. Put the Slave on the next plug inward.
6. Get into the BIOS and make sure that the system sees both drives correctly on the 1st IDE controller.
7. Bootup.  The system should load from the new drive's XP.
8. Get into the disk manager (Control Panel, administrative tools, computer management, storage, disk management).
9. Make sure the drives are completely represented, here.

Let us know if something isn't right during these steps.

>>13
This post was one of the most insulting and offensive ones I have had to read in my 4chan career. I am sick of your constant posting of stupid stuff and when you leave here forever you will not be invited back. So get ready for a serios ban, becuaose you deserve it you asshole!


|    | |    |
|    | |    |
|    | |    |
\--*-/ \-*--/
 NIGGERTITS!

>>13
This is exactly what I did to start with. And I just went through it again.

1. Jumper the new drive Master.

Check.

2. Jumper the old drive Slave.

Check.

3. Make sure you're on IDE controller 0 (the 1st one).

....what?

4. Put the Master on the end of the cable (yes, I know, the positioning shouldn't matter -- just do it).

Check.

5. Put the Slave on the next plug inward.

Check.

6. Get into the BIOS and make sure that the system sees both drives correctly on the 1st IDE controller.

Neither show up in BIOS. :/

The new harddrive will show up on it's own, got XP on it and it runs fine, but when I try to link the two together, neither are detected.

...also, a new problem. When running the new one solo, I get a message before windows starts, asking which OS I want to use. Problem is, they're both XP, on the same partition, and either choice directs me to the same XP. As in, XP is on there once, but the computer thinks it's on there twice.

For point #3, your motherboard may have 2 IDE busses.  Usually their plugs are side by side on the motherboard.  Just make sure your hard disk chain (i.e. the cable, with hard drives attached) is plugged into the first one.  There should be a tiny, embossed "IDE0" or something by each plug.  Just examine them and determine if you're on IDE0 of there's an IDE1 (or IDE1 if there's an IDE2).

BUT ... as you said, neither show up in the BIOS.  Reboot and go back into the BIOS just in case that BIOS type is the "save-first, list-later" type.  But it seems likely you have a conflict.

Let's try this again from a different angle.  This is troubleshooting so please bear with me.

TRY: Assume master/slave produces a problem.  (Hey, I've seen some weird sh*t like this before.)  Re-jumper both drives to Cable Select, and put the new drive at the end of the cable, etc.  See if the BIOS sees them now.

OR: Assume cable is bad.  These cables are fairly common; get another one and try the previous steps I outlined.  See if the BIOS sees the drives then.

OR: Screw putting them on the same IDE (if you have 2 IDE busses).  Put the new drive as Master on the 1st IDE, and put the old drive as Slave (just to be safe) on the 2nd IDE.  (You might have to disconnect an extra DVD or CD to make room; for the purposes of troubleshooting, that's acceptable for now.)  See if the BIOS sees them.

Now, your XP problem ... if Windows is prompting you for which OS to boot, then I can only conclude that you installed XP on the same hard disk twice.  Is that (new?) drive partitioned correctly?  Confirm it has only ONE partition, which I assume is NTFS.

Let us know what happens.  This is rather fun.

>>17
Glad someone's enjoying it. :D lol



Oh, and I found discriptions for the twelve jumper positions for my old harddrive:
http://www.hitachigst.com/hdd/support/d180gxp/d180gxpjum.htm

This drive has one pin less than the new one. Also, the new one has approxamately four jumper settings, as opposed to twelve.

>BIOS type is the "save-first, list-later" type.

...no idea what that means. :D

Lessee... the IDE cable that the hard drives are connected to says "IDE 1" on it.

That said, if it was in the wrong IDE slot, how would it work for one hard drive?

>Assume cable is bad
Cable's good; I tried both connections on the new hard drive. Worked fine.

>Assume master/slave produces a problem
Tried cable select. Again. Still no go.


Also.

>Confirm it has only ONE partition

Did that.

...I'm looking at instructions for setting up the old hard drive, and while it says to put in the power cord if it's a master, it omits saying such if it's a slave.

I assume they left it out 'cause it would be redundant, right >_>

doin' some research, I'm told that the "cable select" setting is only available on a specific kind of cable, and that cable select is the only option FOR said cable.

The original [old] hard drive was configured to cable select to begin with.

I'm thinking it may be a problem with the BIOS...? I mean, the computer is circa 2003, so it's possible. Gonna try this update for it [yes, it is in fact for this specific BIOS, etc]

Upgrading the BIOS didn't help. Shit.

New drive works on cable select configuration, but the minute I plug in the old drive, the comp won't recognize either of them.

>>17
Actually the OP is in serios truolble and you are just macking things worser for him. This is the type of nonsense I would expect from a 10 yeah old not a mature 4chan user. This incidint will being investigating by 4chan authoritys, and I'm sure you will be banned as a result. In future, plesea do'nt be so unhalpfull and rude, and maybe you will juts be left alone.

We must still confirm by looking at the motherboard (not the IDE cable) that you're set on the 1st or only IDE controller.

Thanks for the link about the jumper settings on the Deskstar 180GXP.  That's one fucked-up drive, fella.  I would confirm that the drive is entirely readable (via BIOS and via a bootdisk with FDISK on it for partition inspection) when set to the default "16 logical head" setting, "Device 0 (Master)".

Once that's confirmed (which you may have done already), then mark one drive as master and the other slave and see if the BIOS recognizes them both.  Don't use the "Device 0 (Slave present)" setting.

The point here is once confirmed singly on IDE0, then set together as master/slave, the drive chain should function.

What size is the new drive?  You can google for general ranges of computer age and compatibility with drive sizes ... but even so, usually the BIOS just defaults to some setting that gives you the BIOS maximum of the drive, not the full size of the drive itself.  Well, there's some uncertainty there.

At this point, alas, pending further information of relevance, you should consider selling the drive for another one.  Luckily, reasonably large IDE drives are cheap.  You should be able to get an old 20 or 40GB drive from a local or regional small computer store for maybe 15 bucks, and they'd be glad to get rid of it.

[It's not the cable... I just tried it with another IDE cable from another computer. Same result. x_x]

>That's one fucked-up drive, fella

What? Why do you say that?


>....16 logical head setting

I haven't changed the jumper group. Every test I've done has been with the 16 logical head setting [I was mistaken earlier when I said it was 15] 'cause that's what it started out as, and that's how the computer always read it as.

>usually the BIOS just defaults to some setting that gives you the BIOS maximum of the drive, not the full size of the drive itself

Not a concern, thankfully. BIOS would have limited the new one to 137 gig, if I remember correctly, and it's reading at closer to 238/


Old drive size is 111 gig (listed as 120 gig), new one is 250 gig. My comp isn't really having problems with the new drive at all, aside from going apeshit when I try to connect it to the old one.

I know the old drive works. Hell the only thing wrong with it is I fucked up XP on it. The whole point of getting the new drive I got is so I could slave the old one to it and keep the shit on it, as opposed to having to format the drive to reinstall windows.

Also.

>The point here is once confirmed singly on IDE0

...I don't understand. Are you refering to earlier when you suggested plugging one of 'em into where a CD drive would go? On the other IDE cable?

Also, question. There is an updated driver for the old hard drive. Once installed, would that affect <i> all </i> relations with said drive [including bios], or would it only affect how windows uses it?

No offense; I said the drive was fucked-up due to the 15/16 head crap.  It's been a long time since I've had to worry about CHS (cylinders, heads, sectors) settings for hard disks, and believe me, I don't miss that at all.  :^)

As for IDE0 and 1, I suggest separating the drives so that they aren't on the same controller.  If you have two IDE controllers on the motherboard, then you can connect up to 4 IDE devices.  Since you can just move them around a bit, then got from (I assume) this configuration:

IDE0: Master (new hard disk), Slave (old hard disk)
IDE1: Master or Slave (CDROM)

... to this:

IDE0: Master (new hard disk), Slave (CDROM)
IDE1: Master or Slave (old hard disk)

Now, we must address the "driver" thing.  I don't know what you mean.  Are you using some sort of hard disk size-adjusting driver like the stuff from Ontrack?  That might well explain all this fuss.

New HDD and GTFO

>>28
I just spent $80 on this new one; I'd like to explore all the possibilities without having to get another one.

>>27

>As for IDE0 and 1, I suggest separating the drives so that they aren't on the same controller

'kay. I'll try that, then. Although if that does work, I won't be able to use either my DVD drive or CD drive...but it's better than nothing.

>Now, we must address the "driver" thing

I've never used a driver for a hard drive. Up until recently I never knew there WERE drivers for hard drives. All I know is when I went to Dell to see if there was any updates for my comp that might fix this, and it listed one for my old hard drive. Too bad Dell doesn't fucking list what those upgrades actually fucking DO.

>>29
Please look at my diagram in message >>27.  All you need to do is re-arrange the devices on the drive chains, not remove them.  To wit:

IDE0: HDD1, HDD2
IDE1: CD, DVD

... becomes:

IDE0: HDD1, CD
IDE1: HDD2, DVD

... which works just as well provided they're jumpered correctly.

>>30
To wit, alas, yea verily this whale be a faggot.

>>30
I knew exactly what you meant [but thanks for the effort :3]

I was refering to the fact that the cd drives on my computer are in larger bins than the hard drives, making switching one for the other impossible, and there's only maybe two inches between the connection points on the cables. They won't reach.

>>31
I BITE MY THUMB AT YOU, SIR

....And now everything's out the window. My computer isn't recognizing my old hard drive, period. Which is the hard drive it came with.

sweetmotheroffuckinghell

I put on my robe and wizard hat.

Just tried the old HD in another computer; it results in the same problems I've been having, with two notible exceptions.

One, the HD I slaved it to actually showed up in BIOS whilest being master. Two, for whatever reason, the CD drive magically dissapeared during this as well, and it's on the seccond fucking IDE cable. O___o


...although actually the computer I tested this on is older than mine. [And was hit by fucking lightning years ago.] It's also the one I've been using to post from. It's circa 2001, BIOS version A02 [as opposed to A03, which my computer had before I updated it the other day to A04] and has a seagate 40 gig HD.




So... new thread topic: Data recovery. ;__;

...And methods of figuring out exactly WHY the HD isn't working. And potential ways of fixing it, if possible.

At some point, a man's gotta concede.  Tip the piece over and shake the hand of your opponent.

In other words, try to recover whatever data you can, and set those two drives aside as suspicious trash.  Hard disks are fortunately cheap and for another 30 bucks or more, you'll get past all this.

When a hard disk is appropriately jumpered Cable Select and slapped on the cable anywhere, then the BIOS should see it without any problems.  Again, if you still want to confirm any of that, just simply the system (get rid of all other IDE devices and confine yourself to IDE0 and the end plug) and then work your way "up" (i.e. more complexity) from there.  Computer work is a matter of making simple, confirmed changes, one step at a time.  As soon as you assume, or take two or more steps at once, you're risking missing a problem or configuration and then you'll suffer.

Trashed computer stuff looks every bit as functional as the working stuff.  THAT's why you have to be methodical.

>>37

First, I wanted to thank you for the help you've given. :3

>Tip the piece over and shake the hand of your opponent.

I don't know how the fuck I managed to catch that Chess reference. I suck at chess. [What with the whole "GOD JUST FUCKING GO ALREADY" mentality, etc]


I'd like to reiterate that the point of all this was to access data on the old drive, not to have more space available. [although having more space is a side benefit.]

The drive not working is currently a problem, but not an ultimatium. I need the data, and I'll pay out the ass to get it if I need to.