March 23, 20233 yr I really need some help now. Servers been running fine for nearly two years and today I got a disk error on my Samsung 980 M2. I kinda expected it since I have two and the other one failed a couple of months back. It was replaced and my server kept on running. Â Today I experienced a similar error on my second 980 (all though not identical - many loop2 errors and corruption messages) so I switched my docker.img over to the newly replaced M2 (now a 980 Pro) and thought everything was alright. Â Now all of a sudden I am getting errors on my 980 Pro as well (disk about 2 months old) and after a reboot it just became unmountable. Â I have attached the diag and would like to point out that me discovering the initial disk error was this afternoon. I have since upgraded to 6.12.rc2, but I am don't think that is the problem. Â Hopefully you can find something. Â Regards, Thomas unraid-20230324-0003.zip
March 24, 20233 yr Author Update: Â Were able to mount the M2 drive but whilst copying from that drive to the array I am now getting this error: Â Mar 24 09:47:02 Algarheim emhttpd: read SMART /dev/sdc Mar 24 09:47:06 Algarheim kernel: XFS (md4p1): Metadata corruption detected at xfs_dinode_verify+0xa0/0x732 [xfs], inode 0x11cb6dc8a dinode Mar 24 09:47:06 Algarheim kernel: XFS (md4p1): Unmount and run xfs_repair Mar 24 09:47:06 Algarheim kernel: XFS (md4p1): First 128 bytes of corrupted metadata buffer: Mar 24 09:47:06 Algarheim kernel: 00000000: 49 4e 81 f8 03 02 00 00 00 00 00 63 00 00 00 64 IN.........c...d Mar 24 09:47:06 Algarheim kernel: 00000010: 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 ................ Mar 24 09:47:06 Algarheim kernel: 00000020: 61 24 bd 9f 21 bd a9 64 55 a7 bc 8e 00 00 00 00 a$..!..dU....... Mar 24 09:47:06 Algarheim kernel: 00000030: 64 1c c8 ec 0d ee 51 79 00 00 00 00 00 19 df e2 d.....Qy........ Mar 24 09:47:06 Algarheim kernel: 00000040: 00 00 00 00 00 00 01 9e 00 00 00 00 00 00 00 01 ................ Mar 24 09:47:06 Algarheim kernel: 00000050: 00 00 00 02 00 00 00 00 00 00 00 00 83 a8 d9 b8 ................ Mar 24 09:47:06 Algarheim kernel: 00000060: ff ff ff ff 44 f6 0a 69 00 00 00 00 00 00 6a 9b ....D..i......j. Mar 24 09:47:06 Algarheim kernel: 00000070: 00 00 00 46 00 0e 66 b9 00 00 00 00 00 00 00 00 ...F..f......... Mar 24 09:47:12 Algarheim emhttpd: read SMART /dev/sdf Mar 24 09:47:15 Algarheim kernel: XFS (md4p1): Metadata corruption detected at xfs_dinode_verify+0xa0/0x732 [xfs], inode 0x11cb6dc8a dinode Mar 24 09:47:15 Algarheim kernel: XFS (md4p1): Unmount and run xfs_repair Mar 24 09:47:15 Algarheim kernel: XFS (md4p1): First 128 bytes of corrupted metadata buffer: Mar 24 09:47:15 Algarheim kernel: 00000000: 49 4e 81 f8 03 02 00 00 00 00 00 63 00 00 00 64 IN.........c...d Mar 24 09:47:15 Algarheim kernel: 00000010: 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 ................ Mar 24 09:47:15 Algarheim kernel: 00000020: 61 24 bd 9f 21 bd a9 64 55 a7 bc 8e 00 00 00 00 a$..!..dU....... Mar 24 09:47:15 Algarheim kernel: 00000030: 64 1c c8 ec 0d ee 51 79 00 00 00 00 00 19 df e2 d.....Qy........ Mar 24 09:47:15 Algarheim kernel: 00000040: 00 00 00 00 00 00 01 9e 00 00 00 00 00 00 00 01 ................ Mar 24 09:47:15 Algarheim kernel: 00000050: 00 00 00 02 00 00 00 00 00 00 00 00 83 a8 d9 b8 ................ Mar 24 09:47:15 Algarheim kernel: 00000060: ff ff ff ff 44 f6 0a 69 00 00 00 00 00 00 6a 9b ....D..i......j. Mar 24 09:47:15 Algarheim kernel: 00000070: 00 00 00 46 00 0e 66 b9 00 00 00 00 00 00 00 00 ...F..f......... Mar 24 09:47:30 Algarheim emhttpd: read SMART /dev/sde Mar 24 09:47:30 Algarheim emhttpd: read SMART /dev/sdb Mar 24 09:49:50 Algarheim kernel: mdcmd (59): set md_write_method 1 Mar 24 09:49:50 Algarheim kernel: Â
March 24, 20233 yr Community Expert Diags are after rebooting so we can0t see what happened. Â 14 minutes ago, Ulf Thomas Johansen said: XFS (md4p1): Unmount and run xfs_repair Check filesystem on disk4.
March 24, 20233 yr Author Multiple reboots, yes. This started as a M2-issue, but now it's also hitting the array which I find strange. Â Planning on file system check, but need to let copy job from M2 finish.
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.