使用 clonezilla 恢复系统分区后，当我启动时，由于 BTRFS 错误，该分区被强制只读。我很确定clonezilla分区映像没问题
dmesg 输出这些错误：
[ 79.693242] systemd-journald[594]: File /var/log/journal/70cf9b43b18548dba2f9e8d59e694030/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.
[ 102.571835] BTRFS error (device nvme0n1p5): level verify failed on logical 21189033984 mirror 1 wanted 1 found 0
[ 102.572056] BTRFS error (device nvme0n1p5): level verify failed on logical 21189033984 mirror 2 wanted 1 found 0
[ 102.572152] BTRFS warning (device nvme0n1p5): Skipping commit of aborted transaction.
[ 102.572155] BTRFS error (device nvme0n1p5: state A): Transaction aborted (error -5)
[ 102.572157] BTRFS: error (device nvme0n1p5: state A) in cleanup_transaction:2021: errno=-5 IO failure
[ 102.572160] BTRFS info (device nvme0n1p5: state EA): forced readonly
[ 143.474666] systemd-journald[594]: /var/log/journal/70cf9b43b18548dba2f9e8d59e694030/user-1000.journal: Journal file corrupted, rotating.
[ 143.474681] systemd-journald[594]: Failed to rotate /var/log/journal/70cf9b43b18548dba2f9e8d59e694030/system.journal: Read-only file system
[ 143.474687] systemd-journald[594]: Failed to rotate /var/log/journal/70cf9b43b18548dba2f9e8d59e694030/user-1000.journal: Read-only file system
[ 143.475018] systemd-journald[594]: Failed to write entry to /var/log/journal/70cf9b43b18548dba2f9e8d59e694030/user-1000.journal (30 items, 889 bytes) despite vacuuming, ignoring: Bad message
这些错误可能来自于恢复分区吗？
看起来像是一些硬件问题，但我在同一磁盘的另一个分区上安装了 Windows，并且运行正常。是SSD盘。
我再次恢复了分区，结果相同，clonezilla 没有给出错误并报告图像正常。
我尝试使用 gparted live 进行修复，gparted 告诉我它无法修复分区，
我也尝试过btrfs check --force /dev/nvme0n1p5，它修复了大量错误并意外完成。