November 16, 20223 yr I have a disk on the array that is unmountable and has read errors. Is it toast? Version: 6.11.3 xfs repair status: Phase 1 - find and verify superblock... superblock read failed, offset 0, size 524288, ag 0, rval -1 fatal error -- Input/output error recent disk log entries in the red: Nov 16 11:08:21 Beelzebub kernel: I/O error, dev sdg, sector 196 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 0 Nov 16 11:08:21 Beelzebub kernel: Buffer I/O error on dev sdg1, logical block 132, async page read Nov 16 11:08:21 Beelzebub kernel: Buffer I/O error on dev sdg1, logical block 133, async page read Nov 16 11:08:21 Beelzebub kernel: Buffer I/O error on dev sdg1, logical block 134, async page read Nov 16 11:08:21 Beelzebub kernel: Buffer I/O error on dev sdg1, logical block 135, async page read beelzebub-diagnostics-20221116-1103.zip
November 16, 20223 yr Community Expert Solution Disk does appear to be failing, xfs_repair cannot repair a disk that returns a read error, hence the input/output error, since there's no parity best bet is to clone it with ddrescue then run xfs_repair.
November 16, 20223 yr Author Thanks for the tip. I've got some drives on the way. I'll clone it and set up parity.
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.