Search results

Hi all during pve8to9 --full I get this error FAIL: systemd-boot meta-package installed. This will cause problems on upgrades of other boot-related packages. Remove 'systemd-boot' See https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#sd-boot-warning for more information. this is the output...

Hi all I'm getting same error after proxmox-kernel-helper upgrade from 8.1.0 to 8.1.1 I've understood that a fix has been already requested (thanks), but I haven't understood if I can do something right now before restarting proxmox as suggested after a kernel update Should I execute what's...

Now, I have downloaded again new kernel with apt-get update apt-get install pve-kernel-6.8.12-7-pve probably something was missing since it was downloaded again, even if it seems to be already in place Then I've manually updated grub using nano /etc/default/grub and replacing GRUB_DEFAULT...

I don't use ZFS My /boot/efi partition is this, on vfat sda2 │ vfat FAT32 7968-5017 1010.3M 1% /boot/efi So proxmox-boot-tool is still something that I have to check? I've read, but I'm not sure, that if I don't use ZFS, but vfat, proxmox-boot-tool...

Hi @cheiss I'm getting a similar error after I accidentally stopped last update I've created a new thread but I'm really worried to do a wrong thing. Any suggestion? Thanks

@leesteken thanks for your help, I've found those two pages related to upgrade from 7 to 8 https://pve.proxmox.com/wiki/Upgrade_from_7_to_8 https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#sysboot_determine_bootloader_used running efibootmgr -v I get Boot0004* proxmox...

after reboot, I still get old kernel Yes, my first installation was on PVE 7. I really don't know what is ESP, and I'm not an expert... I found these two threads on forum with ESP as tag https://forum.proxmox.com/tags/esp/ But they are old and I haven't found any help I have a single machine...

@leesteken nope, my first Proxmox installation, done more than 1 year ago, was directly on hw. The mess was due to my faulty stop during last update today, I always update when there is something available Thanks @gfngfn256, I'll try to reboot now

This is the result of update-initramfs -u update-initramfs: Generating /boot/initrd.img-6.8.12-7-pve 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. and...

apt-get dist upgrade result is Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. and the other command gives this WARNING: apt does not have a stable...

I get this Linux new 5.15.126-1-pve #1 SMP PVE 5.15.126-1 (2023-10-03T17:24Z) x86_64 The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux...

Hi all I accidentally stopped Proxmox update from 8.3.2 to 8.3.3 and this is the latest log I've got from update terminal et:6 http://download.proxmox.com/debian/pve bookworm/pve-no-subscription amd64 proxmox-kernel-6.8.12-7-pve-signed amd64 6.8.12-7 [103 MB] Get:7...

And also, with previous installation i had also a second disk named "DATI" as local-lvm, where most of VMs and LXCs where located Can I just mount it? To get back all VMs and LXCs without restoring them from backup, is there a way copying some folders/files from what I have in my old disk...

Thanks for you time! Now I've done all the others, I didn't before because I saw same subfolders already in place The only one it fails is this one ubuntu@ubuntu:~$ sudo mount /dev/sdc1 /media/old_pve/boot mount: /media/old_pve/boot: wrong fs type, bad option, bad superblock on /dev/sdc1...

I've added a debug to the pmxcfs command root@ubuntu:/# pmxcfs -l [main] notice: resolved node name 'ubuntu' to '192.168.1.91' for default node IP address fuse: device not found, try 'modprobe fuse' first [main] crit: fuse_mount error: No such file or directory [main] notice: exit proxmox...

Done I've exited from chroot, executed command modprobe fuse and reenter to chroot but I get same error root@ubuntu:/# pmxcfs -l [main] notice: resolved node name 'ubuntu' to '192.168.1.91' for default node IP address fuse: device not found, try 'modprobe fuse' first [main] crit: fuse_mount...

You mean something like this? 127.0.0.1 localhost.localdomain localhost 192.168.1.113 pve.beelink pve 192.168.1.91 pve.ubuntu ubuntu # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes...

BTW my previous installation was not in cluster and I'm not going to go to cluster with the new one

@fabian last command give me this error ubuntu@ubuntu:/media/old_pve$ sudo chroot /media/old_pve root@ubuntu:/# pmxcfs -l [main] crit: Unable to resolve node name 'ubuntu' to a non-loopback IP address - missing entry in '/etc/hosts' or DNS? and this is the /etc/hosts that seems to be the one...

@fabian @gfngfn256 Strangely the /etc/pve folder in the old disk is empty