Skip to contentSkip to conversation

Help with my btfrs corruption after a power failure!

DISCUSSION [email protected] 2 participants 2 messages Mar 10, 2020 Btrfs file system

lore
Share & tools
lore
#0 lore raw

Hello! I need some tips on how to repair the btrfs partition, following repeated power outages from home.
The situation: For several months I have stopped using xpenology in favor of another dedicated Linux distribution for network storage (at another location I ran into the same btrfs corruption issue, but then I didn't have much data on the server and I didn't shake my head. in solving the problem). Now being the NAS server on which all the family documents can be found. On it are installed 3 hdds: one of 2 Tb and 2 of 1 Gb configured in raid1 since using xpenology. The tried commands were:

btrfs scrub start /srv/dev-disk-by-label-2018.05.11-19-05-54 \ v15266 / btrfs scrub status -dR /srv/dev-disk-by-label-2018.05.11-19-05-54 \ v15266 /

And

btrfs check --check-data-csum / dev / md126
Checking filesystem on / dev / md126
UUID: 3ce16830-f95b-4f0c-b96f-bd6f10c435e2
checking extents
checksum verify failed on 358432768 found 5BFBA855 wanted 0F952A4E checksum verify failed on 358432768 found 5BFBA855 wanted 0F952A4E Invalid key type (BLOCK_GROUP_ITEM) found in root (202) ignoring invalid key
Invalid key type (BLOCK_GROUP_ITEM) found in root (202) ignoring invalid key
Invalid key type (BLOCK_GROUP_ITEM) found in root (202) ignoring invalid key
Invalid key type (BLOCK_GROUP_ITEM) found in root (202) ignoring invalid key
Invalid key type (BLOCK_GROUP_ITEM) found in root (202) ignoring invalid key

What is more surprising to me is, that partition configured with raid1 btrfs have been corrupted from those power outages.

Thank you for your attention

Regards,
Stefan Hodea

#1 lore raw
Quoted 33 lines · On 10.03.20 г. 10:22 ч., [email protected] wrote:

Hello! I need some tips on how to repair the btrfs partition, following repeated power outages from home.
The situation: For several months I have stopped using xpenology in favor of another dedicated Linux distribution for network storage (at another location I ran into the same btrfs corruption issue, but then I didn't have much data on the server and I didn't shake my head. in solving the problem). Now being the NAS server on which all the family documents can be found. On it are installed 3 hdds: one of 2 Tb and 2 of 1 Gb configured in raid1 since using xpenology. The tried commands were:

btrfs scrub start /srv/dev-disk-by-label-2018.05.11-19-05-54 \ v15266 / btrfs scrub status -dR /srv/dev-disk-by-label-2018.05.11-19-05-54 \
v15266 /

And

btrfs check --check-data-csum / dev / md126
Checking filesystem on / dev / md126
UUID: 3ce16830-f95b-4f0c-b96f-bd6f10c435e2
checking extents
checksum verify failed on 358432768 found 5BFBA855 wanted 0F952A4E checksum verify failed on 358432768 found 5BFBA855 wanted 0F952A4E Invalid key type (BLOCK_GROUP_ITEM) found in root (202) ignoring invalid key
Invalid key type (BLOCK_GROUP_ITEM) found in root (202) ignoring invalid key
Invalid key type (BLOCK_GROUP_ITEM) found in root (202) ignoring invalid key
Invalid key type (BLOCK_GROUP_ITEM) found in root (202) ignoring invalid key
Invalid key type (BLOCK_GROUP_ITEM) found in root (202) ignoring invalid key

Quoted 4 lines

What is more surprising to me is, that partition configured with raid1 btrfs have been corrupted from those power outages.

Thank you for your attention

What kernel version are you using and what is the version of progs?

Quoted 4 lines

Regards,
Stefan Hodea