June 9, 20233 yr Hi, I could use some help with the below syslog errors. It doesn't seem to affecting operation of my Unraid server, but I feel like I better fix it. I am in the process of running SMART extended tests on both of my array disks. I understand that I need to Start my array in Maintenance Mode then through the webgui, do a filesystem check. Is this equivalent to running xfs_repair? The error references "dm-1", how do I identify which disk has the issue? I ran the below commands to identify the "dm-1" KNAME. SYSLOG ERRORS Jun 9 10:58:48 Tower kernel: XFS (dm-1): Metadata CRC error detected at xfs_dir3_block_read_verify+0x7c/0xf1 [xfs], xfs_dir3_block block 0x182ba4640 Jun 9 10:58:48 Tower kernel: XFS (dm-1): Unmount and run xfs_repair Jun 9 10:58:48 Tower kernel: XFS (dm-1): First 128 bytes of corrupted metadata buffer: Jun 9 10:58:48 Tower kernel: 00000000: 39 73 00 a0 57 58 2e 37 bc 03 a3 8d 69 e2 d7 c3 9s..WX.7....i... Jun 9 10:58:48 Tower kernel: 00000010: 7b a5 40 fa d6 72 05 af 72 7e 97 87 88 60 28 10 {[email protected]~...`(. Jun 9 10:58:48 Tower kernel: 00000020: ec 40 a5 a7 6a 38 a5 8b 7a 80 31 fd e4 60 b9 03 [email protected]..`.. Jun 9 10:58:48 Tower kernel: 00000030: 77 e0 6a 20 2a c6 cf 7d 4d 56 9f 9d f6 fa a3 46 w.j *..}MV.....F Jun 9 10:58:48 Tower kernel: 00000040: 30 93 45 ef 67 1b 65 95 36 81 25 ba 93 21 ed 5c 0.E.g.e.6.%..!.\ Jun 9 10:58:48 Tower kernel: 00000050: 6d 33 ab dd 30 72 42 80 74 67 12 10 16 56 ae 33 m3..0rB.tg...V.3 Jun 9 10:58:48 Tower kernel: 00000060: 64 15 29 7c e9 55 e4 13 0d ba 0c c0 66 d7 6d 3d d.)|.U......f.m= Jun 9 10:58:48 Tower kernel: 00000070: 2d b5 0d 0f af d4 45 42 d0 3e ed 53 06 73 d0 ea -.....EB.>.S.s.. Jun 9 10:58:48 Tower kernel: XFS (dm-1): metadata I/O error in "xfs_da_read_buf+0x9a/0xff [xfs]" at daddr 0x182ba4640 len 8 error 74 Jun 9 10:58:58 Tower kernel: XFS (dm-1): Metadata corruption detected at xfs_dir3_data_reada_verify+0x53/0x64 [xfs], xfs_dir3_data_reada block 0x182ba4640 Jun 9 10:58:58 Tower kernel: XFS (dm-1): Unmount and run xfs_repair Jun 9 10:58:58 Tower kernel: XFS (dm-1): First 128 bytes of corrupted metadata buffer: Jun 9 10:58:58 Tower kernel: 00000000: 39 73 00 a0 57 58 2e 37 bc 03 a3 8d 69 e2 d7 c3 9s..WX.7....i... Jun 9 10:58:58 Tower kernel: 00000010: 7b a5 40 fa d6 72 05 af 72 7e 97 87 88 60 28 10 {[email protected]~...`(. Jun 9 10:58:58 Tower kernel: 00000020: ec 40 a5 a7 6a 38 a5 8b 7a 80 31 fd e4 60 b9 03 [email protected]..`.. Jun 9 10:58:58 Tower kernel: 00000030: 77 e0 6a 20 2a c6 cf 7d 4d 56 9f 9d f6 fa a3 46 w.j *..}MV.....F Jun 9 10:58:58 Tower kernel: 00000040: 30 93 45 ef 67 1b 65 95 36 81 25 ba 93 21 ed 5c 0.E.g.e.6.%..!.\ Jun 9 10:58:58 Tower kernel: 00000050: 6d 33 ab dd 30 72 42 80 74 67 12 10 16 56 ae 33 m3..0rB.tg...V.3 Jun 9 10:58:58 Tower kernel: 00000060: 64 15 29 7c e9 55 e4 13 0d ba 0c c0 66 d7 6d 3d d.)|.U......f.m= Jun 9 10:58:58 Tower kernel: 00000070: 2d b5 0d 0f af d4 45 42 d0 3e ed 53 06 73 d0 ea -.....EB.>.S.s.. Jun 9 10:58:58 Tower kernel: XFS (dm-1): Metadata CRC error detected at xfs_dir3_block_read_verify+0x7c/0xf1 [xfs], xfs_dir3_block block 0x182ba4640 Jun 9 10:58:58 Tower kernel: XFS (dm-1): Unmount and run xfs_repair Jun 9 10:58:58 Tower kernel: XFS (dm-1): First 128 bytes of corrupted metadata buffer: Jun 9 10:58:58 Tower kernel: 00000000: 39 73 00 a0 57 58 2e 37 bc 03 a3 8d 69 e2 d7 c3 9s..WX.7....i... Jun 9 10:58:58 Tower kernel: 00000010: 7b a5 40 fa d6 72 05 af 72 7e 97 87 88 60 28 10 {[email protected]~...`(. Jun 9 10:58:58 Tower kernel: 00000020: ec 40 a5 a7 6a 38 a5 8b 7a 80 31 fd e4 60 b9 03 [email protected]..`.. Jun 9 10:58:58 Tower kernel: 00000030: 77 e0 6a 20 2a c6 cf 7d 4d 56 9f 9d f6 fa a3 46 w.j *..}MV.....F Jun 9 10:58:58 Tower kernel: 00000040: 30 93 45 ef 67 1b 65 95 36 81 25 ba 93 21 ed 5c 0.E.g.e.6.%..!.\ Jun 9 10:58:58 Tower kernel: 00000050: 6d 33 ab dd 30 72 42 80 74 67 12 10 16 56 ae 33 m3..0rB.tg...V.3 Jun 9 10:58:58 Tower kernel: 00000060: 64 15 29 7c e9 55 e4 13 0d ba 0c c0 66 d7 6d 3d d.)|.U......f.m= Jun 9 10:58:58 Tower kernel: 00000070: 2d b5 0d 0f af d4 45 42 d0 3e ed 53 06 73 d0 ea -.....EB.>.S.s.. Jun 9 10:58:58 Tower kernel: XFS (dm-1): metadata I/O error in "xfs_da_read_buf+0x9a/0xff [xfs]" at daddr 0x182ba4640 len 8 error 74 root@Tower:~# lsblk --output NAME,KNAME,TYPE,SIZE,MOUNTPOINT NAME KNAME TYPE SIZE MOUNTPOINT loop0 loop0 loop 116.8M /lib/firmware loop1 loop1 loop 19.4M /lib/modules sda sda disk 14.3G └─sda1 sda1 part 14.3G /boot sdb sdb disk 232.9G └─sdb1 sdb1 part 232.9G sdc sdc disk 5.5T └─sdc1 sdc1 part 5.5T sdd sdd disk 3.6T └─sdd1 sdd1 part 3.6T sde sde disk 3.6T └─sde1 sde1 part 3.6T sdf sdf disk 3.6T └─sdf1 sdf1 part 3.6T md1 md1 md 3.6T └─md1 dm-0 crypt 3.6T md2 md2 md 3.6T └─md2 dm-1 crypt 3.6T PS: I found this related forum post for guidance and also the Unraid Wiki: https://docs.unraid.net/legacy/FAQ/check-disk-filesystems/ Edited June 9, 20233 yr by lessismore
June 9, 20233 yr Community Expert 5 hours ago, lessismore said: how do I identify which disk has the issue? Please post the diagnostics.
June 13, 20233 yr Author Thanks, here is the diagnostics and the two extended SMART reports for the two drives that make up my array. I have two parity drives that I'm running extended SMART test on now. These 4 drives make up my total unraid setup. tower-diagnostics-20230613-1513.ziptower-smart-20230613-1509.ziptower-smart-20230613-1510.zip
June 13, 20233 yr Community Expert The log rotated so cannot see the boot process, reboot (take the opportunity to update to v6.11.5 first since that release has a serious known issue formatting disks) and post new diags after array start.
June 14, 20233 yr Author Thanks JorgeB. I've updated to v6.11.5 then rebooted. I haven't started the array yet. Here are the diagnostics:tower-diagnostics-20230614-1522.zip Edited June 14, 20233 yr by lessismore typo
June 15, 20233 yr Author I ran the Filesystem Check with option -nv. It completed in only 49 seconds. Below is a copy and paste of the status output from within the Unraid GUI as well as another diagnostic pack. Check Filesystem Log 20230616 084149.txt tower-diagnostics-20230616-0843.zip
June 16, 20233 yr Community Expert Solution Run it again without -n or nothing will be done, if it asks for it use -L
June 19, 20233 yr Author I ran it with option -v to repair Then ran a check again with option -nv. Both logs attached. Repair 20230619 option -v.txt Check after Repair 20230619 option -nv.txt tower-diagnostics-20230619-1105.zip
June 20, 20233 yr Author Thanks, I started the array and am not seeing the error anymore. Not sure what you meant by check the lost+found, but attached is a list of the files. lost+found directory.txt Edited June 20, 20233 yr by lessismore
June 20, 20233 yr Community Expert Those could be previous data files that were not complete or lost the name, though it's not very easy to check them.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.