Saturday at 08:48 AM2 days Upgraded from C246 to B760. Enabled all ASPM settings, upgraded the ASM firmware to the intel one for later chipsets from silverstone.Since then, after a while, usually in the middle of the night, I had 4 out of 5 drives connected to it refuse to spin up with errors listed.I changed the asm card for a different one, and now one drive has got the same errors and shutdown.Some data from the log below"[Sat Aug 8 04:30:12 2026] md: disk5 read error, sector=12943531216[Sat Aug 8 04:30:12 2026] unraidd5: attempt to access beyond end of devicesdi: rw=0, sector=12943531288, nr_sectors = 8 limit=0[Sat Aug 8 04:30:12 2026] md: disk5 read error, sector=12943531224[Sat Aug 8 04:30:12 2026] unraidd5: attempt to access beyond end of devicesdi: rw=0, sector=12943531296, nr_sectors = 8 limit=0[Sat Aug 8 04:30:12 2026] md: disk5 read error, sector=12943531232[Sat Aug 8 04:30:12 2026] unraidd5: attempt to access beyond end of devicesdi: rw=0, sector=12943531304, nr_sectors = 8 limit=0[Sat Aug 8 04:30:12 2026] md: disk5 read error, sector=12943531240[Sat Aug 8 04:30:12 2026] XFS (md5p1): metadata I/O error in "xfs_imap_to_bp+0x60/0xd0" at daddr 0x3037e9cd0 len 32 error 5[Sat Aug 8 04:30:12 2026] XFS (md5p1): metadata I/O error in "xfs_imap_to_bp+0x60/0xd0" at daddr 0x3037e9cd0 len 32 error 5[Sat Aug 8 04:30:12 2026] XFS (md5p1): metadata I/O error in "xfs_imap_to_bp+0x60/0xd0" at daddr 0x3037e9cd0 len 32 error 5[Sat Aug 8 04:30:12 2026] unraidd5: attempt to access beyond end of devicesdi: rw=0, sector=8589934784, nr_sectors = 8 limit=0[Sat Aug 8 04:30:12 2026] md: disk5 read error, sector=8589934720[Sat Aug 8 04:30:12 2026] unraidd5: attempt to access beyond end of devicesdi: rw=0, sector=8589934792, nr_sectors = 8 limit=0[Sat Aug 8 04:30:12 2026] md: disk5 read error, sector=8589934728[Sat Aug 8 04:30:12 2026] unraidd5: attempt to access beyond end of devicesdi: rw=0, sector=8589934800, nr_sectors = 8 limit=0[Sat Aug 8 04:30:12 2026] md: disk5 read error, sector=8589934736[Sat Aug 8 04:30:12 2026] unraidd5: attempt to access beyond end of devicesdi: rw=0, sector=8589934808, nr_sectors = 8 limit=0[Sat Aug 8 04:30:12 2026] md: disk5 read error, sector=8589934744[Sat Aug 8 04:30:12 2026] XFS (md5p1): metadata I/O error in "xfs_imap_to_bp+0x60/0xd0" at daddr 0x200000080 len 32 error 5[Sat Aug 8 04:30:12 2026] XFS (md5p1): metadata I/O error in "xfs_imap_to_bp+0x60/0xd0" at daddr 0x200000080 len 32 error 5[Sat Aug 8 04:30:12 2026] XFS (md5p1): metadata I/O error in "xfs_imap_to_bp+0x60/0xd0" at daddr 0x200000080 len 32 error 5"
Saturday at 11:34 AM1 day Author Did a memtest as the first CPU was faulty and had MCE storm errors. RAM is new 32gb DDR4 3200, passed fine.tower-diagnostics-20260808-1232.zip
Yesterday at 08:49 AM1 day Disk5 dropped offline:Aug 8 02:17:25 Tower kernel: ata13: SATA link down (SStatus 0 SControl 310)Aug 8 02:17:25 Tower kernel: ata13.00: disable deviceThis is typically a power/connection issue.
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.