Hey, a few weeks ago one of my data drives was faulty. I replaced it and rebuild parity.

Now the parity drive is disabled, it's relatively new about 2,5 years old.Extended Smart test was okay. I switched power and SATA cable, still disabled. Can someone take a look at the log files?

Thank you server-smart-20260312-1006.zip

server-diagnostics-20260312-1808.zip

The syslog in the diagnostics indicates that you have file system corruption on disk2. You would need to run check filesystem to correct this.

The syslog in the diagnostics is the RAM copy and only shows what happened since the reboot so we cannot see why parity was disabled.   It could be worth enabling the syslog server to get a log that survives a reboot so we can see what happened prior to the reboot in the future. The mirror to flash option is the easiest to set up, but if you are worried about excessive wear on the flash drive you can put your server’s address into the Remote Server field.

The SMART information does not show any issues with the parity drive. Other issues such as cabling (power or SATA) are far more common than dtive isdues so check that again. it may be worth trying to rebuild the parity drive again to get it enabled. If the drive is disabled again then with the syslog server enabled we may get a better indication of why.

25 minutes ago, itimpi said:

you have file system corruption on disk2

@anny587

You didn't mention that disk2 was unmountable. That is more serious than disabled parity because it means none of the files that were on disk2 are currently accessible. As mentioned, check filesystem on disk2, from the webUI, and post the output.

1 hour ago, anny587 said:

one of my data drives was faulty. I replaced it and rebuild parity.

You mean you rebuilt the data disk from parity.

Was it disk2 that you rebuilt at that time? If so, was it actually mountable when you rebuilt it?

Yes it was disk 2 that is new, I rebuilt from parity.

I enabled the remote server syslog.

I started the array in maintenance mode and used check filesystem and was able to fix the file sytem error.

How would I go about rebuilding parity drive?

Stop the array select no disk? Start again and select the drive again?

5 minutes ago, anny587 said:

started the array in maintenance mode and used check filesystem and was able to fix the file sytem error.

Now start the array in normal (not maintenance) mode and post new diagnostics.

Here are the new diagnostics.

server-diagnostics-20260312-1956.zip

5 minutes ago, anny587 said:

How would I go about rebuilding parity drive?

Stop the array select no disk? Start again and select the drive again?

The process is the same for parity and data drives.

Missing a step as after unselecting the parity dtive you need to start the array (to make Unraid ‘forget’ the assignment), and then stop the array before assigning it again and starting the array to start rebuilding it.

9 minutes ago, anny587 said:

Stop the array select no disk? Start again and select the drive again?

As mentioned, you left out a step. It wouldn't actually let you reselect the drive while the array was started anyway.

Repair on disk2 looks good, no lost+found.

Restoring parity took some time, but so far everything is back to normal. Thank you very much for your help in this.