Quote:
Originally Posted by NullNix
... CHKDSK later acquired RECOVER's abilities, and does the RECOVER thing in the single obscure situation in which you were *meant* to run RECOVER: i.e. if the root directory was sufficiently FUBAR that no directories could be located ... I see that CHKDSK has improved a bit: it's at least putting the files into subdirectories now...
|
CHKDSK really wants to run if it sees a dirty bit on a drive, and I have had that too much lately with SLOW (really really slow) SD card access over kindle USB. Nothing FUBAR -- all good if I "just say no" to the disk check, but it gets annoying after awhile and I say yes. I guess I should say no, make a backup copy, and then let checkdisk either say my disk was fine, and now and then decide to FUBAR all over my disk. I need a tool to reset that dirty bit (making the disk look like it cleanly dismounted, which it APPEARED to do, but apparently did not).
So really, Windows and linux both have their mean streaks -- either on GPT disks in linux, or on slow disks in Windows... The problem with my EXT4 disk is that my original virtualbox raw VMDK for it claims it has 1K sectors, but now after it was "fsck"ed up, it has 4K sectors that it claims are "misaligned". So if the whole partitions are not starting where they should, then obviously the superblocks are all fake too (both because of a shift in where it thinks the partition starts AND because of the wrong sector or block size. A mess. I have a backup of the first 100mb of the disk from before it ws damaged, and I wrote that back to the drive, but no help after fsck deleted EVERY file from it. Testdisk sees two partitions with the same name (over and over) at 1986 and at 1988. Meh, tired of dicking with it now. I have some android code I want to dick with yet today...