You mean running xfs_repair on /dev/sdx1 correct? Unfortunately that was the most likely result but still worth a try, the strange part is that clearly there's an XFS filesystem on that disk:
Nov 30 20:35:46 Tower kernel: XFS (md3): Mounting V5 Filesystem
Nov 30 20:35:47 Tower kernel: XFS (md3): Metadata CRC error detected at xfs_inobt_read_verify+0x12/0x5a [xfs], xfs_inobt block 0x18
Nov 30 20:35:47 Tower kernel: XFS (md3): Unmount and run xfs_repair
Nov 30 20:35:47 Tower kernel: XFS (md3): First 128 bytes of corrupted metadata buffer:
Nov 30 20:35:47 Tower kernel: 00000000: 11 00 04 7f 00 00 00 fc 57 de 24 68 e1 01 a6 03 ........W.$h....
Nov 30 20:35:47 Tower kernel: 00000010: 80 45 1a e6 46 a0 a4 53 00 00 00 01 00 0a 40 9d .E..F..S......@.
Nov 30 20:35:47 Tower kernel: 00000020: f0 ac fe df 81 ba bd 46 8d 48 33 94 94 df 43 5d .......F.H3...C]
Nov 30 20:35:47 Tower kernel: 00000030: 00 00 00 0b d3 5d 74 2d ff ff ff 7f ff ff bf ff .....]t-........
Nov 30 20:35:47 Tower kernel: 00000040: ff ff ff ff ff ff ff ff ff ff fa 7f ff ff bf ff ................
Nov 30 20:35:47 Tower kernel: 00000050: ff ff ff ff ff ff ff ff ff ff fa 3f ff ff bf ff ...........?....
Nov 30 20:35:47 Tower kernel: 00000060: ff ff ff ff ff ff ff ff ff ff f9 ff ff ff bf ff ................
Nov 30 20:35:47 Tower kernel: 00000070: ff ff ff ff ff ff ff ff ff ff f0 bf ff ff bf ff ................
Nov 30 20:35:47 Tower kernel: XFS (md3): metadata I/O error in "xfs_btree_read_buf_block.constprop.0+0x7a/0xc7 [xfs]" at daddr 0x18 len 8 error 74
Nov 30 20:35:47 Tower kernel: XFS (md3): Failed to read root inode 0x80, error 117
Nov 30 20:35:47 Tower root: mount: /mnt/disk3: mount(2) system call failed: Structure needs cleaning.
But it's not the first time this happens, I guess it might depend on what's damaged or the kind of damage, UFS explorer is probably the best bet to try and recover some data, other option would be contacting the XFS mailing list to see if they can revive the fs.