March 23, 20215 yr Community Expert Looks more like a connection/power problem, replace both cables on that disk and try again.
March 23, 20215 yr Author 3 minutes ago, JorgeB said: Looks more like a connection/power problem, replace both cables on that disk and try again. okay will try that but now my server is spamming these errors in syslog. Mar 23 14:54:21 Unraid nginx: 2021/03/23 14:54:21 [alert] 7015#7015: worker process 4716 exited on signal 6 Mar 23 14:54:22 Unraid nginx: 2021/03/23 14:54:22 [alert] 7015#7015: worker process 4768 exited on signal 6 Mar 23 14:54:23 Unraid nginx: 2021/03/23 14:54:23 [alert] 7015#7015: worker process 4822 exited on signal 6 Mar 23 14:54:24 Unraid nginx: 2021/03/23 14:54:24 [alert] 7015#7015: worker process 4951 exited on signal 6 Mar 23 14:54:25 Unraid nginx: 2021/03/23 14:54:25 [alert] 7015#7015: worker process 5038 exited on signal 6 Mar 23 14:54:26 Unraid nginx: 2021/03/23 14:54:26 [alert] 7015#7015: worker process 5091 exited on signal 6 Mar 23 14:54:27 Unraid nginx: 2021/03/23 14:54:27 [alert] 7015#7015: worker process 5141 exited on signal 6 Mar 23 14:54:28 Unraid nginx: 2021/03/23 14:54:28 [alert] 7015#7015: worker process 5192 exited on signal 6 Mar 23 14:54:29 Unraid nginx: 2021/03/23 14:54:29 [alert] 7015#7015: worker process 5235 exited on signal 6 Mar 23 14:54:30 Unraid nginx: 2021/03/23 14:54:30 [alert] 7015#7015: worker process 5278 exited on signal 6 Mar 23 14:54:31 Unraid nginx: 2021/03/23 14:54:31 [alert] 7015#7015: worker process 5329 exited on signal 6 Mar 23 14:54:32 Unraid nginx: 2021/03/23 14:54:32 [alert] 7015#7015: worker process 5373 exited on signal 6
March 23, 20215 yr Community Expert Rebooting should fix that, make sure you don't have multiple browser windows open on the GUI.
March 23, 20215 yr Author 2 hours ago, JorgeB said: Looks more like a connection/power problem, replace both cables on that disk and try again. Looks like it was a bad sata power splitter cause now after connecting that drive directly it's been doing parity check for almost 2.5hours now and so far none of those errors have come up. Although it is already showing more than 20k sync errors. Should run I parity check with correction once and if it finishes without those errors??
March 23, 20215 yr Community Expert Sync errors are expected because of the previous data corruption, if the ATA errors were solved you should run a correcting check.
Archived
This topic is now archived and is closed to further replies.