Never had this issue and I’ve been running unraid for years. I had to unfortunately hard reset while the server was booting up

I’m not seeing any errors so far at 28% or any failures with the drives.

How to handle this?

You are likely to get better informed feedback if you attach your system’s diagnostics (with everything in the one zip file) to your next post in this thread. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog.

Yep makes snese

homeserver-diagnostics-20260222-0810.zip

So some things...

1. I'm seeing high read speeds on disk 3. Cancelled smart test and hasnt changed. The read speed is 100 mb/s + compared to 9 mb/s for parity check

2. I have smart short running on that which seems to be stuck on 90%

3. There was a tmp appdata folder for some reason that I deleted -> Share appdata_tmp_20250510110541 is an implied array-only share, but files / folders exist on the cache -> never noticed this before. Could have been there for a long time

4. disk 3 is zfs and where I backup appdata too

Edited February 22Feb 22 by andyd

Either wait for the smart self-test to complete before attempting parity check, or wait until after parity check to attempt self-test

Smart shorts passed on all other disks. It's just the one. I'm not sure about waiting for parity check to end - that's the reason why I'm posting. I don't think 15 days makes sense.

1. I cancelled parity check

2. restarted

3. parity check started again - is there a way to not have this auto start?

4. smart check stuck at 90% while there are high reads on the drive - ~188 MB/s

don't really understand what's going on with the high read speeds

homeserver-diagnostics-20260222-0912.zip

Ok well smart test passed and read speeds now 0 MB/s 🤷‍♂️

3 hours ago, andyd said:

So some things...

1. I have smart short running on that which seems to be stuck on 90%

note that the SMART short test is not really meaningful (unless it fails). Only passing the extended test is a good indication that the drive is in good shape.

Yeah I was only running it because it seemed to be the problem drive and then noticed it was stalling with the test too. I’m waiting for my monthly parity check so I’ll try extended later

There was something else reading from disk3 in the first diags.

Missed your last message. I'm coming back to this because it's parity check for the month and it's the same problem. This has never happened before.

So yeah, something is reading on that drive but it only seems to happen during parity check now because it's normal otherwise. Could the drive be corrupted in some way? It's where I do my zfs backups but I don't see any zfs errors. The extended test took over a day to finish but it didn't have any errors

Edited March 1Mar 1 by andyd

Of course parity check reads all drives.

On 2/23/2026 at 3:23 AM, JorgeB said:

something else reading from disk3