Hints towards troubleshooting a Missing 'Deasserted' message in the SEL
Missing 'Deasserted' Messages in the System Event Log (SEL)
Some examples of how these may show in the log are:
Processor problem with missing a deasserted event:
2 | 12/19/2017 | 05:30:50 | Processor #0x0d | Transition to Non-recoverable | Asserted
3 | 12/19/2017 | 05:30:50 | Unknown #0x28 | | Asserted
4 | 12/19/2017 | 05:30:50 | Unknown #0x28 | | Asserted
5 | 12/19/2017 | 05:30:50 | Unknown #0x28 | | Asserted
6 | 12/19/2017 | 05:30:50 | Unknown #0x28 | | Asserted
7 | 12/19/2017 | 05:30:50 | Unknown #0x28 | | Asserted
8 | 12/19/2017 | 05:30:50 | Unknown #0x28 | | Asserted
9 | 12/19/2017 | 05:30:50 | Unknown #0x28 | | Asserted
a | 12/19/2017 | 05:30:50 | Unknown #0x28 | | Asserted
}}}
Error-correcting code (ECC) Memory problems with missing a deasserted event:
2 | 02/01/2018 | 16:35:33 | Memory #0x1b | Transition to Non-critical from OK | Asserted
3 | 02/01/2018 | 17:06:32 | Memory #0x1b | Transition to Critical from less severe | Asserted
}}}
Proceed as follows:
2. Restart the integrated Dell Remote Access Controller (iDRAC) with racadm racreset hard command.
Note: When iDRAC is booted up, again, it takes normally 1-2 minutes after power is applied to the system.
3. Clear SEL log.
To verify if the deasserted message were logged correctly, unplug the power cable at the chassis and insert it, again, a few seconds later. Then, the SEL should show if the message is logged.
Important Note: The link(s) to Dell are herein offered for your convenience and should not be viewed as an endorsement by Intel of the content, products, or services offered there.
A power cord from the chassis must have been removed; thus, the iDRAC noticed it and triggered the log.