Hello, I'm new and having this issue. My partition got damaged and I've lost all my data. I bought a New Harddrive and while transferring large files my partition got corrupted. Sorry if I missed anything. I ran Testdisk and this is what I got back.
TestDisk 7.1, Data Recovery Utility, July 2019
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org
Disk /dev/sdb - 6001 GB / 5589 GiB - CHS 729601 255 63
Partition Start End Size in sectors
1 P EFI System 20346196 20353683 7488 [EFI System Partitio
2 P MS Data 22741784 22762522 20739 [NO NAME]
3 P MS Data 30629640 30650378 20739 [NO NAME]
4 P MS Data 35874064 35894802 20739 [NO NAME]
5 P MS Data 39046328 39067066 20739 [NO NAME]
6 P MS Data 43779471 43782350 2880 [NO NAME]
7 P MS Data 44686288 44707026 20739 [NO NAME]
8 P MS Data 86400064 86413919 13856
9 P Mac HFS 91821898 1550489419 1458667522
10 P MS Data 1643897463 1643918201 20739 [NO NAME]
11 P MS Data 2081131393 2081133054 1662 [DISK IMAGE]
12 P MS Data 2081138945 2081140606 1662 [DISK IMAGE]
13 P MS Data 2081146113 2081147774 1662 [DISK IMAGE]
14 P MS Data 2081153281 2081154942 1662 [DISK IMAGE]
15 P MS Data 2081168513 2081170174 1662 [DISK IMAGE]
16 P MS Data 2081170305 2081171966 1662 [DISK IMAGE]
17 P MS Data 2081185409 2081187070 1662 [DISK IMAGE]
18 P MS Data 2081187073 2081188734 1662 [DISK IMAGE]
19 P MS Data 2202784193 2202785854 1662 [DISK IMAGE]
20 P MS Data 2202785857 2202787518 1662 [DISK IMAGE]
21 P MS Data 2202801985 2202803646 1662 [DISK IMAGE]
22 P MS Data 2202813889 2202815550 1662 [DISK IMAGE]
23 P MS Data 2202819777 2202821438 1662 [DISK IMAGE]
24 P MS Data 2202845057 2202846718 1662 [DISK IMAGE]
25 P MS Data 2202846721 2202848382 1662 [DISK IMAGE]
26 P MS Data 2202872001 2202873662 1662 [DISK IMAGE]
27 P MS Data 2230320768 2230334623 13856
28 P MS Data 2853532688 2853553426 20739 [NO NAME]
29 P EFI System 2903024716 2903032715 8000 [EFI System Partitio
30 P MS Data 2903311760 2903332498 20739 [NO NAME]
31 P MS Data 3113497344 3117689583 4192240 [NO NAME]
32 P EFI System 3132867596 3132875595 8000 [EFI System Partitio
33 P MS Data 3143780880 3143801618 20739 [NO NAME]
34 P MS Data 3185756816 3185777554 20739 [NO NAME]
35 P Linux filesys. data 8287965453 8290474600 2509148 [^O M-+wM-4^Y-~[pM-$
36 P Linux filesys. data 9680911304 9684083208 3171905 [M-1M-3~R~SM-0^O~Z~X
37 P Linux filesys. data 9842198202 9843240854 1042653 [5<M-=nȦM-R|ބʸ~HM-;M
]
[ Quit ] [ Return ] >[Deeper Search] [ Write ]
Partition Damaged
Forum rules
When asking for technical support:
- Search for posts on the same topic before posting a new question.
- Give clear, specific information in the title of your post.
- Include as many details as you can, MOST POSTS WILL GET ONLY ONE OR TWO ANSWERS.
- Post a follow up with a "Thank you" or "This worked!"
- When you learn something, use that knowledge to HELP ANOTHER USER LATER.
Before posting, please read https://www.cgsecurity.org/testdisk.pdf
When asking for technical support:
- Search for posts on the same topic before posting a new question.
- Give clear, specific information in the title of your post.
- Include as many details as you can, MOST POSTS WILL GET ONLY ONE OR TWO ANSWERS.
- Post a follow up with a "Thank you" or "This worked!"
- When you learn something, use that knowledge to HELP ANOTHER USER LATER.
Before posting, please read https://www.cgsecurity.org/testdisk.pdf
-
recuperation
- Posts: 3026
- Joined: 04 Jan 2019, 09:48
- Location: Hannover, Deutschland (Germany, Allemagne)
Re: Partition Damaged
What is your question, please?
Your case description is below average.
Please fill out the following form:
1.Which operating systems can be booted from your computer where the incident happened?
List them all!
2. Which version of Testdisk do you use?
3.Do you prevent/reduce write access to the failed drive/file system?
[Yes/no]
4. If yes, how is that done?
[ ] I removed the failed drive and connected it to another computer (not linux) as an external drive => risky
[ ] I am using a live linux from a USB stick on the machine with the broken drive => good
[ ] I am booting a linux system on a different system and connect the drive externally once the linux finished booting => good
5. Is the broken drive a drive where an operating system resides on or is it a data drive?
6. What technology is your disk (HDD, SDD, USB stick, Compact Flash card, SD card,...)?
7. What is the size of your disk?
8. Who is the maker of your failed drive?
9. What is the model?
10. Is the drive something you bought "naked" one or does it come with a housing and a connector for a computer (p.e. like "WD My Passort")?
11. If possible, provide a logfile from smartmontools!
Instructions:
viewtopic.php?f=5&t=10910
12. What has been the partitioning scheme used on the failed drive (MBR (old partition table style), GPT, Superfloppy)
13. How many partitions have been on the broken drive, what was their size, what was their file system?
14. Is your drive visible in your operating system (Windows: Disk management, Linux use lsblk command, get information using hdparm command)
15. Is the partition scheme containing your partitions still visible?
14. Describe the supposed event when your system went from "OK" to "broken"!
15. Is your disk showing signs of failures such as
-clicking noises
-permanent reboot (spindel speed up followed by a stop)
-no spindel speed up
?
16. Do you use encryption, if yes, which one?
17. If you use encryption, what is the scope?
[ ] full drive
[ ] partition
[ ] file container
[ ] single files
Your case description is below average.
Please fill out the following form:
1.Which operating systems can be booted from your computer where the incident happened?
List them all!
2. Which version of Testdisk do you use?
3.Do you prevent/reduce write access to the failed drive/file system?
[Yes/no]
4. If yes, how is that done?
[ ] I removed the failed drive and connected it to another computer (not linux) as an external drive => risky
[ ] I am using a live linux from a USB stick on the machine with the broken drive => good
[ ] I am booting a linux system on a different system and connect the drive externally once the linux finished booting => good
5. Is the broken drive a drive where an operating system resides on or is it a data drive?
6. What technology is your disk (HDD, SDD, USB stick, Compact Flash card, SD card,...)?
7. What is the size of your disk?
8. Who is the maker of your failed drive?
9. What is the model?
10. Is the drive something you bought "naked" one or does it come with a housing and a connector for a computer (p.e. like "WD My Passort")?
11. If possible, provide a logfile from smartmontools!
Instructions:
viewtopic.php?f=5&t=10910
12. What has been the partitioning scheme used on the failed drive (MBR (old partition table style), GPT, Superfloppy)
13. How many partitions have been on the broken drive, what was their size, what was their file system?
14. Is your drive visible in your operating system (Windows: Disk management, Linux use lsblk command, get information using hdparm command)
15. Is the partition scheme containing your partitions still visible?
14. Describe the supposed event when your system went from "OK" to "broken"!
15. Is your disk showing signs of failures such as
-clicking noises
-permanent reboot (spindel speed up followed by a stop)
-no spindel speed up
?
16. Do you use encryption, if yes, which one?
17. If you use encryption, what is the scope?
[ ] full drive
[ ] partition
[ ] file container
[ ] single files