anonymous3759

You are correct, that was the issue. For some reason I had created a folder named "cache" in "/mnt/user". Cleaning that up resolved the error. Thanks.

The "Fix Common Problems" plugin recently started reporting the error "Share cache is identically named to a disk share". I did in fact make the mistake of naming one of the devices in my Cache pool "Cache" back when I built it years ago (the other disk is "Cache 2"). 1. Is this in fact an issue I should be concerned about or should I just tell the plugin to ignore the error? 2. If it is an issue, is there an easy way to rename the device or do I need to remove the device from the pool, rename it, and rebuild? Thanks!

To close the loop on this, running another parity check does now report 0 errors corrected. Somehow I must have interrupted the first parity build when I added the parity drive. Thanks folks.

Understood, I was going to let this check finish first then re-run it (it was paused by the Parity Check Tuning plugin). The parity check is destroying performance to the point where copying files to the share fails and Plex is buffering, so that will be the next issue I tackle after I get the parity checks reporting zero errors.

Will do. Thanks.

No, actually I learned about that plugin after the initial setup. The process I used BTW was to set up the array without the parity drive, transferred my data (about 8TB or so), then added the parity drive. Hold on, I might have totally lied when I said I didn't change anything about the assignments after that first parity check. I may have build the system with 2x 6TB, copied my data, added the parity drive, then added the 2x 6TB a day or so after. There was a lot of shuffling of drives between systems.

Yes, the initial parity build appears to have gone fine. No changes have been made to the disk assignments since then AFAIK. Diagnostics attached. Thanks. calculon-diagnostics-20200502-1352.zip

I am a new user of Unraid, and just set my array up one month ago (4x6 TB drives + 1 10 TB parity drive). My first monthly scheduled parity check kicked off, and it is reporting millions of sync errors corrected (see attached screenshot). I assume this is not normal. I am using the "Parity Check Tuning" plugin in order to only run the parity check at night, and it is only its second night. All drives pass a short SMART check. Is it possible I did something wrong when I set up the array?