If it passes all tests, then the problem is usually located somewhere else in your system. SeaTools thoroughly tests your Seagate, Maxtor-brand, and Quantum-brand ATA drives. If you really, really need to ensure the correctness of your data, use at least two external hard drives with identical copies of your data and store them in separate places - preferably in a safe.More tips and information for when the SeaTools diagnostic passes but your drive is still not acting right. ) can give you complete protection from data loss. When using DVDs, you should regularly verify the data contents an in case of any read errors try to recover as much data as possible, the copy the data to a brand new DVD (or harddisk). Otherwise you would have been noticed about an unreadable sector at the time of creating the archive.ĭVDs are not very good long term archiving data carriers. On the other hand, if the archive had been created successfully back in 2000-2003, chances are that either no error occurred when reading from the HDD or the error could be repaired.
caused by a defect HDD sector that was not corrected) at the time of creating the archive, this cannot be detected by verifying the archive because the archiver will have saved the defect data, faithfully assuming it to be correct. If there had been a defect in the file data (e.g. It is not possible to verify the contents of a zipped file. here for an example with 7Zip).īut: This method can and will only check whether the archive is functionally o.k. ) usually includes a ways of veryfying that an archive isn't corrupt (see e.g. Urgent data backup and hardware replacement is recommended. Degradation of this parameter may indicate imminent drive failure. This is a serious shortcoming, for if such a drive contains marginal sectors that consistently fail only after some time has passed following a successful write operation, then the drive will never remap these problem sectors. However, some drives will not immediately remap such sectors when written instead the drive will first attempt to write to the problem sector and if the write operation is successful then the sector will be marked good (in this case, the "Reallocation Event Count" (0xC4) will not be increased). Read errors on a sector will not remap the sector immediately (since the correct value cannot be read and so the value to remap is not known, and also it might become readable later) instead, the drive firmware remembers that the sector needs to be remapped, and will remap it the next time it's written. If an unstable sector is subsequently read successfully, the sector is remapped and this value is decreased. In the block from the wiki I posted, you can read about it.Ĭount of "unstable" sectors (waiting to be remapped, because of unrecoverable read errors). It depends on how the harddisk firmware treats the bad sectors.
0 kommentar(er)
