Proxmox VE 8.2 released!

[tirk]

Buenos días, tengo instalado PROXMOX8.2.7 en un disco ssd de 480GB con la partición /dev/sda3 LVM es de 319GB ¿como puedo re dimensionar la partición en vez de 319 sean 479GB? muchas gracias


Good morning, I have PROXMOX8.2.7 installed on a 480GB SSD with the /dev/sda3 LVM partition is 319GB, how can I resize the partition instead of 319 being 479GB? thank you so much

 

[Suporte-mclovin]

Esta nova versão é boa, principalmente por ser mais intuitiva para a visualização web

 

[mandapublicidad]

Hello, I'm new here.
I don't know if my query belongs in this thread, I apologize.

I have Proxmox 8.2.7 installed on a remotely managed server.
A few days ago, I wanted to update Proxmox, which ended in a loss of connection to the server. I tried restarting it, removing power remotely, but it didn't work.
When I connected a monitor to it, I see that it doesn't display anything. I restart it again, but it shows several version errors, having to activate a recovery boot.
This worked, but when I checked the available updates, I found that there are 2 DEBIAN updates that are "unavailable in the repository".

E: Failed to fetch https://metadata.ftp-master.debian....lkit/oath-toolkit_2.6.7-3.1+deb12u1_changelog Changelog unavailable for oath-toolkit=2.6.7-3.1+deb12u1 (404 Not Found [IP: 151.101.134.132 443]) : 100

E: Failed to fetch https://metadata.ftp-master.debian.org/changelogs/main/l/linux/linux_6.1.112-1_changelog Changelog unavailable for linux=6.1.112-1 (404 Not Found [IP: 151.101.134.132 443]) RC: 100

Both Updates are from the "http://security.debian.org/debian-security" repository

How can I resolve this?
Is it a good idea to disable that repository and update the PVE repository only? (I don't know if there are any dependencies).

Thank you very much.

 

[t.lamprecht]

Hello, I'm new here.
I don't know if my query belongs in this thread, I apologize.

I have Proxmox 8.2.7 installed on a remotely managed server.
A few days ago, I wanted to update Proxmox, which ended in a loss of connection to the server. I tried restarting it, removing power remotely, but it didn't work.
When I connected a monitor to it, I see that it doesn't display anything. I restart it again, but it shows several version errors, having to activate a recovery boot.
This worked, but when I checked the available updates, I found that there are 2 DEBIAN updates that are "unavailable in the repository".

E: Failed to fetch https://metadata.ftp-master.debian.org/changelogs/main/o/oath-toolkit/oath-toolkit_2.6.7-3.1+deb12u1_changelog Changelog unavailable for oath-toolkit=2.6.7-3.1+deb12u1 (404 Not Found [IP: 151.101.134.132 443]) : 100

E: Failed to fetch https://metadata.ftp-master.debian.org/changelogs/main/l/linux/linux_6.1.112-1_changelog Changelog unavailable for linux=6.1.112-1 (404 Not Found [IP: 151.101.134.132 443]) RC: 100

Both Updates are from the "http://security.debian.org/debian-security" repository

How can I resolve this?
Is it a good idea to disable that repository and update the PVE repository only? (I don't know if there are any dependencies).

Thank you very much.

This is the general 8.2 release thread, please open a new one for such not directly related issues.
There it would be good to describe how you installed Proxmox VE (official ISO or on top of Debian) and what you mean with "rescue mode" (the grub boot entry for an older Kernel?) also post all configured repos, like the ouput of

head -n-0 /etc/apt/sources.list /etc/apt/sources.list.d/*

 

[fabian]

for the Debian security repository, changelogs used to not be published on the metadata server until they were imported into the next stable point release. it seems to have been improved, but there might still be some delay between package upload and metadata import, since security uploads are handled in a private, separate infrastructure.. both changelogs are online for me (now ).

 

[XabiX]

Any idea on when we can expect 8.3 with 6.10 kernel? Required for r8126 drivers in the kernel etc...

Merci

 

[mandapublicidad]

This is the general 8.2 release thread, please open a new one for such not directly related issues.
There it would be good to describe how you installed Proxmox VE (official ISO or on top of Debian) and what you mean with "rescue mode" (the grub boot entry for an older Kernel?) also post all configured repos, like the ouput of

head -n-0 /etc/apt/sources.list /etc/apt/sources.list.d/*

Thank you for your reply, I apologize for taking so long to reply.

When I read your reply, the packages were already available. Before replying, I wanted to run the update as I have done before.
From that moment on, my server behaved very strangely at boot time. Sometimes it booted well, but many times it didn't. Not even from the grub "recovery mode" of previously installed versions.

As the system was too unstable, I performed a clean install of 8.2 and 8.1. Both installed well, but behaved the same way. I don't understand why when migrating from 7.4 to 8.1 the system worked as expected.

Finally, I performed a clean install of 7.4, which is the version before the migration.
Now the server is stable.

My server is an "Intel Xeon E-2286M, 64GB RAM, 2 x NVME + 1 SATA, 2 x ETH GB. Purchased in 2020".

 

[gfngfn256]

I performed a clean install of 8.2 and 8.1

When you say clean - do you mean a completely wiped OS disk?
IDK your setup on the other disks (NVME/SATA), ZFS, LVMs etc. But if I were you I would start completely clean. I assume you have backups of any LXCs & VMs. You can later try & restore them - once you have a STABLE system.
What NICS are those?

 

[mandapublicidad]

When you say clean - do you mean a completely wiped OS disk?
IDK your setup on the other disks (NVME/SATA), ZFS, LVMs etc. But if I were you I would start completely clean. I assume you have backups of any LXCs & VMs. You can later try & restore them - once you have a STABLE system.
What NICS are those?

After many attempts to recover the system with version 8.2, I decided to change the disk for a new one, and install everything from scratch.

I performed the installation from the proxmox ISO on a brand new disk (SATA 1TB).
I find it strange that the installation of version 8.1 did not work, since it is the version that I installed 6 months ago when I migrated from version 7.4 that I had installed to 8.1.

Fortunately, I had backups of my machines, so installing from scratch was not a problem.
The strange thing is that I could not install version 8.1 again, having to return to version 7.4 to provide service.

Now, version 7.4 seems stable.

The 2 NVME disks are in ZFS.

My NICs:
Ethernet controller: Intel Corporation Ethernet Connection (7) I219-V (rev 10)
Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)

I've been using proxmox for 2 years, previously I was using vmware.
My server has been running 24/7 for 4 years. I've never had any issues with it until this problem.

 

[gfngfn256]

I decided to change the disk for a new one, and install everything from scratch.

So even if you remove ALL disks from the system (including those 2 NVMEs) - just having the single clean sata disk connected - you were unable to install PVE 8.2 ? This is rather surprising to me. What CPU, MB & RAM do you have? Your NICs seem pretty generic.

 

[mandapublicidad]

So even if you remove ALL disks from the system (including those 2 NVMEs) - just having the single clean sata disk connected - you were unable to install PVE 8.2 ? This is rather surprising to me. What CPU, MB & RAM do you have? Your NICs seem pretty generic.

I disconnected the NVME drives and left only the SSD to do the clean install.
I was very surprised/puzzled that the installation of PVE 8.1 or 8.2 finished correctly, but after rebooting the server, grub was launched and then... black screen.

If memory serves me right, before the update that failed, my PVE was version 8.2.3.

I ended up desperate, because I did not understand the problem. Everything pointed to a hardware problem.

As a last resort, before giving up, I installed PVE version 7.4 and it worked!!!. I updated PVE and it worked. I installed the NVME HDDs and it detected them correctly.I set up the network (vlans) and restored the virtual machines and they all worked as expected (I just had to change the hardware parameter of the windows machines: "machine: PC-i440fx-8.1" to "machine: pc-q35-7.2").

My little server:
CPU: Intel(R) Xeon(R) E-2286M CPU @ 2.40GHz (8 cores - 16 threads)
MotherBoard: SYWZ S210H
RAM: 2x Samsung 32GB DDR4 2666MHz

As soon as I can, I'll buy a new computer, migrate the virtual machines and re-run the tests. I don't know what happened and it puzzles me a lot.

Thanks for your concern about my problem.

 

[gfngfn256]

but after rebooting the server, grub was launched and then... black screen.

Sounds like adding nomodeset to the kernel boot line would probably help.
BTW, when you had the "black screen" was the PVE instance available/accessible on the NW?

 

[jerrythea]

Any idea on when we can expect 8.3 with 6.10 kernel? Required for r8126 drivers in the kernel etc...

Merci

I am also tracking this for the WisdPi 5 gbs USB adapter.

I have confirmed full bidirectional speed on kernel 6.10 (Fedora 40).

On kernel 6.8 best I can get is full speed down, 1/2 speed up (or vice versa, cannot remember right this second).

 

[tirk]

How to make backups of containers and MV on a USB disk?

 

[t.lamprecht]

How to make backups of containers and MV on a USB disk?

This has nothing to do with the Proxmox VE 8.2 release, please open a new thread for such questions.

In advance: You can format any USB disk with a file-system and mount it on the PVE host, then you can add the path it's mounted too to PVE as storage and use that as backup target.

 

[mandapublicidad]

Sounds like adding nomodeset to the kernel boot line would probably help.
BTW, when you had the "black screen" was the PVE instance available/accessible on the NW?

The system was not available after GRUB, nor did I have network access. I did not try nomodeset.
I have the HDD where the failed version is loaded. As soon as I have the opportunity for a new server, I will perform the VM migration and do new tests.
Thank you very much.

 

[evrimsel]

Thanks to everyone who contributed.