[SOLVED] Installation stuck

synthetic64 · Oct 4, 2020

Hi! I am trying to install proxmox but installation process stucks. Can't figure out why..

Here is log:

Code:

Version 2.19.1266. Copyright (C) 2020 American Megatrends, Inc.
BIOS Date: 06/02/2020 17:13:50 D33SL-12.01
Press <DEL> or <ESC> to enter setup.
[    0.000000] Linux version 5.4.34-1-pve (build@pve) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP PVE 5.4.34-2 (Thu, 07 May 2020 10:02:02 +0200) ()
[    0.000000] Command line: BOOT_IMAGE=/boot/linux26 ro ramdisk_size=16777216 rw nomodeset console=ttyS0,115200n8
[    0.000000] KERNEL supported cpus:
[    0.000000]   Intel GenuineIntel
[    0.000000]   AMD AuthenticAMD
[    0.000000]   Hygon HygonGenuine
[    0.000000]   Centaur CentaurHauls
[    0.000000]   zhaoxin   Shanghai
[    0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
[    0.000000] x86/fpu: xstate_offset[3]:  576, xstate_sizes[3]:   64
[    0.000000] x86/fpu: xstate_offset[4]:  640, xstate_sizes[4]:   64
[    0.000000] x86/fpu: Enabled xstate features 0x1b, context size is 704 bytes, using 'compacted' format.
[    0.000000] BIOS-provided physical RAM map:
[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009afff] usable
[    0.000000] BIOS-e820: [mem 0x000000000009b000-0x000000000009ffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000003e2dffff] usable
[    0.000000] BIOS-e820: [mem 0x000000003e2e0000-0x000000003e2fffff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x000000003e300000-0x000000007a20dfff] usable
[    0.000000] BIOS-e820: [mem 0x000000007a20e000-0x000000007a21dfff] reserved
[    0.000000] BIOS-e820: [mem 0x000000007a21e000-0x000000007defafff] usable
[    0.000000] BIOS-e820: [mem 0x000000007defb000-0x000000007dfd2fff] reserved
[    0.000000] BIOS-e820: [mem 0x000000007dfd3000-0x000000007e0a6fff] usable
[    0.000000] BIOS-e820: [mem 0x000000007e0a7000-0x000000007e3f8fff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x000000007e3f9000-0x000000007f347fff] reserved
[    0.000000] BIOS-e820: [mem 0x000000007f348000-0x000000007f7fffff] usable
[    0.000000] BIOS-e820: [mem 0x000000007f800000-0x000000007fffffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fd000000-0x00000000fe7fffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000047fffffff] usable
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] SMBIOS 3.0.0 present.
[    0.000000] DMI: Default string Default string/Default string, BIOS 5.13(D33SL-12.01) 06/02/2020
[    0.000000] tsc: Detected 2200.000 MHz processor
[    0.000033] last_pfn = 0x480000 max_arch_pfn = 0x400000000
[    0.000157] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT
[    0.000329] total RAM covered: 16376M
[    0.000906] Found optimal setting for mtrr clean up
[    0.000908]  gran_size: 64K  chunk_size: 16M         num_reg: 5      lose cover RAM: 0G
[    0.001019] last_pfn = 0x7f800 max_arch_pfn = 0x400000000
[    0.005426] found SMP MP-table at [mem 0x000fcf40-0x000fcf4f]
[    0.005712] check: Scanning 1 areas for low memory corruption
[    0.005719] Using GB pages for direct mapping
[    0.006582] RAMDISK: [mem 0x33a9b000-0x35d44fff]
[    0.006589] ACPI: Early table checksum verification disabled
[    0.006596] ACPI: RSDP 0x00000000000F05B0 000024 (v02 ALASKA)
[    0.006601] ACPI: XSDT 0x000000007E0A7098 0000AC (v01 ALASKA A M I    01072009 AMI  00010013)
[    0.006609] ACPI: FACP 0x000000007E0ABFA0 000114 (v06 ALASKA A M I    01072009 AMI  00010013)
[    0.006618] ACPI: DSDT 0x000000007E0A71D8 004DC1 (v02 ALASKA A M I    01072009 INTL 20061109)
[    0.006623] ACPI: FACS 0x000000007E3F7080 000040
[    0.006626] ACPI: FPDT 0x000000007E0AC0B8 000044 (v01 ALASKA A M I    01072009 AMI  00010013)
[    0.006631] ACPI: FIDT 0x000000007E0AC100 00009C (v01 ALASKA A M I    01072009 AMI  00010013)
[    0.006635] ACPI: MCFG 0x000000007E0AC1A0 00003C (v01 ALASKA A M I    01072009 MSFT 00000097)
[    0.006639] ACPI: WDAT 0x000000007E0AC1E0 0001AC (v01 ALASKA A M I    01072009 MSFT 00010013)
[    0.006644] ACPI: APIC 0x000000007E0AC390 000078 (v04 INTEL  TIANO    00000001 MSFT 00000000)
[    0.006648] ACPI: BDAT 0x000000007E0AC408 000030 (v01                 00000000      00000000)
[    0.006653] ACPI: HPET 0x000000007E0AC438 000038 (v01 ALASKA A M I    00000001 MSFT 01000013)
[    0.006657] ACPI: UEFI 0x000000007E0AC470 000042 (v01 ALASKA A M I    00000002      01000013)
[    0.006661] ACPI: SSDT 0x000000007E0AC4B8 001901 (v02 PmRef  CpuPm    00003000 INTL 20061109)
[    0.006666] ACPI: DMAR 0x000000007E0ADDC0 000060 (v01 INTEL  BDW      00000001 INTL 00000001)
[    0.006670] ACPI: SPCR 0x000000007E0ADE20 000050 (v02 A M I  APTIO V  01072009 AMI. 0005000D)
[    0.006674] ACPI: HEST 0x000000007E0ADE70 0000A8 (v01 INTEL  VND      00000001 INTL 00000001)
[    0.006679] ACPI: BERT 0x000000007E0ADF18 000030 (v01 INTEL  VND      00000001 INTL 00000001)
[    0.006683] ACPI: ERST 0x000000007E0ADF48 000230 (v01 INTEL  VND      00000001 INTL 00000001)
[    0.006687] ACPI: EINJ 0x000000007E0AE178 000150 (v01 INTEL  VND      00000001 INTL 00000001)
[    0.006692] ACPI: WSMT 0x000000007E0AE2C8 000028 (v01 ALASKA A M I    01072009 AMI  00010013)
[    0.006848] No NUMA configuration found
...
[   16.053280] systemd-udevd[1121]: Using default interface naming scheme 'v240'.
[   16.053444] systemd-udevd[1081]: Using default interface naming scheme 'v240'.
[   16.053795] systemd-udevd[1088]: Using default interface naming scheme 'v240'.
[   16.054396] systemd-udevd[1069]: Using default interface naming scheme 'v240'.
[   16.070684] systemd-udevd[1088]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
[   16.070714] systemd-udevd[1069]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
[   16.070833] igb 0000:05:00.0 enp5s0: renamed from eth4
[   16.138953] igb 0000:04:00.0 enp4s0: renamed from eth3
[   16.170908] systemd-udevd[1121]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
[   16.170910] systemd-udevd[1081]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
[   16.171032] igb 0000:03:00.0 enp3s0: renamed from eth2
[   16.182138] ixgbe 0000:0a:00.1: Multiqueue Enabled: Rx Queue count = 4, Tx Queue count = 4 XDP Queue count = 0
[   16.219441] igb 0000:02:00.0 enp2s0: renamed from eth0
[   16.339703] ixgbe 0000:0a:00.1: MAC: 6, PHY: 27, PBA No: 000700-000
[   16.345991] ixgbe 0000:0a:00.1: 00:e2:69:11:8d:65
[   16.404075] ixgbe 0000:0a:00.1: Intel(R) 10 Gigabit Network Connection
[   16.513228] systemd-udevd[1058]: Using default interface naming scheme 'v240'.
[   16.763387] ixgbe 0000:0b:00.0: Multiqueue Enabled: Rx Queue count = 4, Tx Queue count = 4 XDP Queue count = 0
[   16.900741] ixgbe 0000:0b:00.0: MAC: 6, PHY: 27, PBA No: 000700-000
[   16.907011] ixgbe 0000:0b:00.0: 00:e2:69:11:8d:66
[   16.966682] ixgbe 0000:0b:00.0: Intel(R) 10 Gigabit Network Connection
[   17.315387] ixgbe 0000:0b:00.1: Multiqueue Enabled: Rx Queue count = 4, Tx Queue count = 4 XDP Queue count = 0
[   17.452741] ixgbe 0000:0b:00.1: MAC: 6, PHY: 27, PBA No: 000700-000
[   17.459018] ixgbe 0000:0b:00.1: 00:e2:69:11:8d:68
[   17.518646] ixgbe 0000:0b:00.1: Intel(R) 10 Gigabit Network Connection
[   17.527052] ixgbe 0000:0a:00.0 eno1: renamed from eth1
[   17.594941] ixgbe 0000:0b:00.0 eno3: renamed from eth2
[   17.617422] ixgbe 0000:0a:00.1 eno2: renamed from eth0
[   17.652925] ixgbe 0000:0b:00.1 eno4: renamed from eth3
[   18.092032] pps pps4: new PPS source ptp4
[   18.096109] ixgbe 0000:0b:00.1: registered PHC device on eno4
[   18.330717] pps pps5: new PPS source ptp5
[   18.334860] ixgbe 0000:0b:00.0: registered PHC device on eno3
[   18.560002] pps pps6: new PPS source ptp6
[   18.564151] ixgbe 0000:0a:00.1: registered PHC device on eno2
[   18.876698] pps pps7: new PPS source ptp7
[   18.880905] ixgbe 0000:0a:00.0: registered PHC device on eno1

Motherboard: D33SL_6L
CPU: Intel Atom C3558
GPU: none. Have serial port instead.
RAM: DDR4 SO-DIMM 8+8Gb

oguz · Oct 5, 2020

hi,

where does it get stuck? does the installer just not show up, or what do you see on the screen?

there's a debug mode in the installer, where you can run commands between major install steps to see if things are working as expected. see the related documentation [0] (the section "Install Proxmox VE (Debug mode)" )

Code:

Starts the installation in debug mode. A console will be opened at several installation steps. This helps to debug the situation if something goes wrong. To exit a debug console, press CTRL-D. This option can be used to boot a live system with all basic tools available. You can use it, for example, to repair a degraded ZFS rpool or fix the bootloader for an existing Proxmox VE setup.

[0]: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#installation_installer

synthetic64 · Oct 5, 2020

Hi,
Here what i get in Debug Mode:

Code:

Version 2.19.1266. Copyright (C) 2020 American Megatrends, Inc.
BIOS Date: 06/02/2020 17:13:50 D33SL-12.01
Press <DEL> or <ESC> to enter setup.

Loading Proxmox Installer ...
Loading initial ramdisk ...
Welcome to the Proxmox VE 6.2 installer
initial setup startup
mounting proc filesystem
mounting sys filesystem
comandline: BOOT_IMAGE=/boot/linux26 ro ramdisk_size=16777216 rw quiet splash=verbose proxdebug nomodeset console=ttyS0,115200n8
loading drivers:  ahci mac_hid sdhci_pci i2c_ismt qat_c3xxx i2c_i801 pcspkr wdat_wdt intel_rapl_perf intel_cstate aesni_intel ghash_clmulni_intel crc32_pclmul crct10dif_pclmul kvm_intel intel_powerclamp x86_pkg_temp_thermal intel_rapl_common
searching for block device containing the ISO proxmox-ve-6.2-1
with ISO ID 'd39f6c1c-92f3-11ea-8823-3bf1bb1bc4e6'
testing again in 5 seconds
[    5.330842] sd 3:0:0:0: [sdb] No Caching mode page found
[    5.336179] sd 3:0:0:0: [sdb] Assuming drive cache: write through
testing device '/dev/sdb' for ISO
found Proxmox VE ISO
Debugging mode (type 'exit' or press CTRL-D to continue startup)
exit

after typing "exit" nothing happens... CTRL-D also doesn't do anything...

All installation menus seems to be graphical. My motherboard have no VGA. Does proxmox installer have ASCII installation menus? Can it be installed using serial console port? In this thread people say that it is possible to install proxmox withoug graphic card. How?

oguz · Oct 5, 2020

synthetic64 said:
All installation menus seems to be graphical. My motherboard have no VGA.

oh yeah that explains a lot

synthetic64 said:
Does proxmox installer have ASCII installation menus? Can it be installed using serial console port?

unfortunately no. however if you're limited by that, you can install the latest debian and add the repository on top [0]

[0]: https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Buster

synthetic64 · Oct 5, 2020

oguz said:
unfortunately no. however if you're limited by that, you can install the latest debian and add the repository on top [0]
[0]: https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Buster

Thank you. I will try that =)

synthetic64 · Oct 5, 2020

I started Debian install with options "vga=normal fb=false console=ttyS0,115200n8" and managed to get everything installed. The only thing that I concern is how much stuff (in megabytes) left from Debian that proxmox will never use? Thanks =)

oguz · Oct 6, 2020

synthetic64 said:
I started Debian install with options "vga=normal fb=false console=ttyS0,115200n8" and managed to get everything installed.

great!

synthetic64 said:
The only thing that I concern is how much stuff (in megabytes) left from Debian that proxmox will never use? Thanks =)

if you installed with minimal options this can be pretty much disregarded (proxmox is based on debian after all)

Search

Search

[SOLVED] Installation stuck

synthetic64

New Member

oguz

Proxmox Retired Staff

synthetic64

New Member

oguz

Proxmox Retired Staff

synthetic64

New Member

synthetic64

New Member

oguz

Proxmox Retired Staff