slobert

Thanks for the tip. I've got some drives on the way. I'll clone it and set up parity.

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

Apologies. Won't happen again.

Hope you don't mind I piggyback on your thread - I'm having a similar issue. Trying to add a device to my array (also SAS drive), but I can't assign it to a disk and the mount button is grayed out in Unassigned Devices. I've successfully swapped and added devices to the array in the past leading me to believe there might be an issue with this drive (it's an ebay special). The 'Beelzebub emhttpd: device /dev/sdc has size zero' log entry repeats itself. I'm not sure which troubleshooting steps to take at this point and was hoping I could get some guidance. Thank you. beelzebub-diagnostics-20201124-2003.zip