Missing data in Shares after replacing a bad drive

[ani3114]

I have an array of 8 disks (1 parity). One of my disk (disk 2) started getting read errors so went ahead and replaced it following the steps. The disk was rebuilt from parity drive, but my Shares got messed up after the replacement.

When I go to individual disks using /mnt/diskx/Movies/English/All, I am able to see the folders and data but when I try to access the same from shares /mnt/user/Movies/English/All, I get an error (/bin/ls: reading directory '.': Structure needs cleaning).

This issue is impacting my Plex docker as it reads data from Shares.

 

In the logs, I see metadata corruption error as below

 

Apr 19 17:35:38 Tower kernel: XFS (md2): metadata I/O error in "xfs_imap_to_bp+0x5c/0xa2 [xfs]" at daddr 0x4a6c16a0 len 32 error 117
Apr 19 17:35:39 Tower kernel: XFS (md2): Metadata corruption detected at xfs_buf_ioend+0x51/0x284 [xfs], xfs_inode block 0x4a6c16a0 xfs_inode_buf_verify
Apr 19 17:35:39 Tower kernel: XFS (md2): Unmount and run xfs_repair
Apr 19 17:35:39 Tower kernel: XFS (md2): First 128 bytes of corrupted metadata buffer:
Apr 19 17:35:39 Tower kernel: 00000000: a1 31 c6 76 04 f5 41 c0 c7 76 8c ff 92 8f b1 b6 .1.v..A..v......
Apr 19 17:35:39 Tower kernel: 00000010: 0b 9b e6 6d 91 77 63 11 ff ff fd f6 61 46 fb ca ...m.wc.....aF..
Apr 19 17:35:39 Tower kernel: 00000020: 01 5d cc 88 b3 e6 ee 68 65 0b e6 4b b8 f1 b6 37 .].....he..K...7
Apr 19 17:35:39 Tower kernel: 00000030: 2a 48 7a fb ba cb 8a 43 78 58 64 43 22 12 00 8b *Hz....CxXdC"...
Apr 19 17:35:39 Tower kernel: 00000040: 78 03 8f bc 21 21 50 5f 4a 76 de 82 01 b3 4e eb x...!!P_Jv....N.
Apr 19 17:35:39 Tower kernel: 00000050: d2 4c 30 df 1b f8 83 ff 2f fb 4e 6f c0 8d b2 48 .L0...../.No...H
Apr 19 17:35:39 Tower kernel: 00000060: 44 80 0a 4d c8 28 70 ab e1 82 f1 bb 2c 52 50 b2 D..M.(p.....,RP.
Apr 19 17:35:39 Tower kernel: 00000070: e3 72 fb 9b 5f 21 d2 c5 92 09 c8 46 4e 36 c3 fd .r.._!.....FN6..

 

I am not able to figure out if this is an issue with yet another disk failure or something went wrong with the earlier replacement procedure. Attaching the diagnostic logs.

tower-diagnostics-20220413-2000.zip

[ChatNoir]

As stated in the log extract, you should check filesystem for disk 2.

[ani3114]

Ran the check file systems. Attached output, what should be done next.

unraidcheckfs.txt

[JorgeB]

Run it again without -n or nothing will be done, if it asks for -L use it.