Separate names with a comma.
Discussion in 'Memory and Storage' started by BTRY B 529th FA BN, Apr 25, 2010.
Do SSD drives need Check Disk?
No.... SSDs all have wear levelling technology which ensures all "blocks" (if you will) are checked automatically and wear evenly. In fact, even stored information will be moved from location to location throughout the life of your ssd quite unlike that of the hard drive. This is different than a hard drive where it is possible that areas are never used or checked, thus necessitating the checkdisk function.
Yes. All drives have the potential for file system corruption, due to corruption by the drive - (very rare on SSDs, but can still happen), power failure, system crash, etc.
What is more important, rather than drive technology, is the format used. Formats like FAT32 are unstable, and system crashes, power failures, etc. can severely corrupt the files and directories on the drive. You may need to use checkdisk software in order to repair the corruption.
Modern formats like NTFS are very stable, and highly resistant to system crashes and power failures. However, SSDs with a write-back cache but without a supercapacitor backup, can still allow NTFS partitions to be corrupted in a power failure situation. [SSDs without write-caching (e.g. Intel) or a write-cache with backup supercapacitor (e.g. Sandforce controller), are safe].
There is no need to regularly perform a surface scan, with SSDs - as the internal processor will periodically move data around as part of 'wear levelling'. When it is moved, it is checked for accuracy, and defective parts of the flash memory are deactivated and the data moved to a spare area.
That said, there is no need to perform surface scans of conventional HDs. The internal processor in normal HDs will regularly scan the data when idle, to ensure that all the data is readable, and weakening areas of data will be 'repaired' by moving the data to a spare area automatically.
Summary. SSDs are no different to HDs in terms of getting errors.
Most errors are software errors, caused by saving to the drive being interrupted by a serious system crash or power failure. Checkdisk will be required to check that the files are OK under some circumstances (very few on NTFS or other advanced formats).
Normal HDs can be protected from corruption by system crash and power-failure by disabling 'write caching' - but this is very slow. Some SSDs have ways of getting around this.
Errors on the drive (bad sectors) can occur on SSDs and HD (but are rare on SSDs). Both types of drive technology regularly scan the data automatically to check for bad sectors.
Nice add on!!!
Think I'll check disk my SSD right now
To be precise, individual bit errors on SSDs are actually fairly common (on the order of 10^-7 or something) but due to error recovery, actual uncorrected bit errors are extremely low (10^-15 to 10^-18 [with SandForce's claims]). Similar to how human DNA replication is fairly error prone (10^-3 bases without any 3'-5' exonuclease activity) but with proofreading, excision repair, homologous recombination and whatnot becomes much more accurate (10^-8 or more). The amount of machinery and effort the typical cell devotes to DNA repair is frankly impressive ... the same can be said of IO devices in the modern day world.
Apologies for the lack of references. There was a whitepaper by Supertalent that covered this well ... I don't seem to have it for some reason.
PS I can't believe I just used a biology example in a post about IO storage devices. Lol.
As noted by Mark R, Chkdsk can perform two different functions:
1) Check for logical errors
2) Check for physical errors
While they can be related, a logical error doesn't necessarily mean there's anything physically "wrong" with the disk. Win98, with its FAT operating system, often presented logical errors with scrambled directories and other niceties. NTFS is much more resistant to logical corruption. I don't thiink I've EVER seen a scrambled NTFS directory.