-2

Do some solid state drives have a hard time dealing with instructions when they have low free space? Or should I expect that the drive is at the end of its life (at just over 1 year)?

Background:

My friend has a Toshiba Q Series (Model: THNSNJ256GCST) solid state drive that is about a year old and while downloading a game (~50 GB) from Steam, it became completely unresponsive. His computer suddenly locked up, rebooted and then told him he had no OS.

On the off chance that it could be recovered, he left it with me to see what I could do about recovering the drive or at least some of the files. I was able to do so with the help of another topic.

Before the drive was fixed:

Whenever I had the drive connected to my computer, the boot processes took a minute or two longer when detecting devices. Almost like the BIOS recognized a device there, tried to identify it, couldn't and decided to move on after a timeout period.

Using the answer linked above, I connected the drive to power only, turned the computer on for about 20 minutes, shut down the computer, connected the data cable and the drive was then recognized. When I tried to copy a large number of files off of the drive through Windows File Explorer, the drive became unresponsive again.

I was able to do this again after leaving it connected, power only, to my computer for about 8 hours while at work the next day (20-30 minutes didn't work this time). This time I used batch scripts to transfer the files and then deleted the game files from the drive. Since then it seems to be working fine (I'll update on this if the drive becomes unresponsive again).

With the downloaded files, the drive only had about 10% free space left on it, which leads me to wonder if it just needs a certain amount of free space to work correctly.

Daniel T.
  • 3
  • 4
  • You should list the Model number of the drive. The problem sounds like it is specific to specific models of SSDs. – surfasb Nov 04 '15 at 18:06
  • 2
    "Whenever I had the drive connected to my computer, the boot processes took a minute or two longer when detecting devices. " - *This basically confirms that there is something seriously wrong with the device.* If the drive is not using the current firmware, updating the firmware after you backup the data, would be a smart thing to do. The bad news is IF there is an update, and the firmware update addresses a problem with the firmware that prevents this problem, your friend likely should replace the drive. – Ramhound Nov 04 '15 at 18:06
  • @surfasb I've added the model number as suggested. – Daniel T. Nov 04 '15 at 23:35
  • @Ramhound I haven't found any firmware updates for this drive. I actually can't find any official information from Toshiba about this drive at all which makes me wonder about how long ago the drive was manufactured. – Daniel T. Nov 04 '15 at 23:37
  • Give us the model information. Toshiba out sources their SSD manufacturing. – Ramhound Nov 05 '15 at 00:03

1 Answers1

0

With the downloaded files, the drive only had about 10% free space left on it, which leads me to wonder if it just needs a certain amount of free space to work correctly.

The file system free space shouldn't have any appreciable impact on how well the storage device functions. It certainly shouldn't cause the drive to not be detected at all by the system firmware (historically BIOS, these days most often UEFI).

When I tried to copy a large number of files off of the drive through Windows File Explorer, the drive became unresponsive again.

Well, to answer the question in the title: I can't say for sure that this drive is about to die, but I can tell you that I wouldn't trust it for anything after it behaving like you describe. Even more so because if you are unlucky, misbehaving storage devices on SATA can freeze the whole system, and not just the one device that is having difficulties.

Check SMART data; that might give a clue as to what the problem is. Note that some drives are known to be notorious liars in SMART, and even if it doesn't and SMART indicates everything is well within the drive's intended operational limits that doesn't mean that the drive is fine. The BIOS might have a feature that allows you to run a self-test; if so, run a short self-test and look at the results, but treat the results as just one more data point and certainly not an absolute truth either way.

Even if the drive is nominally usable, I would consider it to be going through the final stages of dying, get as much of the important data off it as I could, and replace it. If it's still under warranty, return it to the manufacturer or reseller through their RMA process after getting the data off it.

Properly spec'd SSDs don't die from normal use, but unfortunately SSDs' failure modes tend to be pretty much catastrophic: it's happily chugging along one moment, then completely dead the next, and there's little to nothing you can do about it. This is because the primary failure with modern SSDs isn't so much flash failure as controller problems. (All the stories you hear about SSDs failing early are very likely to be controller problems, much more so than flash wear.)

While you're telling your friend that he will need to buy a new drive, also explain to him the value of proper backups. (Local, secondary storage or online backups in the cloud; just something that can be used to restore a system to bare metal.) He might very well thank you profusely later.

user
  • 29,449
  • 11
  • 99
  • 144
  • SMART is new to me, though I did see the setting for turning it off in my BIOS. I'll check the SMART data when I get back later this afternoon. I see that it can be checked through the command prompt but is there a specific tool you would recommend instead? – Daniel T. Nov 04 '15 at 19:30
  • @DanielT. Since I don't run Windows myself, I can't suggest any Windows tool for the job. On Linux, I would suggest the command-line tool `smartctl` which is often installed by default. It's likely that the BIOS setting you found doesn't actually *turn off* SMART, but more likely that it treats SMART "failed" status values as unimportant. – user Nov 04 '15 at 19:37
  • I tracked down a Windows distribution of `smartctl` and gave it a run and it came back clean, but like you said, it could still have problems. I had suggested to my friend that (if the drive stayed functional) he could use this drive as a secondary data drive as long as he didn't put anything important on it. Based on the information you provided about SATA being able to hang the entire system, I'll give him a warning if he still wants to try. Thank you for all the information, it was a big help. – Daniel T. Nov 05 '15 at 00:02