What happened:

• My parity drive (ST10000VN0008) was suddenly disabled by Unraid.

• No recent power outages or system reboots occurred.

• The drive is still visible in the Main tab, but marked as disabled from the array.

What I’ve tried so far:

• Checked all power and SATA cables — everything is securely connected.

• No unusual mechanical sounds from the drive.

• SMART short test passed; extended SMART test currently in progress.

Questions:

1. Is it safe to trust this drive and re-enable it?

2. What might the system logs reveal about why it was disabled?

3. If I remove and reassign the same disk as parity, will Unraid automatically start a rebuild?

Update:
After re-enabling the parity drive and starting a parity check, the system completely freezes during the process — I lose access to the web UI and SSH.
Only a full reboot restores functionality, but the parity check never finishes.

Could this indicate a failing drive, a bad SATA controller/port, or something else?
The system runs fine otherwise, as long as the parity check is not running.

Thanks in advance for your help!

nasmiguel-smart-20250720-1830.zip

Update #2:

I have already tried swapping both:

- The SATA cable (new one)

- The port: previously connected to an LSI SAS HBA, now moved directly to motherboard SATA

After doing this, the parity drive (ST10000VN0008) is still being disabled or causing system lockups when I attempt a parity check.

SMART shows no reallocated, pending, or uncorrectable sectors.

But I do see 955 UDMA CRC errors, likely from before replacing the cable.

The drive has 18,420 power-on hours and passes both short and extended SMART tests.

Could this be a firmware issue with this model? Or is the disk just unstable under load despite a clean SMART report?

Thanks again for your help.

Enable the syslog server and post that after a crash, together with the full diagnostics.

Hi,
After replacing the power cable and leaving the server powered off for a few hours, I attempted the parity sync again — and surprisingly, everything started working properly again. No crashes so far.
The sync is currently running and progressing without issues.
Is there any way I can stress-test or further verify this parity disk?
It passed an extended SMART test (smartctl -t long) without any errors, but since it's almost out of warranty, I want to be 100% sure before it expires.
Should I run additional stress tools (like badblocks, fio, or anything else) to validate long-term reliability?

Thanks in advance!

15 minutes ago, migasrt3 said:

Is there any way I can stress-test or further verify this parity disk?

You can run a parity check after the sync is done, that will do a full surface read.

Thanks!

That makes sense I'll run a parity check as soon as the sync completes, to force a full surface read and confirm stability.

Since the SMART extended test already passed, if the parity check finishes cleanly as well, I’ll consider the disk stable though I’ll still keep an eye on it given it nearly got disabled before.

Appreciate the help!

Good morning, the parity check just finished and completed without any issues. Do we have any terminal commands available to run tests on the disk?

If the parity check completed without errors the disk should be OK, you can also run an extended SMART test, but it's somewhat redundant. I would just keep monitoring for a week or so, and then run another parity check.

I'll keep an eye on it. Could it be temperature-related? It's been very hot around here lately.

What is the max temp the drive is reaching?

that I have seen at most 37 degrees

That's not hot at all. I like to keep them under 45C, but even 50C is typically not a problem.