SSD malfunctioning--- able to save?

Dudeguyy

Distinguished
Jun 12, 2014
35
0
18,530
I have W 8.1 running on a custom rig with 2 TB storage HDD and 64 GB SSD for the OS.

Unplugged power supply from surge protector when system kept awakening from sleep for no reason.

The next morning, could not boot from SSD. Had to install W8 from recovery onto HDD and currently booting from that.

Tried refresh/repair/reset startup options as well as cmd prompt utilities (chkdsk, sfc scannow, bootrec commands) but nothing could restore SSD OS to normal functioning. Sfc wouldn't even initiate for some reason, which is probably a whole nother issue.

Tried wipe and clean install of W8 on SSD but still no dice. Seemed to be locked or inaccessible upon startup.

SSD not listed under Computer upon startup. However, awakens with system notification popup (SSD drive D: listed as well as random system reserve partition I didn't create) upon awakening computer from HIBERNATION.

Any idea what is going on? Is this SSD able to be salvaged or is it toast?
 
Solution
I confess that I'm having difficulty understanding the numbers.

FWIW, I found the following SMART stats for version 2.4 of the firmware:

http://webcache.googleusercontent.com/search?strip=1&q=cache:http://sourceforge.net/p/smartmontools/mailman/message/31850001/

It does appear that attribute 173 (whatever it is) has a problem. In the other example its raw value is 38655754245 which equates to 0x000900100005 in hexadecimal. This would suggest that the raw value consists of three 16-bit values, namely 0x0005, 0x0010, and 0x0009.

http://www.google.com/search?q=38655754245+in+hex

Attribute 175 is described as "Program_Fail_Count_Chip", but this may or may not be correct. In any case yours has a normalised value of 92 which would...

Dudeguyy

Distinguished
Jun 12, 2014
35
0
18,530
Fzabkar... Ran SpeedFan online analysis of the SSD. This is what it turned up:



Your hard disk is a ADATA SP600 with firmware 2.1.
NOTE: a S.M.A.R.T. model for this hard disk is not available (yet). Attribute comparison has been made against standard values. New models are computed often and in the future this hard disk should take advantage of the additional crowd knowledge.

Your hard disk temperature is 39C.

Attribute Current Raw
Raw Read Error Rate 100 000000000000
Throughput Performance 100 000000000000
Spin Up Time 100 000000000000
Reallocated Sector Count 100 000000000000
Seek Error Rate 100 000000000000
Seek Time Performance 100 000000000000
Power On Hours Count 100 000000000EEC
Spin Retry Count 100 000000000000
Power Cycle Count 100 0000000005EB
Unknown attribute 167 100 000000000000
Unknown attribute 168 100 000000000000
Unknown attribute 169 100 000000000000
Unknown attribute 173 1 000000000000
Unknown attribute 175 92 000000000000
Power Off Retract Count 100 000000000026
Current Pending Sector 100 000000000000
Write head 100 000000000000
Unknown attribute 243 100 0000000024F6

All the attributes of your hard disk are above the S.M.A.R.T. thresholds set by the manufacturer. This is good.

The overall fitness for this drive is 92%.
The overall performance for this drive is 100%.



Obviously I'm no expert, but should that unknown attribute 173 be at 1? Other than that, to an untrained eye, nothing seems off.

I will continue to work with anybody who has any idea why it's doing this stuff. I appreciate all the help greatly!
 
I confess that I'm having difficulty understanding the numbers.

FWIW, I found the following SMART stats for version 2.4 of the firmware:

http://webcache.googleusercontent.com/search?strip=1&q=cache:http://sourceforge.net/p/smartmontools/mailman/message/31850001/

It does appear that attribute 173 (whatever it is) has a problem. In the other example its raw value is 38655754245 which equates to 0x000900100005 in hexadecimal. This would suggest that the raw value consists of three 16-bit values, namely 0x0005, 0x0010, and 0x0009.

http://www.google.com/search?q=38655754245+in+hex

Attribute 175 is described as "Program_Fail_Count_Chip", but this may or may not be correct. In any case yours has a normalised value of 92 which would suggest that there is a problem of some kind.

It appears that revision 2.4 of the firmware may not be reporting raw values for several of the attributes. One can only imagine why. Perhaps if we could identify the flash controller, then we may be able to find documentation for generic SMART attributes.

 
Solution

Dudeguyy

Distinguished
Jun 12, 2014
35
0
18,530
Sooo... excuse me fzabkar, I'm a bit of a noob when it comes to SMART reports and SSD workings. This is my first one. You seem much more knowledgeable in this than I am. What does this all mean?

I am thinking of just buying a 128 GB SSD new online, doubling my storage, cutting my losses, and starting over. I've already gotten everything I need off of this one. Is it totally failed or is there some way to save it?
 
What I'm saying is that terms such as Spin and Seek make no sense when referring to an SSD (which neither spins nor seeks). These are HDD attributes. In fact it's not just the SMART software that is reporting these attributes incorrectly, it's JMicron's own lousy "technical" documentation. Therefore one would have to ask whether any interpretation of JMicron's attribute values could be relied upon.

The Power On Hours Count is telling you that the drive has recorded 3820 hours (= 0xEEC). That seems reasonable. However, most of the other raw values are zero, including the problematic (?) ones, 173 and 175. That makes it difficult to reach any kind of conclusion as to their actual state. NAND flash chips have a finite number of Program/Erase cycles before they wear out, and the normalised value of 1 in the Erase Count attribute (173) would appear to be suggesting that this has already happened. But I'm not certain.