Jump to content

Unable to write to cache


Go to solution Solved by JorgeB,

Recommended Posts

From fix common problems I'm getting this:

Unable to write to cache

Drive mounted read-only or completely full

 

That is the only problem that shows up, In the pool devices it shows I have 514 GB free. 

I only realized there was a problem because one of my docker containers stopped working.

 

the diagnostics is attached. 

 

Thank you!

tower-diagnostics-20220919-1715.zip

Edited by grande.andre
Link to comment
  • Solution
Sep 19 12:25:53 Tower kernel: BTRFS error (device sdf1): block=2395218591744 write time tree block corruption detected

This usually means bad RAM or other kernel memory corruption, Ryzen with overclocked RAM like you have is known to corrupt data, so you should fix that, then run memtest.

 

 

Sep 17 16:59:52 Tower kernel: macvlan_broadcast+0x10e/0x13c [macvlan]
Sep 17 16:59:52 Tower kernel: macvlan_process_broadcast+0xf8/0x143 [macvlan]

Unrelated, macvlan call traces are usually the result of having dockers with a custom IP address and will end up crashing the server, upgrading to v6.10 and switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)), or see below for more info.

Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...