Cobra Forum

Linux => Hardware => Topic started by: kalpana on Oct 11, 2023, 04:09 AM

Title: problem with a btrfs partition (not sure if hardware or soiftware)
Post by: kalpana on Oct 11, 2023, 04:09 AM
A short premise: I have KDE Neon (latest release) and today, after an update (via terminal), I didn't manage to get the graphical desktop. After doing a chroot with Kubuntu (in another partition of the same PC) I noticed that the problem was /dev/sdc2 (a btrfs partition on a sata disk 500 Gb added to my PC, where I have some backups not very important, at least so I believe  ). Modifying etc/fstab in KDE Neon (so that /dev/sdc2 is no more "auto", but "noauto" mounted) I managed to have a normal graphical desktop in KDE Neon.

But I didn't manage to rescue that partition, following the instruction of several websites.
1. It was impossible to mount /dev/sdc2, because
Code:
can't read superblock on /dev/sdc2, while the other partition of that hd sata, that is /dev/sdc1 was correctly mounted.
2. Via gparted it was impossible to fix the problem. I tried several terminal commands such as
Code:
sudo mount -o recovery /dev/sdc2 /mnt/added, and then
Code:
sudo btrfs check --repair /dev/sdc2

Code:
btrfs scrub /mnt/added
Code:
sudo btrfs rescue zero-log /dev/sdc2

Code:
mount -t btrfs -o ro,usebackuproot /dev/sda2 /mnt/added

I.g. with this command sudo
Code:
btrfs rescue super-recover /dev/sdc2
I get this answer:
Code:
All supers are valid, no need to recover
3. It seems that the problem was:
Code:
parent transid verify failed on 64356352 wanted 5141 found 5136

Indeed:

Code:
sudo btrfs check /dev/sdc2
Opening filesystem to check...
parent transid verify failed on 64356352 wanted 5141 found 5136
parent transid verify failed on 64356352 wanted 5141 found 5136
parent transid verify failed on 64356352 wanted 5141 found 5136
Ignoring transid failure
ERROR: root [5 0] level 0 does not match 2

ERROR: cannot open file system
This is an hardware or a software problem?
And therefore what should I do?
Thank you!