PVE3.1 install

[DarwinCam]

Greetings,
I'm having issues with installation of VE from ISO files, I've tried both 3.1 and 2.3 and each fails when creating the volume group PVE where it claims it already exists.

Here's a screen shot of the 3.1 error:


and here's a screen shot of the 2.3 error:


It appears the accepted answer is that this is caused from a previous install, but I'm not buying it. This test install is on new Dell M620 (128Gb ram, dual intel 2.5 x 6 core proc) Raid 1 136Gb drive. Each screen shot reports errors before the group creation and I'm unsuccessful in figuring out what they mean. After each attempt, I have initialized the virtual drive that for all intents and purposes obliterates all drive content, reverting it back to empty.

I welcome any and all help to work through this, my goal is to get this up and running and test against our vmWare install.

Thank you,

Darwin

 

[m.ardito]

fake/sw raid? post raid controller details...

I'm not sure... it shows two disks, sda and sdc ?

Marco

 

[mir]

One configuration has this:

Internal controllers:
PERC S110 (software RAID)

 

[m.ardito]

if it is sw raid, disable it, try installing wheezy (mdraid), and then pve over it.
http://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Wheezy

Marco

 

[DarwinCam]

Hardware. PERC H710 2 physical disks 2 each 136Gb 15K rpm. My suspicion is that it would be possible that the installer doesn't know about the virtual disks. I'm going to break my raid and try it again.

 

[DarwinCam]

I'll look at this, thank you.

 

[DarwinCam]

I see in the description of the install it appears to be for AMD processor, (debian-7.2.0-amd64-netinst.iso) will it install on the server with Intel(R) Xeon(R) E5-2640?

 

[m.ardito]

it should amd64 stands for x86-64 http://en.wikipedia.org/wiki/X86-64

Marco

 

[mir]

That does not mean it is a kernel for AMD simply it means installing a 64bit OS.

 

[mir]

Maybe the driver is missing in the kernel?

 

[pirateghost]

I see in the description of the install it appears to be for AMD processor, (debian-7.2.0-amd64-netinst.iso) will it install on the server with Intel(R) Xeon(R) E5-2640?

AMD64 is the moniker for a 64bit version.

There is not an 'Intel' version. AMD 64 runs on all current AMD and Intel processors. It is not an 'AMD only' version.

Sent from my Nexus 5

 

[DarwinCam]

I'm running through the Debian install, and it appears to be going well. There are a couple of drivers one was for the QLogic raid card and one for the NIC that it wanted to install BUT since I'm using the idrac I'm not sure how to get them installed...guess I'll run through it once and see what happens.

Thank you to the replies about the AMD notation, I've not used Debian before so this path is some what new, we have a mix of RedHat/CentOS so just something more to learn...but that's not a bad thing.

 

[pirateghost]

AMD64 is not a Debian thing. It is a universal 64 bit thing. Some people label it AMD64, while others label it x86-64

Sent from my Nexus 5

 

[m.ardito]

yes, see that link above http://en.wikipedia.org/wiki/X86-64
<<x86-64 (also known as x64, x86_64 and amd64)>>

Marco

 

[DarwinCam]

Another hickup...

While I made it through the installation instructions here: http://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Wheezy I have an odd issue that I've not run into before. First a bit of backgroundDuring the install I get a prompt for two drivers one for the integrated 10Gbe NIC and the other for the RAID card. I download and install each driver, and they installed with no errors or warnings. For this first run install I choose the default disk/file layout, just to see what happens. The installation finishes and upon reboot, hangs after the bios load and the on-screen message says "Scaning for devices. Please wait, this may take several minutes...."

I suspect I know what's going on, but don't know how to get though it. During the install, when I'm allowed to choose the hard drive, I can see all drives (selections include onboard SD cards) BUT the drive of choice is a 136Gb and during the install it shows as 146Gb. Apparently it's not reading the drive size correctly, and I do not understand how it could show a larger size than it should be. Of course there's no option to change. I have not encountered an error like this before and hope the collective knowledge base here has a suggestion.

Thank you to everyone that has provided guidance thus far!

Darwin