Spartacus09

Thank you for this, I completely forgot I set this to schedule and I noticed my CPU going crazy this morning. Mine was running a file integrity check also. I need to space out the drive checks so it doesn't hit the CPU so hard all at once.

I got this too with 6.8.3 stable at 4am this morning when everything got updated on both my unraid boxes, was about to post as well. Good to know, I'll wait on the fix common problems update then.

So quick question on the best way/how to configure, I have a nightly appdata backup at 5am and want the docker containers (that are stopped for the backups) updated after backup completion. I've already configured the backup and I have set 'Update Applications On Restart' to yes. If I leave the docker auto update settings 'Update Check Frequency' to Disabled will it still check for updates and complete during the nightly backup?

Just started using unRAID it was extremely easy to setup and use, I was able to convert all of my esxi VMs over and migrate my docker instances easily. I'm up to 12 storage drives and counting, looking to max out the drive limit . Even if I don't win, I'd love to be able to purchase one of the badges if they go up for sale.

Restarting apparently clears the errors associated, or at least there are no errors now after replacing the ram in A1/A2.

Thanks so a guy here was receiving a channel 0 dimm 0 error also with a supermicro mobo sounds like SM labels start at 0: https://serverfault.com/questions/792225/how-to-find-which-memory-has-ce-error Looks like its likely slot A2 then, ill give that shot. What is the steps to clear that hardware error out of the logs so I can see if it comes back? (I updated unraid versions previously and it cleared it but didn't reoccur til a week or so later).

Is there a command to identify which memory slot this error is referring or list all of them, I'm assuming its likely A1 of the 8 slots. I'm not sure if it starts at channel #1 or channel #0 and might be A2 though (motherboard manual calls A1 channel A). Jul 14 21:33:07 unRAID kernel: mce: [Hardware Error]: Machine check events logged Jul 14 21:33:07 unRAID kernel: EDAC sbridge MC0: HANDLING MCE MEMORY ERROR Jul 14 21:33:07 unRAID kernel: EDAC MC1: 1 CE memory scrubbing error on CPU_SrcID#0_Ha#1_Chan#1_DIMM#0 (channel:1 slot:0 page:0x109a826 offset:0x0 grain:32 syndrome:0x0 - area:DRAM err_code:0008:00c0 socket:0 ha:1 channel_mask:2 rank:0) Jul 15 04:21:17 unRAID kernel: mce: [Hardware Error]: Machine check events logged Jul 15 04:21:17 unRAID kernel: EDAC sbridge MC0: HANDLING MCE MEMORY ERROR Jul 15 04:21:17 unRAID kernel: EDAC MC1: 1 CE memory scrubbing error on CPU_SrcID#0_Ha#1_Chan#1_DIMM#0 (channel:1 slot:0 page:0x109a826 offset:0x0 grain:32 syndrome:0x0 - area:DRAM err_code:0008:00c0 socket:0 ha:1 channel_mask:2 rank:0) Jul 15 04:40:06 unRAID root: Fix Common Problems: Error: Machine Check Events detected on your server Jul 15 11:31:07 unRAID kernel: mce: [Hardware Error]: Machine check events logged Jul 15 11:31:07 unRAID kernel: EDAC sbridge MC0: HANDLING MCE MEMORY ERROR Jul 15 11:31:07 unRAID kernel: EDAC MC1: 1 CE memory scrubbing error on CPU_SrcID#0_Ha#1_Chan#1_DIMM#0 (channel:1 slot:0 page:0x109a826 offset:0x0 grain:32 syndrome:0x0 - area:DRAM err_code:0008:00c0 socket:0 ha:1 channel_mask:2 rank:0) Jul 15 18:31:29 unRAID kernel: mce: [Hardware Error]: Machine check events logged Jul 15 18:31:29 unRAID kernel: EDAC sbridge MC0: HANDLING MCE MEMORY ERROR Jul 15 18:31:29 unRAID kernel: EDAC MC1: 1 CE memory scrubbing error on CPU_SrcID#0_Ha#1_Chan#1_DIMM#0 (channel:1 slot:0 page:0x109a826 offset:0x0 grain:32 syndrome:0x0 - area:DRAM err_code:0008:00c0 socket:0 ha:1 channel_mask:2 rank:0)

Good to know, I’ll look for it to error again, and warranty replace it if it pops back up, luckily crucial has lifetime warranty like most ram manuf.

I appreciate Squid, I found how to get to the syslog and found this appeared to be the error: "EDAC MC1: 1 CE memory scrubbing error on CPU_SrcID#0_Ha#1_Chan#1_DIMM#0 (channel:1 slot:0 page:0x109a826 offset:0x0 grain:32 syndrome:0x0 - area:DRAM err_code:0008:00c0 socket:0 ha:1 channel_mask:2 rank:0)" Which is odd because its R-dimm ram, I ran memtest for 72 hours and several passes, ipmi sensors are reporting no issues, and I have no stability problems. I noticed my ram happened to be running at 1866 though instead of 2133 so I corrected that and reseated all the dimms. I also updated to the latest version 6.7.2 release, it appears to be either gone or it cleared due to the update, I'll repost with the diags if it reoccurs. Thanks!

Getting the message: "Your server has detected hardware errors. You should install mcelog via the NerdPack plugin, post your diagnostics and ask for assistance on the unRaid forums. The output of mcelog (if installed) has been logged" from the fix common problems app. I have the mcelog already installed, what do I need to do to check this? General Specs: Intel Xeon E5-2660 v3 Supermicro X10SRH-CLN4F (3008 controller flashed to it-mode) 8x 16GB DDR4-R Crucial Ram