January 2, 20251 yr Hello, I've been troubleshooting array issues where drives become disabled. Adjusting spindown time seemed to solve the problem, but it has come back. The parity drive is disabled with many errors, the array won't stop, and rebooting from the CLI won't work. I've checked the cables, but I will check again—attached diagnostics. tower-diagnostics-20250102-0933.zip
January 2, 20251 yr Community Expert Solution Two disks dropped offline at the same time: Jan 2 09:00:41 Tower kernel: md: disk0 read error, sector=13704464880 Jan 2 09:00:41 Tower kernel: md: disk0 read error, sector=13704464888 Jan 2 09:00:42 Tower kernel: md: disk1 read error, sector=13704464888 Jan 2 09:00:42 Tower kernel: md: disk1 read error, sector=13704464896 This suggests a power/connection issue, see if they share something like a power splitter.
January 2, 20251 yr Author Thank you. There is indeed a power splitter for those two drives. I've reseated it and will look into replacing it. I am currently rebuilding the array.
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.