We're missing a little bit of information here, so this idea is a "maybe" thing in two parts. Both of them depend on the exact way you transferred your data from your old HDD to this new one, and whether that matches with the options set in BIOS Setup for your drives.
For quick background, your description suggests that, at boot time, your system cannot make any sense of what is on the HDD and receives error messages and keeps on re-trying to read it. That causes it to work at 100%, AND to fail and to use up a lot of time re-trying. My two ideas are working towards finding whether that is because the BIOS settings don't match the way the HDD was originally Partitioned before data was copied to it.
1. For SATA hard drives there are often two way that the BIOS can deal with them. The "normal" way is to use them as proper SATA drives, or maybe known as AHCI devices. In addition, many mobos still have a configuration option for some of their SATA ports (sometimes, this option applies to ALL SATA ports at once) called IDE or PATA Emulation, or maybe Compatibility. This was a work-around included in a lot of BIOS's a decade ago because SATA drives and Windows XP were introduced at nearly the same time. Win XP did NOT have a device driver for this new AHCI type of device, but it always did have a way to add the required driver at the time of the initial installation IF you chose to do that. Many people did not. Instead, they used the "Compatibility" setting in BIOS. This basically did NOT use any of the new features of SATA drives and used only the existing IDE drive features, thus making Windows think that it was dealing with drives it DID already have a built-in driver for, and it was happy. (This configuration option was no longer needed with Windows Vista and later, but may people continued to use it anyway.) The "problem" with that, though, is that some of the organization data on the HDD is different, depending on which BIOS option was set when the HDD first was Partitioned and Formatted. So, if you had a HDD done in the "IDE Emulation" mode and then changed the BIOS setting there to AHCI or true SATA, the BIOS could not read the disk any more, generating continuous read errors. Now, YOU have installed a SSD, and most such devices specifically recommend or require that you set the BIOS option for the SATA port it is connected to to be AHCI. Often this means that ALL of your SATA ports now are being used as AHCI devices. So, IF your HDD was originally done under an IDE Emulation setting, now your mobo cannot read the drive any more. That's one possibility.
2. The second possibility is what type of Partition scheme has been used. Until a few years ago the only option (almost) was called the MBR system. It is limited to drives of no more than 2 TB. So to use newer larger HDD's a new Partition system called GPT was introduced, and it can handle drives MUCH larger than any made today. The organization of data is different for these two systems, so Windows needs to have device drivers for both if they both are used in one system. In addition (this MAY not apply to you, OP), in order to BOOT from a device using the new GPT Partition system, your BIOS must have a feature called UEFI Support and have it enabled. That last item is NOT required if your BOOT device is still using the older MBR system; since most SSD's are under 2 TB, either Partition system may have been used when it was Partitioned. BUT if your HDD is set up under the GPT system, then Windows still will need to have the device driver for GPT-partitioned devices installed to be able to use it. And just to make that a little tricky, some Windows 32-bit versions never had such a driver included with them, and that driver was only available for 64-bit versions of Windows. So, IF it happens that your SSD was Partitioned using the older MBR system (that would be just fine) BUT the HDD was set up on another machine using the GPT system, then it is possible that your Windows does NOT have the required GPT-type device driver installed, and it is WINDOWS that cannot find (well, understand, really) any data to use on that HDD.
So, what can be done to fix this, if either of those scenarios is the cause? Basically the same solution - wipe out the data on the HDD and re-Partition it properly. BUT you MUST ensure you have a full copy of all your data from it somewhere safe before doing this!! When you are SURE you have a good safe copy of EVERYTHING, you can proceed in this sequence.
A. Install the HDD in any machine that can access it cleanly. Under Windows Disk Management, for every Partition that is present, RIGHT-click on it and Delete the Partition, until all of them are gone and the entire disk is just Unallocated Space. Back out and shut down, and remove the HDD.
B. Install that HDD in your "troubled" machine. When you start up, go directly into BIOS Setup and check the configuration of the SATA ports. Ensure that they all are set to "Native SATA" or "AHCI"; if you have to change anything, be sure to SAVE and EXIT. The machine should reboot cleanly from the SSD without any long delays, but you will NOT be able to "see" that HDD in Windows Explorer. Use Disk Management to find that HDD - it may be lower down in the list, so remember that the list SCROLLS. RIGHT-click on the large Unallocated Space and choose the Create a New Simple Volume. Watch carefully about a few options before proceeding. Make sure to choose the MBR system, not GPT. You want it to use up ALL of the available space on that HDD in this one volume. This Partition does NOT need to be bootable since you are only going to boot from the SSD. It will propose to set up the NTFS File System, and that is OK. You will have the choice of using a Quick Format or a Full Format. Quick will do the basic job pretty quickly. A Full Format will do a thorough check of the entire drive and isolate any Bad Sectors so they don't cause any future problems, but it may take several hours to do. When you have all the options set your way, let the process run. When it finishes, back out of Disk Management and reboot. Your system should boot up and you should now be able to see the HDD as an empty drive in Explorer.
c. Copy all your old files back onto the new empty 2 TB HDD from the back up you have.
Facebook
Twitter
Instagram