Solved search in file manager completely quit working dead instantly finds nothing (bad Samsung EVO SSD)

I tried turning on 'rapid mode' but it claims internal system errors?
Maybe cause this is an older motherboard AM3 cpu 760g chipset.

again ran long smart test and it terminates with failing LBA.
IMO that is a problem

I wont buy another of these. I have a lot of the WDC SSD, with no issues so far, should buy one of those.

gsmartcontrol shows many CRC errors. Yesterday I changed the SATA cable.

I have tried running extended smart test, and it always quits.
'interrupted (host reset)'
PC is set to not sleep

running another extended smart test

I think today. will put a WDC SSD in this PC from another PC and see how it does

I will put this Samsung in that other PC and see how it does

They are both win 11 pro PC running AM3 boards. Maybe dp a simple swap.

long test quits again
at best this board and this drive are incompatible or my multiple SATA cables are all bad.
at worst drive is dying




log says this who knows .... what it means... keeps complaining of errors at end of the log

SMART Extended Self-test Log Version: 1 (1 sectors)
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Interrupted (host reset) 80% 2613 -
# 2 Extended offline Interrupted (host reset) 80% 2613 -
# 3 Extended offline Interrupted (host reset) 90% 2612 -
# 4 Short offline Completed without error 00% 2612 -
# 5 Short offline Completed without error 00% 2607 -
# 6 Extended offline Interrupted (host reset) 90% 2607 -

SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

SCT Status Version: 3
SCT Version (vendor specific): 256 (0x0100)
Device State: Active (0)
Current Temperature: 30 Celsius
Power Cycle Min/Max Temperature: 26/40 Celsius
Lifetime Min/Max Temperature: 20/42 Celsius
Specified Max Operating Temperature: 70 Celsius
Under/Over Temperature Limit Count: 0/0
SMART Status: 0xc24f (PASSED)

SCT Temperature History Version: 2
Temperature Sampling Period: 1 minute
Temperature Logging Interval: 10 minutes
Min/Max recommended Temperature: 0/70 Celsius
Min/Max Temperature Limit: 0/70 Celsius
Temperature History Size (Index): 128 (47)

Index Estimated Time Temperature Celsius
48 2024-02-28 07:20 25 ******
... ..( 3 skipped). .. ******
52 2024-02-28 08:00 25 ******
53 2024-02-28 08:10 ? -
54 2024-02-28 08:20 34 ***************
55 2024-02-28 08:30 34 ***************
56 2024-02-28 08:40 34 ***************
57 2024-02-28 08:50 35 ****************
58 2024-02-28 09:00 35 ****************
59 2024-02-28 09:10 35 ****************
60 2024-02-28 09:20 34 ***************
... ..( 6 skipped). .. ***************
67 2024-02-28 10:30 34 ***************
68 2024-02-28 10:40 35 ****************
... ..( 3 skipped). .. ****************
72 2024-02-28 11:20 35 ****************
73 2024-02-28 11:30 34 ***************
74 2024-02-28 11:40 35 ****************
75 2024-02-28 11:50 34 ***************
... ..( 2 skipped). .. ***************
78 2024-02-28 12:20 34 ***************
79 2024-02-28 12:30 35 ****************
... ..( 15 skipped). .. ****************
95 2024-02-28 15:10 35 ****************
96 2024-02-28 15:20 36 *****************
97 2024-02-28 15:30 36 *****************
98 2024-02-28 15:40 36 *****************
99 2024-02-28 15:50 35 ****************
... ..( 21 skipped). .. ****************
121 2024-02-28 19:30 35 ****************
122 2024-02-28 19:40 26 *******
123 2024-02-28 19:50 27 ********
124 2024-02-28 20:00 28 *********
125 2024-02-28 20:10 26 *******
... ..( 2 skipped). .. *******
0 2024-02-28 20:40 26 *******
1 2024-02-28 20:50 34 ***************
2 2024-02-28 21:00 37 ******************
3 2024-02-28 21:10 38 *******************
4 2024-02-28 21:20 37 ******************
5 2024-02-28 21:30 37 ******************
6 2024-02-28 21:40 33 **************
7 2024-02-28 21:50 33 **************
8 2024-02-28 22:00 32 *************
9 2024-02-28 22:10 36 *****************
10 2024-02-28 22:20 35 ****************
11 2024-02-28 22:30 35 ****************
12 2024-02-28 22:40 36 *****************
13 2024-02-28 22:50 36 *****************
14 2024-02-28 23:00 35 ****************
... ..( 4 skipped). .. ****************
19 2024-02-28 23:50 35 ****************
20 2024-02-29 00:00 34 ***************
21 2024-02-29 00:10 34 ***************
22 2024-02-29 00:20 34 ***************
23 2024-02-29 00:30 31 ************
24 2024-02-29 00:40 34 ***************
... ..( 4 skipped). .. ***************
29 2024-02-29 01:30 34 ***************
30 2024-02-29 01:40 33 **************
31 2024-02-29 01:50 34 ***************
32 2024-02-29 02:00 34 ***************
33 2024-02-29 02:10 33 **************
34 2024-02-29 02:20 33 **************
35 2024-02-29 02:30 29 **********
36 2024-02-29 02:40 26 *******
... ..( 2 skipped). .. *******
39 2024-02-29 03:10 26 *******
40 2024-02-29 03:20 27 ********
41 2024-02-29 03:30 32 *************
42 2024-02-29 03:40 35 ****************
43 2024-02-29 03:50 29 **********
44 2024-02-29 04:00 32 *************
45 2024-02-29 04:10 31 ************
46 2024-02-29 04:20 27 ********
47 2024-02-29 04:30 37 ******************

SCT Error Recovery Control:
Read: Disabled
Write: Disabled

Device Statistics (GP Log 0x04)
Page Offset Size Value Flags Description
0x01 ===== = = === == General Statistics (rev 1) ==
0x01 0x008 4 210 --- Lifetime Power-On Resets
0x01 0x010 4 2613 --- Power-on Hours
0x01 0x018 6 5430792217 --- Logical Sectors Written
0x01 0x020 6 83583950 --- Number of Write Commands
0x01 0x028 6 4255324426 --- Logical Sectors Read
0x01 0x030 6 70487925 --- Number of Read Commands
0x01 0x038 6 2347000 --- Date and Time TimeStamp
0x04 ===== = = === == General Errors Statistics (rev 1) ==
0x04 0x008 4 0 --- Number of Reported Uncorrectable Errors
0x04 0x010 4 14 --- Resets Between Cmd Acceptance and Completion
0x05 ===== = = === == Temperature Statistics (rev 1) ==
0x05 0x008 1 30 --- Current Temperature
0x05 0x020 1 42 --- Highest Temperature
0x05 0x028 1 20 --- Lowest Temperature
0x05 0x058 1 70 --- Specified Maximum Operating Temperature
0x06 ===== = = === == Transport Statistics (rev 1) ==
0x06 0x008 4 8294 --- Number of Hardware Resets
0x06 0x010 4 0 --- Number of ASR Events
0x06 0x018 4 7251 --- Number of Interface CRC Errors
0x07 ===== = = === == Solid State Device Statistics (rev 1) ==
0x07 0x008 1 0 N-- Percentage Used Endurance Indicator
|||_ C monitored condition met
||__ D supports DSN
|___ N normalized value

SATA Phy Event Counters (GP Log 0x11)
ID Size Value Description
0x0001 2 651 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 1 R_ERR response for non-data FIS
0x0006 2 1 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 665 Transition from drive PhyRdy to drive PhyNRdy
0x000a 2 664 Device-to-host register FISes sent due to a COMRESET
0x000b 2 0 CRC errors within host-to-device FIS
0x000d 2 1 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 1 R_ERR response for host-to-device non-data FIS, non-CRC

Samsung EVO 860‘s are great SSD’s
I haven’t quite been able to keep up with what you’re trying to do in all these threads, it’s all pretty hectic. But do you think there is a chance you possibly might be the cause of the stressed drive?

antspants said:

Samsung EVO 860‘s are great SSD’s
I haven’t quite been able to keep up with what you’re trying to do in all these threads, it’s all pretty hectic. But do you think there is a chance you possibly might be the cause of the stressed drive?

Click to expand...

smart tests dont lie
looking on other forums people have said similar things about these samsung drives

sdowney717 said:

smart tests dont lie
looking on other forums people have said similar things about these samsung drives

Click to expand...

That’s not what I said.

antspants said:

That’s not what I said.

Click to expand...

How could I be the cause of an SSD failing smart tests?

I am going to swap some drives around and see if the drive continues to fail the smart tests etc.. in a different PC

By punishing it? You’ve been (from what I can comprehend from your threads) writing, rewriting, chopping and changing the drive content. It’s just a question.

antspants said:

By punishing it? You’ve been (from what I can comprehend from your threads) writing, rewriting, chopping and changing the drive content. It’s just a question.

Click to expand...

Ridiculous. A drive is a machine made to simply run properly in many different conditions of use.
It has failed twice now and had to be wiped and started over. This will be the 3rd time and it is going in a different PC to see if it fails over there. It is going in a PC which sees a lot less usage. Fails are minor ones but they show issues, which the smart test is exposing.

file things are getting corrupted on the drive or it would not be acting this way

This Samsung drive recently corrupted itself doing a change over from IDE to AHCI, which the spinner WDC in this PC which is a clone handled fine
I wiped it and restored the OS

Now second issue was searching fails.

3rd issue I have not mentioned. WMC is having troubles going full screen and windowed with long delays with this Samsung drive. An exact clone on the WDC in this machine, WMC works perfectly and instantly switching. Only thing different is the drive. same PC

sdowney717 said:

Ridiculous.

Click to expand...

OK cheers. Sorry, I’ll let you alone to get back to having a chat with yourself. I just thought you might be lonely in here. I have a good heart, I was just interacting.

same result with putting the Samsung EVO in a different PC. It booted up fine, except for the graphics card being different altering the screen display, you would never know it came from a different PC

Same LBA failure long test.

I put the WDC SSD into the first machine from the less used second machine and am cloning it back from its WDC spinner drive.
I also made a backup drive on an Hitachi spinner for the second machine so as not to lose anything.

IMO, the Samsung EVO is starting to fail. At least it is going into a PC which wont see much use, but I should buy a new WDC SSD for it.

This issue has further resolved itself. The MSI 7596 board quit working. Got stuck in a bios boot loop. I turned it off and on, and its dead...
Just as well as it was only a SATA II motherboard and was a free PC. I will keep the Samsung EVO 860 and may try it in an old dell laptop.

I built up an ASUS M488TD-M which is SATA III (6gb/s). I used a WDC BLUE SSD 500 gb. Installed WMC and it is perfect.
It has a Phenom II x4 955 CPU and 16gb DDR3. I added a 1TB spinner Hitachi SATA drive and put all the other drives from the failed PC in the EMachines case, so have 4 hard drives in it, but not the Samsung EVO. I also shared all my 14 TB of recorded TV to this ASUS so WMC can watch all the stored recordings of OTA TV. And I put 2 tuner cards and one has an FM tuner! into the ASUS.

Fun times today for sure. Took hours to figure out all this stuff. Anyway, it is working perfectly for now. I have been playing with it for hours and I can't find anything wrong. Boots up win 11 23H2 super fast and very responsive. Of course it is not like a new high performance machine. But for what we will use it for, it is perfect. I prefer ASUS over MSI, so just as well the MSI board failed. I had inherited the MSI from my dead FIL.

I submitted a warrantee claim to Samsung on the drive. I bought it new from Amazon in December 2020 and it is covered for 5 years.
The immediate reply from them is will take a few day for a response.

I put that drive in an old Dell D630 laptop and had the same weird symptom using WMC, takes forever to play recorded TV or move full screen and back.
I put the original Fujitsu drive in that Dell laptop. Installed WMC and set up recorded media location and it is instant play back and going full screen and back to windowed. Something is going on with it.

And the MSI dead board, I reset the CMOS by moving a jumper, then the bios worked again. So will use it as a test bed and for cloning drives etc...

Today I got my RMA drive from Samsung warrantee, they gave me a new Evo 870!
Agreed with me the EVO 860 I had was bad.
Very pleased with Samsung now.