"Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being destroyed because the -L option was used. - scan filesystem freespace and inode maps... clearing needsrepair flag and regenerating metadata sb_ifree 160, counted 108 sb_fdblocks 729008010, counted 730399085 - 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 imap claims a free inode 2238793491 is in use, correcting imap and clearing inode cleared inode 2238793491 - 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 entry "Backup_Error-24-09-2023_23-26-31.log" at block 0 offset 1152 in directory inode 2147483887 references free inode 2238793491 clearing inode number in entry at offset 1152... - agno = 3 clearing reflink flag on inodes when possible Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... bad hash table for directory inode 2147483887 (no data entry): rebuilding rebuilding directory inode 2147483887 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... Maximum metadata LSN (1:288358) is ahead of log (1:2). Format log to cycle 4. done"
Rebooted out of maintenance mode and drive seems to be up and running. No errors. This issue possibly due to a bad sata cable causing corruption?
Well, that seems to have done it. ETA is a more reasonable 9 hours, disk error are zero at the moment on both drives. Have included diags as requested just the same.
StephenCND's post in Drive is showing as "Unmountable: Unsupported or no drive system". was marked as the answer