elgaton

Member
  • Content count

    3
  • Joined

  • Last visited

Community Reputation

0 Neutral

About elgaton

Profile Information

  • OS
    Windows 8 x64
  1. Hi jaclaz, sorry if I did not reply before, due to my heavy workload I hadn't time to continue the recovery until these days. I imaged the whole drive, then ran chkdsk - it worked perfectly, only two files (.NET Framework resources DLLs) were lost in the process, the rest stayed perfectly intact. Thank you very much for giving me some advice and details about the inner workings of NTFS!
  2. Thanks, I'll image the whole drive now (instead of just the first partition), then run CHKDSK; I'll tell you the results in two or three days (I'm a bit busy as exams are near).
  3. Hi all, some days ago I ran diskpart clean on the wrong hard drive. Upon realizing what I had done, I immediately turned off the computer, so as to minimize the damage. The partition map on my 250 GiB hard drive was as follows: Windows primary partition (filled the first portion of the hard disk)Linux partition with EXT4 filesystem (about 22 GiB)Linux swap partition (about 4 GiB)Reading the technical documentation about the diskpart tool, I saw that the command I gave cleans only the partition table and the MBR, so I downloaded TestDisk 6.14-WIP, booted from a Linux Live CD and launched it. I needed to perform a deep search as the NTFS partition was not found with the simple one (it was found using the backup boot sector instead). The tool finally found all the partitions, so I rewrote the partition table and restored the NTFS boot sector with the backup copy stored into the filesystem. I then rebooted and performed a read-only filesystem check on both partitions (using fsck.ext4 from a Linux Live CD for the Linux partition and chkdsk from a WinPE USB key for the Windows one). While the EXT4 filesystem was clean and intact, the CHKDSK tool reported instead that there were errors in the MFT. At this point, I imaged the NTFS partition, fearing that TestDisk had failed to recognize its start sector. The tool reported that the partition started at cylinder 0, head 1, sector 1, however I don't know if it's right given that: I had Adobe products installed and that they make use of the FlexNet protection, which writes to sector 32 of the HDD (it might have confused TestDisk);before writing the partition table, I checked the list of files in the NTFS partition, some were not listed and I attributed that to minor corruption.Could anyone please suggest me what to do at this point? I don't know whether it would be safer to run CHKDSK, letting it fix the filesystem (but potentially causing data loss), or to manually inspect the first sectors of the HDD to check if the filesystems really starts on the first sector or not. Thanks!