search

jiangcuo / Proxmox-Arm64

Proxmox VE & PBS unofficial arm64 version
GNU Affero General Public License v3.0
387 stars 41 forks source link

Does not install on Orange Pi 5 #47

Closed cantalupo555 closed 1 year ago

cantalupo555 commented 1 year ago

I'm using Orange Pi 5 with Armbian Debian, kernel 6.5 edge.

At the end of the command it displays an error: apt install proxmox-ve postfix open-iscsi

I used the wiki as an installation reference: https://github.com/jiangcuo/Proxmox-Arm64/wiki/Install-Proxmox-VE-on-Debian-bullseye

Creating config file /etc/perl/XML/SAX/ParserDetails.ini with new version
Setting up open-iscsi (2.1.3-5) ...
Created symlink /etc/systemd/system/sysinit.target.wants/iscsid.service → /lib/systemd/system/iscsid.service.
Created symlink /etc/systemd/system/iscsi.service → /lib/systemd/system/open-iscsi.service.
Created symlink /etc/systemd/system/sysinit.target.wants/open-iscsi.service → /lib/systemd/system/open-iscsi.service.
Setting up libwbclient0:arm64 (2:4.13.13+dfsg-1~deb11u5) ...
Setting up libjson-glib-1.0-0:arm64 (1.6.2-1) ...
Setting up libbytes-random-secure-perl (0.29-1) ...
Setting up libvirglrenderer1:arm64 (0.8.2-5+deb11u1) ...
Setting up proxmox-backup-client (2.4.1-1) ...
Setting up liblttng-ust-ctl4:arm64 (2.12.1-1) ...
Setting up libknet1:arm64 (1.24-pve2) ...
Setting up shared-mime-info (2.0-1) ...
Setting up python3-requests (2.25.1+dfsg-2) ...
Setting up swtpm (0.8.0~bpo11+3) ...
Setting up python3-ldb (2:2.2.3-2~deb11u2) ...
Setting up thin-provisioning-tools (0.9.0-1) ...
Setting up libqt5core5a:arm64 (5.15.2+dfsg-9) ...
Setting up libtemplate-perl (2.27-1+b3) ...
Setting up libxml-libxml-perl (2.0134+dfsg-2+b1) ...
update-perl-sax-parsers: Registering Perl SAX parser XML::LibXML::SAX::Parser with priority 50...
update-perl-sax-parsers: Registering Perl SAX parser XML::LibXML::SAX with priority 50...
update-perl-sax-parsers: Updating overall Perl SAX parser modules info file...
Replacing config file /etc/perl/XML/SAX/ParserDetails.ini with new version
Setting up libwww-robotrules-perl (6.02-1) ...
Setting up criu (3.16-2) ...
Setting up libqt5dbus5:arm64 (5.15.2+dfsg-9) ...
Setting up libhtml-parser-perl (3.75-1+b1) ...
Setting up libxslt1.1:arm64 (1.1.34-4+deb11u1) ...
Setting up libcrypt-ssleay-perl (0.73.06-1+b3) ...
Setting up libsndfile1:arm64 (1.0.31-2) ...
Setting up liblttng-ust0:arm64 (2.12.1-1) ...
Setting up libiscsi7:arm64 (1.19.0-3) ...
Setting up libgfrpc0:arm64 (9.2-1) ...
Setting up libavahi-client3:arm64 (0.8-5+deb11u2) ...
Setting up libio-socket-ssl-perl (2.069-1) ...
Setting up libhttp-message-perl (6.28-1) ...
Setting up gnutls-bin (3.7.1-5+deb11u3) ...
Setting up libhttp-negotiate-perl (6.01-1) ...
Setting up librados2 (17.2.6-pve1) ...
Setting up libhttp-cookies-perl (6.10-1) ...
Setting up libpulse0:arm64 (14.2-2) ...
Setting up libgfchangelog0:arm64 (9.2-1) ...
Setting up libhtml-tree-perl (5.07-2) ...
Setting up libspice-server1:arm64 (0.14.3-2.1) ...
Setting up xsltproc (1.1.34-4+deb11u1) ...
Setting up cifs-utils (2:6.11-3.1+deb11u1) ...
update-alternatives: using /usr/lib/aarch64-linux-gnu/cifs-utils/idmapwb.so to provide /etc/cifs-utils/idmap-plugin (idmap-plugin) in auto mode
Setting up libqt5network5:arm64 (5.15.2+dfsg-9) ...
Setting up libcephfs2 (17.2.6-pve1) ...
Setting up swtpm-tools (0.8.0~bpo11+3) ...
Adding group `tss' (GID 121) ...
Done.
Warning: The home dir /var/lib/tpm you specified can't be accessed: No such file or directory
Adding system user `tss' (UID 112) ...
Adding new user `tss' (UID 112) with group `tss' ...
Not creating home directory `/var/lib/tpm'.
Setting up libradosstriper1 (17.2.6-pve1) ...
Setting up lxc-pve (5.0.2-2) ...
Created symlink /etc/systemd/system/multi-user.target.wants/lxc-monitord.service → /lib/systemd/system/lxc-monitord.service.
Created symlink /etc/systemd/system/multi-user.target.wants/lxc-net.service → /lib/systemd/system/lxc-net.service.
Created symlink /etc/systemd/system/multi-user.target.wants/lxc.service → /lib/systemd/system/lxc.service.
Setting up librbd1 (17.2.6-pve1) ...
Setting up libgfapi0:arm64 (9.2-1) ...
Setting up libcups2:arm64 (2.3.3op2-3+deb11u2) ...
Setting up libhttp-daemon-perl (6.12-1+deb11u1) ...
Setting up libthrift-0.13.0 (0.13.0-6) ...
Setting up glusterfs-common (9.2-1) ...
Adding group `gluster' (GID 122) ...
Done.
Setting up ceph-fuse (17.2.6-pve1) ...
Created symlink /etc/systemd/system/remote-fs.target.wants/ceph-fuse.target → /lib/systemd/system/ceph-fuse.target.
Created symlink /etc/systemd/system/ceph.target.wants/ceph-fuse.target → /lib/systemd/system/ceph-fuse.target.
Setting up corosync (3.1.7-pve1) ...
Created symlink /etc/systemd/system/multi-user.target.wants/corosync.service → /lib/systemd/system/corosync.service.
Setting up python3-rados (17.2.6-pve1) ...
Setting up librgw2 (17.2.6-pve1) ...
Setting up python3-rbd (17.2.6-pve1) ...
Setting up samba-libs:arm64 (2:4.13.13+dfsg-1~deb11u5) ...
Setting up glusterfs-client (9.2-1) ...
Setting up libsmbclient:arm64 (2:4.13.13+dfsg-1~deb11u5) ...
Setting up smbclient (2:4.13.13+dfsg-1~deb11u5) ...
Setting up python3-rgw (17.2.6-pve1) ...
Setting up python3-cephfs (17.2.6-pve1) ...
Setting up ceph-common (17.2.6-pve1) ...
Adding group ceph....done
Adding system user ceph....done
Setting system user ceph properties....done
chown: cannot access '/var/log/ceph/*.log*': No such file or directory
Setting file flags is only supported on regular files and directories, cannot set on '/var/log/journal'.
Created symlink /etc/systemd/system/multi-user.target.wants/ceph.target → /lib/systemd/system/ceph.target.
Created symlink /etc/systemd/system/multi-user.target.wants/rbdmap.service → /lib/systemd/system/rbdmap.service.
Setting up pve-qemu-kvm (7.2.0-8) ...
Setting up spiceterm (3.2-2) ...
Setting up liblwp-protocol-https-perl (6.10-1) ...
Setting up libwww-perl (6.52-1) ...
Setting up libproxmox-acme-perl (1.4.4) ...
Setting up libpve-apiclient-perl (3.2-1) ...
Setting up liblvm2cmd2.03:arm64 (2.03.11-2.1) ...
Setting up dmeventd (2:1.02.175-2.1) ...
Created symlink /etc/systemd/system/sockets.target.wants/dm-event.socket → /lib/systemd/system/dm-event.socket.
dm-event.service is a disabled or a static unit, not starting it.
Setting up libxml-parser-perl:arm64 (2.46-2) ...
Setting up libxml-twig-perl (1:3.52-1) ...
Setting up libnet-dbus-perl (1.2.0-1+b1) ...
Setting up libpve-common-perl (7.4-2) ...
Setting up lvm2 (2.03.11-2.1) ...
update-initramfs: deferring update (trigger activated)
Created symlink /etc/systemd/system/sysinit.target.wants/blk-availability.service → /lib/systemd/system/blk-availability.service.Created symlink /etc/systemd/system/sysinit.target.wants/lvm2-monitor.service → /lib/systemd/system/lvm2-monitor.service.
Created symlink /etc/systemd/system/sysinit.target.wants/lvm2-lvmpolld.socket → /lib/systemd/system/lvm2-lvmpolld.socket.
Setting up pve-cluster (7.3-3) ...
Created symlink /etc/systemd/system/multi-user.target.wants/pve-cluster.service → /lib/systemd/system/pve-cluster.service.
Job for pve-cluster.service failed because the control process exited with error code.
See "systemctl status pve-cluster.service" and "journalctl -xe" for details.
Setting up libpve-cluster-perl (7.3-3) ...
Setting up libpve-http-server-perl (4.2-3) ...
Setting up libpve-access-control (7.4.1) ...
Setting up libpve-cluster-api-perl (7.3-3) ...
Setting up librados2-perl (1.3-1) ...
Setting up libpve-storage-perl (7.4-3) ...
Setting up pve-firewall (4.3-4) ...
Created symlink /etc/systemd/system/multi-user.target.wants/pvefw-logger.service → /lib/systemd/system/pvefw-logger.service.
Created symlink /etc/systemd/system/multi-user.target.wants/pve-firewall.service → /lib/systemd/system/pve-firewall.service.
Job for pve-firewall.service failed because the control process exited with error code.
See "systemctl status pve-firewall.service" and "journalctl -xe" for details.
Job for pve-firewall.service failed because the control process exited with error code.
See "systemctl status pve-firewall.service" and "journalctl -xe" for details.
Setting up libpve-guest-common-perl (4.2-4) ...
Setting up pve-container (4.4-6) ...
Setting up pve-ha-manager (3.6.1) ...
watchdog-mux.service is a disabled or a static unit, not starting it.
Created symlink /etc/systemd/system/multi-user.target.wants/pve-ha-lrm.service → /lib/systemd/system/pve-ha-lrm.service.
Job for pve-ha-lrm.service failed because the control process exited with error code.
See "systemctl status pve-ha-lrm.service" and "journalctl -xe" for details.
Created symlink /etc/systemd/system/multi-user.target.wants/pve-ha-crm.service → /lib/systemd/system/pve-ha-crm.service.
Job for pve-ha-crm.service failed because the control process exited with error code.
See "systemctl status pve-ha-crm.service" and "journalctl -xe" for details.
Setting up qemu-server (7.4-4+pve1) ...
Created symlink /etc/systemd/system/multi-user.target.wants/qmeventd.service → /lib/systemd/system/qmeventd.service.
Setting up pve-manager (7.4-16) ...

Configuration file '/etc/apt/sources.list.d/pveport.list'
 ==> File on system created by you or by a script.
 ==> File also in package provided by package maintainer.
   What would you like to do about it ?  Your options are:
    Y or I  : install the package maintainer's version
    N or O  : keep your currently-installed version
      D     : show the differences between the versions
      Z     : start a shell to examine the situation
 The default action is to keep your current version.
*** pveport.list (Y/I/N/O/D/Z) [default=N] ? y
Installing new version of config file /etc/apt/sources.list.d/pveport.list ...
Installing new version of config file /etc/network/if-post-down.d/vlan ...
Installing new version of config file /etc/network/if-pre-up.d/vlan ...
ipcc_send_rec[1] failed: Connection refused
ipcc_send_rec[2] failed: Connection refused
ipcc_send_rec[3] failed: Connection refused
Unable to load access control list: Connection refused
Created symlink /etc/systemd/system/multi-user.target.wants/pvedaemon.service → /lib/systemd/system/pvedaemon.service.
Created symlink /etc/systemd/system/multi-user.target.wants/pveproxy.service → /lib/systemd/system/pveproxy.service.
Created symlink /etc/systemd/system/multi-user.target.wants/spiceproxy.service → /lib/systemd/system/spiceproxy.service.
Created symlink /etc/systemd/system/multi-user.target.wants/pvestatd.service → /lib/systemd/system/pvestatd.service.
Created symlink /etc/systemd/system/getty.target.wants/pvebanner.service → /lib/systemd/system/pvebanner.service.
Created symlink /etc/systemd/system/multi-user.target.wants/pvescheduler.service → /lib/systemd/system/pvescheduler.service.
Created symlink /etc/systemd/system/timers.target.wants/pve-daily-update.timer → /lib/systemd/system/pve-daily-update.timer.
Created symlink /etc/systemd/system/sysinit.target.wants/pvenetcommit.service → /lib/systemd/system/pvenetcommit.service.
Created symlink /etc/systemd/system/pve-manager.service → /lib/systemd/system/pve-guests.service.
Created symlink /etc/systemd/system/multi-user.target.wants/pve-guests.service → /lib/systemd/system/pve-guests.service.
Backing up lvm.conf before setting pve-manager specific settings..
'/etc/lvm/lvm.conf' -> '/etc/lvm/lvm.conf.bak'
Setting 'global_filter' in /etc/lvm/lvm.conf to prevent zvols from being scanned:
global_filter=["a|.*|"] => global_filter=["r|/dev/zd.*|"]
Job for pvestatd.service failed because the control process exited with error code.
See "systemctl status pvestatd.service" and "journalctl -xe" for details.
dpkg: error processing package pve-manager (--configure):
 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 (--configure):
 dependency problems - leaving unconfigured
Processing triggers for fontconfig (2.13.1-4.2) ...
Processing triggers for initramfs-tools (0.140) ...
ln: failed to create hard link '/boot/initrd.img-6.5.0-rc5-edge-rockchip-rk3588.dpkg-bak' => '/boot/initrd.img-6.5.0-rc5-edge-rockchip-rk3588': Operation not permitted
update-initramfs: Generating /boot/initrd.img-6.5.0-rc5-edge-rockchip-rk3588
update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.5.0-rc5-edge-rockchip-rk3588
Image Name:   uInitrd
Created:      Wed Sep 27 13:03:08 2023
Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
Data Size:    30158440 Bytes = 29451.60 KiB = 28.76 MiB
Load Address: 00000000
Entry Point:  00000000
update-initramfs: Armbian: Symlinking /boot/uInitrd-6.5.0-rc5-edge-rockchip-rk3588 to /boot/uInitrd
ln: failed to create symbolic link '/boot/uInitrd': Operation not permitted
update-initramfs: Symlink failed, moving /boot/uInitrd-6.5.0-rc5-edge-rockchip-rk3588 to /boot/uInitrd
renamed '/boot/uInitrd-6.5.0-rc5-edge-rockchip-rk3588' -> '/boot/uInitrd'
update-initramfs: Armbian: done.
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
Processing triggers for libc-bin (2.31-13+deb11u6) ...
Processing triggers for rsyslog (8.2102.0-2+deb11u1) ...
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for pve-ha-manager (3.6.1) ...
Errors were encountered while processing:
 pve-manager
 proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@orangepi5:~#
jiangcuo commented 1 year ago

https://github.com/jiangcuo/Proxmox-Arm64/wiki/Install-Proxmox-VE-on-Debian-bullseye#troubleshooting

You should review your /etc/hosts file according to the instructions above.

cantalupo555 commented 1 year ago

This is my file /etc/hosts

127.0.0.1       localhost.localdomain localhost

# The following lines are desirable for IPv6 capable hosts
::1     localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
2804:29b8:509d:e762:fe8a:f6f4:95c6:1400 debian
SuperKali commented 1 year ago

@cantalupo555 you should add the ip address of the orange pi with the current hostname

Just like this:

image

cantalupo555 commented 1 year ago

Hi, @SuperKali I only have IPv6. My IPv4 is local.

Thanks you.

SuperKali commented 1 year ago

@cantalupo555 if you see, when you do the command hostname --ip-address the ip address should be 192.168.1.125, this means you've configured it correctly.

cantalupo555 commented 1 year ago

@SuperKali

Thank you very much, it worked. I'm using Armbian based on Debian 12 (bookworm).

root@orangepi5:~# hostname --ip-address
2804:29b8:509d:e762::7a3 192.168.1.113

I'm going to change the domain to orangepi5.cantalupo.com.br and open the port to have external access to the proxmox panel via IPv6. image

Captura de tela 2023-09-28 183527