Search found 6 matches
- 11 Dec 2017, 23:27
- Forum: Partition Recovery
- Topic: Bad ending head/Can't open filesystem. Filesystem seems damaged.
- Replies: 5
- Views: 5319
Re: Bad ending head/Can't open filesystem. Filesystem seems damaged.
Hi there, do you have any other suggestions for what I can try in order to recover my partition using TestDisk? Any help would be greatly appreciated. Many thanks!
- 06 Dec 2017, 20:22
- Forum: Partition Recovery
- Topic: Bad ending head/Can't open filesystem. Filesystem seems damaged.
- Replies: 5
- Views: 5319
Re: Bad ending head/Can't open filesystem. Filesystem seems damaged.
Thank you so much for your help, it is greatly appreciated. Unfortunately I couldn't see my files ("Can't open filesystem. Filesystem seems damaged.")
chkdsk c: resulted in the following: "Unable to determine volume version and state. CHKDSK aborted".
diskpart shows Volume 0 as Ltr C; Fs RAW ...
chkdsk c: resulted in the following: "Unable to determine volume version and state. CHKDSK aborted".
diskpart shows Volume 0 as Ltr C; Fs RAW ...
- 01 Dec 2017, 21:03
- Forum: Partition Recovery
- Topic: Bad ending head/Can't open filesystem. Filesystem seems damaged.
- Replies: 5
- Views: 5319
Re: Bad ending head/Can't open filesystem. Filesystem seems damaged.
Many thanks! I should have noticed that it detected EFI partition type. I completed another deeper scan and got this message at the end:
Check the harddisk size: HD jumper settings, BIOS detection...
The harddisk (1000 GB / 931 GiB) seems too small! (< 1942 GB / 1808 GiB)
The following partitions ...
Check the harddisk size: HD jumper settings, BIOS detection...
The harddisk (1000 GB / 931 GiB) seems too small! (< 1942 GB / 1808 GiB)
The following partitions ...
- 29 Nov 2017, 20:20
- Forum: Partition Recovery
- Topic: Bad ending head/Can't open filesystem. Filesystem seems damaged.
- Replies: 5
- Views: 5319
Bad ending head/Can't open filesystem. Filesystem seems damaged.
Hello,
My Windows 10 no longer boots up; my C: drive comes up as RAW. I was able to run a deeper search using TestDisk, but had this warning at the start: Warning: Bad ending head (CHS and LBA don't match). At the end of the deeper search, I can't access the files (by pressing p) in the RAW ...
My Windows 10 no longer boots up; my C: drive comes up as RAW. I was able to run a deeper search using TestDisk, but had this warning at the start: Warning: Bad ending head (CHS and LBA don't match). At the end of the deeper search, I can't access the files (by pressing p) in the RAW ...
- 27 Nov 2017, 23:14
- Forum: Partition Recovery
- Topic: Launching TestDisk from Windows 10 Boot Menu (CMD)
- Replies: 3
- Views: 9899
Re: Launching TestDisk from Windows 10 Boot Menu (CMD)
Many thanks, Christophe! Your help and quick response was much appreciated - I was able to start TestDisk as per your instructions. I accidentally interrupted the deep scan, but it seemed to have found the missing partion; I will run it again tomorrow. In the meantime, I got this message early on in ...
- 24 Nov 2017, 17:29
- Forum: Partition Recovery
- Topic: Launching TestDisk from Windows 10 Boot Menu (CMD)
- Replies: 3
- Views: 9899
Launching TestDisk from Windows 10 Boot Menu (CMD)
Hello,
My computer doesn't boot up anymore: automatic repair fails and none of the Windows 10 advanced recovery options work. The C: drive is listed as RAW. I'd like to use TestDisk to repair the partition/boot sector, however I'd like to confirm first which version to use in 64-bit Windows 10 cmd ...
My computer doesn't boot up anymore: automatic repair fails and none of the Windows 10 advanced recovery options work. The C: drive is listed as RAW. I'd like to use TestDisk to repair the partition/boot sector, however I'd like to confirm first which version to use in 64-bit Windows 10 cmd ...