I have a seagate barracuda 7200.11 500gb hdd that I used to use as my primary drive. I am now using an SSD and connected the sata drive up to use as a second drive but it is only showing as being 500mb rather than GB I have formatted the drive but it seems to default to this smaller size. Any help on getting it back to full size much appreciated.
Can you post screen from disk management showing all details so we can see
Hi Samuria
Screen shot attached as requested
Many thanks
- - - Updated - - -
Samuria
Forgot to mention it was Disk 3 labeled old 500GB Drive
Regards
Make a capture with the snipping tool then upload it, How to Upload and Post Screenshots and Files at Ten Forums and it will be easier for others to view it.
If that was a drive you had booted windows from it likely has some system partitions that will rob you of a bit of disk space.
In Disk Management in the lower pane, Disk 2 is showing as Unknown Not Initialized. How do you have the drive attached to the computer? Is it internally or is it via a USB adapter, dock or Enclosure? If the later, are you using the USB-SATA adapter with it's own power adapter? Are you plugging the USB drive into the Back USB port (desktop)?
If internally, try a different power plug, and a different Data cable. Put your ear next to the drive, do you hear it spinning up? Or is it silent, cold?
Not only that, but the so-called ' OLD 500GB Hard Drive' is not what the OP thinks it is. It is actually the first partition on disk 3, is only 400MB and has been formatted and named in error. The second partition on disk 3 is 110.84GB and labelled 'OLD 120GB SSD' and the third partition of disk 3 is a 471MB recovery partition.
I would guess that the real 500GB hard drive is disk 2, the one that does not initialise. And my suspicion for the reason it doesn't initialise is that at some point the old 500GB drive was cloned to (or from) another of the disks in this system and both disks now have the same disk signature. Windows can only mount one of them.
@drew1000, please confirm if this is indeed the case, and if so, which disk is the clone of the old 500GB disk.
Fixing Disk Signature Collisions s BlogIn most cases, you can operate with cloned disk images unaware that they have duplicate disk signatures. However, on the off chance you attach a cloned disk to a Windows system that has a disk with the same signature, you will suffer the consequences of disk signature collision...
...Windows requires the signatures to be unique, so when you attach a disk that has a signature equal to one already attached, Windows keeps the disk in “offline” mode and doesn’t read its partition table or mount its volumes...
NB: do NOT follow the steps in the above article to try and fix this. It's an old article and applies to MBR disks on legacy systems. The EFI partition on disk 0 suggests this is a UEFI system with GPT disks.
Open a Command Prompt (Admin) and type DISKPART then in Diskpart run the following commands...
(don't worry, all they do is display information about your disks)LIST DISK
SELECT DISK 2
UNIQUEID DISK
now, if you did clone the old disk, select the disk you cloned it to/from (for example, if it was disk 0, then use 0 in place of # in the next command)SELECT DISK #
UNIQUEID DISK
Please copy and paste the results into a post, then we can see how best to proceed. When done, type EXIT to close Diskpart.
Last edited by Bree; 11 Apr 2019 at 21:32.
Quote
