HDD freezes after writing big ammounts of data under Windows

kubci98

Commendable
Oct 12, 2016
2
0
1,510
Hi,
I am having an issue on my ASUS F556 laptop. I have decided to install an SSD, which I put into the main HDD slot, and moved the original HDD to the DVD slot. Then I have installed Windows 10 on the SSD and elementaryOS on the HDD.
However, every time, when I am writing a lot of data to the HDD using Windows (copying files from ext. hard drive, downloading Steam games, etc.), the hard drive freezes after a while (3-7 minutes), and then it doesn't respond until I restart the computer. Task manager says that it is being 100% used, although there are no processes using it. If I try to open the drive in Explorer, it lets me navigate the root folder and sometimes some subfolders too, but if I go too deep in the folder structure, or if I try to edit something, it goes into Not Responding state. Also, if I try to restart the computer, it gets stuck on "Restarting" screen, and never actually turns off. I have no other issues with the drive, if I don't start writing big amounts of data, it doesn't freeze even after a few hours of regular usage.
There are no issues when I am using elementary, therefore I don't think this is an hardware issue. CrystalDiskInfo says that the drive is in good state (although it doesn't work if the drive has already frozen, and it goes into Not responding if the drive freezes while the program is open).
Does anybody know what the problem might be? Thanks in advance.
 
Solution
I see. Well, the good news is that it sounds like the hard drive is OK according to the tests. So what I'd recommend is that you try the suggestion about giving a go of the HDD with a different computer with and without using the drive caddy, to see if there's a difference. If it works without those issues while connected without the caddy, then it would probably mean that the caddy is the one to blame.
You could also try updating your OS if you have available updates and see if that fixes things up.
Hey there, kubci98.

It is strange indeed. Anyway, having in mind you're experiencing HDD issues, even if there's a chance that it might not be a hardware problem, it's better to be safe than sorry, so I'd suggest that you backup your important data just to be on the safe side.
SMART data does not always provide the full picture, that's why after you backup your files, you should download the HDD manufacturer's diagnostic tool and run the tests, to see if anything alarming pops-up.
Try the drive with a different computer, to see if you'd still experience the same problems. Check if the HDD caddy that you're using has a driver you can install to see if that fixes the issue.

Hope that helps. Please let me know how everything goes.
Boogieman_WD
 

kubci98

Commendable
Oct 12, 2016
2
0
1,510


OK, so I did all the tests that Seagate Seatools had to offer, but none of them found any problem.
But I have noticed something that might be interesting - there is always a change in writing speed after the first 650-700MB.
When I was downloading stuff over Steam, the disc always froze after every 700-750MBs (then stopped working completely).
But then I tried copying some stuff from the SSD to the HDD (wanted to make screenshots of copying dialogs but I couldnt save them after the disc froze, not even to the SSD):
18 GB folder - doing fine the first 700MB, then complete freeze.
1.6GB folder - slows down after the first 700MB (from 400MB/s to 40MB/s), but then completes.
1.3GB iso file, 900MB iso file, 950MB avi file - same as 1.6GB folder
3.8GB iso file - slows down after the first 700MB, halts at 1.8GB and freezes.
I mean, sure, it might be just coincidence, but I just thought this might bring some light into why this is happening.

BTW, I have all my data backed up, learned to do that the hard way 2 years ago. But thanks for the reminder
:).
 
I see. Well, the good news is that it sounds like the hard drive is OK according to the tests. So what I'd recommend is that you try the suggestion about giving a go of the HDD with a different computer with and without using the drive caddy, to see if there's a difference. If it works without those issues while connected without the caddy, then it would probably mean that the caddy is the one to blame.
You could also try updating your OS if you have available updates and see if that fixes things up.
 
Solution