I backed up my code (the thing I really needed) Im thinking of switching do arch with my friend to learn more about arch
but I'm really wanting to get my stuff back
It seems your BTRFS device has some critical damage, most likely the reason why you can't boot.
[ 123.321425] BTRFS info (device sdd3): using crc32c (crc32c-intel) checksum algorithm
[ 123.321433] BTRFS info (device sdd3): using free space tree
[ 126.443602] BTRFS info (device sdd4): using crc32c (crc32c-intel) checksum algorithm
[ 126.443610] BTRFS info (device sdd4): using free space tree
[ 126.552487] BTRFS error (device sdd4): parent transid verify failed on logical 166215680 mirror 1 wanted 16216 found 15590
[ 126.560861] BTRFS error (device sdd4): parent transid verify failed on logical 166215680 mirror 2 wanted 16216 found 15590
[ 126.560872] BTRFS warning (device sdd4): couldn't read tree root
[ 126.561178] BTRFS error (device sdd4): open_ctree failed
[ 141.462599] BTRFS: device label home devid 1 transid 16216 /dev/sdd4 scanned by pool-udisksd (2766)
[ 141.463067] BTRFS info (device sdd4): using crc32c (crc32c-intel) checksum algorithm
[ 141.463074] BTRFS info (device sdd4): using free space tree
[ 141.463902] BTRFS error (device sdd4): parent transid verify failed on logical 166215680 mirror 1 wanted 16216 found 15590
[ 141.768988] BTRFS error (device sdd4): parent transid verify failed on logical 166215680 mirror 2 wanted 16216 found 15590
[ 141.768994] BTRFS warning (device sdd4): couldn't read tree root
[ 141.769136] BTRFS error (device sdd4): open_ctree failed
[ 163.063027] SGI XFS with ACLs, security attributes, realtime, scrub, repair, quota, no debug enabled
[ 163.072547] JFS: nTxBlock = 8192, nTxLock = 65536
[ 173.551313] BTRFS: device label home devid 1 transid 16216 /dev/sdd4 scanned by mount (4282)
[ 173.551649] BTRFS info (device sdd4): using crc32c (crc32c-intel) checksum algorithm
[ 173.551654] BTRFS info (device sdd4): using free space tree
[ 173.584542] BTRFS error (device sdd4): parent transid verify failed on logical 166215680 mirror 1 wanted 16216 found 15590
[ 173.593005] BTRFS error (device sdd4): parent transid verify failed on logical 166215680 mirror 2 wanted 16216 found 15590
[ 173.593016] BTRFS warning (device sdd4): couldn't read tree root
[ 173.593258] BTRFS error (device sdd4): open_ctree failed
[ 174.560357] FAT-fs (sdd1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 174.651409] FAT-fs (sdd2): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 174.688683] BTRFS: device label home devid 1 transid 16216 /dev/sdd4 scanned by mount (4627)
[ 174.688997] BTRFS info (device sdd4): using crc32c (crc32c-intel) checksum algorithm
[ 174.689004] BTRFS info (device sdd4): use zstd compression, level 3
[ 174.689005] BTRFS info (device sdd4): using free space tree
[ 174.689593] BTRFS error (device sdd4): parent transid verify failed on logical 166215680 mirror 1 wanted 16216 found 15590
[ 174.701312] BTRFS error (device sdd4): parent transid verify failed on logical 166215680 mirror 2 wanted 16216 found 15590
[ 174.701325] BTRFS warning (device sdd4): couldn't read tree root
[ 174.701526] BTRFS error (device sdd4): open_ctree failed
[ 280.455040] ntfs3: Max link count 4000
[ 280.455044] ntfs3: Enabled Linux POSIX ACLs support
[ 280.455044] ntfs3: Read-only LZX/Xpress compression included
You can try the solution given here,
if this doesn't work,
Please, post any errors found at any stage. If none of this works, then as mentioned in this article try contacting the btrfs maintainers with the logs (their IRC channel and mailing list is given in this article, you can try contacting them on both)
how would I put my /home corrupted data onto another drive for later recovery
To create a backup of the whole drive you could use dd.
This command (adjust path!) would create a compressed image file:
sudo dd if=/dev/sda4 conv=sync,noerror bs=64K | gzip -c > /PATH/TO/DRIVE/backup_image.img.gz
It will require a lot of space and take a long time. Also it will still contain the filesystem error and hence can not be mounted and you can not access your data.
It could help, if you manage to break something even more trying to repair the filesystem with the commands @NaN gave you.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.