May I know what is the software name and version you are using? Is the Intel® SSD connected to Intel® SATA controller?
De SSD is connected to the Gigabyte Motherboard Gigabyte SATA port, and sometimes on a ARECA ARC-1880 RAIDController as a passthrough disk. Both SATA ports are working without problems the last two years.
The software version of the Solid-State Drive toolbox is 3.2.3
On this moment it's connected on the Gigabyte SATA Port.
You can try using a different SATA cable, and make sure you are connecting the drive to the main adapter in your motherboard.
If the issue persists, it would be good to check the SMART details using Intel® SSD toolbox.
Also, you may consider performing a Secure Erase on the SSD.
What a strange recommedation. Cable is bad only for 0.0001% of data? Erase disk with OS? Thanx, but no.
Maybe other ideas?
This type of behavior can be caused by different reasons: corrupted file system, connection problems (port, cable), faulty drive, memory problems, etc.
Our previous recommendations can help you discard some of the common causes.
Please keep in mind that you may Contact Support to engage a support engineer in your region, and we will be able to assist.
I am sure that problem is in the hardware. Data fault appears in exact same place. That cant have place because of cable connection or memory problems.
Memory is OK. Cable is OK also.
I suppose that bad blocks on the SSD should me marked or relocated by the drive itself, not by the chkdsk utility. But there is no such activity on my X25 drive.
So, maybe there is any other tools to diagnose drive and force internal software to work properly?
The Full Diagnostic scan from Intel® Solid State Drive Toolbox performs two tests:
- Read Scan - checks every logical block address (LBA) for READ errors.
- Data Integrity Scan - uses free space to write random data and read it back to ensure data
If the full scan does not complete, you can use Windows* Check disk utility to scan and repare file system errors, as you mentioned, the SSD has mechanisms to detect bad blocks and reallocate the data. Due to the nature of the test (read and write from drive) it can be affected by bad cables and memory issues in the computer as well.
The best way to diagnose any hardware problems in the SSD itself is to review the SMART details, that can be done with the toolbox as well.
If you would like us to help with that, please export the drive details, you can access this function on the home screen, and click Export. Then you can attach the resulting .CSV file to this thread using the Advanced Editor options.
For more information, please check the Intel® Solid-State Drive Toolbox User Guide.
It is important to mention that the Intel® SSD X25 Series is currently End of Life, we would expect these drives to have reached their expected lifespan by now.
I have 16 relocated blocks on drive.
Fullscan stops at 30% with error, mentioned earlier. Reading scan is all ok. Drive have 89% life remainig.
Chkdsk resets system after some time of checking and there no any logs stored in windows application event.
Sometime my systemhang and become unresponsive just after the start-up.
I have attached my log.
X25drive.csv.zip 4.8 K
The only 2 things found in the log are the ones you mentioned, 16 Re-allocated Sectors and Media Wearout indicator at 90. If the amount of re-allocated sectors does not increase periodically, you may be able to use the drive for some more time; however, it is always a best practice to keep a backup of the data, and if possible, use a drive in optimum condition as boot drive.
Please take into account that this drive was part of the first generation of Intel® SSD's. It is past its expected lifespan, and this specific unit is actually out of warranty since 2013.
The SSD is starting to show its wear, however, it may still work for some time. You would need to perform further testing to discard or confirm the culprit for the system reboots and lockups. Other common causes for this behavior may be OS problems, faulty SATA port and cable, failing applications, viruses, corrupted drivers, bad memory modules/slots, etc.