Hi, this is my first time here. I am trying to install Proxmox 8.0 (proxmox-ve_8.0-2.iso) and I have issues.
I have verified the GPG signature and checksums before flashing the USB drive.
1. My LCD monitor displays an error message about input timing as soon as I start the installation.
I get the GRUB-like boot loader, and as soon as I pick the first option "Install Proxmox VE (Graphical)", the monitor becomes black and displays the error.
Monitor: DELL ST2320L
Output: VGA. There is no other video output.
I do not get such error with the Debian 12.0.2 installation media.
Can I start the installation from another machine using SSH? Any pointer would be appreciated.
Note: the same issue happens with Proxmox 8.1.
2. I cannot use the Live media as an APT repository
I installed Debian 12 and tried registering the APT repository from the live media:
/etc/apt/sources.list
apt does not complain, but it could not find packages to install proxmox-ve, openssh-server and open-iscsi.
3. I cannot install Proxmox manually using the .deb files under packages/
I found the packages needed for the installation were not in the APT repository, but in a different directory named "packages".
This was hard. I had to resolve packages dependencies by hand. I did it.
Then, when installing
I edited that file and removed `--quiet` to get more info, I got this:
systemctl status pve-firewall.service :
journalctl -xeu pve-firewall.service :
Skipping the rest, it's more of the same and repeats the output of the systemctl status command above.
The commands for
Since it was able to install the PVE kernel, I have booted that kernel and tried resuming installing the packages. Same error.
Now I am out of ideas. Please note this is a fresh Debian 12.0.2 installation, it has not been configured yet.
I saw that a new version came out (Proxmox 8.1). I am considering trying it, but I would like to avoid restarting from scratch if possible.
Also, the cluster has no network access.
Thank you for reading and for your interest in helping me.
/nb
I have verified the GPG signature and checksums before flashing the USB drive.
1. My LCD monitor displays an error message about input timing as soon as I start the installation.
I get the GRUB-like boot loader, and as soon as I pick the first option "Install Proxmox VE (Graphical)", the monitor becomes black and displays the error.
Code:
The current input timing is not supported by the monitor display.
Please change your input timing to 1920x1080@60Hz or any other monitor listed timing as per the monitor specifications.Monitor: DELL ST2320L
Output: VGA. There is no other video output.
I do not get such error with the Debian 12.0.2 installation media.
- Install Proxmox VE (Terminal UI): same error
- Install Proxmox VE (Serial Console Debug Mode): same error
- Rescue Boot: error, rpool not found. Goes back to the boot loader.
Can I start the installation from another machine using SSH? Any pointer would be appreciated.
Note: the same issue happens with Proxmox 8.1.
2. I cannot use the Live media as an APT repository
I installed Debian 12 and tried registering the APT repository from the live media:
/etc/apt/sources.list
Code:
deb [trusted=yes] file:/media/proxmox/PVE bookworm pveapt does not complain, but it could not find packages to install proxmox-ve, openssh-server and open-iscsi.
3. I cannot install Proxmox manually using the .deb files under packages/
I found the packages needed for the installation were not in the APT repository, but in a different directory named "packages".
This was hard. I had to resolve packages dependencies by hand. I did it.
Then, when installing
pve-firewall, the install failed with this message:
Code:
Setting up pve-firewall (5.0.2) ...
Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145.
Setting up libpve-storage-perl (8.0.1) ...
Setting up libpve-guest-common-perl (5.0.3) ...
Setting up pve-container (5.0.3) ...
Setting up pve-ha-manager (4.0.2) ...
watchdog-mux.service is a disabled or a static unit, not starting it.
Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145.
Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145.
Setting up qemu-server (8.0.6) ...
Setting up pve-manager (8.0.3) ...
Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145.
**dpkg:** error processing package pve-manager (--install)
installed pve-manager package post-installation script subprocess returned error exit status 1
**dpkg:** dependency problems prevent configuration of proxmox-ve:
proxmox-ve depends on pve-manager; however:
Package pve-manager is not configured yet.
**dpkg:** error processing package proxmox-ve (--install):
dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.36-9+deb12u2) ...
Processing triggers for man-db (2.11.2-2) ...
Processing triggers for pve-ha-manager (4.0.2) ...
Errors were encountered while processing:
pve-manager
proxmox-veI edited that file and removed `--quiet` to get more info, I got this:
Code:
Job for pve-firewall.service failed because the control process exited with error code.
See "systemctl status pve-firewall.service" and "journalctl -xeu pve-firewall.service" for details.
Job for pve-firewall.service failed because the control process exited with error code.
See "systemctl status pve-ha-lrmservice" and "journalctl -xeu pve-ha-lrm.service" for details.
Job for pve-firewall.service failed because the control process exited with error code.
See "systemctl status pve-ha-crm.service" and "journalctl -xeu pve-ha-crm.service" for details.systemctl status pve-firewall.service :
Code:
x pve-firewall.service - Proxmox VE firewall
Loaded: loaded (/lib/systemd/system/pve-firewall.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since <date>
hostname pve-firewall: ipcc_send_rec[1] failed: Connection refused
hostname pve-firewall: ipcc_send_rec[2] failed: Connection refused
hostname pve-firewall: ipcc_send_rec[3] failed: Connection refused
hostname pve-firewall: Unable to load access control list: Connection refused
hostname pve-firewall: ipcc_send_rec[1] failed: Connection refused
hostname pve-firewall: ipcc_send_rec[2] failed: Connection refused
hostname pve-firewall: ipcc_send_rec[3] failed: Connection refused
hostname pve-firewall: systemd[1]: pve-firewall.service: Control process exited, code=exited, status=111/n/a
hostname pve-firewall: systemd[1]: pve-firewall.service: Failed with result 'exit-code'.
hostname pve-firewall: systemd[1]: Failed to start pve-firewall-service - Proxmox VE firewall.journalctl -xeu pve-firewall.service :
Code:
The process' exit code is 'exited' and its exit status is 111.
Date hostname systemd[1]: pve-firewall.service: Failed with result 'exit-code'.
Subject: Unit failed
Defined-By: systemd
Support: https://www.debian.org/support
The unit pve-firewall.service has entered the 'failed' state with result 'exit-code'.Skipping the rest, it's more of the same and repeats the output of the systemctl status command above.
The commands for
pve-ha-lrm and pve-ha-crm give the exact same error (Connection refused).Since it was able to install the PVE kernel, I have booted that kernel and tried resuming installing the packages. Same error.
Now I am out of ideas. Please note this is a fresh Debian 12.0.2 installation, it has not been configured yet.
I saw that a new version came out (Proxmox 8.1). I am considering trying it, but I would like to avoid restarting from scratch if possible.
Also, the cluster has no network access.
Thank you for reading and for your interest in helping me.
/nb
Last edited: