svargas

A couple questions: It did pass the full smart-test and the parity check completed with zero errors, so does that show data on the array is good and not corrupt? Would there be any benefit to run another parity check tonight with write corrections to parity unchecked? Also the dashboard is still showing the parity drive unhealthy. I will order another parity drive to have on hand, I have stop Plex and moved Emby to another server. This is only running a VM, so that I can hold off until next month. Once I get the new parity drive, would running Dynamix File Integrity, show any file corruption on the disks before writing the data to a new parity drive. If I remember you have check a box, saying something about knowing the data is good in order to replace a parity drive... Thanks again for the help and any advice, you have so that I don't pass on corruption to the new drive.... SV

Here is a full smart-test, with diags.... Thanks for the support SV lego90-smart-20240320-0922.zip lego90-diagnostics-20240319-2053.zip

One of my server's which has parity check before, with no errors, Last night I kick off a parity check last night with 0 sync errors reported. But the GUI reported smart error on the parity drive showing 6103 errors. I ran Fix Common Problems plugin for logs, but did report any problems. I stopped the array and ran smart-test report on the parity drive and it passed. I have seen sync errors the data drives in the past and if the number increases I would just replace the drive. I never seen errors on the parity. When restarted the array 6103 errors zeroed. Since error number never increase in the last 5 hours of the parity check could this point to a drive in the array going bad or just the parity drive going bad and needs to be replaced. If someone could provide next steps to keep my data safe Thanks SV lego90-smart-20240319-1011.zip

The card has been flashed IT mode and in use in couple of systems I am replacing the motherboard because a newer MSI Z590 tomhawk fell into my hands. I have tried many different bios combinations to the point of lucking my self out. I had to clear the cmos to get back in. I called MSI for support and was told that it was to technical and needed to submit a ticket. The response was to install windows which has nothing to due with it not posting up and not show up in the bios. In booting with Unraid it is not listed in system devices under tools. Since I don't think I will get an answer from MSI. I thought maybe someone mite have seen this issue too Thanks for advice SV

The problem is I got notification that it finished and was complete. I did reboot the server per your suggestion yesterday and kick off another parity syn this time it did complete as it should of and my data is protected. If this is some glitch would happens when I run monthly parity syn's will I need to run it twice too. Thanks for taking the time to review my logs....

Here you go... In my archive norification msg Notice [LEGO99] - Parity-Sync finished (0 errors) this morning Thanks for the help lego99-diagnostics-20230426-1307.zip

Hello I just had this problem on a new server build after copying data over to new server. I started parity syn late yesterday an it finished per the logs, but the syn was all so canceled. So unraid wants to rerun parity syn. If the fix is just rebooting the server and rerun parity syn, I guess I will try that for tonight, but the question remains why is this happening is this a bug with 6.11.5?