This is the 2nd time I've had this issue and would love to know what causes it. I've attached my diag file.

 

Here is what I see in my log:

Feb 24 21:32:39 UNRAID kernel: BTRFS critical (device nvme0n1p1): corrupt leaf: root=5 block=284124921856 slot=0 ino=109145, name hash mismatch with key, have 0x00000000c7e8ba55 expect 0x0000000006a3fa50
Feb 24 21:32:39 UNRAID kernel: BTRFS critical (device nvme0n1p1): corrupt leaf: root=5 block=284124921856 slot=0 ino=109145, name hash mismatch with key, have 0x00000000c7e8ba55 expect 0x0000000006a3fa50
Feb 24 21:32:51 UNRAID kernel: BTRFS critical (device nvme0n1p1): corrupt leaf: root=5 block=284124921856 slot=0 ino=109145, name hash mismatch with key, have 0x00000000c7e8ba55 expect 0x0000000006a3fa50
Feb 24 21:32:51 UNRAID kernel: BTRFS critical (device nvme0n1p1): corrupt leaf: root=5 block=284124921856 slot=0 ino=109145, name hash mismatch with key, have 0x00000000c7e8ba55 expect 0x0000000006a3fa50
Feb 24 21:33:03 UNRAID kernel: BTRFS critical (device nvme0n1p1): corrupt leaf: root=5 block=284124921856 slot=0 ino=109145, name hash mismatch with key, have 0x00000000c7e8ba55 expect 0x0000000006a3fa50
Feb 24 21:33:03 UNRAID kernel: BTRFS critical (device nvme0n1p1): corrupt leaf: root=5 block=284124921856 slot=0 ino=109145, name hash mismatch with key, have 0x00000000c7e8ba55 expect 0x0000000006a3fa50
Feb 24 21:33:15 UNRAID kernel: BTRFS critical (device nvme0n1p1): corrupt leaf: root=5 block=284124921856 slot=0 ino=109145, name hash mismatch with key, have 0x00000000c7e8ba55 expect 0x0000000006a3fa50
Feb 24 21:33:15 UNRAID kernel: BTRFS critical (device nvme0n1p1): corrupt leaf: root=5 block=284124921856 slot=0 ino=109145, name hash mismatch with key, have 0x00000000c7e8ba55 expect 0x0000000006a3fa50
Feb 24 21:33:27 UNRAID kernel: BTRFS critical (device nvme0n1p1): corrupt leaf: root=5 block=284124921856 slot=0 ino=109145, name hash mismatch with key, have 0x00000000c7e8ba55 expect 0x0000000006a3fa50
Feb 24 21:33:27 UNRAID kernel: BTRFS critical (device nvme0n1p1): corrupt leaf: root=5 block=284124921856 slot=0 ino=109145, name hash mismatch with key, have 0x00000000c7e8ba55 expect 0x0000000006a3fa50
Feb 24 21:33:39 UNRAID kernel: BTRFS critical (device nvme0n1p1): corrupt leaf: root=5 block=284124921856 slot=0 ino=109145, name hash mismatch with key, have 0x00000000c7e8ba55 expect 0x0000000006a3fa50
Feb 24 21:33:39 UNRAID kernel: BTRFS critical (device nvme0n1p1): corrupt leaf: root=5 block=284124921856 slot=0 ino=109145, name hash mismatch with key, have 0x00000000c7e8ba55 expect 0x0000000006a3fa50
Feb 24 21:33:51 UNRAID kernel: BTRFS critical (device nvme0n1p1): corrupt leaf: root=5 block=284124921856 slot=0 ino=109145, name hash mismatch with key, have 0x00000000c7e8ba55 expect 0x0000000006a3fa50
Feb 24 21:33:51 UNRAID kernel: BTRFS critical (device nvme0n1p1): corrupt leaf: root=5 block=284124921856 slot=0 ino=109145, name hash mismatch with key, have 0x00000000c7e8ba55 expect 0x0000000006a3fa50
Feb 24 21:34:03 UNRAID kernel: BTRFS critical (device nvme0n1p1): corrupt leaf: root=5 block=284124921856 slot=0 ino=109145, name hash mismatch with key, have 0x00000000c7e8ba55 expect 0x0000000006a3fa50
Feb 24 21:34:03 UNRAID kernel: BTRFS critical (device nvme0n1p1): corrupt leaf: root=5 block=284124921856 slot=0 ino=109145, name hash mismatch with key, have 0x00000000c7e8ba55 expect 0x0000000006a3fa50
Feb 24 21:34:15 UNRAID kernel: BTRFS critical (device nvme0n1p1): corrupt leaf: root=5 block=284124921856 slot=0 ino=109145, name hash mismatch with key, have 0x00000000c7e8ba55 expect 0x0000000006a3fa50
Feb 24 21:34:15 UNRAID kernel: BTRFS critical (device nvme0n1p1): corrupt leaf: root=5 block=284124921856 slot=0 ino=109145, name hash mismatch with key, have 0x00000000c7e8ba55 expect 0x0000000006a3fa50

 

Any ideas what could be causing it?

 

unraid-diagnostics-20190224-2132.zip

That's metadata corruption, it could be caused for example by a flipped bit in RAM, you should run memtest, you also should avoid overclocked RAM, or better yet use a server with ECC RAM.

Thanks, I'll check but I don't think that is the case. I had this issue with my ryzen 2700x, ram and mobo which I used for a month before returning them Friday. Now it happened again with my i9, new mobo, and new ram running their stock speeds.

 

Do I need to format the cache drives again?

Ryzen is known to corrupt data with overclocked RAM, various users have found parity sync errors, but there could be other issues, best wasy forward is to backup cache, format and restore data.

 

Ahh, thanks! I guess it's possible this transferred over from the ryzen build.