Windows 10: Storage HDD slows PC down substantially

Wow - no idea what the problem is. I hope you get it sorted with a Samsung SSD. Sorry we couldn't be of more help.

 

I can't help I am afraid because I have a similar problem. I hadn't found your post when I posted a help request earlier at external hard drives impacting startup performance

Certainly bizarre because like you I have two drives that are not actually doing anything unless I access them but are working very hard on startup

 

I know its weird hey? I've read about quite a few people having the same issue but no one can offer a solution. I can also understand 1 drive having an issue and its a drive problem but 3 drives in about 6 months!
I've removed the drive from my computer and copied everything over to an external drive and now my PC is flying again and everything is accessible and working from the external drive.
Hopefully the new SSD will offer a solution as it will only be a 500Gig compared to a 2TB as I have a suspicion that the capacity was causing the issue, weird but I'll keep you informed.

 

Did you ever try partitioning the 2TB into, say, 2x1TB partitions to see if that made a difference? Just curious.

 

Unfortunately I never got the opportunity as it started giving issues straight after I transferred my data onto it. Just kept getting error messages although every scan I did was clear.

 

Is that a suck it and see idea or is there any scientific reason for it. In my case they disks are working using resources when they aren't being utilised so I don't see how partitioning would make any difference. You may well have a very good reason for thinking otherwise.

 

It's just so odd. I have a Samsung 250GB SSD for my OS, a 1TB WD internal spinner, a 2TB Seagate internal spinner and a 5TB Seagate external HDD, and I have no problems whatsoever.

 

Well, let's see. We'll look at basic partitioning information from Wikipedia:

Creating more than one partition has the following advantages:

• Separation of the operating system (OS) and program files from user files. This allows image backups (or clones) to be made of only the operating system and installed software.
• Having a separate area for operating system virtual memoryswapping/paging.
• Keeping frequently used programs and data near each other.
• Having cache and log files separate from other files. These can change size dynamically and rapidly, potentially making a file system full.
• Use of multi-boot setups, which allow users to have more than one operating system on a single computer. For example, one could install Linux, BSD, Mac OS X, Microsoft Windows or other operating systems on different partitions of the same HDD and have a choice of booting into any compatible operating system at power-up.
• Protecting or isolating files, to make it easier to recover a corrupted file system or operating system installation. If one partition is corrupted, other file systems may not be affected.
• Raising overall computer performance on systems where smaller file systems are more efficient. For instance, large HDDs with only one NTFS file system typically have a very large sequentially accessedMaster File Table (MFT) and it generally takes more time to read this MFT than the smaller MFTs of smaller partitions.
• "Short stroking", which aims to minimize performance-eating head repositioning delays by reducing the number of tracks used per HDD.[3] The basic idea is that you make one partition approx. 20–25% of the total size of the drive. This partition is expected to: occupy the outer tracks of the HDD, and offer more than double the throughput — less than half the access time. If you limit capacity with short stroking, the minimum throughput stays much closer to the maximum. This technique, however, is not related to creating multiple partitions, but generally just creating a partition less than the disk size.
  • For example, a 1 TB disk may have an access time of 12 ms at 200 IOPS (at a limited queue depth) with an average throughput of 100 MB/s. When it is partitioned to 100 GB (and the rest left unallocated) access time may be decreased to 6 ms at 300 IOPS (with a bigger queue depth) with an average throughput of 200 MB/s.
• Partitioning for significantly less than the full size available when disk space is not needed can reduce the time for diagnostic tools such as checkdisk to run or for full image backups to run.

So, I don't know - do you consider that a "suck it and see idea"?

Your situation is a bit different than the OP's.

 

Just a thought, have you tried turning off Fast StartUp.

This really shouldn't make a difference with just the one Operating System on the SSD but it gave me problems when I had Windows 7 on SSD & Windows 10 Preview on HD. When Windows 7 was rebooted it saw numerous HD errors because Windows 10 hadn't effectively closed the HDs.

 

Yes I did turn off fast startup and it actually slowed things down even more. With my "H" drive removed, it makes no difference whatsoever if its on or off.
The only things on my SSD "C" drive are my O/S, Office & ESET Anti Virus.