ZFS pool creation error on CM3588 (rockchip)

[brightside]

Hi helpful forum folks,

I recently installed Proxmox VE 8.3.3 on the eMMC of the FriendlyElec CM3588 (with Rockchip 3588) using their instructions and the official image on the FriendlyElec website .

I installed two 2tb NVME drives to the board. When I go to add ZFS pool, I get the following error:
"command /sbin/zpool list -HpPLo name,size,alloc,free,frag,dedup,health failed: exit code 1 (500)"

When I enter the command /sbin/zpool list -HpPLo name,size,alloc,free,frag,dedup,health into the shell, I get the following error:

"The ZFS modules cannot be auto-loaded. Try running 'modprobe zfs' as root to manually load them"

When I run modprobe zfs, I get the following error:

"modprobe: FATAL: Module zfs not found in directory /lib/modules/6.1.99"

I then attempted to install zfs-dkm`, zfsutils-linux, and pve-headers-$(uname -r). The ZFS packages seemed to install without issue, but when trying to install the pve headers, I got the following errors:

E: Unable to locate package pve-headers-6.1.99
E: Couldn't find any package by glob 'pve-headers-6.1.99'

I added the "No-Subscription" repository and updated all packages, still no dice ,(however I did get the following note: "Skipping acquire of configured file 'pve-no-subscription/binary-arm64/Packages' as repository 'http://download.proxmox.com/debian/pve bookworm InRelease' doesn't support architecture 'arm64'")

I then ran `apt-cache search pve-headers` and this is the output:
```
pve-headers-5.10-1-openeuler - The Proxmox Edge Kernel Headers
pve-headers-5.10-1-openeuler-dbgsym - debug symbols for pve-headers-5.10-1-openeuler
pve-headers-5.10-openeuler - Latest Proxmox Edge Kernel Headers
pve-headers-5.10.0-1-openeuler - The Proxmox Edge Kernel Headers
pve-headers-5.10.0-1-openeuler-dbgsym - debug symbols for pve-headers-5.10.0-1-openeuler
pve-headers-5.10.0-2-openeuler - The Proxmox Edge Kernel Headers
pve-headers-5.10.0-2-openeuler-dbgsym - debug symbols for pve-headers-5.10.0-2-openeuler
pve-headers-6.1-generic - Latest Proxmox Edge Kernel Headers
pve-headers-6.1.119-generic - The Proxmox Edge Kernel Headers
pve-headers-6.1.119-generic-dbgsym - debug symbols for pve-headers-6.1.119-generic
pve-headers-6.12-pve - Latest Proxmox Edge Kernel Headers
pve-headers-6.12.11-2-pve - The Proxmox Edge Kernel Headers
pve-headers-6.12.11-2-pve-dbgsym - debug symbols for pve-headers-6.12.11-2-pve
pve-headers-6.12.11-3-pve - The Proxmox Edge Kernel Headers
pve-headers-6.12.11-3-pve-dbgsym - debug symbols for pve-headers-6.12.11-3-pve
pve-headers-6.12.3-1-pve - The Proxmox Edge Kernel Headers
pve-headers-6.12.3-1-pve-dbgsym - debug symbols for pve-headers-6.12.3-1-pve
pve-headers-6.12.3-2-pve - The Proxmox Edge Kernel Headers
pve-headers-6.12.3-2-pve-dbgsym - debug symbols for pve-headers-6.12.3-2-pve
pve-headers-6.6-openeuler - Latest Proxmox Edge Kernel Headers
pve-headers-6.6-phytium - Latest Proxmox Edge Kernel Headers
pve-headers-6.6.0-4-openeuler - The Proxmox Edge Kernel Headers
pve-headers-6.6.0-4-openeuler-dbgsym - debug symbols for pve-headers-6.6.0-4-openeuler
pve-headers-6.6.0-5-openeuler - The Proxmox Edge Kernel Headers
pve-headers-6.6.0-5-openeuler-dbgsym - debug symbols for pve-headers-6.6.0-5-openeuler
pve-headers-6.6.0-6-openeuler - The Proxmox Edge Kernel Headers
pve-headers-6.6.0-6-openeuler-dbgsym - debug symbols for pve-headers-6.6.0-6-openeuler
pve-headers-6.6.0-openeuler - The Proxmox Edge Kernel Headers
pve-headers-6.6.0-openeuler-dbgsym - debug symbols for pve-headers-6.6.0-openeuler
pve-headers-6.6.0-phytium - The Proxmox Edge Kernel Headers
pve-headers-6.6.0-phytium-dbgsym - debug symbols for pve-headers-6.6.0-phytium
```

Here is output of `pveversion -v`:

```
proxmox-ve: 8.3.0 (running kernel: 6.1.99)
pve-manager: 8.3.3 (running version: 8.3.3/bbba1c53a1a65b24)
proxmox-kernel-helper: 8.1.0
ceph-fuse: 17.2.7-pve3
corosync: 3.1.7-pve3
criu: 3.17.1-2+deb12u1
dnsmasq: 2.90-4~deb12u1
glusterfs-client: 10.3-5
ifupdown: residual config
ifupdown2: 3.2.0-1+pmx11
libjs-extjs: 7.0.0-5
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.4
libpve-access-control: 8.2.0
libpve-apiclient-perl: 3.3.1
libpve-cluster-api-perl: 8.0.10
libpve-cluster-perl: 8.0.10
libpve-common-perl: 8.2.9+port1
libpve-guest-common-perl: 5.1.6
libpve-http-server-perl: 5.1.2
libpve-network-perl: 0.10.0+port
libpve-rs-perl: 0.9.0
libpve-storage-perl: 8.3.3
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.4.0-4
proxmox-backup-client: 3.3.2-2
proxmox-backup-file-restore: 3.3.2-2
proxmox-firewall: 0.5.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.0
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.6
proxmox-widget-toolkit: 4.3.4
pve-cluster: 8.0.10
pve-container: 5.2.2+port1
pve-docs: 8.3.1
pve-edk2-firmware: not correctly installed
pve-firewall: 5.1.0
pve-firmware: not correctly installed
pve-ha-manager: 4.0.6
pve-i18n: 3.2.4
pve-qemu-kvm: 9.2.0-2
pve-xtermjs: 5.3.0-3
qemu-server: 8.3.7
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.9.0+port
vncterm: 1.8.0
zfsutils-linux: 2.2.7-pve1
```

Thanks in advance for any help you can offer!

 

[leesteken]

Proxmox VE requires a 64-bit x86 processor (as the official manual will show you) and SD-cards or (e)MMC drives are a very bad choice for Proxmox and/or ZFS (as many threads on this forum will show you). Proxmox VE cannot run on ARM and the official Proxmox repository does not provide ARM software, which is probably the issue here. Maybe ask the FirienclyElec people to help you with your non-official-Proxmox and unsupported installation instead?

 

[brightside]

Proxmox VE requires a 64-bit x86 processor (as the official manual will show you) and SD-cards or (e)MMC drives are a very bad choice for Proxmox and/or ZFS (as many threads on this forum will show you). Proxmox VE cannot run on ARM and the official Proxmox repository does not provide ARM software, which is probably the issue here. Maybe ask the FirienclyElec people to help you with your non-official-Proxmox and unsupported installation instead?

Thank you @leesteken,

The computer has four NVME slots. I installed the proxmox OS on eMMC but am planning to use the NVME drives for data storage, in a RAIDZ1 configuration.

The SD card slot will likely be unused (unless someone recommends a good use for it in the proposed configuration?).

I saw someone else mention that they were able to achieve the same setup with this computer, so it must be possible, I am just having trouble finding the thread again.

 

[brightside]

Found the answer in a couple of website articles (here and here). Pre-compiled headers can already be found in /opt/archives of the FriendlyElec official Proxmox image. The following fixed things (after a reboot):

dpkg -i /opt/archives/*
apt install --reinstall zfs-dkms zfsutils-linux