Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Sensor 0 Warning alert

Description

I recently got a Warning alert and can't figure out the problem or the reason I got it.

Warning
Sensor: 'Sensor #0' had an 'Assertion Event' (Software NMI ; OEM Event Data2 code = 00h ; OEM Event Data3 code = 28h)
2024-06-17 22:31:25

What does this alert mean and why did it happen?

Host ID: b882c7f28a571abc8d3a07cd87598dcc7dcbd72bd4eacc88b36baa3466bc5db4

Session ID: cec3c2cb-5519-edfe-6d20-93283ebc6547

Problem/Justification

None

Impact

None

Activity

Show:

Bug Clerk June 24, 2024 at 5:02 PM

This issue has now been closed. Comments made after this point may not be viewed by the TrueNAS Teams. Please open a new issue if you have found a problem or need to re-engage with the TrueNAS Engineering Teams.

Bug Clerk June 24, 2024 at 5:02 PM

Thanks for the bug report. These errors originate from the hardware board management controller, not TrueNAS. Suggest performing standard hardware testing including a memory test.

If your TrueNAS Mini system is still under warranty additional support can be found at

Bonnie Follweiler June 24, 2024 at 2:48 PM

Good Morning .

I have moved this ticket into our queue to review now.
An engineering representative will update with any further questions or details in the near future.

Marino Luna June 22, 2024 at 9:02 PM

ID Record Type Time Stamp GenID(Low) GenID(High) EvMRev Sensor Type Sensor # EvtDir Type Event Data1 Event Data2 Event Data3
00dfh 02h 6670f17dh 33h 00h 04h 13h 00h 6fh a3h 00h 28h

Event Data1 Software NMI
Event Data2 N/A
Event Data3 N/A

Marino Luna June 20, 2024 at 9:12 PM

Is this an automated response or you really need the Debug file again? because I marked the checkbox to upload the debug file through the TrueNAS administration web portal.

Not Applicable

Details

Assignee

Reporter

Labels

Components

Fix versions

Affects versions

Priority

More fields

Katalon Platform

Created June 20, 2024 at 9:01 PM
Updated June 24, 2024 at 5:02 PM
Resolved June 24, 2024 at 5:02 PM