Kevin Mychal M. Ong

Yeah, it did refuse to sync when the drive totally failed. However, my other programs still had access to the other drives. So those programs (Bazarr specifically) updated some SRT files which put the state of my array into the issue you are describing (did I understand correctly?). This went on for around 3 to 4 days before I finally replaced the drive and tried recovering the files. Synology is software RAID. SHR-1 is simply RAID5 in the background but with minor improvements. What I don't understand...

Ok, I think I got it now. What you just explained is definitely the cause of my issue because there were a lot of SRT's that were replaced during the time the drive is in a failed state for 3 days. That sucks. Is there a way to tell the mergerFS/Snapraid combo to immediately (and automatically) stop any access to the array when a single drive fails? In all honesty then, is RAID better than SnapRAID? I had multiple instances of a single drive failure on my Synology NAS (13 drives on SHR-1) and was...

FWIW, these are the order of events: 7/21/2022 @ 4:53 PM - one drive (d3) started getting CurrentPendingSector SMART errors but I just let them be (I know, my bad) 8/17/2022 @ 5:00 AM - last successful Snapraid runner run (touch, diff, sync, scrub, in that order) 8/18 @ 3:35 AM - the same drive got a FailedHealthCheck error when running SMART 8/18 @ 5:00 AM - 8/21 @ 5:00 AM - all daily Snapraid runner runs fail because it's having a hard time reading the failed drive already 8/21 night time - I finally...

I kind of understand what you're saying but not 100%. In your example, for the files that got deleted from disks 1 and 3 and lost disk4 before a sync happens, are those files used by the parity drive in trying to recover the actual files in disk 4 even though they aren't technically the same file? When you say "continually rebuild the files" manually, what do you mean? As in I get a copy from backup and just copy that file over to the new drive? With two parity drives, is this still a problem?

Delete

FWIW, these are the order of events: 7/21/2022 @ 4:53 PM - one drive (d3) started getting CurrentPendingSector SMART errors but I just let them be (I know, my bad) 8/17/2022 @ 5:00 AM - last successful Snapraid runner run (touch, diff, sync, scrub, in that order) 8/18 @ 3:35 AM - the same drive got a FailedHealthCheck error when running SMART 8/18 @ 5:00 AM - 8/21 @ 5:00 AM - all daily Snapraid runner runs fail because it's having a hard time reading the failed drive already 8/21 night time - I finally...

@amadvance do you have any ideas here? The last August 17 run of Snapraid was a success so not sure what's happening here.

Here's the complete fix.log: https://1drv.ms/u/s!AhDXcRksNyfes3HwSuF25vUjEvEO?e=rA768q