Oh, also here's the crash in 7.1:
Boot sector
Status: OK
Backup boot sector
Status: Bad
Sectors are not identical.
A valid NTFS Boot sector must be present in order to access
any data; even if the partition is not bootable.
$MFTMirr location mismatch or first 4 records are fragmented. Run chkdsk ...
Search found 3 matches
- 22 Dec 2017, 10:35
- Forum: Partition Recovery
- Topic: Testdisk 7.1 didn't work; use 7.0
- Replies: 3
- Views: 2567
- 22 Dec 2017, 10:16
- Forum: Partition Recovery
- Topic: Testdisk 7.1 didn't work; use 7.0
- Replies: 3
- Views: 2567
Re: Testdisk 7.1 didn't work; use 7.0
I see now that 7.1 was simulating write:
interface_write()
1 P MS Data 256 1220934399 1220934144 [5tb drive]
simulate write!
Whereas 7.0 was just writing:
interface_write()
1 P MS Data 256 1220934399 1220934144 [5tb drive]
write!
I don't think I did anything differently, and it wasn't ...
interface_write()
1 P MS Data 256 1220934399 1220934144 [5tb drive]
simulate write!
Whereas 7.0 was just writing:
interface_write()
1 P MS Data 256 1220934399 1220934144 [5tb drive]
write!
I don't think I did anything differently, and it wasn't ...
- 20 Dec 2017, 09:36
- Forum: Partition Recovery
- Topic: Testdisk 7.1 didn't work; use 7.0
- Replies: 3
- Views: 2567
Testdisk 7.1 didn't work; use 7.0
I spent about 4 hours trying to recover my 5TB GPT disk using Testdisk 7.1.
I had "initialized" it when Disk Management prompted me to after a Windows 10 update - which was possibly a mistake.
Testdisk 7.1 found the partition easily and showed me all my files, awesome. But when I saved it, Windows ...
I had "initialized" it when Disk Management prompted me to after a Windows 10 update - which was possibly a mistake.
Testdisk 7.1 found the partition easily and showed me all my files, awesome. But when I saved it, Windows ...