opkrandom.blogg.se

Crystaldiskinfo caution fix
Crystaldiskinfo caution fix






crystaldiskinfo caution fix

So generally we can't say that the drive is perfect. Many other tools follow this direction - making questionable if they may be able to report problems at all.Īs you wrote, your SSD already experienced/reported problems.

crystaldiskinfo caution fix

Because of its nature, they may not sensitive enough to report possible problems and happily show (almost) failing drives as perfect. This is especially common for manufacturer-specific tools: they have only one purpose: to minimise warranty replacement of hard disk drives / SSDs. While I do not know the particular situation (as the image does not appear), generally it is common that different software/tools report different health for a hard disk or SSD. Sometimes, read operations resulting in such errors can take a long time due to many retries.I'd suggest to please check: Support -> Frequently Asked Questions -> Why other software displays different health? Which is correct? If you do absolutely nothing about this, only consequences is that you'll get errors when you try to read those sectors. In either case, you can continue using the drive. Maybe the drive was writing to those sectors when power was cut, causing them to be corrupt, even though the drive is physically totally okay. If that value doesn't go up, I don't know what's going on. If it goes up, that means the drive developed new bad sectors, which increases probability that the drive will fail. So you should probably first use something like nfi.exe to find what file is located there, so you know what got corrupted.Īfterwards, reallocated sectors count raw value may or may not go up. Though note that after you do this, whatever data is located there will be corrupted, but you won't get an error anymore when reading it. You might also be able to dig through OS error logs, though this will be more work.įor overwriting them, the hdparm -write-sector function in Linux works. You need to find where those pending sectors are located, and then you need to overwrite them.įor finding them, you can run a SMART test and it will tell you what sector it stops at.








Crystaldiskinfo caution fix