New installation crashes on two systems

johnjdoe

New Member
Mar 1, 2010
20
0
1
Hi,

I use Proxmox since some years. I installed and used for some tests version 1.9 without problems on a DELL Optiplex MT-780.

I downloaded the 2.0 beta (kernel 2.6.32-6-pve) and did the installation procedure on the same machine without problems.

But after rebooting it, I receive after the Grub menu the following messages before the screen blanks:

Loading. please wait...
mount: mounting none on /dev failed: No such device
W: devtmps not available. falling back to tmpfs for /dev
INIT: version 2.08 booting
Using makefile-style concurrent boot in runlevel S.
Synthesizing the initial hotplug events...done
Wating for /dev to be fully populated...ACPI: I/O resource 0000:00:1f.3 [0x3040-0x305f] conflicts with ACPI region SMBI [0x3040-0x304f]

I tried the new Proxmox 2.0 RC with the same results. I tried both versions of Proxmox on a DELL Optiplex MT-790 with the same problems. I have the latest BIOS A10 and tried already a lot of things like disabling some BIOS features etc. but without success.

May I ask you some advices for debugging? Thank you in advance!
 
Reinstallation with the CD (.pve-cd-id.txt: 8e41f634-5892-11e1-908c-001517f8c3e5) I burned with the ISO from here: http://www.proxmox.com/downloads/proxmox-ve/iso-images/107-proxmox-ve-2

After a successful installation and a reboot from the machine I receive the following messages that I filmed with a cam because they appear just some seconds after the screen blanks:

Loading. please wait...
mount: mounting none on /dev failed: No such device
W: devtmps not available. falling back to tmpfs for /dev
INIT: version 2.08 booting
Using makefile-style concurrent boot in runlevel S.
Synthesizing the initial hotplug events...done
Waiting for /dev to be fully populated...ACPI: I/O resource 0000:00:1f.3 [0x3040-0x305f] conflicts with ACPI region SMBI [0x3040-0x304f])

This is reproducible.

Sorry Dietmar but the error is identically the same as the one I posted. I tried on two different DELL machines on which Proxmox 1.9 works fine.

Any hints for debuging are welcome.
 
That error message seem to be from an older kernel. Are you sure you boot the right partition? Wild guess: Maybe you have more than one disk inside that host and there is an old installation somewhere?
 
Dietmar, I *am* sure. I even kill all partitions with gparted. I only have one disk with one empty partition. I tried again to reinstall: no problem. But the same errors with the first boot. :-(

Imho it has to do with the DELL machines in combination of the new Proxmox. Version 1.9 runs well.
 
By the way and just a try, but I installed on the same machine a Debian squeeze without problems...

So the base of the error messages is in relation with pve 2.0 (beta and rc1).

It would be nice to have some hints for resolving the problem. Thank you in advance!
 
Same problem with 2 new Proliant ML380 G7 (Smart Array P410i Controller).
After installing Proxmox 2.0 rc1, I have the following error with the first boot:

The BIOS has corrupted hw-PMU resources ...

Don't know if this link can help:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=617891

linux-base/3 is in the kernel of Debian wheezy (testing):
do I have to install Debian wheezy, and then Proxmox on top of it?

thanks
 
Same problem with 2 new Proliant ML380 G7 (Smart Array P410i Controller).
After installing Proxmox 2.0 rc1, I have the following error with the first boot:

The BIOS has corrupted hw-PMU resources ...

Don't know if this link can help:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=617891

linux-base/3 is in the kernel of Debian wheezy (testing):
do I have to install Debian wheezy, and then Proxmox on top of it?

thanks

Could you report the bug here:
https://bugzilla.proxmox.com/ ?

because it's a different problem.
I'll try to help you.

To be sure: what kernel are you using ? proxmox-pve-kernel?
 
Last edited:
I use proxmox-ve_2.0-8d4f53a0-20.iso

thanks

Ok, so It doesn't boot at the first boot just after the installation ?
As proxmox use redhat 6.2 kernel (currently RHEL6.2 kernel 220.4.1.el6), it must be related to theses bug reports

I found on these bug report
http://bugs.centos.org/view.php?id=5493
that 2.6.32-220.4.2.el6.x86_64 works but not 2.6.32-220.7.1.el6.x86_64

also on hp website said that it should work with kernel > 2.6.32-131.0.15.el6
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02911009
 
> Ok, so It doesn't boot at the first boot just after the installation ?

yes

> As proxmox use redhat 6.2 kernel (currently RHEL6.2 kernel 220.4.1.el6), it must be related to theses bug reports

> I found on these bug report
> http://bugs.centos.org/view.php?id=5493
> that 2.6.32-220.4.2.el6.x86_64 works but not 2.6.32-220.7.1.el6.x86_64

I have the same error
screen.jpg

> also on hp website said that it should work with kernel > 2.6.32-131.0.15.el6
> http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02911009[/QUOTE]

any solution?
 

Attachments

  • screen.jpg
    screen.jpg
    12.4 KB · Views: 6
By chance I found yesterday the reason for my problem(s): The monitor was connected with a kvm switch to the computer (what not disturbed Proxmox 1.9). After connecting the monitor directly to the computer, it started without problems after the first install of Proxmox 2.x and now it runs fine.

Hope this helps!?
 

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!

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 yours easily in our online shop.

Buy now!