JWHIII

I rebooted again and it worked this time. Thanks

Is this correct? It seems to cause a no boot on my server. Thanks

Thanks tower-smart-20231004-0718.zip

Hello, I recently updated my server to 6.12.4 and after the reboot I noticed the one of my array disks was disabled. I looked at SMART test and found no errors. Ran a new SMART test and found no errors. Looked at the Disk Log info and found this. Oct 3 20:28:23 Tower kernel: ata6.00: exception Emask 0x0 SAct 0xc00 SErr 0x0 action 0x0 Oct 3 20:28:23 Tower kernel: ata6.00: irq_stat 0x40000008 Oct 3 20:28:23 Tower kernel: ata6.00: failed command: READ FPDMA QUEUED Oct 3 20:28:23 Tower kernel: ata6.00: cmd 60/78:50:88:00:00/00:00:00:00:00/40 tag 10 ncq dma 61440 in Oct 3 20:28:23 Tower kernel: ata6.00: status: { DRDY ERR } Oct 3 20:28:23 Tower kernel: ata6.00: error: { UNC } Oct 3 20:28:23 Tower kernel: ata6.00: configured for UDMA/133 Oct 3 20:28:23 Tower kernel: sd 6:0:0:0: [sdg] tag#10 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s Oct 3 20:28:23 Tower kernel: sd 6:0:0:0: [sdg] tag#10 Sense Key : 0x3 [current] Oct 3 20:28:23 Tower kernel: sd 6:0:0:0: [sdg] tag#10 ASC=0x11 ASCQ=0x4 Oct 3 20:28:23 Tower kernel: sd 6:0:0:0: [sdg] tag#10 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 88 00 00 00 78 00 00 Oct 3 20:28:23 Tower kernel: I/O error, dev sdg, sector 216 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 Oct 3 20:28:23 Tower kernel: ata6: EH complete Found the "Repairing a File System" section of the user manual. Disk is mountable. Parity is good. Put the array in maintenance mode and ran XFS check filesystem. Here is the output. Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 2 - agno = 3 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... done Finally, here are diagnostic files Thanks for any help tower-diagnostics-20231003-2128.zip

I have two disk shares that are accessed by two devices using NFS. The spamming is so bad I can't see anything else in my logs. Is there still no fix for this?