One share of three is broken.

[dwalt]

Hello,

I had my main share "movies" quit working. I was rebuilding after a bad drive . The files are still there but when I go to "shares - view". It shows 0 directories 0 files.

My other 2 shares are fine. The rebuild completed successfully. How do I get the share "movies" working again?

Diagnostic file attached.

Thanks

microserver_2-diagnostics-20191021-1213.zip

[Frank1940]

OK--  I am not the expert here but you have a problem with disk1.  The smart report contains this:

197 Current_Pending_Sector  -O---K   100   100   000    -    32

At the end of your syslog, you have this sequence:

Oct 21 06:12:57 Microserver-2 kernel: XFS (md1): Metadata corruption detected at xfs_buf_ioend+0x4c/0x95 [xfs], xfs_inode block 0x28086a0 xfs_inode_buf_verify
Oct 21 06:12:57 Microserver-2 kernel: XFS (md1): Unmount and run xfs_repair
Oct 21 06:12:57 Microserver-2 kernel: XFS (md1): First 128 bytes of corrupted metadata buffer:
Oct 21 06:12:57 Microserver-2 kernel: 00000000eeca6479: 6b 6a 58 48 97 ea 8b 55 cf eb 9b 63 3e 24 79 8a  kjXH...U...c>$y.
Oct 21 06:12:57 Microserver-2 kernel: 000000004b7e71b3: 9b e8 62 39 74 f8 17 9e 1d 3c b1 96 e5 de 08 1e  ..b9t....<......
Oct 21 06:12:57 Microserver-2 kernel: 00000000ad314cd8: 6f d8 ab 9c 06 2c 47 df 41 45 7e c5 3a c5 5f 9f  o....,G.AE~.:._.
Oct 21 06:12:57 Microserver-2 kernel: 00000000a4ba82c4: 35 f5 b2 2e a0 25 ef d5 b8 b8 00 a8 2e ee 20 fd  5....%........ .
Oct 21 06:12:57 Microserver-2 kernel: 00000000a5f95b7d: b7 3b 63 ac e6 2f 13 0a 18 f6 13 12 f3 c2 6a 94  .;c../........j.
Oct 21 06:12:57 Microserver-2 kernel: 00000000df4d4e17: 24 eb d6 71 24 69 ce 49 26 3d 25 90 35 08 ef d9  $..q$i.I&=%.5...
Oct 21 06:12:57 Microserver-2 kernel: 000000001ab77d72: 74 3d b8 a8 b7 10 4a d7 04 16 be 14 a6 dd b6 04  t=....J.........
Oct 21 06:12:57 Microserver-2 kernel: 0000000016182d63: fd 2b ad 26 a6 95 09 79 b1 71 33 09 a5 80 b3 53  .+.&...y.q3....S
Oct 21 06:12:57 Microserver-2 kernel: XFS (md1): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x28086a0 len 32 error 117
Oct 21 06:12:57 Microserver-2 kernel: XFS (md1): xfs_imap_to_bp: xfs_trans_read_buf() returned error -117.
Oct 21 06:12:57 Microserver-2 kernel: XFS (md1): Metadata corruption detected at xfs_buf_ioend+0x4c/0x95 [xfs], xfs_inode block 0x28086a0 xfs_inode_buf_verify
Oct 21 06:12:57 Microserver-2 kernel: XFS (md1): Unmount and run xfs_repair
Oct 21 06:12:57 Microserver-2 kernel: XFS (md1): First 128 bytes of corrupted metadata buffer:
Oct 21 06:12:57 Microserver-2 kernel: 000000009d7b12ee: 6b 6a 58 48 97 ea 8b 55 cf eb 9b 63 3e 24 79 8a  kjXH...U...c>$y.
Oct 21 06:12:57 Microserver-2 kernel: 0000000091b320c6: 9b e8 62 39 74 f8 17 9e 1d 3c b1 96 e5 de 08 1e  ..b9t....<......
Oct 21 06:12:57 Microserver-2 kernel: 000000005f0da756: 6f d8 ab 9c 06 2c 47 df 41 45 7e c5 3a c5 5f 9f  o....,G.AE~.:._.
Oct 21 06:12:57 Microserver-2 kernel: 000000009d6419f8: 35 f5 b2 2e a0 25 ef d5 b8 b8 00 a8 2e ee 20 fd  5....%........ .
Oct 21 06:12:57 Microserver-2 kernel: 0000000033280e66: b7 3b 63 ac e6 2f 13 0a 18 f6 13 12 f3 c2 6a 94  .;c../........j.
Oct 21 06:12:57 Microserver-2 kernel: 00000000ae35a76a: 24 eb d6 71 24 69 ce 49 26 3d 25 90 35 08 ef d9  $..q$i.I&=%.5...
Oct 21 06:12:57 Microserver-2 kernel: 0000000036f37b3e: 74 3d b8 a8 b7 10 4a d7 04 16 be 14 a6 dd b6 04  t=....J.........
Oct 21 06:12:57 Microserver-2 kernel: 00000000de39521c: fd 2b ad 26 a6 95 09 79 b1 71 33 09 a5 80 b3 53  .+.&...y.q3....S
Oct 21 06:12:57 Microserver-2 kernel: XFS (md1): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x28086a0 len 32 error 117
Oct 21 06:12:57 Microserver-2 kernel: XFS (md1): xfs_imap_to_bp: xfs_trans_read_buf() returned error -117.

Hopefully @johnnie.black (Who is a real Guru in this area) can tell you what the problem is and give guidance. 

 

You might provide a bit more information about what your earlier problem and which disk was replaced.

Edited October 21, 2019 by Frank1940

[JorgeB]

Replace disk1 then run a filesystem check.

[dwalt]

Thanks for the advice. Data rebuild has started. Will finish in 4 days 5 hours.

[itimpi]

6 hours ago, dwalt said:

Thanks for the advice. Data rebuild has started. Will finish in 4 days 5 hours.

That sounds too long.     I would expect something in the range of 2-3 hours per TB.     It might be worth posting your current diagnostics.

[dwalt]

The rebuild completed with no errors. I ran the file system check which found and corrected a number of errors.

My "movies" share is back on line. Thanks for the help.