February 10, 20242 yr Hello, For a few weeks I've been seeing errors scatter across all disks in my server. These errors occur across all backplanes, cables, ports. They've reappeared following new configs, component replacements, etc. If a new config is applied and no parity device declared, it seems that all disks will hum along without issue. However when a parity action is began, whether sync/rebuild/read, it is inevitable that before long a disk will encounter errors. And then another, and another, until the system pauses that parity action or I intervene to cancel it. Until today when I installed an all new CPU _and_ motherboard. Kicked off a parity sync, and, again, errors begin appearing on every disk. I've replaced: - Controller - RAM - Motherboard - CPU I've attached diagnostics captured immediately after cancelling that parity sync. box-diagnostics-20240209-2006.zip
February 10, 20242 yr Community Expert Some problem with the way your parity is partitioned or something like that. RAID controllers are not recommended for many reasons, maybe this is one of them. You will probably have to wait several hours for @JorgeB It's after 1am in that time zone.
February 10, 20242 yr Community Expert Solution It's a Linux kernel issue with that controller's driver, it should be fine if you downgrade to v6.12.4, or wait for 6.12.7, which should be out next week.
February 11, 20242 yr Author Thank you for that information. As this array has been without parity for some time now while I chased these errors, I opted for the downgrade to v6.12.4. Parity sync is now at 76.7% without encountering a single error.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.