RAM Error during Burn-In - RMA?

Status
Not open for further replies.
Seani

Seani

Dabbler
Joined
Oct 18, 2016
Messages
41
I am currently (for 48h already) burning in ten 8TB Seagate IronWolf 8TB NAS drives in my server using badblocks (all at the same time using tmux). Before that, I ran short, conveyance and long S.M.A.R.T tests on the drives.
Initially I let memtest86 have two full passes on my RAM without any errors or entrys in the IPMI log.

Today I received the "freenas.local daily security run output" email that said:

Code:
freenas.local kernel log messages:

MCA: Bank 12, Status 0x8c000043000800c3
MCA: Global Cap 0x0000000007000c16, Status 0x0000000000000000
MCA: Vendor "GenuineIntel", ID 0x406f1, APIC ID 0
MCA: CPU 0 COR (1) MS channel 3 memory error
MCA: Address 0x8ace801c0
MCA: Misc 0x90004040404068c
MCA: Bank 12, Status 0xcc000f83000800c3
MCA: Global Cap 0x0000000007000c16, Status 0x0000000000000000
MCA: Vendor "GenuineIntel", ID 0x406f1, APIC ID 0
MCA: CPU 0 COR (62) OVER MS channel 3 memory error
MCA: Address 0x8ace97fc0
MCA: Misc 0x90000040040068c
MCA: Bank 12, Status 0x8c000043000800c3
MCA: Global Cap 0x0000000007000c16, Status 0x0000000000000000
MCA: Vendor "GenuineIntel", ID 0x406f1, APIC ID 0
MCA: CPU 0 COR (1) MS channel 3 memory error
MCA: Address 0x8ace955c0
MCA: Misc 0x90004000400068c
MCA: Bank 12, Status 0xcc000083000800c3
MCA: Global Cap 0x0000000007000c16, Status 0x0000000000000000
MCA: Vendor "GenuineIntel", ID 0x406f1, APIC ID 0
MCA: CPU 0 COR (2) OVER MS channel 3 memory error
MCA: Address 0x8ace961c0
MCA: Misc 0x90004000404068c
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 84:16:f9:2a:93:e5 to 80:71:7a:9a:f9:3f on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0
arp: 192.168.1.1 moved from 80:71:7a:9a:f9:3f to 84:16:f9:2a:93:e5 on lagg0

-- End of security output --


The arp: messages don't worry me. I have read that LACP can have that effect (I use the 4 LAN ports of the motherboard in a LACP LAG).

The MCA messages on the other hand do worry me. Does that mean that my RAM is defective or should I try to unplug and then replug the modules to see if it's a connection issue (although I seriously doubt it)? I have 4 days left to send the RAM back to the seller due to the right of withdrawal (I think that's what it's called) in germany. The thing is that the badblocks test is only half way through (second pattern written and read at ~95% right now). It will take ~2 to 3 more days to finish and after that I only have one day left to decide whether I withdraw and send the modules back (and buy a differend kind) or whether I try to establish which RAM stick is faulty and go the way of RMA. Any thoughts or suggestions? For the next 2-3 days my hands are bound since I do not think that it would be wise to interrupt the badblocks test.

My system:
Mainboard: Supermicro X10SRH-CLN4F
CPU: Intel Xeon E5-2620v4
RAM: 4x 16GB Crucial CT16G4RFD4213
HBA: LSI 3008 (on the mainboard) flashed to P12 IT
HDDs: 10x Seagate IronWolf NAS 8TB
SSD (OS): KINGSTON SUV 400 S 3 120GB
PSU: Corsair HX850i
OS: FreeNAS-9.10.2-U1 (86c7ef5)

Suggestions what I should do next in which order would be very welcome. Thanks in advance.
 
DrKK

DrKK

FreeNAS Generalissimo
Joined
Oct 15, 2013
Messages
3,630
You might find this thread useful: https://forums.freenas.org/index.php?threads/memory-errors.10573/

Basically, I would not be using that memory.

Second of all, if you would like, it is possible to suppress the ARP messages quite easily with a sysctl. I believe these are the relevant ones, and they both default to "on":

Code:

net.link.ether.inet.log_arp_movements: 0
net.link.ether.inet.log_arp_wrong_iface: 0
 
Seani

Seani

Dabbler
Joined
Oct 18, 2016
Messages
41
DrKK said:
You might find this thread useful: https://forums.freenas.org/index.php?threads/memory-errors.10573/

Basically, I would not be using that memory.
Click to expand...
Thanks for the advice. I forgot to link the thread you mentioned (I had already read it before posting mine). I thought that maybe there is new information on that matter since the original thread was from 2012.

DrKK said:
Second of all, if you would like, it is possible to suppress the ARP messages quite easily with a sysctl. I believe these are the relevant ones, and they both default to "on":

Code:
net.link.ether.inet.log_arp_movements: 0
net.link.ether.inet.log_arp_wrong_iface: 0
Click to expand...
I will look into it but it's not my priority right now.

I will most likely let the badblocks test finish, order new RAM and send back the RAM I am using now once the new RAM arrives.
 
DrKK

DrKK

FreeNAS Generalissimo
Joined
Oct 15, 2013
Messages
3,630
Our feeling in the community, basically, is that given the complexity of ZFS, the very last thing in the universe we want is RAM we do not trust. 99% of us would immediately replace any RAM that even looked at us wrong.

Replace the RAM sir.
 
T

tvsjr

Guru
Joined
Aug 29, 2015
Messages
959
Replace the RAM. There's even some possibility that the bad RAM may give you invalid badblocks results. You need a good foundation before you start building the house... if the foundation (CPU/RAM/MB) is bad, you're in trouble.

You could always run Memtest which should conclusively prove a memory problem.
 
Seani

Seani

Dabbler
Joined
Oct 18, 2016
Messages
41
tvsjr said:
Replace the RAM. There's even some possibility that the bad RAM may give you invalid badblocks results. You need a good foundation before you start building the house... if the foundation (CPU/RAM/MB) is bad, you're in trouble.

You could always run Memtest which should conclusively prove a memory problem.
Click to expand...

The Badblocks test can finish anyway (I don't mind retesting the drives with the new RAM if errors should occur).
I ordered different RAM and will send the old RAM back to the seller, as soon as the new RAM arrives.
This time, I will have it run 5 passes in memtest86 before I even consider trusting it (even if that takes a week to complete).

I reconsidered my build and now ordered 128GB RAM (4x 32GB 2133 Hynix LRDIMM ECC).
(64GB for 80TB of RAW storage were a bit undersized when following the thumb-rule, anyway.)

I also ordered another 6 8TB NAS drives (which I will have to burn in as well..) and will eventually (when all the burning-in is done) run 2 VDEVs of 6+2 Raid-Z2 with 128GB of RAM. That should suffice for years to come (and will still have space for upgrades (only 4 of 8 RAM slots used and only 16 of 24 HDD bays used).

Thanks for your advice.
 
Status
Not open for further replies.

Similar threads

F
  • Locked
FreeNas security run output - problem with lost pages of memory
Replies
4
Views
3K
Frosch1482
F
Nicholas
  • Locked
Que significa este mensaje: Security Run Output
Replies
2
Views
1K
Nicholas
Nicholas
iliak
help understand daily security run output
Replies
3
Views
2K
iliak
iliak
Glorious1
Concerning notification/error
Replies
6
Views
1K
Glorious1
Glorious1
S
  • Locked
Security Report shows Error. Memtest shows nothing!
Replies
2
Views
1K
Dice
Dice
Top