Question Why windows does not warn about S.M.A.R.T. error?

[overclockoverheat]

I have a SSD that has gone bad. Many files have non readable areas. They don't return corrupt data; they cause a long delay in read retries and then the read fail. Samsung magician returns some bad numbers in S.M.A.R.T. But why does windows not warn me the drive has gone bad? Scanning the drive with Magician shows many bad sectors, but doing a disk scan in windows shows no error.

 

[fzabkar]

I suspect that no SMART attribute has fallen below its threshold, so the drive does not report a SMART fail status.

 

[BFG-9000]

Windows will only pop up a notice if the drive actually reports it is failing. Drive manufacturers are understandably hesitant to program the firmware to report this unless the problem is really bad, because to do so would just mean more warranty costs for them.

I saw a Ford truck with two dead cylinders and no check-engine light. The ECU simply shut off the injectors for those two cylinders and never bothered to warn the driver, who drove around like that for a whole year. If they can delay the check-engine light for long enough, it can fall out of warranty and will no longer be their problem. As you'd imagine this was quite rough running, plus economy didn't improve with the dramatic decrease in displacement as all of the extra oxygen pumped into the exhaust simply caused the mixture to adjust to full rich

 

[Chicano]

I have a SSD that has gone bad. Many files have non readable areas. They don't return corrupt data; they cause a long delay in read retries and then the read fail. Samsung magician returns some bad numbers in S.M.A.R.T. But why does windows not warn me the drive has gone bad? Scanning the drive with Magician shows many bad sectors, but doing a disk scan in windows shows no error.

The BIOS should have S.M.A.R.T. enabled to detect bad sectors in HDDs and is enables by default as far as I know... but since SSDs are not supposed to have sectors, it may be the reason you hadn't noticed the problem. Windows has the CHKDSK tool that detects bad sectors from the moment the OS starts loading, and offers doing the the scan... but if SSDs don't have sectors, it may be the reason the problem went unnoticed. But you can run chkdsk manually to make file system corrections and repair "bad sectors", which information says are present in SSDs in a lower number. Your alternatives are to run chkdsk to detect bad sectors and repair them and to find and repair file system errors. If will do what it can do, and not find what it can't.

CKDSK alternatives
Unlike HDDs, SSDs do not have a built-in mechanism to detect and repair bad sectors. Therefore, you need to use third-party tools or utilities to scan and fix your drive. Some examples are CHKDSK, S.M.A.R.T., CrystalDiskInfo, and SSD Toolbox.


If you don't want to use third party software to check the SSD, this may help
A second search says:
"How to use chkdsk for SSD?
Select Troubleshoot > Advanced options > Command Prompt. Type CHKDSK /f in the elevated command prompt and hit Enter. Wait for the CHKDSK utility to complete the scan, then type Exit and hit Enter."

 

[fzabkar]

Be wary of running CHKDSK against a failing drive. CHKDSK's priority is to ensure that the file system is consistent, and it will often sacrifice your files to that end.