cincura.net

I also tried today shuffling disks on SATA ports, just in case, but it provided zero difference.

I tried the ASM1164 HBA and sadly same behavior as with my original ASM1166. I'll start checking checksums for all the files to see whether there are some differences after reboot and possibly some data corruption. So far I'm operating on assumption it's really just wrong parity. Thinking what else can I test to understand this more. Also, wondering what's so special about sector 3519069768... Going bare metal or building different PC I take as a last resort (time and money consuming).

Hello, I'm running Unraid (6.12.6) as a VM in Proxmox (8.1), using PCIe passthrough for ASM1166 HBA (this to be precise) for my drives. Every time I reboot the physical machine (clean shutdown of Unraid VM) I have 2 parity errors at exactly the same location. kernel: md: recovery thread: P corrected, sector=3519069768 kernel: md: recovery thread: P corrected, sector=3519069800 Running non-correcting check after the correcting check the error does not come back. Only when I reboot the physical machine, the problem reoccurs (rebooting the VM itself is fine). In some forum threads mentioning same sectors I found that IOMMU might be causing the problem. Sadly I can't disable IOMMU, because I need it to passthrough the HBA. SMART (short) on all drives "Completed without error". Any ideas what I could try/test? Or set? I'm waiting for ASM1164 HBA (I'm fine with 4 SATA ports) to test, maybe it will work correctly??? I could probably get JMB585 HBA to test. Worth trying? Thanks. `lspci -nnk` shows: 06:00.0 SATA controller [0106]: ASMedia Technology Inc. ASM1166 Serial ATA Controller [1b21:1166] (rev 02) Subsystem: ZyDAS Technology Corp. ASM1166 Serial ATA Controller [2116:2116] Kernel driver in use: vfio-pci Kernel modules: ahci

I know that New Config basically "resets" the configuration for disks in Main and I can then do whatever change I need to do. But what else is reset by using this tool?