Start a Conversation

Solved!

Go to Solution

1 Rookie

 • 

2 Posts

2928

February 10th, 2022 09:00

DELL R630 Reboots automatically.

1. The server reboots automatically without any intimation. An event of this cycle occurs :

2022-2-10 23:49:10 SYS1003 System CPU Resetting.

2022-2-10 23:49:09 SYS1000 System is turning on.

2022-2-10 23:49:01 SYS1003 System CPU Resetting.

2022-2-10 23:49:01 SYS1001 System is turning off.

2022-2-10 23:48:46 PWR2262 The Intel Management Engine has reported an internal system error.

2022-2-10 23:48:45 RAC0703 Requested system hardreset.

2022-2-10 23:48:45 CPU0000 Internal error has occurred check for additional logs.

2022-2-10 23:48:43 PWR2262 The Intel Management Engine has reported an internal system error.

 What is the solution to it ?

2. If bios is set to default, does it affect the RAID ?

Moderator

 • 

3.5K Posts

September 3rd, 2024 13:18

Hi,

The error logs indicate that the system is rebooting due to a system CPU reset. This could be caused by several factors, including:

  • Hardware issues:
    • CPU overheating: Check the CPU temperature and ensure proper cooling.
    • Power supply issues: Verify that the power supply is functioning correctly and providing sufficient power.
    • Motherboard issues: Inspect the motherboard for any physical damage or loose connections.
  • Software issues:
    • Operating system (OS) bugs or conflicts: Update the OS to the latest version and check for any known issues.
    • Hypervisor (ESXi) bugs or conflicts: Update the hypervisor to the latest version and check for any known issues.
    • Driver issues: Ensure that all drivers are up-to-date and compatible with the hardware.
  • RAID controller issues:
    • RAID controller firmware issues: Update the RAID controller firmware to the latest version.
    • RAID configuration issues: Check the RAID configuration for any errors or inconsistencies.

To troubleshoot the issue, you can try the following steps:

  1. Check the hardware:
    • Inspect the server for any physical damage or loose connections.
    • Check the CPU temperature and ensure proper cooling.
    • Verify that the power supply is functioning correctly and providing sufficient power.
  2. Update the firmware and drivers:
    • Update the iDRAC firmware to the latest version.
    • Update the RAID controller firmware to the latest version.
    • Ensure that all drivers are up-to-date and compatible with the hardware.
  3. Check the software:
    • Update the OS to the latest version and check for any known issues.
    • Update the hypervisor (ESXi) to the latest version and check for any known issues.
    • Check the RAID configuration for any errors or inconsistencies.
  4. Monitor the system:
    • Use the iDRAC to monitor the system temperature, power consumption, and other vital statistics.
    • Look for any patterns or trends that might indicate a hardware or software issue.

Moderator

 • 

4.4K Posts

February 10th, 2022 13:00

Hello GeekToBe,

 

This can be resolved by updating BIOS and iDRAC. See Knowledge Base Article linked:

13G PowerEdge Server, PWR2262 "The Intel Management Engine has reported an internal system error"

https://dell.to/3GJb6lc

 

Resetting the BIOS to default won't affect the RAID, it may change your boot order or other custom BIOS settings.

But hold off on resetting BIOS to defaults to see that BIOS and iDARC firmware resolve the issue.

1 Rookie

 • 

3 Posts

March 8th, 2024 01:47

@DELL-Charles R​ hello Charles R. I face the same problem.

My Dell R730xd reboot loop at boot "Configuring memory ... Done" I see PWR2262 in lclog after upgrade BIOS from 2.17.0 to 2.18.1,and iDrac upgrade from 2.84.84.84 to 2.85.85.85.  

Lifecycle log:

2024-03-08T09:13:33+0800 LOG007 The previous log entry was repeated 1 times.
2024-03-08T09:13:23+0800 SYS1003 System CPU Resetting.
2024-03-08T09:13:22+0800 SYS1000 System is turning on.
2024-03-08T09:13:13+0800 SYS1003 System CPU Resetting.
2024-03-08T09:13:13+0800 SYS1001 System is turning off.
2024-03-08T09:12:58+0800 RAC0703 Requested system hardreset.
2024-03-08T09:12:57+0800 CPU0000 Internal error has occurred check for additional logs.
2024-03-08T09:12:57+0800 LOG007 The previous log entry was repeated 1 times.
2024-03-08T09:12:33+0800 PWR2262 The Intel Management Engine has reported an internal system error.
2024-03-08T09:12:34+0800 LOG007 The previous log entry was repeated 1 times.
2024-03-08T09:12:23+0800 SYS1003 System CPU Resetting.
2024-03-08T09:12:22+0800 SYS1000 System is turning on.
2024-03-08T09:12:13+0800 SYS1003 System CPU Resetting.
2024-03-08T09:12:13+0800 SYS1001 System is turning off.
2024-03-08T09:11:58+0800 RAC0703 Requested system hardreset.
2024-03-08T09:11:57+0800 CPU0000 Internal error has occurred check for additional logs.
2024-03-08T09:11:57+0800 LOG007 The previous log entry was repeated 1 times.
2024-03-08T09:11:33+0800 PWR2262 The Intel Management Engine has reported an internal system error.
2024-03-08T09:11:33+0800 LOG007 The previous log entry was repeated 1 times.
2024-03-08T09:11:23+0800 SYS1003 System CPU Resetting.
2024-03-08T09:11:22+0800 SYS1000 System is turning on.
2024-03-08T09:11:13+0800 SYS1003 System CPU Resetting.
2024-03-08T09:11:13+0800 SYS1001 System is turning off.
2024-03-08T09:10:58+0800 RAC0703 Requested system hardreset.
2024-03-08T09:10:57+0800 CPU0000 Internal error has occurred check for additional logs.
2024-03-08T09:10:57+0800 LOG007 The previous log entry was repeated 1 times.
2024-03-08T09:10:35+0800 PWR2262 The Intel Management Engine has reported an internal system error.

Moderator

 • 

3.9K Posts

March 8th, 2024 08:10

Hi,

 

Were you facing an issue with the error "PWR2262 The Intel Management Engine has reported an internal system error." and you updated the BIOS and iDRAC or you updated the firmware and faced the issue?

 

I may suggest you to do a rollback to check if the issue still persist. If yes, please remove all components except the below and try to turn on the server to check if still have an error:

 

System board
● One power supply unit
● One processor (CPU) in socket CPU1
● One memory module (DIMM) installed in socket A1
● Left control panel (for power button functionality)
● One backplane card

1 Rookie

 • 

2 Posts

September 3rd, 2024 05:10

We are facing the same problem, my server is getting rebooted 24-48 hours and it is a production system.

Model PowerEdge T440
Operating System VMware ESXi
Operating System Version 8.0.2 Update 2 Patch 40 (build-23825572) Kernel 8.0.2 (x86_64)
BIOS Version 2.21.1
iDRAC Firmware Version 7.00.00.172

Lifecycle Logs:

CTL129 The boot media of the Controller RAID Controller in Slot 4 is Disk.Virtual.239:RAID.Slot.4-1.
SYS1003 System CPU Resetting.
SYS1000 System is turning on.
ISM0007 The iDRAC Service Module communication with iDRAC has ended.
SYS1001 System is turning off.
SYS1003 System CPU Resetting.
USR0032 The session for ismUtil from 169.254.1.2 using REDFISH is logged off.
USR0030 Successfully logged in using ismUtil, from 169.254.1.2 and REDFISH.
ISM0047 The iDRAC Service Module (iSM) successfully connected with iDRAC by using the IPv4 protocol.
ISM0004 The iDRAC Service Module has successfully started communication with iDRAC.
CTL129 The boot media of the Controller RAID Controller in Slot 4 is Disk.Virtual.239:RAID.Slot.4-1.
SYS1003 System CPU Resetting.
SYS1000 System is turning on.
SYS1001 System is turning off.
SYS1003 System CPU Resetting.
ISM0007 The iDRAC Service Module communication with iDRAC has ended.

No Events found!

Top