Faulty SSD? (data transfer errors)

Associate
Joined
31 Oct 2005
Posts
247
Location
Yorkshire
no nosying
 

Attachments

  • k6dMqHG.png
    k6dMqHG.png
    82 KB · Views: 19
  • AHJQw3U.png
    AHJQw3U.png
    49.3 KB · Views: 10
  • lljJjlu.png
    lljJjlu.png
    82.2 KB · Views: 9
Last edited:
all you can do is back it up and keep your eye on it,idk if its still in warranty?

it could just be a software bug
 
Doesn't seem to be any of the normal indicators of a failing SSD - its not using retiring blocks or using reserve blocks, error correction counts are nominal, etc.
 
its strange that the health of the drive has dropped 13% since you have had the drive considering its only been in the system since Saturday afternoon.

what errors are you getting when copying over data? you shouldn't be getting errors when transferring data to it, I have 2 x 850 evos (250GB) and get no errors when transferring data between the two.
 
Forget about it. Its your controller. I have 2 Dell M6300 laptops with sandisk Ultra 256Gb and they both show the same symptoms, however both have been chugging away for over 2 years ime. When i moved one Ultra to another laptop for a few weeks the errors stopped piling up and the health never dropped below 88% Wouldn't sweat it tbh. Seems theres some weird Sandisk attribute in SMART that causes this, i've not experienced data corruption (SFC'ed them now and then) or problems, just the annoying SMART reports.
 
what motherboard do you have?

other option to try is to connect is to a sata 2 port instead of sata 3 providing they both use different controllers and see if you still get the same issues.

you will not get your full read and write as its using sata 2 but will see if you still get the errors or not still appearing.
 
It could be that A8 attribute - depending on controller its an unrecoverable error counter on some drives and on others just used as a flag for debugging and actual data is meaningless - it could be the first piece of software is mistakenly identifying it as an error counter or it could be an actual error counter in which case A8 is most often caused by link failure i.e. a dodgy cable. (I don't know enough about which controller implements it as what to be any more helpful than that though).
 
Last edited:
Back
Top Bottom