Hello,
After a power outage and not having an UPS, I ended up with my volume being corrupted. From what I’ve gathered by searching on the web, it seems to be a corrupted metadata issue with my LVM. Currently, I have a RAID 0 setup consisting of 3x6TB and 1x4TB. I tried the method suggested in this forum section, but every time I attempt to run a btrfs check --repair, I get the following error:
I really need your help, and this is the first time I’m facing this type of issue, so I’m a bit lost.
If you need more details, feel free to ask, especially if it helps me recover my data.
After a power outage and not having an UPS, I ended up with my volume being corrupted. From what I’ve gathered by searching on the web, it seems to be a corrupted metadata issue with my LVM. Currently, I have a RAID 0 setup consisting of 3x6TB and 1x4TB. I tried the method suggested in this forum section, but every time I attempt to run a btrfs check --repair, I get the following error:
Code:
enabling repair modeWARNING: Do not use --repair unless you are advised to do so by a developer or an experienced user, and then only after having accepted that no fsck can successfully repair all types of filesystem corruption. Eg. some software or hardware bugs can fatally damage a volume. The operation will start in 10 seconds. Use Ctrl-C to stop it.10 9 8 7 6 5 4 3 2 1Starting repair.Opening filesystem to check...parent transid verify failed on 11483596980224 wanted 505698 found 505099parent transid verify failed on 11483596980224 wanted 505698 found 505099parent transid verify failed on 11483596980224 wanted 505698 found 505099Ignoring transid failureWARNING: could not setup extent tree, skipping itCouldn't setup device treeERROR: cannot open file systemIf you need more details, feel free to ask, especially if it helps me recover my data.
Statistics: Posted by Ikaru — Yesterday, 19:08