~ giải ngố

Solution from forum garudalinux

btrfs check --repair /dev/sda3 
enabling repair mode
WARNING:

	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 1
Starting repair.
Opening filesystem to check...
parent transid verify failed on 165848678400 wanted 396666 found 395534
parent transid verify failed on 165848678400 wanted 396666 found 395534
parent transid verify failed on 165848678400 wanted 396666 found 395534
Ignoring transid failure
Checking filesystem on /dev/sda3
UUID: bb5e830b-8781-4a34-9000-e067c0d074e5
repair mode will force to clear out log tree, are you sure? [y/N]: y
[1/7] checking root items
Fixed 0 roots.
[2/7] checking extents
No device size related problem found
[3/7] checking free space cache
cache and super generation don't match, space cache will be invalidated
[4/7] checking fs roots
[5/7] checking only csums items (without verifying data)
[6/7] checking root refs
Recowing metadata block 165848678400
ERROR: fails to fix transid errors
[7/7] checking quota groups skipped (not enabled on this FS)
found 157650124800 bytes used, error(s) found
total csum bytes: 120225104
total tree bytes: 788234240
total fs tree bytes: 572751872
total extent tree bytes: 65667072
btree space waste bytes: 148617112
file data blocks allocated: 186271449088
 referenced 183664615424

⸻ ~ giải ngố