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
For sure.
For
fsck /dev/nvme0n1p2:The filesystem driver knows the size of the filesystem is larger than the physical size of the partition it is on. Because of that it refuses to do anything with it until that discrepancy is sorted.
Boot to a USB/ISO, run cfdisk, extend the partition size back to original or larger, then run fsck on the partition again.
😭😭😭🤧 THANKS!!
im saved. My machines saved. Thanks a lot!!
Whrt happened anyway? Why
cfdiskdidnt wipe the data? I thought it would everything after 32g, but all my data is un touched. What happened?The partition table is just a set of pointers to various places on the physical disk where partitions should be, inside those partitions are filesystems with all your data. It's like the table of contents in a book. You can mess around with the table of contents and make the page numbers for chapters different, but all the words in the book are still there.
Now you're lucky that filesystem drivers are fairly smart these days. They sanity check things all the time. When you write the partition table to disk all the active filesystem drivers get notified of the changes, so they can keep track of things. When the driver noticed that the size of your filesystem exceeded the size of your partition, it basically was like "Hold it right there, I'm not touching any of this!". At that point the filesystem would have been forcibly unmounted and disconnected, which is why none of your commands worked after running cfdisk, they were on that filesystem.
Note that your approach was almost the right way to do it. To make your filesystem bigger you can expand the partition using cfdisk ( as long as there is physical room on the disk!) and then run a program called resize2fs , and it will expand the filesystem to suit.
Similarly, you can shrink the filesystem in the same kind of way, except you run resize2fs first and command it to shrink the filesystem to a particular size. It will do that (assuming there's enough free space in your filesystem to do so) then you shrink the corresponding partition with cfdisk to match.
Of course, as you've learned, resizing partitions is moderately risky so backups are a good idea. Having said that I routinely expand filesystems in VMs like this without backups - I make the VMs disk larger in its settings, then run cfdisk and expand the partition, then run resize2fs.
I sincerely appreciate your consideration to help and explain
Its funny that i tried resize partitions without knowing how to do that. I thought i should format new partitions after editing partition table coz thats what i did when installing linux, but im wrong again ig.
we would all like to thank @[email protected] for his amazing, non-meme contribution 👏
Anti Commercial AI thingy
CC BY-NC-SA 4.0cfdisk only changes the partition table, this table like a small paper that you store at the front (or back) of drive where you put information, it's just a list of coordinates like from this point to this point is your home, from this to this is your yard, from this to this is your neighbor. Just because you changed the values on your paper doesn't actually make your neighbor closer or further.
System read this list to figure out where are the "borders" between different sections that you defined to load and use them logically for multiple file systems.
It's a marvellous feeling, right?
We thank Dave for his decisive contribution. For future occasions try to backup everything before doing operations of this type. This small script works very well for me:
https://github.com/cleverwise/cya
That allows you to backup even hot systems. Just mount an external disc in /home/cya and run the script with sudo...
The existing file system appears to have been damaged possibly because cfdisk has not adjusted (shrinked) the existing file system before changing the partition settings. In my case, this kind of thing I only dare to do with gparted if partitions contain file systems with data.
I would try the second option I mentioned above, as my last chance: to start a live-rescue and look that allows us to gparted, but I am not very optimistic about it