Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • 2
    First things first, write nothing... "I have determined that the disk is alive but the partition map seems to be corrupt" - are you confident? Some USB to SATA adapters will present 4k sectors for 512B disks, making them "look corrupt" when accessed natively as 512B disks - connecting via a similar adapter can make things "look fine". (Conversely, it could be the dock being non-standard, not the original adapter)
    – Attie
    Commented May 23 at 11:31
  • 1
    I’m voting to close this question because you're asking for crash-course partition recovery. You're all over the place. Commented Jun 22 at 11:24
  • The partitions in 2nd image can not co-exist, one of them is wrong. You analyze the one starting at LBA and it does not have valid BS, so probably this one is wrong. You're clueless, you shouldn't be doing this. Commented Jun 22 at 11:25
  • 1
    Thanks Joel for considering that incompetent people aren't allowed the possibility of developing skills, much appreciated.
    – frumbert
    Commented Jun 23 at 22:00
  • The risks involved to your data are significant when you are trying to learn on a non-standard custom/weird setup like this. Given that you could come back here with "I followed your instructions but now all my data is irretrievably gone", this isn't really the sort of situation where you want to learn at the level you appear to be at currently. Writing a full image of the drive is THE key to minimizing potential issues enough to mitigate this risk. Commented Jun 25 at 18:52