Maticks Posted May 3 Share Posted May 3 since upgrading to 6.12.10 ive had BRFS errors not on my main cache setup but my second cache pool. A reboot always fixes it, rolling back to 6.12.8 seems to stop the BRFS issues, but is there a fix here i can apply? tower-diagnostics-20240503-1654.zip.crdownload Quote Link to comment
JorgeB Posted May 3 Share Posted May 3 May 3 14:04:23 Tower kernel: BTRFS error (device nvme1n1p1): block=11586651668480 write time tree block corruption detected This usually means a RAM problem, and btrfs is also detecting data corruption, start by running memtest. Quote Link to comment
Maticks Posted May 5 Author Share Posted May 5 ive tried different sticks and in different slots works fine for 12 hours then starts error again. it's weird behaviour. Quote Link to comment
Maticks Posted May 5 Author Share Posted May 5 lots of people downgraded to 6.11.5 who ran into this but i can't seem to do that anymore? is there a command to force that version to downgrade ? Quote Link to comment
Maticks Posted May 5 Author Share Posted May 5 (edited) May 5 15:50:51 Tower kernel: BTRFS error (device sde1): parent transid verify failed on logical 13897975595008 mirror 2 wanted 1008412 found 1008417 May 5 15:50:51 Tower kernel: BTRFS error (device sde1): parent transid verify failed on logical 13897975595008 mirror 1 wanted 1008412 found 1008417 May 5 15:50:51 Tower kernel: BTRFS: error (device sde1: state A) in __btrfs_free_extent:3076: errno=-5 IO failure May 5 15:50:51 Tower kernel: BTRFS info (device sde1: state EA): forced readonly May 5 15:50:51 Tower kernel: BTRFS error (device sde1: state EA): failed to run delayed ref for logical 13897975300096 num_bytes 16384 type 176 action 2 ref_mod 1: -5 May 5 15:50:51 Tower kernel: BTRFS: error (device sde1: state EA) in btrfs_run_delayed_refs:2150: errno=-5 IO failure May 5 15:50:51 Tower kernel: BTRFS warning (device sde1: state EA): Skipping commit of aborted transaction. May 5 15:50:51 Tower kernel: BTRFS: error (device sde1: state EA) in cleanup_transaction:1992: errno=-5 IO failure happened a lot quicker this time Edited May 5 by Maticks Quote Link to comment
JorgeB Posted May 5 Share Posted May 5 5 hours ago, Maticks said: lots of people downgraded to 6.11.5 who ran into this but i can't seem to do that anymore? I understood there wasn't a problem with v6.12.8? Quote Link to comment
Maticks Posted May 5 Author Share Posted May 5 6.12.8 is crashing for me the same way with BTRFS. I will try change out the motherboard, processor and memory see if that fixes it. its weird my main cache drive is fine just my second cache pool is having this issue. but a repair has no errors. Quote Link to comment
JorgeB Posted May 6 Share Posted May 6 There have been some users with btrfs issues after updating from v6.11 to v6.12, if the hardware is not suspected, I would suggest recreating the pool, or trying zfs instead. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.