New
#31
How to recover ntfs partition
-
-
New #32
1. The Windows Disk Management screenshot attachment is invalid. Please upload it again. (Tip: Preview your post and check everything is OK before hitting the Submit button)
2. Yes, the partition info and filesystem info is an exact replica of my 1TB HDD. And that leads me to believe that PW is fetching the info from the File System and not by actually reading the Disk Structure( OK, we are also learning.:)) Your disk structure in the data area may still be different.
3. Yes, you can write the MBR using Bootice. ( I wanted you to try PW before getting on to it.) Download your Windows bit version - 32 bit or 64bit - from Booooooooting ? View topic - [ BOOTICE: A poweful boot-related utility ] - v1.3.2.1 Extract the rar file to get the exe file to run.
Check you have selected the right drive, click on Process MBR. Check the current MBR type shown( just for info). As a precautionary measure Backup MBR (the current one). Then select Windows NT 5.x /6.x MBR and then Install/Config. That should install the MBR. (You can also view sector 0 before and after by clicking on Sector Edit and viewing sector 0 )
{You may find some help to familiarise yourself with Bootice here Lost partitions!}
-
New #33
Ok, surface test was aborted by my great laptop (sometimes shuts down, must be some power issues).
I tried the Power Data Recovery Tool and recovered the data that was important to me.
Will try out ntfsfix and ntfsfsck now. If not successful I will try bootice.
And not to forget, the snap of the disk management tool. Not sure if it helps.
-
New #34
ntfsfix seems to have fixed the sector count but has problems with the MFT, but I cant mount it on Linux yet. ntfsck only approves the wrong MFT. Will reboot with PW and see what it says now and if Windows can mount it.
Code:$ sudo ntfsfix /dev/sdb1 Mounting volume... Failed to read last sector (4294965176): Invalid argument HINTS: Either the volume is a RAID/LDM but it wasn't setup yet, or it was not setup correctly (e.g. by not using mdadm --build ...), or a wrong device is tried to be mounted, or the partition table is corrupt (partition is smaller than NTFS), or the NTFS boot sector is corrupt (NTFS size is not valid). FAILED Attempting to correct errors... Failed to read last sector (4294965176): Invalid argument HINTS: Either the volume is a RAID/LDM but it wasn't setup yet, or it was not setup correctly (e.g. by not using mdadm --build ...), or a wrong device is tried to be mounted, or the partition table is corrupt (partition is smaller than NTFS), or the NTFS boot sector is corrupt (NTFS size is not valid). FAILED Failed to startup volume: Invalid argument Failed to read last sector (4294965176): Invalid argument HINTS: Either the volume is a RAID/LDM but it wasn't setup yet, or it was not setup correctly (e.g. by not using mdadm --build ...), or a wrong device is tried to be mounted, or the partition table is corrupt (partition is smaller than NTFS), or the NTFS boot sector is corrupt (NTFS size is not valid). Trying the alternate boot sector The alternate bootsector is usable Set sector count to 1953525103 instead of 4294965176 Rewriting the bootsector The boot sector has been rewritten Processing $MFT and $MFTMirr... Reading $MFT... OK Reading $MFTMirr... ntfs_mst_post_read_fixup_warn: magic: 0x2602496e size: 1024 usa_ofs: 14464 usa_count: 49164: Invalid argument ntfs_mst_post_read_fixup_warn: magic: 0x806e4003 size: 1024 usa_ofs: 4040 usa_count: 59173: Invalid argument ntfs_mst_post_read_fixup_warn: magic: 0x1fecf8f7 size: 1024 usa_ofs: 57175 usa_count: 21310: Invalid argument ntfs_mst_post_read_fixup_warn: magic: 0x8e1eaecd size: 1024 usa_ofs: 47645 usa_count: 19843: Invalid argument OK Comparing $MFTMirr to $MFT... FAILED $MFTMirr error: Invalid mft record for $MFT.
Code:$ sudo ntfsck /dev/sdb1 ntfs_mst_post_read_fixup_warn: magic: 0x2602496e size: 1024 usa_ofs: 14464 usa_count: 49164: Invalid argument ntfs_mst_post_read_fixup_warn: magic: 0x806e4003 size: 1024 usa_ofs: 4040 usa_count: 59173: Invalid argument ntfs_mst_post_read_fixup_warn: magic: 0x1fecf8f7 size: 1024 usa_ofs: 57175 usa_count: 21310: Invalid argument ntfs_mst_post_read_fixup_warn: magic: 0x8e1eaecd size: 1024 usa_ofs: 47645 usa_count: 19843: Invalid argument $MFTMirr error: Invalid mft record for '$MFT'.
Last edited by Gerrit; 08 Jan 2014 at 02:41.
-
New #35
PW now shows the correct usage of the drive. Disk management still shows it as RAW drive. Windows cant mount it and it also does not offer to format the drive anymore. It just says its inaccessible.
-
New #36
Bootice doesnt help either. In the beginning it says "Unknown MBR". I tried both, Windows NT 5.x and 6.x MBR, but still inaccessible and RAW drive.
Will start another surface test with another computer, but this will take at least 11 hours.
-
-
New #38
In Elevated Command Prompt :
Problems found? Repaired? Run command again to prove.Code:chkdsk/f G:
Reboot afterwards. Drive is still RAW?
-
New #39
Yes, I know that it changed the sector count. The partition size is corrected and used/unused space is fine. But still Windows cant mount the drive, even worse (or maybe not), before windows wanted to format the drive. Now it says it is just inaccessible (it takes a pretty long time until Windows gives a message).
Will run ntfsfix again today evening when partition wizard has finished the surface test (this time on another computer to avoid the power issues of the laptop).
-
Quote
Related Discussions