You may also want to read this forum.
2 x Samsung EVO 870 4 TB nach knapp einem Jahr mit defekten Sektoren
Hallo liebes Forum! Ich stehe momentan ein bisschen auf der Leitung, denn ich habe ein kurioses Problem, das ich so noch nie bei einen meiner SSD angetroffen habe. Seit gut 10 Jahren verwende ich Samsung SSD, derzeit ua 2 x Samsung EVO 870 4 TB (neben einer 980 Pro und einer älteren 860 Pro)...www.computerbase.de
System Name | Main |
---|---|
Processor | R7 5950x |
Motherboard | MSI x570S Unify-X Max |
Cooling | converted Eisbär 280, two F14 + three F12S intake, two P14S + two P14 + two F14 as exhaust |
Memory | 16 GB Corsair LPX bdie @3600/16 1.35v |
Video Card(s) | GB 2080S WaterForce WB |
Storage | six M.2 pcie gen 4 |
Display(s) | Sony 50X90J |
Case | Tt Level 20 HT |
Audio Device(s) | Asus Xonar AE, modded Sennheiser HD 558, Klipsch 2.1 THX |
Power Supply | Corsair RMx 750w |
Mouse | Logitech G903 |
Keyboard | GSKILL Ripjaws |
VR HMD | NA |
Software | win 10 pro x64 |
Benchmark Scores | TimeSpy score Fire Strike Ultra SuperPosition CB20 |
What I'm worried about is that the value that should be counted in SMART ID "05" (reallocated sector count) is replaced with SMART ID "FC" to deceive it? That's what it means.One one of my unaffected drives it went from 1210 two weeks ago to 1222 now. Still no bad sectors. For me, it can do whatever it wants, as long as there are no new bad sectors later.
I have a firmware update I can do, but I assume that won't magically fix my SSD, the damage is done.
System Name | Main |
---|---|
Processor | R7 5950x |
Motherboard | MSI x570S Unify-X Max |
Cooling | converted Eisbär 280, two F14 + three F12S intake, two P14S + two P14 + two F14 as exhaust |
Memory | 16 GB Corsair LPX bdie @3600/16 1.35v |
Video Card(s) | GB 2080S WaterForce WB |
Storage | six M.2 pcie gen 4 |
Display(s) | Sony 50X90J |
Case | Tt Level 20 HT |
Audio Device(s) | Asus Xonar AE, modded Sennheiser HD 558, Klipsch 2.1 THX |
Power Supply | Corsair RMx 750w |
Mouse | Logitech G903 |
Keyboard | GSKILL Ripjaws |
VR HMD | NA |
Software | win 10 pro x64 |
Benchmark Scores | TimeSpy score Fire Strike Ultra SuperPosition CB20 |
Not sure why some here to expect consumer grade hw not to fail (at all).
Ignoring that this might have been preventable in some form (by Samsung),
anything just close to +99% reliability will cost multiple times more, one reason mil/space stuff isnt cheap.
The damage to some of your data is done (those files that are partly stored in bad sectors), but the SSD can be brought back to a fully usable state. I've been using my affected SSD for over 10 months now and the original bad sectors have been remapped with good ones, as well as no new ones developing (probably thanks to the firmware update). Of course, i don't fully trust this SSD anymore, and i shall RMA it eventually, but the SSD can recover from the problem.
But once you get all your intact files off the drive and delete the couple affected files that can't be fully read out anymore, then the drive should remap the bad sectors and you will have the full capacity worth of good sectors again.
System Name | Work Computer | Unfinished Computer |
---|---|
Processor | Core i7-6700 | Ryzen 5 5600X |
Motherboard | Dell Q170 | Gigabyte Aorus Elite Wi-Fi |
Cooling | A fan? | Truly Custom Loop |
Memory | 4x4GB Crucial 2133 C17 | 4x8GB Corsair Vengeance RGB 3600 C26 |
Video Card(s) | Dell Radeon R7 450 | RTX 2080 Ti FE |
Storage | Crucial BX500 2TB | TBD |
Display(s) | 3x LG QHD 32" GSM5B96 | TBD |
Case | Dell | Heavily Modified Phanteks P400 |
Power Supply | Dell TFX Non-standard | EVGA BQ 650W |
Mouse | Monster No-Name $7 Gaming Mouse| TBD |
Yup, same as any other drive. Make sure you update firmware before formatting and thank your lucky stars that the format table wasn't stored in a block that went bad.Is this as simple as copying everything over to another drive and then formatting this one? Sorry, this is my first real SSD so I'm in foreign territory.
Is this as simple as copying everything over to another drive and then formatting this one? Sorry, this is my first real SSD so I'm in foreign territory.
And there is a possibility that the value that should be counted with SMART ID "05" (the number of reassigned sectors) is replaced with SMART ID "FC" to deceive.
RMA probably won't fix the problem.
SMART ID "05" (the number of reallocated sector count) is important. Increasing this is a big problem. Because it is the bad sectors that are relocated.We will watch that value, but even if it had something to do with bad sectors, it wouldn't be too relevant to the end user, as long as the files stored on the drive never get affected. If the drive can prevent that intelligently, and prevent it for the whole guaranteed TBW or more (most SSDs can write almost twice their TBW before any drive failures) as well as 5+ years, then it would behave exactly as expected and everyone would be happy.
Processor | Core 2 Quad Q9650 |
---|---|
Motherboard | XFX nForce 780i SLI |
Cooling | Zalman |
Memory | 4x1GB Ballistix DDR2-1066 |
Video Card(s) | 2x Quadro FX 4800 |
Storage | 2x WD RE3 500GB RAID 0 |
Display(s) | Apple Cinema HD |
Case | Chieftec Dragon |
Audio Device(s) | Sound Blaster X-Fi |
Power Supply | Corsair 500W |
Software | Windows 7 Ultimate x64 |
System Name | Main |
---|---|
Processor | R7 5950x |
Motherboard | MSI x570S Unify-X Max |
Cooling | converted Eisbär 280, two F14 + three F12S intake, two P14S + two P14 + two F14 as exhaust |
Memory | 16 GB Corsair LPX bdie @3600/16 1.35v |
Video Card(s) | GB 2080S WaterForce WB |
Storage | six M.2 pcie gen 4 |
Display(s) | Sony 50X90J |
Case | Tt Level 20 HT |
Audio Device(s) | Asus Xonar AE, modded Sennheiser HD 558, Klipsch 2.1 THX |
Power Supply | Corsair RMx 750w |
Mouse | Logitech G903 |
Keyboard | GSKILL Ripjaws |
VR HMD | NA |
Software | win 10 pro x64 |
Benchmark Scores | TimeSpy score Fire Strike Ultra SuperPosition CB20 |
we dont even know (iirc) what the cause is, might be a part that isnt even made by samsung.