I was hunting on another issue and came across a couple errors in my log file and wanting to know if these would be concerning.

 

 

Hardware Error - it seems to say it was ECC corrected, but I've never actually seen this happen before.  Is this a sign that something is failing?  

 

Quote

 

Mar 30 04:40:04 TODD-Svr emhttpd: read SMART /dev/sdb

Mar 30 04:40:05 TODD-Svr emhttpd: read SMART /dev/sdj

Mar 30 04:41:11 TODD-Svr kernel: {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1

Mar 30 04:41:11 TODD-Svr kernel: {1}[Hardware Error]: It has been corrected by h/w and requires no further action

Mar 30 04:41:11 TODD-Svr kernel: {1}[Hardware Error]: event severity: corrected

Mar 30 04:41:11 TODD-Svr kernel: {1}[Hardware Error]: Error 0, type: corrected

Mar 30 04:41:11 TODD-Svr kernel: {1}[Hardware Error]: fru_text: CorrectedErr

Mar 30 04:41:11 TODD-Svr kernel: {1}[Hardware Error]: section_type: memory error

Mar 30 04:41:11 TODD-Svr kernel: {1}[Hardware Error]: node:0 device:0

Mar 30 04:41:11 TODD-Svr kernel: {1}[Hardware Error]: error_type: 2, single-bit ECC

 

 

 

I found multiple instances of a "failed login, spaced throughout the end of the startup routine.

There is no specific pattern of a command happening either immediately above or below the timeline of these fails.

Typically there is either a Smart read or a disk fan adjustment command above and/or below those login fails, but some are close in time and others are hours apart so that doesnt seem like a pattern.

 

Any way to track down what this is?
 

Quote

 

Mar 29 16:42:14 TODD-Svr sSMTP[3167]: Authorization failed (535 5.7.8 Authentication credentials invalid.)

Mar 30 00:10:08 TODD-Svr sSMTP[32506]: Authorization failed (535 5.7.8 Authentication credentials invalid.)

Mar 30 00:20:02 TODD-Svr sSMTP[15029]: Authorization failed (535 5.7.8 Authentication credentials invalid.)

Mar 31 00:20:02 TODD-Svr sSMTP[7622]: Authorization failed (535 5.7.8 Authentication credentials invalid.)

Apr 1 00:10:09 TODD-Svr sSMTP[30855]: Authorization failed (535 5.7.8 Authentication credentials invalid.)

Apr 1 00:20:01 TODD-Svr sSMTP[899]: Authorization failed (535 5.7.8 Authentication credentials invalid.)

Apr 1 02:01:01 TODD-Svr sSMTP[4567]: Authorization failed (535 5.7.8 Authentication credentials invalid.)

Apr 1 12:03:02 TODD-Svr sSMTP[25055]: Authorization failed (535 5.7.8 Authentication credentials invalid.)

Apr 2 00:20:01 TODD-Svr sSMTP[7227]: Authorization failed (535 5.7.8 Authentication credentials invalid.)

 

 

 

Edited April 2, 20251 yr by TODDLT

8 hours ago, TODDLT said:

Is this a sign that something is failing?  

Typically, a sign of a DIMM going bad, unless it was a one-time thing.

On 4/3/2025 at 2:48 AM, JorgeB said:

Typically, a sign of a DIMM going bad, unless it was a one-time thing.

 

I have not seen those same errors, but I did find the below that appeared to occur during startup.

 

Quote

 

Apr 2 18:19:01 TODD-Svr kernel: pci 0000:01:00.0: BAR 9: no space for [mem size 0x00400000 64bit]

Apr 2 18:19:01 TODD-Svr kernel: pci 0000:01:00.0: BAR 9: failed to assign [mem size 0x00400000 64bit]

Apr 2 18:19:01 TODD-Svr kernel: pci 0000:01:00.0: BAR 7: no space for [mem size 0x00040000 64bit]

Apr 2 18:19:01 TODD-Svr kernel: pci 0000:01:00.0: BAR 7: failed to assign [mem size 0x00040000 64bit]

Apr 2 18:19:01 TODD-Svr kernel: pci 0000:00:01.0: PCI bridge to [bus 01]

Apr 2 18:19:01 TODD-Svr kernel: pci 0000:00:01.0: bridge window [io 0xe000-0xefff]

Apr 2 18:19:01 TODD-Svr kernel: pci 0000:00:01.0: bridge window [mem 0xf7600000-0xf76fffff]

Apr 2 18:19:01 TODD-Svr kernel: pci 0000:02:00.0: BAR 9: no space for [mem size 0x00400000 64bit]

Apr 2 18:19:01 TODD-Svr kernel: pci 0000:02:00.0: BAR 9: failed to assign [mem size 0x00400000 64bit]

Apr 2 18:19:01 TODD-Svr kernel: pci 0000:02:00.0: BAR 7: no space for [mem size 0x00040000 64bit]

Apr 2 18:19:01 TODD-Svr kernel: pci 0000:02:00.0: BAR 7: failed to assign [mem size 0x00040000 64bit]

.

.

Apr 2 18:19:13 TODD-Svr mcelog: failed to prefill DIMM database from DMI data

 

 

I also see the same failed login errors randomly occurring but not continually.

 

Newly noticed in the log:

 

Quote

 

Apr 2 18:19:02 TODD-Svr kernel: bond0: option primary: mode dependency failed, not supported in mode balance-rr(0)

.

.

Apr 2 18:19:19 TODD-Svr root: Verifying package networkstats-2022.08.25-x86_64-1.txz.

Apr 2 18:19:19 TODD-Svr root: Installing package networkstats-2022.08.25-x86_64-1.txz:

Apr 2 18:19:19 TODD-Svr root: PACKAGE DESCRIPTION:

Apr 2 18:19:19 TODD-Svr root: Package networkstats-2022.08.25-x86_64-1.txz installed.

Apr 2 18:19:19 TODD-Svr root: Starting the vnstat daemon...

Apr 2 18:19:19 TODD-Svr root: No interfaces found in database, adding available interfaces...

Apr 2 18:19:19 TODD-Svr root: Interface "tunl0" added. Warning: no bandwidth limit has been set.

Apr 2 18:19:19 TODD-Svr root: Interface "eth0" added with 1000 Mbit bandwidth limit.

Apr 2 18:19:19 TODD-Svr root: Interface "eth1" added with 1000 Mbit bandwidth limit.

Apr 2 18:19:19 TODD-Svr root: Interface "bond0" added with 2000 Mbit bandwidth limit.

Apr 2 18:19:19 TODD-Svr root: Interface "vhost0" added with 2000 Mbit bandwidth limit.

Apr 2 18:19:19 TODD-Svr root: -> 5 new interfaces found.

 

 

 

Any help or insight on the above is appreciated.

 

 

Those are unrelated and not necessarily a problem.