Failed to get Error Log Address Range APEI [Fix]
How difficult is that to install latest Operating system on a older hardware? Say CentOS 7.x on Wipro NetPower Model: Z1240 server? I thought NetPower Model: Z1240 is not that old and installing CentOS 7 on it should be a cake walk. But the reality is, stuck with BIOS error – “ERST Failed to get Error Log Address Range APEI: Can not request [mem xxxx] for APEI BERT registers”. So how did I fix this error? Does this mean Wipro NetPower Z1240 cannot run CentOS 7? Let’s find out below:
Before we talk about the solution, here’s what the server is powered by – Super Micro motherboard with Adaptec Raid Bios V5.2-0 [Build 17544].
Below is the snapshot of it.
Here’s the complete error message when the server booted for installation – Error ERST Failed to get Error Log Address Range APEI: Can not request [mem xxxx] for APEI BERT registers.
So how to fix that? I did bit of googling to see if someone has faced similar issue. Fortunately, I could find a hint by Super Micro that helped to solve the issue.
How to fix Failed to get Error Log Address Range APEI?
Step 1: Boot the server into the BIOS mode and navigate to «Advanced» > ACPI configuration . (Advanced Configuration and Power Interface)
Step 2: In the next screen, disable ACPI APIC Support as shown below:
Step 3: Save BIOS settings and reboot the server.
That’s it! Now you should be able to install CentOS 7.
Proxmox VE 3.2 released!
MimCom
Active Member
Has anyone tried an in-place upgrade from 2.3 to 3.2? http://pve.proxmox.com/wiki/Upgrade_from_2.3_to_3.0 was updated last December, not sure if there are any new gotchas.
Proxmox Staff Member
the described inplace upgrade uses the pve repository — this repo is 3.1 and will not change anymore.
so after doing the upgrade, you have a 3.1 system, which you can upgrade easily by following the guide here:
http://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_3.x_to_latest_3.2
Best regards,
Tom
Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation
MimCom
Active Member
I’ll shut it down tonight and run through the steps.
MimCom
Active Member
So I uninstalled apache2, renamed the logfile, and re-ran the upgrade. It choked on the lack of apache2, so I reinstalled and re-ran again.
Member
Proxmox VE is 64-bit only (amd64), so there are no i386 packages.
seems you did some custom settings on your box, querying i386 packages which are do not exist.
Problem: Failed to fetch https://enterprise.proxmox.com/debia. wheezy/Release Unable to find expected entry ‘pve-enterprise/binary-i386/Packages’ in Release file (Wrong sources.list entry or malformed file)
I found solution:
after check:
# dpkg —print-foreign-architectures
i’ve did:
# dpkg —remove-architecture i386
and after that: apt-get update & apt-get dist-upgrade
..works well
I have no idea why i386 arch was applied to system but solution may be usefull for someone.
[SOLVED] Connection failed (Error 500: failed to get address info for: pve: Name or service not known) — Solved
JeanPassos
Member
I have a proxmox in version 7.0-11 that is presenting the error, just when I click on its shell, on any pve and on the server itself.
Error failed (Error 500: failed to get address info for: pve: Name or service not known), has anyone ever experienced this error?
Moayad
Proxmox Staff Member
my first guess is the hostname is not correct, could you check on hostname , hostnamectl status , and /etc/hosts , otherwise, is anything in interesting in Syslog?
Best regards,
Moayad
Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation
JeanPassos
Member
JeanPassos
Member
Moayad
Proxmox Staff Member
Glad that you solved your issue yourself
I will go ahead and make your thread as [SOLVED] to help other people who have the same issue.
Best regards,
Moayad
Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation
About
The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!
Quick Navigation
Get your subscription!
The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.
Server boot problem after shutdown
Emanuele Rizzo
New Member
Hello, I installed Proxmox VE 5.1 on three nodes (SunFire x4140).
They worked until I shutdowned them. After the shutdown they don’t boot and reboot continuosly.
I reinstalled Proxmox VE on a node. If I reboot it, the node boots correctly but If I shutdow it, a boot problem recurs.
I tried to start the node with live linux but there wasn’t any bootlog file in /var/log to check.
Someone can help me, please?
fireon
Famous Member
Best Regards
Fireon
Deutsch PVE Dokumentation: http://deepdoc.at
DEEPDOC.AT — enjoy your brain
Emanuele Rizzo
New Member
fireon
Famous Member
Best Regards
Fireon
Deutsch PVE Dokumentation: http://deepdoc.at
DEEPDOC.AT — enjoy your brain
Emanuele Rizzo
New Member
I tried to install Ubuntu on these nodes and they work correctly, so I excluded hardware faults.
The server boots (I can see grub list) and starts proxmox. Just before the login console appears, it restarts
fireon
Famous Member
Best Regards
Fireon
Deutsch PVE Dokumentation: http://deepdoc.at
DEEPDOC.AT — enjoy your brain
Emanuele Rizzo
New Member
As I wrote in the first post there isn’t any record in logfile (syslog, kern.log — there aren’t bootlog and dmesg in /var/log directory).
The last record in syslog is:
«Jun 21 11:40:30 pvenode8 systemd[1]: Stopped PVE Cluster Ressource Manager Daemon.»
The last record in kern.log is:
«Jun 21 11:40:26 pvenode8 pve-guests[2673]: end task UPID venode8:00000A79:0000E484:5B2B728A:stopall::root@pam: OK»
I know that it is very strange, but it is so and I do not know what to do
fireon
Famous Member
Best Regards
Fireon
Deutsch PVE Dokumentation: http://deepdoc.at
DEEPDOC.AT — enjoy your brain
Emanuele Rizzo
New Member
fireon
Famous Member
Best Regards
Fireon
Deutsch PVE Dokumentation: http://deepdoc.at
DEEPDOC.AT — enjoy your brain
Emanuele Rizzo
New Member
I installed proxmox 5.2 and run commands you suggested after first boot
# dmesg -l warn
[ 0.052103] #2 #3 #4 #5
[ 0.172791] mtrr: your CPUs had inconsistent variable MTRR settings
[ 0.310070] ACPI: PCI Interrupt Link [LUB0] enabled at IRQ 23
[ 0.884531] ACPI: PCI Interrupt Link [LUB2] enabled at IRQ 22
[ 1.547231] [Firmware Warn]: GHES: Poll interval is 0 for generic hardware error source: 1, disabled.
[ 1.768600] ACPI: PCI Interrupt Link [LSA0] enabled at IRQ 21
[ 1.769997] ACPI: PCI Interrupt Link [LSA1] enabled at IRQ 20
[ 1.772070] ACPI: PCI Interrupt Link [LMAC] enabled at IRQ 23
[ 1.772479] ACPI: PCI Interrupt Link [LNEB] enabled at IRQ 19
[ 1.773024] aacraid 0000:07:00.0: can’t disable ASPM; OS doesn’t have ASPM control
[ 1.773744] aacraid: Comm Interface enabled
[ 1.778118] ACPI: PCI Interrupt Link [LE3B] enabled at IRQ 43
[ 1.937066] ACPI: PCI Interrupt Link [LNEA] enabled at IRQ 18
[ 2.097267] ACPI: PCI Interrupt Link [LNED] enabled at IRQ 17
[ 2.257192] ACPI: PCI Interrupt Link [LNEC] enabled at IRQ 16
[ 2.320858] ACPI: PCI Interrupt Link [LMAD] enabled at IRQ 22
[ 2.864919] ACPI: PCI Interrupt Link [LSA2] enabled at IRQ 21
[ 3.374308] mlx4_core 0000:83:00.0: Requested number of MACs is too much for port 1, reducing to 1
[ 3.374311] mlx4_core 0000:83:00.0: Requested number of VLANs is too much for port 1, reducing to 1
[ 4.099758] ACPI: PCI Interrupt Link [IIM0] enabled at IRQ 47
[ 4.656916] ACPI: PCI Interrupt Link [IIM1] enabled at IRQ 46
[ 5.200881] ACPI: PCI Interrupt Link [ISI0] enabled at IRQ 45
[ 5.202480] ACPI: PCI Interrupt Link [ISI1] enabled at IRQ 44
[ 5.203432] ACPI: PCI Interrupt Link [ISI2] enabled at IRQ 47
[ 14.116531] spl: loading out-of-tree module taints kernel.
[ 14.121195] znvpair: module license ‘CDDL’ taints kernel.
[ 14.121197] Disabling lock debugging due to kernel taint
[ 14.771197] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 19
[ 16.534663] device-mapper: thin: Data device (dm-3) discard unsupported: Disabling discard passdown.
[ 17.716772] new mount options do not match the existing superblock, will be ignored
# dmesg -l err
[ 1.547131] ERST: Failed to get Error Log Address Range.
[ 1.663332] APEI: Can not request [mem 0xd7fb8830-0xd7fb8883] for APEI BERT registers
[ 3.374321] mlx4_core 0000:83:00.0: command 0x34 failed: fw status = 0x2
[ 3.374387] mlx4_core 0000:83:00.0: Fail to get port 1 uplink guid
[ 3.374452] mlx4_core 0000:83:00.0: command 0x34 failed: fw status = 0x2
[ 3.374513] mlx4_core 0000:83:00.0: Fail to get port 2 uplink guid
[ 3.374571] mlx4_core 0000:83:00.0: Fail to get physical port id
[ 8.730955] print_req_error: I/O error, dev sr0, sector 1252960
[ 10.362073] print_req_error: I/O error, dev sr0, sector 1252964
[ 10.362132] Buffer I/O error on dev sr0, logical block 313241, async page read
[ 10.998074] print_req_error: I/O error, dev sr0, sector 248
[ 11.288948] print_req_error: I/O error, dev sr0, sector 248
[ 11.289004] Buffer I/O error on dev sr0, logical block 62, async page read
[ 11.295197] print_req_error: I/O error, dev sr0, sector 252
[ 11.295254] Buffer I/O error on dev sr0, logical block 63, async page read
[ 11.581948] print_req_error: I/O error, dev sr0, sector 512
[ 11.593198] print_req_error: I/O error, dev sr0, sector 512
[ 11.593280] Buffer I/O error on dev sr0, logical block 128, async page read
[ 12.436948] print_req_error: I/O error, dev sr0, sector 516
[ 12.437030] Buffer I/O error on dev sr0, logical block 129, async page read
[ 12.444073] print_req_error: I/O error, dev sr0, sector 4096
[ 12.444155] Buffer I/O error on dev sr0, logical block 1024, async page read
[ 12.465948] print_req_error: I/O error, dev sr0, sector 4100
[ 12.466029] Buffer I/O error on dev sr0, logical block 1025, async page read
[ 12.488064] Buffer I/O error on dev sr0, logical block 313238, async page read
[ 12.508938] Buffer I/O error on dev sr0, logical block 313239, async page read
[ 12.530938] Buffer I/O error on dev sr0, logical block 313238, async page read
[ 14.661600] k10temp 0000:00:18.3: unreliable CPU thermal sensor; monitoring disabled
[ 14.661773] k10temp 0000:00:19.3: unreliable CPU thermal sensor; monitoring disabled
[ 14.807763] Error: Driver ‘pcspkr’ is already registered, aborting.
Proxmox won’t start after IP change
horizn
Member
Hi,
I had working proxmox on Dell R700 server. Initially with private IP on WAN and LAN interface. I have changed WAN IP to external one and then Proxmox won’t start with following error:
AaronWalker
New Member
If your /etc/pve folder is empty, you have issues.
Regarding your network issue, when you switch it back to the original configuration, does it work?
Also R700s are really old.
wolfgang
Proxmox Retired Staff
please check the following files and if the ip addresses are correct.
/etc/hosts
/etc/corosync/corosync.conf
Best regards,
Wolfgang
Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation
horizn
Member
If your /etc/pve folder is empty, you have issues.
Regarding your network issue, when you switch it back to the original configuration, does it work?
Also R700s are really old.
horizn
Member
please check the following files and if the ip addresses are correct.
/etc/hosts
/etc/corosync/corosync.conf
horizn
Member
wolfgang
Proxmox Retired Staff
Best regards,
Wolfgang
Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation
horizn
Member
yes it is. My /etc/hosts file:
but when I am trying to run it:
horizn
Member
fabian
Proxmox Staff Member
Best regards,
Fabian
Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation
horizn
Member
My /etc/hosts looks like:
1.2.3.4 proxmox.domain.com proxmox pvelocalhost gdynia
192.168.100.1 proxmox.domain.com proxmox pvelocalhost gdynia
what is wrong here?
fabian
Proxmox Staff Member
Best regards,
Fabian
Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation
horizn
Member
wolfgang
Proxmox Retired Staff
This line must be like this. Assume your server name is gdynia
Best regards,
Wolfgang
Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation
horizn
Member
This line must be like this. Assume your server name is gdynia
horizn
Member
This line must be like this. Assume your server name is gdynia
fabian
Proxmox Staff Member
Best regards,
Fabian
Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation
horizn
Member
fabian
Proxmox Staff Member
Best regards,
Fabian
Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation
horizn
Member
About
The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!
Quick Navigation
Get your subscription!
The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.