i fear not.
are you using a 2,5" disk connected to USB3? Iāve had many of those cause troubles with btrfs (only) and wasted lots of time trying to fix the fs. if your data is valuable grab a rescue-image of the disk first and do all the (experimental) btrfs-recovery stuff on that; if you can mount the disk ro you can (probably) still copy the data.
if you do chunk-recover you will have to wait for it to finish; but after that scrub will still show (unrecoverable) errors or fail and balance will most likely not be possible.
in my experience the fastest way is to copy all data and re-create a new btrfs on the disk; you might check the disk itself with badblocks and smartctl before.
GOOD LUCK!
If i try to mount it - that doesnĀ“t work:
pi@nextcloudpi:/media $ sudo mount -t btrfs -o ro,usebackuproot /dev/sda1 /media/nvme/
mount: /media/nvme: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error.
pi@nextcloudpi:/media $ sudo mount -t btrfs -o rootflags=recovery,nospace_cache /dev/sda1 /media/nvme/
mount: /media/nvme: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error.
pi@nextcloudpi:/media $ sudo btrfs rescue zero-log /dev/sda1
checksum verify failed on 1048576 found 000000B6 wanted 00000000
checksum verify failed on 1048576 found 000000B6 wanted 00000000
bad tree block 1048576, bytenr mismatch, want=1048576, have=0
ERROR: cannot read chunk root
ERROR: could not open ctree
I hope i can get my data back iĀ“m now very afraid that i have executed yesterday the dd comand not correctly during my read/write test. ā¦ oh my god:-(
is it anyhow possible to recover the data ? IĀ“m not sure if i have executed wrong command, but it could be possibleā¦