#corrupted btrfs disk image file recovery

31 messages · Page 1 of 1 (latest)

full flame
#

had a catastrophic failure of a writethrough disk cache containing btrfs vm disk images. both completely unmountable. i've tried the usual recovery approaches to no avail. offering reward for successful data recovery. file carving works to a minimal extent but is useless without path data.

regular mount attempt:

[10113.417241] BTRFS info (device loop0): first mount of filesystem 109fc8c0-557f-4ea1-9de8-ac8888464f6d
[10113.417276] BTRFS info (device loop0): using crc32c (crc32c-intel) checksum algorithm
[10113.417290] BTRFS info (device loop0): disk space caching is enabled
[10113.439147] BTRFS error (device loop0): level verify failed on logical 75317248 mirror 1 wanted 1 found 0
[10113.445609] BTRFS error (device loop0): level verify failed on logical 75317248 mirror 2 wanted 1 found 0
[10113.445697] BTRFS warning (device loop0): couldn't read tree root
[10113.447289] BTRFS error (device loop0): open_ctree failed

attached screenshot is dmesg from when the failure occurred

rancid niche
#

@full flame you said there was money involved?

full flame
#

beware that i've tried all the usual recovery steps you'd find with brief google searches

rancid niche
#

this is in a vm?

full flame
#

and the people in #btrfs on irc have told me "... good luck"

full flame
rancid niche
#

did you make backups ie with snapper?

full flame
#

compress=zstd

#

if i had backups i wouldn't be looking to pay people to recover the data

grizzled mason
#

I think killer means snapshots, not backups

#

snapshots that might also be corrupted

rancid niche
#

this

full flame
#

doubt it. either way the btrfs tools don't dare even attempt to read the disks much so

grizzled mason
#

and you know, covering basics, I assume that you can't mount the drive in another system because that fails?

full flame
#

i'm already on another system, i have dd copies of the drives at failure-time stored on there, and that's what i am operating on right now

#

mounting the images presents the same problems as attempting to mount them in the original system yes

grizzled mason
#

yeah, sorry for stupid question, I just like to make sure other methods don't randomly work even if they shouldn't

full flame
#

this is >1tb of data, so no matter how many recent writes have been corrupted before the vm failed, surely the vast majority of it should be intact since it was at rest

#

(across two btrfs partitions)

grizzled mason
#

@chilly imp do you know / know anyone?

graceful flint
grizzled mason
graceful flint
#

i haven't seen it mentioned explicitly, just wanna make sure

grizzled mason
#

In DM with me :p

graceful flint
#

oh lol sad

full flame
#

terabytes of unnamed files are near useless