On 2019/11/6 下午11:52, Sergiu Cozma wrote:
> Hi, thanks for taking the time to help me out with this.
> 
> The history is kinda bad, I tried to resize the partition but gparted
> failed saying that the the fs has errors and after throwing some
> commands found on the internet at it now I'm here :(

Not sure how gparted handle resize, but I guess it should use
btrfs-progs to do the resize?

> 
> Any chance to recover or rebuild the chunk tree?

I don't think so. Since it's wiped, there is no guarantee that only
chunk tree is wiped.

THanks,
Qu


> 
> 
> On Wed, Nov 6, 2019, 13:34 Qu Wenruo <quwenruo.btrfs@gmx.com> wrote:
>>
>>
>>
>> On 2019/11/5 下午11:04, Sergiu Cozma wrote:
>>> hi, i need some help to recover a btrfs partition
>>> i use btrfs-progs v5.3.1
>>>
>>> btrfs rescue super-recover https://pastebin.com/mGEp6vjV
>>> btrfs inspect-internal dump-super -a https://pastebin.com/S4WrPQm1
>>> btrfs inspect-internal dump-tree https://pastebin.com/yX1zUDxa
>>>
>>> can't mount the partition with
>>> BTRFS error (device sdb4): bad tree block start, want 856119312384 have 0
>>
>> Something wiped your fs on-disk data.
>> And the wiped one belongs to one of the most essential tree, chunk tree.
>>
>> What's the history of the fs?
>> It doesn't look like a bug in btrfs, but some external thing wiped it.
>>
>> Thanks,
>> Qu
>>
>>> [ 2295.237145] BTRFS error (device sdb4): failed to read chunk root
>>> [ 2295.301067] BTRFS error (device sdb4): open_ctree failed
>>>
>>