sir_ferguson

Hi everyone, I recently tried to optimize my server for power efficiency. Powertop had 0% on for all package c states. After playing around with BIOS settings for a while I figured out that everything seemingly works if i set "C State Limit" to the highest stated ("C7" for me) instead of "Auto". After that, power top displays percentages for all package c states and I save around 4w at idle. The problem is, after a while the server just halts. No Web Interface. No SSH. Not even when directly connected to the server. After this I have to manually reset. I know Ryzen CPUs have issues with C States on Linux. However my server is running on an Intel i5 4670. Any ideas? For me the problem has been hard to diagnose since the it only occurs after the server has been running for a while.

Ahh ok. Sorry for the confusion.

Ohh I just realized that the log says "P corrected". Does that mean only the parity got corrected and my data is fine? If so all I have to do is rebuild the parity drive which I have to do anyway, right?

Thank you for your advice. Sorry for the misleading title, I did not know how else to describe it. All drives are assigned correctly, but after removing the old drive the parity drive is invalid. But what about the corrected sectors. Do I not have to worry about them? Maybe I could rebuild them with the old drive? Cancel Parity check. Add old drive again. Rerun parity check. Remove old drive. Unassign parity drive. Rebuild parity drive.

Ok so here is the situation. I had issues with a drive so I moved all its data to the other drives. Because I wasn't using it I wanted to remove it from the array. After resetting the config and restarting the array, I was asked if the Parity drive is still ok. Not wanting to recompute the parity drive and thinking it wasn't an issue since the other drive was empty anyway I clicked yes. Afterwards I ran a parity check. It took me a bit before realizing my mistake. It checked ~4.3% of the array and corrected 539 Sync errors. Looking at the logs confirmed my suspicion: Aug 18 12:39:55 Stallman kernel: md: recovery thread: P corrected, sector=0 Aug 18 12:39:55 Stallman kernel: md: recovery thread: P corrected, sector=8 Aug 18 12:39:55 Stallman kernel: md: recovery thread: P corrected, sector=16 Aug 18 12:39:55 Stallman kernel: md: recovery thread: P corrected, sector=24 Aug 18 12:39:55 Stallman kernel: md: recovery thread: P corrected, sector=32 Aug 18 12:39:55 Stallman kernel: md: recovery thread: P corrected, sector=40 ... So basically my first few sectors are probably garbage now. I doubt canceling the Parity Check will restore the sectors. However maybe there is a way to check which files might be effected. My array is only 33% full, so with insane luck maybe nothing important was stored there. Anyway, I got myself in a bit of a mess. What's the best way to proceed?