S.Ilver Posted July 15 Share Posted July 15 Hi I was running a regular parity check and noticed a small number of errors that were corrected. Afterwards I ran a second check without writing the corrections to parity to make sure the first check resolved everything and now there seems to be significantly more errors 600+. I'm not sure what the cause might be or what next steps I should take. I'm running 6.12.10. egghouse-diagnostics-20240715-1246.zip egghouse-smart-20240715-1015.zip egghouse-smart-20240715-1014.zip egghouse-smart-20240715-1016.zip Quote Link to comment
S.Ilver Posted July 15 Author Share Posted July 15 (edited) 3 hours ago, JorgeB said: Start by running memtest. Thanks! I ran memtest and it reported no errors. What next steps should I look into? Edited July 15 by S.Ilver Quote Link to comment
JorgeB Posted July 16 Share Posted July 16 memtest is only definitive if it finds errors, if you have multiple sticks try using the server with just one, then run a correcting check followed by a non correcitng one, if the 2nd one still detects new errors repeat with a different stick. Quote Link to comment
S.Ilver Posted July 17 Author Share Posted July 17 (edited) So I pulled one stick of RAM and then started a correcting check and it seemed like that was going to be the solution it found fewer errors than it had previously, but then the parity check seems to have stalled out at 90% and the current speed is <1 MB/S. I paused it(or well tried to pause it, I don't think unraid is actually pausing it) as I wasn't really sure what else to do about this and grabbed the diagnostics. When I first noticed it slowed down last night I double checked all my docker and containers to make sure they were all paused and that nothing else was writing to the disk and it doesn't seem like anything is. egghouse-diagnostics-20240717-0710.zip Edited July 17 by S.Ilver Quote Link to comment
JorgeB Posted July 17 Share Posted July 17 Unraid driver crashed, this is almost always a hardware issue, retry with the other RAM stick. Quote Link to comment
S.Ilver Posted July 18 Author Share Posted July 18 (edited) So I retried it with the other stick of RAM and had the same results and tried with a new couple sticks of RAM I was saving for another project, though with the new sticks of RAM it happened even sooner. I downloaded the diagnostics from the new try. egghouse-diagnostics-20240718-0738.zip Edited July 18 by S.Ilver Quote Link to comment
JorgeB Posted July 18 Share Posted July 18 Unraid driver still crashing, is this a new server or was it working fine before with the same hardware and Unraid release? Quote Link to comment
S.Ilver Posted July 18 Author Share Posted July 18 (edited) It was working perfectly, leading up until this. I've had no issues with anything on it before. I've had it running since around November of last year. Edited July 18 by S.Ilver Quote Link to comment
Solution JorgeB Posted July 18 Solution Share Posted July 18 Then it's almost certainly hardware, if it's not RAM, could be board/CPU Quote Link to comment
S.Ilver Posted July 18 Author Share Posted July 18 Are there any ways for me to test either of them and try it narrow it down? Or is best bet to pull and swap parts. Quote Link to comment
JorgeB Posted July 18 Share Posted July 18 3 minutes ago, S.Ilver said: Or is best bet to pull and swap parts. This. Quote Link to comment
S.Ilver Posted July 18 Author Share Posted July 18 Thanks for all the help. Hopefully I'll be able get started on swapping parts and able to report back with the server in function order in the near future. Quote Link to comment
S.Ilver Posted July 23 Author Share Posted July 23 Swapped the CPU and no errors on the next parity check I ran. Thanks for all of the help! 1 Quote Link to comment
Recommended Posts
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.