New SSD going read-only at random times about once a month.

k.yepes · 12-06-2020, 05:07 PM

I did notice this: See how below it says "5" command failed due to icrc error?

I think this has now happened 5 times to me...(where the drive misbehaved like this)

Code:

Pending Defects log (GP Log 0x0c) not supported

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x0001  2            5  Command failed due to ICRC error
0x0002  2            0  R_ERR response for data FIS
0x0003  2            0  R_ERR response for device-to-host data FIS
0x0004  2            0  R_ERR response for host-to-device data FIS
0x0005  2            0  R_ERR response for non-data FIS
0x0006  2            0  R_ERR response for device-to-host non-data FIS
0x0007  2            0  R_ERR response for host-to-device non-data FIS
0x0008  2            0  Device-to-host non-data FIS retries
0x0009  2            8  Transition from drive PhyRdy to drive PhyNRdy
0x000a  2            8  Device-to-host register FISes sent due to a COMRESET
0x000b  2            0  CRC errors within host-to-device FIS
0x000d  2            0  Non-CRC errors within host-to-device FIS
0x000f  2            0  R_ERR response for host-to-device data FIS, CRC
0x0010  2            0  R_ERR response for host-to-device data FIS, non-CRC
0x0012  2            0  R_ERR response for host-to-device non-data FIS, CRC
0x0013  2            0  R_ERR response for host-to-device non-data FIS, non-CRC

computersavvy · 12-07-2020, 09:15 PM

Quote:

Originally Posted by k.yepes

I called newegg today and honestly I feel like the gentleman I spoke to had no clue. They basically told me, "well- since you didn't buy our warranty you need to call samsung, here 1800-726-7864". I called them (not being sure if they were open because it is a Sunday) and the automated robot transferred me to a SEAGATE recording (I did not know SAMSUNG drives were SEAGATE??!?) where they told me they were closed. I will call them back tomorrow and see what they say.

If you are still within the 90 day window after purchase newegg will RMA it. If beyond the 90 days then the mfgr warranty applies. I have been through that hassle.

k.yepes · 12-07-2020, 09:18 PM

I am just outside. 8/25 was my purchase date.

computersavvy · 12-07-2020, 09:19 PM

Quote:

Originally Posted by k.yepes

I did notice this: See how below it says "5" command failed due to icrc error?

I think this has now happened 5 times to me...(where the drive misbehaved like this)

Code:

Pending Defects log (GP Log 0x0c) not supported

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x0001  2            5  Command failed due to ICRC error
0x0002  2            0  R_ERR response for data FIS
0x0003  2            0  R_ERR response for device-to-host data FIS
0x0004  2            0  R_ERR response for host-to-device data FIS
0x0005  2            0  R_ERR response for non-data FIS
0x0006  2            0  R_ERR response for device-to-host non-data FIS
0x0007  2            0  R_ERR response for host-to-device non-data FIS
0x0008  2            0  Device-to-host non-data FIS retries
0x0009  2            8  Transition from drive PhyRdy to drive PhyNRdy
0x000a  2            8  Device-to-host register FISes sent due to a COMRESET
0x000b  2            0  CRC errors within host-to-device FIS
0x000d  2            0  Non-CRC errors within host-to-device FIS
0x000f  2            0  R_ERR response for host-to-device data FIS, CRC
0x0010  2            0  R_ERR response for host-to-device data FIS, non-CRC
0x0012  2            0  R_ERR response for host-to-device non-data FIS, CRC
0x0013  2            0  R_ERR response for host-to-device non-data FIS, non-CRC

I would be more concerned with lines 9 and a which are probably related.

k.yepes · 12-08-2020, 06:48 PM

One thing- I took apart my box today to double check and make sure all the cable connections were good. I remembered when I saw it that I had bought one of those little adaptor carriages that holds the SSD and makes it fit like an old school hard drive in your rack. My cables install into the carriage, and the hard drive snaps into the carriage like an 8 bit nintendo game. So basically this is acting like an "extension cable" for the sata wiring. I took the hard drive and carriage out, and I cut the end off of the carriage so it is just a mechanical mount adaptor, there is no more circuitry in it. I am testing it now. Maybe this was causing connection problems? This thing was only $7.99 on amazon.

ondoho · 12-09-2020, 12:55 PM

Quote:

Originally Posted by k.yepes

One thing- I took apart my box today to double check and make sure all the cable connections were good. I remembered when I saw it that I had bought one of those little adaptor carriages that holds the SSD and makes it fit like an old school hard drive in your rack. My cables install into the carriage, and the hard drive snaps into the carriage like an 8 bit nintendo game. So basically this is acting like an "extension cable" for the sata wiring. I took the hard drive and carriage out, and I cut the end off of the carriage so it is just a mechanical mount adaptor, there is no more circuitry in it. I am testing it now. Maybe this was causing connection problems?

Seems likely.

k.yepes · 12-13-2020, 01:12 AM

Update - drive acted up again tonight, the "carraige" was not in between the sata cable and drive so this has been removed from the equation. I will be buying a replacement drive tonight and sending this back to Samsung.

k.yepes · 12-16-2020, 06:22 PM

Update- I replaced the drive and I am trying to work with Samsung for a replacement or repair. I bought a WD 500GB SSD "red" this time. I just clonezilla'ed my samsung to the WD drive and I am actually booted into and using the WD-RED now. Let's see if the problem comes back. I will update you all once I know what samsung does. Obviously I should nuke the samsung drive before I send it back (I don't want my personal info accessed).

k.yepes · 12-31-2020, 11:58 PM

Update- been running with the WD "RED" 500gb ssd for about 2 weeks now, no issues so far.

Funny thing samsung took the drive back for a "warranty repair" I got it back today from UPS. The paperwork that came with the drive indicates that it passed all of their testing and they simply just updated the firmware. Do you guys have any other thoughts on this?

ondoho · 01-01-2021, 07:19 AM

Are you sure it's the same drive?
Maybe they just gave you a new one instead of repairing it.

GPGAgent · 01-01-2021, 08:03 AM

Always mark anything you send back for repair in a way only you know. Or keep a note of it's serial number. Then you'll know if it's your drive or a replacement which may not be new.

Did you actually wipe it before sending it back? You said "Obviously I should nuke the samsung drive before I send it back (I don't want my personal info accessed)."

ondoho · 01-01-2021, 08:31 AM

^ nuke and wipe aren't the same thing IMO.
Nuke: destroy the MBR, making the data unusable
Wipe: overwrite every sector of the device

o770 · 01-01-2021, 08:34 AM

Quote:

Originally Posted by k.yepes

Do you guys have any other thoughts on this?

How is the SMART report on the new drive, is everything ok?
I think most SATA controllers were already version II on year 2010, however your system's report is showing this for the EVO drive:

Quote:

Originally Posted by k.yepes

Code:

SATA Version is:  SATA 3.2, 6.0 Gb/s (current: 1.5 Gb/s)

Is that right for your specs?

GPGAgent · 01-01-2021, 08:52 AM

Quote:

Originally Posted by ondoho

^ nuke and wipe aren't the same thing IMO.
Nuke: destroy the MBR, making the data unusable
Wipe: overwrite every sector of the device

how about wipe and nuke then?

k.yepes · 01-01-2021, 01:01 PM

Before I sent the drive in I took it to work and connected it to a work PC. I deleted all he partitions, formatted the drive, and then used SHRED command to write random data across the drive 4 full times before changing it to all zeros.

Of course I took a picture of all of the numbers before I shipped it back, and looking at what they returned everything matches.