Windows 7 Not Recognizing HDs

wiredcrazy

Honorable
Nov 8, 2013
4
0
10,510
Okay, so I have three WD Caviar Black 1TB drives installed. Everything was fine until my main drive (C:\) with the OS installed failed. So I got a new drive, installed Windows 7 Pro fine, but now it won't recognize the other drives. Well, sort of won't. I had a C:\ partitioned into two drives, a D:\ and a Z:\. It won't recognize the Z:\ at all, but it DOES recognize the D:\. However, it now lists it as "New Volume", and nothing I had on it is showing up. Which really kind of sucks as I had most of my backups off my C:\ there. All three drives are recognized in BIOS so I have no idea what could be going on. Any suggestions? Thanks for any help.

By the way, I have a Gigabyte X58A-UD7 motherboard.
 
Solution
Your use of terminology is a little confusing.

Physical disks (actual hard drive units, in this case you say 3x 1TB Caviar blacks) must be partitioned and formatted in order to be used in a computer. This partition may extend to use all of the available space on one physical disk, or some smaller part of it. Thus, one physical disk has the potential to contain more than one disk partition. Depending on how you set these partitions up, they may be assigned a drive letter (this is the most common/popular method). These partitions, once created, formatted and assigned a drive letter, then appear in your OS, for example, in "my computer" in windows. In windows installations, the OS partition (the primary partition on which the operating...

Szyrs

Distinguished
Aug 28, 2013
218
0
18,810
Google Chkdsk, download it, run it and use it to recover your lost partitions. It should be able to find your lost data and rebuild your lost partitions, making the data accessible. It takes a little bit of thought to learn how to use but it's come in handy for me many many times. Much more handy than any other recovery software.
 

wiredcrazy

Honorable
Nov 8, 2013
4
0
10,510
Well, I feel kind of idiotic as my D:\ was the partitoned part of my C:\ (D'oh!) but I bought an enclosure and was able to recover most of my backups. But it's still not recognizing the third hard drive.
 

Szyrs

Distinguished
Aug 28, 2013
218
0
18,810
Your use of terminology is a little confusing.

Physical disks (actual hard drive units, in this case you say 3x 1TB Caviar blacks) must be partitioned and formatted in order to be used in a computer. This partition may extend to use all of the available space on one physical disk, or some smaller part of it. Thus, one physical disk has the potential to contain more than one disk partition. Depending on how you set these partitions up, they may be assigned a drive letter (this is the most common/popular method). These partitions, once created, formatted and assigned a drive letter, then appear in your OS, for example, in "my computer" in windows. In windows installations, the OS partition (the primary partition on which the operating system is installed) is ALWAYS "C:"

In your first post, it sounded like your setup was this:
;
Physical disk 0/1TB Caviar Black 01 = C: + D: + Z:

So in "my computer" you would have had these three drives appear as separate drives.

When you say that D: was a partition of C:, it sounds as if you may have attempted to partition your Physical disk that contained your C: partition. For reasons that I hope are more obvious to you now, this action would corrupt your windows install by pretty much destroying your C: partition.

If in fact you had three physical disks - that is to say 3 separate 1TB caviar black hard drives, then how was each drive partitioned because if the first physical disk was divided into 2 partitions, C: & D:, and Z: occupied an entirely separate physical disk, then that leaves an entire physical disk unaccounted for. OR if instead one physical disk was divided into 3 partitions (C:, D: & Z:) (which is what you've written) and only the C: partition is corrupted, then chkdsk may still recover your partition table, which will allow you access to your D: & Z: partitions - although you'll want to immediately back them up to a separate physical disk.

As good sense dictates, there is almost no use at all in backing up your system or data to the same physical disk, as it is disk failure that you are trying to protect yourself from.

Please explain again what your partition configuration was, with reference to the 3 physical disks that you listed in the original post. Also, please confirm that all three partitions (C:, D: & Z:) all existed at the same time, and that you did not partition your C: into two partitions, D: & Z:

That will make your question easier to answer.




 
Solution

wiredcrazy

Honorable
Nov 8, 2013
4
0
10,510
Previous setup:
HDD1- two partitions, C:\, D:\ (I'd actually forgotten the D:\ was a partition)
HDD2- H:\
HDD3- Z:\

Current setup
HDD1 -C:\
HDD2- D:\ (The H:\ got assigned a new drive letter as the D:\ partition is no longer there)
HDD3- No longer recognized.
 

Szyrs

Distinguished
Aug 28, 2013
218
0
18,810
If you open "Disk Management" what does it say for the Z:?

Start menu > right click "my computer > select "Manage" and find Disk Management towards the bottom of the tree in the left hand pane of the window that opens.

Just to confirm, you've not had any trouble with data loss on your HHD2? It'sonly the Z: that you are now trying to recover?

 

wiredcrazy

Honorable
Nov 8, 2013
4
0
10,510
Sorry for the delayed reply, I didn't receive an e-mail telling me anyone had replied to my topic. Here's a screenshot of Disk Management.
http://img.photobucket.com/albums/v715/wired_crazy/Disk.jpg

I noticed it changed/removed the drive letter for the 3rd hard drive. Could that possibly be why Windows won't recognize it in Explorer? I'm going to try changing the drive letter now. Thanks for all your help.

[edit] EUREKA! That was it! I've no idea why Windows would remove the drive letter but all I had to do was reassign the drive letter. Thanks again to all who helped.
 

Szyrs

Distinguished
Aug 28, 2013
218
0
18,810
Windows assigns the drive letters. Conflicts in that area are usually related to the drive's unique ID - I've only ever had issues with it from drives that used to be in RAID arrays... Glad you sorted it!
 

TRENDING THREADS