I was editing my disk and when i wrote the changes and exited cfdisk, no cli command worked. Thats when i realized that im f-ed up.

This what happened: I have 3 partitions, 512M efi, a 100G root partition and some free (unallocated) space. I had 84G worth data in the root patition. I totally forgot that and shrinked the root partition to 32G to extend the free space. I was using cfdisk tool for this. I wrote the changes and rebooted my machine, by long pressing power button coz no cli commands worked after writing those chrnges, to see this.

So is it possible to recover my machine now?

:_ )

SOLUTION Thanks to @[email protected]. cfdisk just updates the partition table. So no worry about data damage . To fix this, live boot -> resize the partition back its original size -> fsck that partition. For more explanation, refer @[email protected] comment

  • 30p87@feddit.de
    link
    fedilink
    arrow-up
    5
    ·
    7 months ago

    Live boot and, if possible back up everything first. Everything as in the whole disk. So ``` dd if=/dev/nvme0n1 of=backup-disk

    • t0mri@lemmy.mlOP
      link
      fedilink
      arrow-up
      3
      ·
      7 months ago

      I dont think doing back up is possible. Coz i shrinked a 100g partition into 32g which had 84g of data. Is it possible?

      • MartianSands
        link
        fedilink
        arrow-up
        6
        ·
        7 months ago

        What they’re suggesting is to back up the whole disk, rather than any single partition. Anything you do to the partition to try and recover it has the potential to make a rescuable situation hopeless. If you have a copy of the exact state of every single bit on the drive, then you can try and fix it safe in the knowledge that you can always get back to exactly where you are now if you make it worse

        • MartianSands
          link
          fedilink
          arrow-up
          3
          ·
          7 months ago

          Also, it’s probably possible to fix the partition so that it’s as big as it used to be. It’s likely that some of your data is corrupted already, but the repartitioning won’t have erased the old data except here or there where it’s written things like new file tables in space it now considers unused