LordShad0w

Ah ok! I just wondered as my setup never goes above the base clock from what I see. Thank you so much for explaining. 🙂 I am running all my dockers on an SSD as per the docs recommendations. My board does not support NVME drives, sadly. (I mean, it does currently but the motherboard that is going in this summer does not as it is a bit older and will also drop me to DDR4) What I had in mind was raising the clock in BIOS to something a bit higher, but I won't go that route now. Unfortunately with the RamPocalypse upon us, attaining faster RAM than what I have on hand is just not in the cards. Anyway, thank you again so much for the breakdown, I appreciate it immensely!

If I posted in the wrong section, could someone move it to the correct one please? 🙂

Ok. Could you elaborate on that? I don't understand they why or why not, or what the issues or benefits may be. Kind of what I was asking. 😉

Hey all 🙂 I have run my server at base clock since I built it. Intel i9 12900K @ 3200MHz Temps are very stable and RARELY even hit 60c. I am running a 360mm AIO with Noctua industrial PWM 3k RPM fans. My question is, is there any real benefit to raising the clock speeds? Even conservatively at 4500MHz is fairly tame for this processor. I just am not sure what actual benefit it would provide. Would it speed up VM's or help Dockers run more responsively, or just be hot and waste power for no gain? I know the benefits on my main rig because I do occasionally do some gaming on it, but I am clueless when it comes to my server on this. Any info or comments are welcomed.

I got the Dockers restored using exactly this. Thanks man!

Ok RAM checks out and is all good with the new stick. Still had a crap ton of BTRFS errors though. Main Cache was FUBAR. Shifted everything to the array, powered down, removed bad SSD, installed new one, rebooted, assigned to old slot, formatted, moved data back to Cache from Array then rebooted again. Checked logs with Enhanced Logs and so far, all is well. I also did a full check on the new SSD itself and it also reports 0 errors. Thank you so much for helping me through this as I would not have arrived here on my own to start repairing things.

Ok cool, Thank You man. I will give that a go.

It is good RAm and is the same type (DDR5) and I have it on hand. Just wondering if I can use it to get the server back up and running until my new parts come since it will not be until end of May that they arrive.

Can I safely put in the 32GB stick I have in my main machine without hurting anything? It is a known good and tested stick (just did memtest last week) so I would be going from 64 in the server down to 32.

Also, for the Dockers, there are only 12 that run on startup. They all say 58 minutes ago, but only 2 of them say (healthy), how do I know which ones are the faulty ones that keep restarting?

I did just run memtest, there were errors but aapparently the list was too long to show all of them in the log.

Ok thanks, i will look for that. I do also see a bunch of nginx errors but don't know what to make of them

Ok. I have a different mobo with new ram coming in soon. The Docker img, I never really knew what it should be so I just picked what I thought would be "enough" when I first made it years back. I can change it to whatever you recommend no problem. I use disk space manager to balance the array for all my media. Perhaps it moved that as well? If you can tell me how to fix that I will make it happen. I will run a check on the ram asap in the meantime.

Sure, give me a sec

So, while things are working again, I have a major problem. Aside from about 20 shows, all the others in my TV share are gone. Thing is, when I calculate the size of the share, it comes in at just over 4TB. I have tried to see if they got moved to another disk somehow, but no joy. It is odd since it shows the 4TB but when I look at the array numbers, the 16TB drive that had the bulk of my tv shows went from 65% filled down to 49%. I can not understand who that much data just vanished into thin air. Did you guys see anything that would indicate an operation that might account for this happening when you looked over the logs? Thanks guys.