You are not logged in.
Pages: 1
Hey there.
So, my home partition on my ssd (in the past 24h) has been having issues mounting. On mobile, so i can't produce a whole lot of logs right now.
On boot, journalctl -xb reports
BTRFS error (device nvme0n1p4): tree first mismatch detected, bytenr=64401833984 parent_transid=245599 key expected=(64058605568,169,536870912) has =(64058605568,169,0)
BTRFS error (device nvme0n1p4): tree first mismatch detected, bytenr=64401833984 parent_transid=245599 key expected=(64058605568,169,536870912) has =(64058605568,169,0)
BTRFS error (device nvme0n1p4 state A:): Transaction aborted (error -5)
BTRFS: error (device nvme0n1p4 state A) in __btrfs_free_extent:3205: errno=-5 IO failure
BTRFS error (device nvme0n1p4 state EA): failed to run delayed ref for logical 6406073488 num_bytes 16384 type 176 action 2 ref_mod 1: -5
BTRFS: error (device nvme0n1p4 state EA) in btrfs_run_delayed_refs:2154: errno=-5 IO faileure
BTRFS: error (device nvme0n1p4 state EA) in btrfs_replay_log:2100: errno=-5 IO failure (Failed to recover log tree)
mount: /home: can't read superblock on /dev/nvme0n1p4.
dmesg(1) may have more information after failed system call.
BTRFS error (device nvme0n1p4 state EA): open_ctree failed: -5
home.mount: Mount process exited, code=exited, status=32/n/a
home.mount: Failed with result 'exit code'.
Failed to mount /home
Dependency failed for Local File Systems.dmesg reports the same BTRFS above. I am unable to mount the partition to read the drive so i can back up the drive.
My search for solution did yield a suggestion to try btrfs rescue zero-log. Is this safe to do? I don't mind losing a minute of writes per the warning that came with the suggestion.
Offline
Hey there.
home.mount: Mount process exited, code=exited, status=32/n/a home.mount: Failed with result 'exit code'. Failed to mount /home Dependency failed for Local File Systems.dmesg reports the same BTRFS above. I am unable to mount the partition to read the drive so i can back up the drive.
My search for solution did yield a suggestion to try btrfs rescue zero-log. Is this safe to do? I don't mind losing a minute of writes per the warning that came with the suggestion.
Definitely not an expert take but if you're having problems with the superblock then your filesystem is most probably corrupt.
Last time I had a similar issue(but on a filesystem/block I didn't really care about), re-formating fixed it.
Offline
Try 'btrfs-restore -D' to see if any files could be restored to different medium.
Offline
Offline
Pages: 1