My monthly parity check started last night and I received the below error message regarding one of my drives. The check has yet to complete, as it usually takes a day or two. Can anyone suggest how to proceed? Diagnostics attached. Thanks

Unraid Disk 15 error

Jan 1, 12:40 AM

Alert [MEDIA-SERVER] - Disk 15 in error state (disk dsbl)

ST18000NM003D-3DL103_ZVTA5635 (sdi)

media-server-diagnostics-20260101-0935.zip

It's not logged as a disk problem, and SMART looks fine, so most likely it's a power/connection issue.

5 hours ago, JorgeB said:

It's not logged as a disk problem, and SMART looks fine, so most likely it's a power/connection issue.

OK, thanks! I will reseat the cables for that drive once parity check completes. Weird, as I haven;t touched anything in weeks.

Will simply rebooting after fixing cables reset the error? Or do I need to still rebuild or run another parity check? Can you point me to rebuilding onto itself steps/instructions?

Thanks!

Edited January 2Jan 2 by wdpaynter

With that many disks, I recommend dual parity.

12 minutes ago, wdpaynter said:

once parity check completes

Since you have single parity and a disabled disk, it can't really do a parity check anymore, only a read check.

1 minute ago, trurl said:

With that many disks, I recommend dual parity.

Since you have single parity and a disabled disk, it can't really do a parity check anymore, only a read check.

Ok, so stop it and fix cables? How do I rebuild the disabled disk? Thx!

https://docs.unraid.net/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array/#re-enabling-a-disabled-disk-rebuilding-onto-itself

4 minutes ago, trurl said:

https://docs.unraid.net/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array/#re-enabling-a-disabled-disk-rebuilding-onto-itself

Thank you!

The rebuild seems to have finished successfully. Thank you both for your help! One thing I have been getting is errors during parity checks. I beleive it is due to my Parity Tuning Settings and having it "pause" during nightly scheduled Mover, but am not experienced enough. I thought I had it set up correctly, but again, am uncertain. Could y'all look at the attached and/or give me any suggestions please? Should I simply ignore these errors? Is there a better way of operating?

Thanks

I think I may have figured this out. I think it was my SMTP/Gmail password for my notification settings. I created an App Password in Gmail and my Test in settings was succesful. Not sure how to test it otherwise to see if it resolves the issue I describe above. I guess I'll wait till the next Parity Check nest month.

@itimpi may be able to confirm.