![]() ![]() The ONLY 'problems' that clone software have with bad drive sectors ( not bad NTFS cluster resords ) are: Note, run ChkDsk /b inside Windows after successfully 'fixing' a bad drive sector outside Windows. Generally, especially for 1:1 cloning, cloning software only cares about unreadable drive sectors, there is a difference between an unreadable drive sector and a bad NTFS cluster record.įor example, I can manually edit the NTFS $BadClus log file and put any crapola I want into it, even claiming that 50% of the drive is bad, or some such silliness, but the number of bad NTFS cluster records is meaningless to a separate drive reading/copying/cloning program, because it will just copy the drive sectors that happen to contain the $BadClus log records to the target drive ( where it will be meaningless, but can be 'cleared' or made accurate by running ChkDsk /b ). except when NOT doing a 1:1 clone, where the cloning software instead offers to clone only used sectors, then it reeds the NTFS records and only copies NTFS files, not copying drive sectors that are not called for as storage by NTFS records. With rare exceptions, cloning software does not care about bad NTFS cluster record ( not drive sectors ) as recorded in the NTFS $BadClus file, nor does cloning software care about the data contents of any other NTFS file or the data contents of any sector. That means that regardless of what you do with the hard disk, even repairing it, the cloning software will see that bad sector being reported & act accordingly. Problem is that that bad sector is recorded in the NTFS file system tables.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |