You should be okay with CHKDSK. I'd leave it running if I were you. Better to let it finish than to stop it in the middle of something.
There probably was a better way to restore the FAT for that volume than using TESTDISK, but it's too late now. All Microsoft filesystems store two copies of the partition table and I'm pretty sure also the FAT. On FAT16 and FAT32, they're stored at the beginning and end of each partition, but in NTFS, the second is stored in the middle of the partition.
What CHKDSK may be doing, however, is to produce file segments, which won't actually translate to "files". That will frustrate you even more. I don't know offhand of any automated tool that will piece them back together either, but at least *making* them doesn't actually render the data inaccessible.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
no subject
Date: 2006-01-04 07:52 pm (UTC)There probably was a better way to restore the FAT for that volume than using TESTDISK, but it's too late now. All Microsoft filesystems store two copies of the partition table and I'm pretty sure also the FAT. On FAT16 and FAT32, they're stored at the beginning and end of each partition, but in NTFS, the second is stored in the middle of the partition.
What CHKDSK may be doing, however, is to produce file segments, which won't actually translate to "files". That will frustrate you even more. I don't know offhand of any automated tool that will piece them back together either, but at least *making* them doesn't actually render the data inaccessible.