On Mon, May 18, 2020 at 8:12 AM <a.mux@xxxxxxxxx> wrote: > > Hi, > > due to a crash while resizing my / btrfs partition with gparted, my HD was left in a unmountable state. > > This is on me: resizing a partition moving it to the right via gparted is a risky operation per se. "to the right" means you were moving the starting point of the file system? Was the size changing too? What is the nature of the crash? Gparted crashed? The whole environment crashed? Power failure? Is there a dmesg or gparted log? Do you have a backup of the GPT before the resize? By comparing the GPT before it was changed, to its current state, and that of the super block found (or not) at the expected locations for both GPT states, it might be possible to infer where in the resize things went wrong. It's important to look at the GPT and *not* repair it if it's damaged. Any damage to the GPT might preserve useful information about the prior state. # gdisk/fdisk -l /dev # btrfs insp dump-s -a /dev > I am confident that all my data is still in the HD, and with proper guidance from the tools it will be possible to mount back the fs. The UI of the tools is a bit hard for me to understand. If this was moving the starting point of the file system, it's possibly difficult to recover if the crash happened while moving the partition. This copies the file system in sections - it's basically broken for the duration of the move and isn't atomic. -- Chris Murphy
