i had several dockers that after my server did a kernel panic seem to have reverted to an older config. and im routinely getting kernel panics now.

makarov-diagnostics-20230826-0046.zip tower-diagnostics-20230825-2346.zip

I believe I also got a call trace? I think it said

Post new diags after array start.

i also found this in my clipboard from the logs. i think it might be related? it looks like issues with my cache drive.

Quote

BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 71, gen 0

 

makarov-diagnostics-20230826-0913.zip

Btrfs is detecting data corruption in the pool, also the docker image is corrupt, Ryzen with overclocked RAM is known to corrupt data, suggest correcting that then recreate the docker image and scrub the pool.

alright i am making some changes and adding more drives tomorrow, i will swap out ram and i dont think its over clocked its supposed to be 3200 or 3400 but i will correct it if thats also there. and ill rebuild the qbittorent docker

5 hours ago, illegal-deference8464 said:

supposed to be 3200 or 3400

That's overclocked for your CPU, see the link above.

so i finally got this all reconnected and everything reseated, i have one drive showing as disabled so when attempting to start the array in maintenance mode to rebuild it i had to leave before i could start it and it crashed while i was gone. makarov-diagnostics-20230901-2308.zip so im gonna attempt to rebuild disc 5 with the same disc now that im home and watching it

 

@JorgeB any other ideas? i can try to get another diagnostic bundle and i was running syslog when it crashed on me last time. i also have clocked the ram down to the 1886 since its 2x2 8Gb sticks,

Post another syslog but if it's still crashing there could be another hardware issue.

here is syslog from last crash and i havent ran it since

syslog

The log shows some disks issues, but nothing that would cause a crash, one thing you can try is to boot the server in safe mode with all docker/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one. 

Awesome thank you ill try that

ok so it kept happening then i remembered that i was having issues with 2 sticks of the ram i put in here and thats why i had extras around. i swapped out the ram for a different set of 2 sticks so we will monitor it now for the next few days and see what happens

 

ok we are up for 2 days straight now slowly enabling more dockers and i think we are working now!. thank you for your help