![]() ![]() ![]() Do a read-only scan of an SSD, it'll show the SSD's controller that it's got a problem reading a sector, and then it'll map that out or rewrite it in order to strengthen that sector, if possible. In episode 338 Gibson clarified 'it is actually detrimental because don't like to be written', but also pointing out that a read-only run could be beneficial: 'SpinRite's Level 1 is a read-only scan, and doing that on an SSD makes a lot of sense. You don't want to run Level 4' In episode 194 of the podcast Security Now! Gibson said that he could 'see absolutely no possible benefit to running SpinRite on a solid-state drive' and later 'SpinRite is all about mechanics and magnetics, neither of which exist, by design, in an SSD'. In episode #387 of the podcast Security Now! Gibson said 'Run Level 2 because Level 1 is not permitted to fix anything' 'The difference is both Level 1 and 2 are read-only, and that's the key. Spinrite can be run and can be effective on SSDs, but running in a higher-level mode than 1 or 2 is detrimental, as it wears the SSD by writing to it unnecessarily. By performing statistical analysis on the succession of results thus obtained, SpinRite is, according to its maker, often able to 'reconstruct' data from damaged sectors, and even in those cases in which complete reconstruction proves impossible, SpinRite is able to extract all intact bits from a partially damaged sector, and to copy them to a new block, thereby minimizing the amount of data lost. This, in turn, allows dynamic head repositioning, whereby, when reading a faulty sector, the reading head is deliberately moved backwards and forwards many times, by varying amounts, in the hope that each time it returns to the sector, it may come to rest in a slightly different position. Another important feature is direct hardware-level access, whereby the drive's internal controller interacts directly with the program, rather than through the operating system. SpinRite is claimed by its developer to have certain unique features, such as disabling of disk write caching, disabling of auto-relocation, compatibility with disk compression, identification of the 'data-to-flux-reversal encoder-decoder' used in a drive, and separate testing of buffered and unbuffered disk read performance. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |