November 4, 2025Nov 4 I recently had one of my new drives go offline in my array. After checking, it reported file system corruption, so I started the array in maintenance mode and ran the fix, which seemed to have sorted it. A week or so later, I noticed my parity check was reporting a bunch of errors but the offending drive wasn't showing as offline, so I took the array down and once again started it in maintenance mode and ran a check. The drive yet again was coming up with file system corruption, so I ran the fix and it seemed to be ok. A week later, same thing again. I've just run the fix for the third time.I'm hoping someone can save me a whole lot of troubleshooting here. I'm wondering if the drive is faulty? No SMART errors are being reported even after running an extended check. The drive is a WD Red (WDC_WD40EFPX) and installed about 3 months ago. Coincidentally and for context, I also had just upgraded Unraid to the latest release candidate 7.2.0 rc1. I'm now on the official release 7.2.0. I'm not sure if it's correlation or causation. Could it be a dodgy connection to the drive? I'm not sure that would manifest this way.Anyone have similar experience? Any suggestions where I should start? I've probably blown away the logs now I've restarted the server. In hindsight, I should have saved logs to see if they revealed anything. Oops.
November 4, 2025Nov 4 Community Expert Post the diagnostics after there are read or write errors with the drive.
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.