Hello!
I'm very new to unRAID and I like the experience thus far but I've hit a snag in my migration process. I have been using Proxmox for perhaps 5 years now and my disk space was running and thought I would try unRAID instead since RaidZ is a hassle with adding more drives.
So in the process of migrating data I'm transferring large amount of data over smb to three new Western Digital Red 8 TB drives, one in parity and two in the array, everything looks good and no SMART-errors are popping up. But after a while I'm getting this in log;
May 3 04:54:36 Tower kernel: XFS (md1): Metadata CRC error detected at xfs_dir3_block_read_verify+0x9c/0xa2 [xfs], xfs_dir3_block block 0x92c66aa8
May 3 04:54:36 Tower kernel: XFS (md1): Unmount and run xfs_repair
May 3 04:54:36 Tower kernel: XFS (md1): First 64 bytes of corrupted metadata buffer:
May 3 04:54:36 Tower kernel: ffff880231fd9000: 58 44 42 33 e5 ac fb 07 00 00 00 00 92 c6 6a a8 XDB3..........j.
May 3 04:54:36 Tower kernel: ffff880231fd9010: 00 00 00 01 00 06 5c 85 dc 12 b4 a6 45 ad 49 da ......\.....E.I.
May 3 04:54:36 Tower kernel: ffff880231fd9020: 97 73 80 02 67 0c 26 9f 00 00 00 00 92 c6 6b 36 .s..g.&.......k6
May 3 04:54:36 Tower kernel: ffff880231fd9030: 0a 70 04 00 00 60 00 20 00 98 00 20 00 00 00 00 .p...`. ... ....
May 3 04:54:36 Tower kernel: XFS (md1): Metadata CRC error detected at xfs_dir3_block_read_verify+0x9c/0xa2 [xfs], xfs_dir3_block block 0x92c66aa8
May 3 04:54:36 Tower kernel: XFS (md1): Unmount and run xfs_repair
May 3 04:54:36 Tower kernel: XFS (md1): First 64 bytes of corrupted metadata buffer:
May 3 04:54:36 Tower kernel: ffff880231fd9000: 58 44 42 33 e5 ac fb 07 00 00 00 00 92 c6 6a a8 XDB3..........j.
May 3 04:54:36 Tower kernel: ffff880231fd9010: 00 00 00 01 00 06 5c 85 dc 12 b4 a6 45 ad 49 da ......\.....E.I.
May 3 04:54:36 Tower kernel: ffff880231fd9020: 97 73 80 02 67 0c 26 9f 00 00 00 00 92 c6 6b 36 .s..g.&.......k6
May 3 04:54:36 Tower kernel: ffff880231fd9030: 0a 70 04 00 00 60 00 20 00 98 00 20 00 00 00 00 .p...`. ... ....
May 3 04:54:36 Tower kernel: XFS (md1): metadata I/O error: block 0x92c66aa8 ("xfs_trans_read_buf_map") error 74 numblks 8
May 3 05:47:28 Tower kernel: XFS (md1): Metadata CRC error detected at xfs_dir3_data_read_verify+0x9c/0xa2 [xfs], xfs_dir3_data block 0x5562e4a8
May 3 05:47:28 Tower kernel: XFS (md1): Unmount and run xfs_repair
May 3 05:47:28 Tower kernel: XFS (md1): First 64 bytes of corrupted metadata buffer:
May 3 05:47:28 Tower kernel: ffff8802324c7000: 58 44 44 33 fe b7 e8 e6 00 00 00 00 55 62 e4 a8 XDD3........Ub..
May 3 05:47:28 Tower kernel: ffff8802324c7010: 00 00 00 01 00 0f cf 09 dc 12 b4 a6 45 ad 49 da ............E.I.
May 3 05:47:28 Tower kernel: ffff8802324c7020: 97 73 80 02 67 0c 26 9f 00 00 00 00 54 cc c3 71 .s..g.&.....T..q
May 3 05:47:28 Tower kernel: ffff8802324c7030: 02 c8 00 18 03 d8 00 18 05 90 00 18 00 00 00 00 ................
May 3 05:47:28 Tower kernel: XFS (md1): Metadata CRC error detected at xfs_dir3_data_read_verify+0x9c/0xa2 [xfs], xfs_dir3_data block 0x5562e4a8
May 3 05:47:28 Tower kernel: XFS (md1): Unmount and run xfs_repair
May 3 05:47:28 Tower kernel: XFS (md1): First 64 bytes of corrupted metadata buffer:
May 3 05:47:28 Tower kernel: ffff8802324c7000: 58 44 44 33 fe b7 e8 e6 00 00 00 00 55 62 e4 a8 XDD3........Ub..
May 3 05:47:28 Tower kernel: ffff8802324c7010: 00 00 00 01 00 0f cf 09 dc 12 b4 a6 45 ad 49 da ............E.I.
May 3 05:47:28 Tower kernel: ffff8802324c7020: 97 73 80 02 67 0c 26 9f 00 00 00 00 54 cc c3 71 .s..g.&.....T..q
May 3 05:47:28 Tower kernel: ffff8802324c7030: 02 c8 00 18 03 d8 00 18 05 90 00 18 00 00 00 00 ................
May 3 05:47:28 Tower kernel: XFS (md1): metadata I/O error: block 0x5562e4a8 ("xfs_trans_read_buf_map") error 74 numblks 8
May 3 05:47:28 Tower kernel: XFS (md1): Metadata CRC error detected at xfs_dir3_data_read_verify+0x9c/0xa2 [xfs], xfs_dir3_data block 0x5562e4a8
May 3 05:47:28 Tower kernel: XFS (md1): Unmount and run xfs_repair
May 3 05:47:28 Tower kernel: XFS (md1): First 64 bytes of corrupted metadata buffer:
May 3 05:47:28 Tower kernel: ffff8802324c7000: 58 44 44 33 fe b7 e8 e6 00 00 00 00 55 62 e4 a8 XDD3........Ub..
May 3 05:47:28 Tower kernel: ffff8802324c7010: 00 00 00 01 00 0f cf 09 dc 12 b4 a6 45 ad 49 da ............E.I.
May 3 05:47:28 Tower kernel: ffff8802324c7020: 97 73 80 02 67 0c 26 9f 00 00 00 00 54 cc c3 71 .s..g.&.....T..q
May 3 05:47:28 Tower kernel: ffff8802324c7030: 02 c8 00 18 03 d8 00 18 05 90 00 18 00 00 00 00 ................
May 3 05:47:28 Tower kernel: XFS (md1): metadata I/O error: block 0x5562e4a8 ("xfs_trans_read_buf_map") error 74 numblks 8
May 3 05:55:12 Tower kernel: XFS (md1): Metadata CRC error detected at xfs_dir3_block_read_verify+0x9c/0xa2 [xfs], xfs_dir3_block block 0x230210e0
May 3 05:55:12 Tower kernel: XFS (md1): Unmount and run xfs_repair
May 3 05:55:12 Tower kernel: XFS (md1): First 64 bytes of corrupted metadata buffer:
May 3 05:55:12 Tower kernel: ffff88023179d000: 58 44 42 33 30 1e d9 52 00 00 00 00 23 02 10 e0 XDB30..R....#...
May 3 05:55:12 Tower kernel: ffff88023179d010: 00 00 00 01 00 09 1d 56 dc 12 b4 a6 45 ad 49 da .......V....E.I.
May 3 05:55:12 Tower kernel: ffff88023179d020: 97 73 80 02 67 0c 26 9f 00 00 00 00 23 02 0f fa .s..g.&.....#...
May 3 05:55:12 Tower kernel: ffff88023179d030: 0d e0 00 80 00 60 00 28 00 a8 00 28 00 00 00 00 .....`.(...(....
May 3 05:55:12 Tower kernel: XFS (md1): Metadata CRC error detected at xfs_dir3_block_read_verify+0x9c/0xa2 [xfs], xfs_dir3_block block 0x230210e0
May 3 05:55:12 Tower kernel: XFS (md1): Unmount and run xfs_repair
May 3 05:55:12 Tower kernel: XFS (md1): First 64 bytes of corrupted metadata buffer:
May 3 05:55:12 Tower kernel: ffff88023179d000: 58 44 42 33 30 1e d9 52 00 00 00 00 23 02 10 e0 XDB30..R....#...
May 3 05:55:12 Tower kernel: ffff88023179d010: 00 00 00 01 00 09 1d 56 dc 12 b4 a6 45 ad 49 da .......V....E.I.
May 3 05:55:12 Tower kernel: ffff88023179d020: 97 73 80 02 67 0c 26 9f 00 00 00 00 23 02 0f fa .s..g.&.....#...
May 3 05:55:12 Tower kernel: ffff88023179d030: 0d e0 00 80 00 60 00 28 00 a8 00 28 00 00 00 00 .....`.(...(....
May 3 05:55:12 Tower kernel: XFS (md1): metadata I/O error: block 0x230210e0 ("xfs_trans_read_buf_map") error 74 numblks 8
May 3 05:57:12 Tower kernel: XFS (md1): Metadata CRC error detected at xfs_dir3_block_read_verify+0x9c/0xa2 [xfs], xfs_dir3_block block 0x383dc8838
May 3 05:57:12 Tower kernel: XFS (md1): Unmount and run xfs_repair
May 3 05:57:12 Tower kernel: XFS (md1): First 64 bytes of corrupted metadata buffer:
May 3 05:57:12 Tower kernel: ffff8800163ea000: 58 44 42 33 ad f7 bd b3 00 00 00 03 83 dc 88 38 XDB3...........8
May 3 05:57:12 Tower kernel: ffff8800163ea010: 00 00 00 01 00 02 29 54 dc 12 b4 a6 45 ad 49 da ......)T....E.I.
May 3 05:57:12 Tower kernel: ffff8800163ea020: 97 73 80 02 67 0c 26 9f 00 00 00 03 83 dc 88 98 .s..g.&.........
May 3 05:57:12 Tower kernel: ffff8800163ea030: 0a 10 04 c0 00 60 00 58 01 08 00 58 00 00 00 00 .....`.X...X....
May 3 05:57:12 Tower kernel: XFS (md1): Metadata CRC error detected at xfs_dir3_block_read_verify+0x9c/0xa2 [xfs], xfs_dir3_block block 0x383dc8838
May 3 05:57:12 Tower kernel: XFS (md1): Unmount and run xfs_repair
May 3 05:57:12 Tower kernel: XFS (md1): First 64 bytes of corrupted metadata buffer:
May 3 05:57:12 Tower kernel: ffff8800163ea000: 58 44 42 33 ad f7 bd b3 00 00 00 03 83 dc 88 38 XDB3...........8
May 3 05:57:12 Tower kernel: ffff8800163ea010: 00 00 00 01 00 02 29 54 dc 12 b4 a6 45 ad 49 da ......)T....E.I.
May 3 05:57:12 Tower kernel: ffff8800163ea020: 97 73 80 02 67 0c 26 9f 00 00 00 03 83 dc 88 98 .s..g.&.........
May 3 05:57:12 Tower kernel: ffff8800163ea030: 0a 10 04 c0 00 60 00 58 01 08 00 58 00 00 00 00 .....`.X...X....
May 3 05:57:12 Tower kernel: XFS (md1): metadata I/O error: block 0x383dc8838 ("xfs_trans_read_buf_map") error 74 numblks 8
And watching the console output it is telling me to run xfs_repair on the drive in question, md1. I started the array in maintenance mode and did just that. I don't have the output from that command at the moment but it was showing me some inode CRC error and told me that it was being repaired, but I tried running the command again before starting the array and another inode CRC error appeared but with another inode address. This kept repeating a couple of times. I tried starting the array and the migration process again but the same message keeps popping up in the log. There are not a lot of them but never the less they get me worried.
I'm running the server on consumer grade hardware at the moment since I have to migrate the data before adding the drives to my normal server. Is this anything to worry about, is my data safe?
Best regards Alex