snare200

Hey everyone, 2403487 errors on the last parity check and parity is shown as disabled. Diagnostics are attached. I am not sure if this is related: A few months back I had a new drive giving me an: Unmountable: No File System. I used xfx_repair, which seemed to fix the issue, but not too long after, I started to get errors on the parity check. ivanka-diagnostics-20190802-0020.zip

That was easy. Thanks!

Hi everyone, I have a drive giving me an "Unmountable: No File System." The drive is only a couple of weeks old, I figured it was a bad drive and swapped it with another one and started the array - after searching this forum, I realized that was a naive thing to do. The new drive also shows as Unmountable. I ran xfs_repair -n; xfs_repair; and xfs_repair -L. xfs_repair is ending with: I've attached the full xfs_repair -L and diagnostics. I'm not sure what the next step is. Thanks for any help! 2ivanka-diagnostics-20190424-0702.zip xfs_repair -L.zip

It's a new supermicro board with ECC memory. The Xeon cpu is 4 years old and the board came out 3 years ago - I figured it would be new enough for my budget.

I appreciate your help, I know this isn't really a hardware forum but I haven't been able to solve the issue. I ran memtest with each stick of ram individually with everything else disconnected from the mb, each stick passed. I tried two sticks at once, they both passed. I tried all four sticks, and the system crashed. Thinking it might be some faulty slots on the mb, I tried the parity sync with just the two sticks in that passed memtest together, and it crashed. I tried swapping out the power supply, still crashed. I guess it comes down to the motherboard or the cpu - is there a way to test either to avoid exchanging/swapping them out ?

It's a Seasonic Power Supply 650W SS-650HT, bought used. Trying to get things going with just 3 drives total.

Memtest also worked fine until around the 30 minute mark and then it froze. It doesn't look like the cpu is overheating and all the fans continue to run. I guess the next step is to try 1 ram stick at a time and then start swapping out components?

I installed nerdpack and turned on the mcelog-128-x86_64-1.txz module, and tried again with FCP in troubleshooting. I've attached the logs. I don't know if this is important but in the last set of tests, it performed as I explained earlier (Parity sync slowing down and eventually crashing after 20-30 minutes). In this set of tests it crashed within 5 minutes of the parity sync--which it does occasionally. FCPsyslog_tail.txt coop-diagnostics-20170205-0803.zip

Logs attached. FCPsyslog_tail.txt coop-diagnostics-20170205-0649.zip

This is my first server build, first time using Unraid, and I don't have a log, so I appreciate your patience. When I start the array, the parity sync begins and hovers around 98 mb/sec for the first 10 minutes or so. Over the next couple of minutes the speed drops to around 3 mb/sec. At around 20 minutes, it becomes unresponsive - Attempting anything in a browser over the network will now timeout, a keyboard plugged directly into the server no longer works. The only thing I can do is a hard shutdown. On restarting, everything works fine again until I try to start the array and the process repeats. I'm afraid I don't know how to get a log before the shutdown.