[SOLVED] Unable to install PVE from Debian 12 via official tutorial

L

linaste

New Member
Aug 20, 2023
21
3
3
Hi,

I recently tried to reinstall the whole PVE system.

After following the tutorial step by step, I always failed after installing the Proxmox VE kernel. Everytime I did systemctl reboot after that, it always stuck on grub command line. And when I ran
Bash: 
linux /boot/vmlinuz-6.5.11-7-pve root=/dev/mmcb1k0p2
boot
the system came to death.

Is there something wrong?
 
Log file while installing proxmox-default-kernel:
Bash: 
> apt install proxmox-default-kernel
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  proxmox-kernel-6.5 proxmox-kernel-6.5.11-7-pve-signed
The following NEW packages will be installed:
  proxmox-default-kernel proxmox-kernel-6.5 proxmox-kernel-6.5.11-7-pve-signed
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 99.6 MB of archives.
After this operation, 557 MB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://download.proxmox.com/debian/pve bookworm/pve-no-subscription amd64 proxmox-kernel-6.5.11-7-pve-signed amd64 6.5.11-7 [99.6 MB]
Get:2 http://download.proxmox.com/debian/pve bookworm/pve-no-subscription amd64 proxmox-kernel-6.5 all 6.5.11-7 [9,540 B]
Get:3 http://download.proxmox.com/debian/pve bookworm/pve-no-subscription amd64 proxmox-default-kernel all 1.0.1 [1,796 B]
Fetched 99.6 MB in 21s (4,709 kB/s)
Selecting previously unselected package proxmox-kernel-6.5.11-7-pve-signed.
(Reading database ... 49699 files and directories currently installed.)
Preparing to unpack .../proxmox-kernel-6.5.11-7-pve-signed_6.5.11-7_amd64.deb ...
Unpacking proxmox-kernel-6.5.11-7-pve-signed (6.5.11-7) ...
Selecting previously unselected package proxmox-kernel-6.5.
Preparing to unpack .../proxmox-kernel-6.5_6.5.11-7_all.deb ...
Unpacking proxmox-kernel-6.5 (6.5.11-7) ...
Selecting previously unselected package proxmox-default-kernel.
Preparing to unpack .../proxmox-default-kernel_1.0.1_all.deb ...
Unpacking proxmox-default-kernel (1.0.1) ...
Setting up proxmox-kernel-6.5.11-7-pve-signed (6.5.11-7) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 6.5.11-7-pve /boot/vmlinuz-6.5.11-7-pve
update-initramfs: Generating /boot/initrd.img-6.5.11-7-pve
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 6.5.11-7-pve /boot/vmlinuz-6.5.11-7-pve
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.5.11-7-pve
Found initrd image: /boot/initrd.img-6.5.11-7-pve
Found linux image: /boot/vmlinuz-6.2.16-20-pve
Found initrd image: /boot/initrd.img-6.2.16-20-pve
Found linux image: /boot/vmlinuz-6.1.0-16-amd64
Found initrd image: /boot/initrd.img-6.1.0-16-amd64
Found linux image: /boot/vmlinuz-6.1.0-15-amd64
Found initrd image: /boot/initrd.img-6.1.0-15-amd64
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Adding boot menu entry for UEFI Firmware Settings ...
done
Setting up proxmox-kernel-6.5 (6.5.11-7) ...
Setting up proxmox-default-kernel (1.0.1) ...
 
Ok so I can't help you with custom install sorry!

But what is the problem with proxmox creating the LVM? You use internal storage?
 
Because I don't really know why it should exist, for me it would only mess up my directory... I've got my system in internal storage, vms and cts in another NVMe drive, local-lvm can only confuse me.
 
You can proceed to the install with the LVM setuped by ProxMox and the install will not use your NVME Drive!

After that into the GUI of the console you can disable the storage local and local-LVM
And you can also create your storage with your NVME drive!

When disabling this storage created by default it will not propose when create a new VM!

Maybe should work for you and not confuse you!

1703919278213.png
 
Somehow I managed to complete the whole installation, it seems like I should run apt remove os-prober before the first reboot.
 
You must log in or register to reply here.
Top Bottom