Very Slow Parity Sync

[Krevos]

Hi guys, I moved my Unraid disks + USB to new hardware today. All previous disks were recognized and can be used again. Disk 1 has several errors but that's not too bad.
Now when I start the parity sync it has really very long - over 3000 days and I can't explain why.
The disk was previously running as a parity disc for about 1 year without any problems, attached is the screenshot from today, almost 6 months without any incidents.
I thawed the Sata connector with a working disk, the power connector too, but this didn't help. I connected it to the additional Sata card with the same result as on the mainboard.
Attached are my diagnostics, thank you very much for your help.

 

[Krevos]

tower-diagnostics-20231214-2345_before_newconifg.zip

[trurl]

Looks like disk1 has disconnected. It won't be disabled because parity isn't valid yet.

 

Check cables, both ends, SATA and power, including splitters.

 

Then post new diagnostics so we can see if we can get a complete SMART report from disk1.

 

Did you know that SSDs in the parity array cannot be trimmed?

[Krevos]

Disk1 - 6TBHDD isnt the Problem, The Problem is the Parity Disk....
I checked all the Cables and Switched theme in all ways nothing that Works fine.
I dont get it yesterday the Parity was normal working and on dec 1 there was the last Parity check made without a problem..
I do a new diagnostics and post the Result

[Krevos]

tower-diagnostics-20231215-1105.zip

[itimpi]

According to your diagnostics disk1 is the problem as it appears to have dropped offline.

 

The parity disk has 1 reallocated sector which is not a problem but is unusual in a new disk so worth keeping an eye on that.

[Krevos]

Thanks itimpi, i took out the disk1 and now its working fine.
How does the Disk1 affect the parity check? I dont get it
Now its on the normal time.... over 1 Day but thats normal

[itimpi]

If you physically removed the disk then Unraid should be emulating it using the parity drive.     Since have single-parity then it should be running a read-check rather than a proper parity check to make sure all other drives can be read correctly.  However that will mean you are currently unprotected against another drive having issues.

 

Assuming the contents of the emulated disk1 look OK, then when it is replaced that content will be what is rebuilt onto the replacement.

[trurl]

Assuming you didn't reset the array configuration (New Config), then it can't be doing a parity check without disk1. According to both of the diagnostics you posted, parity wasn't valid anyway, I assumed because you hadn't built parity yet.

 

Your first post said "parity sync" not parity check, which would mean you were trying to build parity, and diagnostics seems to agree with that.

 

But now you say you are doing a parity check without disk1, which wouldn't be possible. And it seems parity hadn't been built yet anyway. Maybe it is doing a read check as itimpi mentioned.

 

Was parity built? Can you clarify things any?

 

Post new diagnostics and a screenshot of Main - Array Devices.

[trurl]

3 hours ago, itimpi said:

Assuming the contents of the emulated disk1 look OK, then when it is replaced that content will be what is rebuilt onto the replacement.

According to your diagnostics, disk1 is unmountable. And it is not disabled, so it can't be the emulated disk1. And it can't emulate disk1 with parity invalid.

 

34 minutes ago, trurl said:

Post new diagnostics and a screenshot of Main - Array Devices.

Also, a screenshot of Main - Array Operation.