-
Notifications
You must be signed in to change notification settings - Fork 240
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Btrfs partition not mountable #753
Comments
Transid mismatch mostly means the death sentence to a btrfs. But considering it's mmc, and non-kernel btrfs operations, it's pretty unlikely to be a kernel bug. Repair to a status which can pass btrfs check is almost impossible, for data salvage, you can try mount with "-o ro,rescue=all" some some recent kernels, if that mounts, you can try to grab the data. |
I got the same error mounting with "-o ro,rescue=all".
Any more I could do to recover the data? |
You said you did a restore, does it mean you have the backup available and not the original filesystem? You could attempt to restore to another disk, possibly on another computer. I read on CloneZilla website it uses knowledge of btrfs to reduce amount that is copied. It is possible that there is a problem in how that code works, and thus didn't copy important metadata or couldn't recreate it properly, or it placed things misaligned (so btrfs couldn't find all metadata). Perhaps there is some help to be found from clonezilla/forums/etc. Did you have a different partition layout or disk size when you restored? One thing to try is btrfs-restore, which sometime can read data off a broken filesystem. I am sorry the backup/restore didn't work. And when you're back up and running again, perhaps look at |
Hi,
I use Clonezilla to back up and restore a Btrfs partition, but afterwards the restored partition was unmountable.
dmesg:
btrfs check:
btrfs check --repair:
I'm trying to see if there's any way I could recover this partition, or at the very least salvage the data.
The text was updated successfully, but these errors were encountered: