yessi_r

tried the memory test plugin, so far no issues. The odd thing is once i reboot the server it will go a week or 2 with absolutely no issues, then they'll start populating in the logs. guess i'll have to take the server down and do the mem test the old fashioned way.

Hi all, over the past month or so I've been having a lot of stability issues. looking at my logs I noticed that there are a few segfault errors that are appearing. Not entirely sure how to decipher these logs but they seem to suggest issues with the cpu. I don't feel as if I've had this setup (10th gen intel) for very long so I find it a bit hard to believe it's the cpu, but any ideas? I've attached my diagnostics. Unconfirmed 500872.crdownload

yes, i've done drive replacements before, i've just never had to deal with a parity rebuild having an error while swapping parity drives. it's all sorted now. replacement drive rebuild completed with no errors. greatly appreciate the help you provided!

yes.

Yep. Looks like disk 10 failed the extended test pretty much immediately. Similar to when the error popped up as soon as the parity sync started.

Do I need to pause the parity sync and then run this test?

I'll be sure to look into how to add those (smart attribute notification's custom attributes field?) I'll see if i can reseat everything as well. though they're all in supermicro hot swap bays, but i'll check the individual connections. i haven't seen any new errors for that drive since a few min after the parity sync started for the new parity drive and i'm currently about 4.5hrs in. though my dockers are running i don't believe i've written anything new to the actual array as i keep all my docker data on the cache, just phyical files should move once the mover initiates yes correct no disk currently in disk2 the plan was to move my old parity drive to that spot since it's larger than what was there previously and since that was one of the old reiserfs drives i converted to xfs recently. my disk are definitely pretty full, i try to keep enough space for the largest single file size i can see myself having as i heard that was the recommendation, i've disabled docker, do i need to disable vm manager as well? I don't have anything for my VM pointed to my array, but if there's something i'm not aware of i'll make sure to disable that as well. with that said, what do i do now that i've disabled everything and haven't written anything to my array (that i'm aware of, space available is the same as it was prior to this swap)? do i let the new parity drive rebuild finish? or do i revert back to my old parity drive and insert a replacement drive?

here's the smart report download for the disk in question. mediaserver-smart-20240118-1750.zip

Hi all, I recently went to upgrade my parity drive to a larger disk and ran into an issue about less than 1% into the process where i received a Warning message that reads "Array has 1 disk with read errors" (error count is 219) prior to replacing my parity drive i had no errors for any disks. what are my best next steps? do i stop this parity rebuild on the new parity disk, put back in the original parity drive, and replace the bad drive? or let this parity rebuild finish and then address? if the first option, what is the correct order of operations now that i've introduced a new parity drive effectively.... Thanks in advance i'm running Unraid 6.11.1 i'll attach the diagnostics mediaserver-diagnostics-20240118-1707.zip