Corrupted after multiple forceful shutdowns

Corrupted after multiple forceful shutdowns

[notrandom98234]

Hey, I managed to break my btrfs again..
I had to forcefully shutdown multiple times (like 12+) due to a issue unrelated to disk and now I can no longer mount btrfs....
The secondary disk gives "unsupported/invalid hardware sector size 4096" and "ERROR: no btrfs on /dev/dm-2" when mounting but I hope that is only an issue on the kubuntu live environment..

-- diagnostic --
fi show:
Label: 'root'  uuid: 7e486848-9a64-4f36-abf1-cecb1b7c171e
        Total devices 1 FS bytes used 115.64GiB
        devid    1 size 223.26GiB used 153.02GiB path /dev/mapper/crypt

mount:
[  480.712140] BTRFS info (device dm-1): flagging fs with big metadata feature
[  480.712144] BTRFS info (device dm-1): using free space tree
[  480.712145] BTRFS info (device dm-1): has skinny extents
[  480.713920] BTRFS error (device dm-1): bad tree block start, want 103612416 have 17126188627709133626
[  480.714236] BTRFS error (device dm-1): bad tree block start, want 103612416 have 8743983881084155753
[  480.714242] BTRFS warning (device dm-1): couldn't read tree root
[  480.714533] BTRFS error (device dm-1): open_ctree failed

zero-log:
checksum verify failed on 103612416 wanted 0x42f43bde0ae40f0d found 0x0fd72531e6454ed0
checksum verify failed on 103612416 wanted 0x9895f43e1ff3d61a found 0x3cd6c30b4e62e77e
Couldn't read tree root
ERROR: could not open ctree


mount backuproot:
[  501.840688] BTRFS info (device dm-1): flagging fs with big metadata feature
[  501.840692] BTRFS warning (device dm-1): 'usebackuproot' is deprecated, use 'rescue=usebackuproot' instead
[  501.840694] BTRFS info (device dm-1): trying to use backup root at mount time
[  501.840695] BTRFS info (device dm-1): using free space tree
[  501.840696] BTRFS info (device dm-1): has skinny extents
[  501.842357] BTRFS error (device dm-1): bad tree block start, want 103612416 have 17126188627709133626
[  501.842644] BTRFS error (device dm-1): bad tree block start, want 103612416 have 8743983881084155753
[  501.842650] BTRFS warning (device dm-1): couldn't read tree root
[  501.842945] BTRFS critical (device dm-1): corrupt leaf: root=18446744073709551610 block=74006528 slot=0 ino=119572, invalid inode transid: has 45277 expect [0, 45276]
[  501.842950] BTRFS error (device dm-1): block=74006528 read time tree block corruption detected
[  501.843222] BTRFS critical (device dm-1): corrupt leaf: root=18446744073709551610 block=74006528 slot=0 ino=119572, invalid inode transid: has 45277 expect [0, 45276]
[  501.843225] BTRFS error (device dm-1): block=74006528 read time tree block corruption detected
[  501.843228] BTRFS warning (device dm-1): couldn't read tree root
[  501.844379] BTRFS error (device dm-1): parent transid verify failed on 86867968 wanted 45273 found 45276
[  501.844659] BTRFS error (device dm-1): parent transid verify failed on 86867968 wanted 45273 found 45276
[  501.844663] BTRFS warning (device dm-1): failed to read root (objectid=7): -5
[  501.844938] BTRFS critical (device dm-1): corrupt leaf: root=18446744073709551610 block=71024640 slot=0, invalid root generation, have 45277 expect (0, 45275]
[  501.844941] BTRFS error (device dm-1): block=71024640 read time tree block corruption detected
[  501.845210] BTRFS critical (device dm-1): corrupt leaf: root=18446744073709551610 block=71024640 slot=0, invalid root generation, have 45277 expect (0, 45275]
[  501.845212] BTRFS error (device dm-1): block=71024640 read time tree block corruption detected
[  501.845216] BTRFS warning (device dm-1): couldn't read tree root
[  501.845388] BTRFS error (device dm-1): open_ctree failed

btrfs check:
Opening filesystem to check...
checksum verify failed on 103612416 wanted 0x42f43bde0ae40f0d found 0x0fd72531e6454ed0
checksum verify failed on 103612416 wanted 0x9895f43e1ff3d61a found 0x3cd6c30b4e62e77e
checksum verify failed on 103612416 wanted 0x42f43bde0ae40f0d found 0x0fd72531e6454ed0
bad tree block 103612416, bytenr mismatch, want=103612416, have=17126188627709133626
Couldn't read tree root
ERROR: cannot open file system
-- end diagnostic --

Re: Corrupted after multiple forceful shutdowns

[notrandom98234]

Testdisk does find btrfs where it should be in the disk, but I don't think I can repair that if btrfs doesn't even think it's there.

nixos btrfs-progs v6.3.3
kubuntu live btrfs-progs v5.16.2

uname -a:
Linux localhost 6.4.7/zen1 #1-NixOS ZEN SMP PREEMPT_DYNAMIC Tue Jan 1 00:00:00 UTC 1980 x86_64 GNU/Linux

Re: Corrupted after multiple forceful shutdowns

[notrandom98234]

Is it possible to recover the files even if it's without the directory structure? My data is most probably intact and I only have to recover some files..

Re: Corrupted after multiple forceful shutdowns

[Roman Mamedov]

On Sat, 02 Sep 2023 18:29:23 +0000
notrandom98234 <notrandom98234@protonmail.com> wrote:

> Is it possible to recover the files even if it's without the directory
> structure? My data is most probably intact and I only have to recover some
> files..

Check out "btrfs restore"

https://man7.org/linux/man-pages/man8/btrfs-restore.8.html

-- 
With respect,
Roman