mdumont1

Yes, I'm just letting the parity2 build complete since there's no point stopping it until I know it will be bad. There's about 8 hours left on the parity2 build/sync, with only the data past 8TB left to construct. If there's no reason not to trust the parity2 sync currently running then I'll rebuild disk3 on the old parity drive and then test the disabled disk3 to see if it was just a connection issue. Thanks.

The new parity2 drive is shucked from a WD easystore. The old parity2 was place in the easystore enclosure and connected to the system via USB3. My plan was to preclear that drive before adding it back to the array since it previously had errors. The SMART report for the old parity2 is available in the previously attached diagnostics zip under the WD_easystore name. I have attached it directly for convenience. WD_easystore_264D_5A38343051325A34-0-0-20210327-1824 (sdo).txt

Attaching diagnostics zip. The syslog attached to the original post is from this zip file. The system has not been rebooted yet since the drive failure. tower-diagnostics-20210327-1824.zip

The other day I replaced my parity2 drive with a new 14TB drive. During the parity-sync process one of my data drives had write errors and was disabled. The disabled drive is 8TB and the parity1 drive is 8TB. The parity-sync process was less than 8TB in when the drive failed. From what I can tell in the syslog the failure occurred during the nightly mover process. I'm looking for some guidance an the best way to rebuild the failed drive and not lose any data. Some questions: 1. The parity-sync continued after the drive failed and is ongoing. Since the parity1 drive was valid just before the swap of parity2 I'm assuming the disk that is disabled is being emulated to construct parity2. Is this assumption correct? Can I trust this parity-sync? 2. If the parity-sync result can be trusted, Is a reasonable process to get back to a good state to take the old parity2 drive and rebuild the disabled disk on it? syslog.txt

I have this 1TB Seagate Drive. I backed up my data and some of it was corrupt already so I lost some of it and then ran the preclear script to see if the drive is failing. I ran it the first time and there seems to be some strange numbers. I'm a little concerned about the "a change of -509 in the number of sectors pending re-allocation". I have attached the results from the first run After getting all of this not so happy result I decided to run the script again but this time with 3 cycles. I have attached the results from the second run. I'm not quite sure how to understand these results. It seems like the drive is continuously having a different amounts of sectors pending reallocation yet it always ends with During the preclear there were read errors that were displayed in syslog. Also, this drive was previously being used in a cheap external enclosure before being moved to my unRaid box. Is this drive failling? Should I replace it? If so how can I tell based on the preclear results? Thanks Seagate-preclear-2ndRun.txt Seagate-preclear-1stRun.txt