adolfotregosa

Well I give up. No matter what disks I choose I always get sync errors after a reboot. Same sectors coincidentally to what other people have had. May 2 11:15:54 unRaid kernel: md: recovery thread: P corrected, sector=3519069768 May 2 11:15:54 unRaid kernel: md: recovery thread: P corrected, sector=3519069800 I even took the risk and updated the asmedia 1166 firmware, no dice. If this is not an unraid issue and hardware is fine, I dunno what more to do. Is there anything else to do ?? Parity is fine until I reboot. I can stop and restart array, no issues, but if I restart sync errors appear.

ok, so far as testing goes, it seams that EVERY time AFTER reboot, no matter what disks are selected, I will get sync errors. The only sniping rust results came with 2 sync errors and they coincidentally are always the "same sectors", is this case: May 2 11:15:54 unRaid kernel: md: recovery thread: P corrected, sector=3519069768 May 2 11:15:54 unRaid kernel: md: recovery thread: P corrected, sector=3519069800 The parity drive seams to be fine, I think. I mean, if I don't reboot and keep checking parity it always comes with zero sync errors after they are "corrected". basically after every reboot I get sync errors. The "error sectors" are strangely coincident with what other people have gotten in the past. I dunno. Bug ? I am now in the process of doing ONLY the 2TB ssd with the 4TB parity hdd and just for my knowledge, Is it normal that the parity sync keeps going after the 2TB ssd is no more? Probably! But what is it syncing ? air ? So what now ?? lol help !

I have no idea why would they but… I’ll wait for instructions from the masters. I confirm the issue only comes back after a reboot. Write speed is not an issue because of cache. What I want to see is the moment the sync errors appear. In my case I’m wondering if it is at 50%, when the smaller 2Tb ssd stops doing parity.

Ok. I confirm that the sync errors were corrected. I stopped the array, started and re run parity check. Still zero errors. I then rebooted and the 5 errors came back. diagnostics 0750 has 2 parity checks, zero errors. I stopped the array between checks. Diagnostics 1252 is after reboot. 5 errors. What do I do now? unraid-diagnostics-20230503-0750.zip unraid-diagnostics-20230503-1252.zip

Yeah I know. I'm almost sure I did that yesterday, twice, but then I rebooted. It is currently doing another pass to see if they pop up. If they do not, I'll do another pass. If still nothing I'll reboot and then my gut say they are coming back. I'll report when it finishes all the steps.

Wait, I have 3 ssd and 1 nvme. What should I do? Keep only the spinning rust?

I'm currently double checking that. In the beginning I did saw parity check run after rebooting until I changed Shutdown time-out and VM shutdown time-out to a larger value, but I'm almost sure I already run 2 parity checks without rebooting and got the same 5 sync errors. Anyhow, if this parity check does not produce errors but they re-appear after reboot when the reboot seams to be clean, what can I do ? Does the parity check need to go all the way to the end to actually correct errors ?

Hello. I'm scratching my head over this one. Not marvell controller, build in asmedia 1166. It is a qnap ts-664 with 16Gb ram. I never ever got an error shown in the main tab, always zero errors but I always get 5 sync errors when doing the parity, always the same sectors, identical sectors to what has happen to other people around here in the past but they seam to be using marvell controllers at that time. May 2 11:15:54 unRaid kernel: md: recovery thread: P corrected, sector=3519069768 May 2 11:15:54 unRaid kernel: md: recovery thread: P corrected, sector=3519069776 May 2 11:15:54 unRaid kernel: md: recovery thread: P corrected, sector=3519069784 May 2 11:15:54 unRaid kernel: md: recovery thread: P corrected, sector=3519069792 May 2 11:15:54 unRaid kernel: md: recovery thread: P corrected, sector=3519069800 Basically I have no idea on how to fix this one. There is nothing to mess within the bios and messing around with tunable(s) is not fixing the issue. Any suggestions ?? Thank you so much. unraid-diagnostics-20230502-1129.zip

https://www.linux-kvm.org/images/0/06/2012-forum-Q35.pdf I had the idea q35 was here to replace the ancient i440fx, no PCIe chipset, etc