While I was switching distros, I accidentally broke a partition. I’m almost certain that all the data is there, but it doesn’t have a filesystem (I used ext4). Is there anything I can do to fix it, similar to changing the file extension without changing the contents. PS: It’s a data partition. I was trying to resize it, accidentally also moved it to the left, found out that it was taking forever to move it, so I cancelled it. Finished the move to the left operation (I think), but it threw up an error about the filesystem. I don’t remember what it was, though.

Thanks to everyone who suggested Testdisk. It worked almost perfectly.

  • lurch (he/him)@sh.itjust.works
    40·
    1 year ago

    before you change anything it would be good to use dd and save the whole drive to a bigger drive or maybe compress it with gzip while using dd to save it to a slightly smaller one. That takes a very long time, but gives you the ability to start over with your recovery. Only do that if it’s worth to wait several hours.

    photorec can also recover some files by looking at the raw data still there, if all else fails.

    • sun_is_ra@sh.itjust.worksEnglish
      7·
      1 year ago

      use dd and save the whole drive to a bigger drive or maybe compress it with gzip while using dd to save it to a slightly smaller one

      command would be something like this:

      dd if=/dev/…/myparition|gzip status=progress > /mnt/external_hd/mypartition.gzip

      • aodhsishaj@lemmy.world
        5·
        1 year ago

        Wouldn’t you want to use

        dd if=/dev/sda3 of=/dev/sdc1 status=progress && sync

        Where /dev/sda3 is the damaged partition and /dev/sdc1 is the freshly formatted external drive

        You’ll find your attached devices with lsblk

        You’re going to want to make sure /dev/sda3(broken partition) is unmounted so as not to write any more data to it.

        • CMahaff@lemmy.worldEnglish
          4·
          1 year ago

          To add on to this answer (which is correct):

          Your “of” can also just be a regular file if that’s easier to work with vs needing to create a new partition for the copy.

          I’ll also say you might want to use the block size parameter “bs=” on “dd” to speed things up, especially if you are using fast storage. Using “dd” with “bs=1G” will speed things up tremendously if you have at least >1GB of RAM.

        • sun_is_ra@sh.itjust.worksEnglish
          2·
          1 year ago

          this clones one parition to another which is fine if you have free partition with enough space lying around. My code was for taking compressed backup of the partition to be restored later if needed. Its less convenient but doesnt require as much space nor does it require an entire partition

          • aodhsishaj@lemmy.world
            1·
            1 year ago

            Don’t you have to read the partition to compress it, which is fine on a healthy partition but can further damage a broken one?

            • sun_is_ra@sh.itjust.worksEnglish
              11·
              1 year ago

              depends on what you mean by “broken”. If broken means has bad sector or other hardware issue, then yes OP should transfer data to healthy partition and work from there. though it certainly won’t hurt if he attempted to recover data from broken partition (worst the HD dies and OP restore the backup on healthy HD) However he said “i broke my partition” which make me think its software issue, not hardware. in which case, would be faster to recover data directly after taking backup