Ubuntu

System wont boot - Stuck in Emergency Mode - ACPI

Asked by Dave

Our server was rebooted today and I get the following errors:

ACPI Error: No handler for Region [SYSI]
ACPI Error: Region IPMI (ID=7) has no handler
ACPI Error: Method parse/exectuion failed
ACPI Error: Method parse/exectuion failed
ACPI Exception: AE_NOT_EXIST

I have tried the following:
1. Went into GRUB and disabled ACPI
2. Went into GRUB and choose an older linux kernel
3. Removed all external USB devices

Any other help would greatly appreciated.

Thank you

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Dave
Solved:
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#1

Do you have the latest BIOS?
Have you tried setting the BIOS to failsafe settings and/or resetting it?

Revision history for this message
Dave (azdave) said : 		#2

The BIOS has not been updated for some time. I have not tried entering into BIOS yet. This all seems strange to me as the server has been fully functional for 1+ years.

Is there anything else you could recommend?

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#3

If you run:

echo "blacklist acpi_power_meter" | sudo tee -a /etc/modprobe.d/blacklist.conf > /dev/null

(basically adds the line to the file). Then reboot, is it OK?

Source:
https://www.suse.com/support/kb/doc/?id=7010449

Revision history for this message
Dave (azdave) said : 		#4

I have tried this and it still will not boot correctly....here is the exact screen I have showing:

ACPI Error: No handler for Region [SYSI]
ACPI Error: Region IPMI (ID=7) has no handler
ACPI Error: Method parse/exectuion failed
ACPI Error: Method parse/exectuion failed
ACPI Exception: AE_NOT_EXIST, Evaluating _PMC

Welcome to emergency mode! After logging in, type "journalctl -xb............

Press Enter for maintenance

Revision history for this message
Dave (azdave) said : 		#5

It looks like this issue may be resolved...I was provided with wrong information.