Update to 8.2 broke the entire system

[Der Harry]

dpkg -l | grep grub-common doesnt return me anything, im getting very confused

That is no really kernel 6.5 issue

 

[Der Harry]

dpkg -l | grep grub-common doesnt return me anything, im getting very confused

WARNING here

We both assume that you are in the correct chroot.

 

[MrnMrk]

WARNING here

We both assume that you are in the correct chroot.

I am, also, i made progress, i have searched and installed the grub-cloud package and now i was able to make a config file and pin the right kernel. Is there anything else i should do before rebooting?

 

[Der Harry]

I am, also, i made progress, i have searched and installed the grub-cloud package and now i was able to make a config file and pin the right kernel. Is there anything else i should do before rebooting?

sooooooooooooooooooooooooooooooo NOOOOOOO
NOOOOOOOOOOOO

no cloud grub

NOOO!!!!
sorry thats just MYYY testmox

 

[MrnMrk]

sooooooooooooooooooooooooooooooo NOOOOOOO
NOOOOOOOOOOOO

no cloud grub

NOOO!!!!
sorry thats just MYYY testmox

hmm ok lol, lucky i havent rebooted yet, soo, what should i do now

 

[Der Harry]

hmm ok lol, lucky i havent rebooted yet, soo, what should i do now

remove the cloud grub package?

I warned you

Here from my (non virtual Proxmox - in legacy non secure boot non uefi)

I have no freaking idea - nor do I care - if you "probably" also need the uefi version. I don't know.

I know - for sure - that the cloud package is wrong.

root@proxmox:~# apt list --installed | grep grub
grub-common/stable,now 2.06-13+pmx2 amd64 [installed]
grub-pc-bin/stable,now 2.06-13+pmx2 amd64 [installed,automatic]
grub-pc/stable,now 2.06-13+pmx2 amd64 [installed]
grub2-common/stable,now 2.06-13+pmx2 amd64 [installed,automatic]

 

[Der Harry]

hmm ok lol, lucky i havent rebooted yet, soo, what should i do now

Any progress here?

 

[MrnMrk]

Any progress here?

I have solved everything, your steps partially were correct. However, there were some noticeable changes in my system.
I dont have a boot partition, instead boot its rooted in the same pve partition as /boot. Besides, I was missing the entire grub debian package, and certanly the "could" one was wrong, proxmox isnt using that. Proxmox uses the "grub-efi-amd64" one,
~# apt install grub-efi-amd64
~# update-grub
pinned the 6.5 kernel and worked like magic.

 

[Der Harry]

I have solved everything, your steps partially were correct. However, there were some noticeable changes in my system.
I dont have a boot partition, instead boot its rooted in the same pve partition as /boot. Besides, I was missing the entire grub debian package, and certanly the "could" one was wrong, proxmox isnt using that. Proxmox uses the "grub-efi-amd64" one,
~# apt install grub-efi-amd64
~# update-grub
pinned the 6.5 kernel and worked like magic.

I have really doubts that this is a 6.8.x issue - since - the grub.conf was missing.

But ... there is no reason that it's vanishing

Same for the grub-common / grub-<bootloader>

Have fun!

 

[Spaldo]

I just wanted to jump onto the thread and say that I went through the same situation. I updated proxmox 7.4 to 8.2 and I had the same issue where it froze at the same point as the video that @MrnMrk posted. I have gone through this thread and thankfully many of the questions that I am sure would have been asked, the back & forward with @Der Harry... helped. Thankfully I was able to pin the kernel back to 5.15.152 and now it boots. The proxmox itself says version 8.2.2.

I assume that when I followed the original guide from Proxmox to update from 7.2 to 8.x that I have done something wrong which broke the kernel/system on the newer 6.8 line.

So, my post, firstly to thank everyone that contributed and got me booting up again...

But secondly, what do I do now? How do I look at making the newer kernel working and be able to boot into it? I assume by booting back into 5.15 it isn't good with the new proxmox?

 

[MrnMrk]

I just wanted to jump onto the thread and say that I went through the same situation. I updated proxmox 7.4 to 8.2 and I had the same issue where it froze at the same point as the video that @MrnMrk posted. I have gone through this thread and thankfully many of the questions that I am sure would have been asked, the back & forward with @Der Harry... helped. Thankfully I was able to pin the kernel back to 5.15.152 and now it boots. The proxmox itself says version 8.2.2.

I assume that when I followed the original guide from Proxmox to update from 7.2 to 8.x that I have done something wrong which broke the kernel/system on the newer 6.8 line.

So, my post, firstly to thank everyone that contributed and got me booting up again...

But secondly, what do I do now? How do I look at making the newer kernel working and be able to boot into it? I assume by booting back into 5.15 it isn't good with the new proxmox?

I am keeping the kernel to 6.5 until 6.8 bugfix or 6.9 comes out, but my machine is being used as homelab, so is not a big deal for me, maybe for someone with enterprise level is, depends on you.

 

[joransrb]

You need to adopt parts of it.

[root@sysrescue ~]# cat /proc/partitions
major minor  #blocks  name

   8        0  209715200 sda
   8        1  209584111 sda1
   8       14       3072 sda14
   8       15     126976 sda15
  11        0     873472 sr0
  11        1       4096 sr1
   7        0     785932 loop0

[root@sysrescue ~]# mkdir -p /media/RESCUE

[root@sysrescue ~]# mount /dev/sda1 /media/RESCUE

# you might need to do "something something" here
# my testmox system only has one sda1 - I don't need this :)
#### [root@sysrescue ~]# mount /dev/sda1 /media/RESCUE/boot


[root@sysrescue ~]# mount -t proc proc /media/RESCUE/proc
[root@sysrescue ~]# mount -t sysfs sys /media/RESCUE/sys
[root@sysrescue ~]# mount -o bind /dev /media/RESCUE/dev
[root@sysrescue ~]# mount -o bind /run /media/RESCUE/run

# jump in chroot
[root@sysrescue ~]# chroot /media/RESCUE


# validate that we have somethinghere

# we need /boot stuff
root@sysrescue:/# ls /boot
config-6.5.13-5-pve  grub                     pve                      vmlinuz-6.5.13-5-pve
config-6.8.4-2-pve   initrd.img-6.5.13-5-pve  System.map-6.5.13-5-pve  vmlinuz-6.8.4-2-pve
efi                  initrd.img-6.8.4-2-pve   System.map-6.8.4-2-pve

# we need stuff in /etc that is plausible
root@sysrescue:/# cat /etc/hostname
testmox.something.lan

# something in /bin must also be present
root@sysrescue:/# ls /bin | wc -l
1681

root@sysrescue:/# proxmox-boot-tool kernel list
Manually selected kernels:
None.

Automatically selected kernels:
6.5.13-5-pve
6.8.4-2-pve

# pinning 6.5
root@sysrescue:/# proxmox-boot-tool kernel pin 6.5.13-5-pve
Setting '6.5.13-5-pve' as grub default entry and running update-grub.
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.8.4-2-pve
Found initrd image: /boot/initrd.img-6.8.4-2-pve
Found linux image: /boot/vmlinuz-6.5.13-5-pve
Found initrd image: /boot/initrd.img-6.5.13-5-pve
done

root@sysrescue:/# exit


[root@sysrescue ~]# reboot

thank you @Der Harry , this saved the day for me

 

[why-be-banned]

thank you, this works for me :

proxmox-boot-tool kernel pin 6.5.13-5-pve
proxmox-boot-tool refresh

 

[jprcrna]

Hello guys,
I don't know if i must create a new thread or write my problem here, tell me.

I have one proxmox (only one i don't know why) with this problem.
After last update 8.2.4, it can't boot anymore, stuck on "loading linux 6.8.12-1-pve ..."
So i tried to boot on other kernel, that's boot with the older 5.15.102, not with 6.5.x (i have not try all kernel)

I have read all this thread but i don't know what to do now for having a good boot with the last kernel
Can you help me please ?

 

[jprcrna]

Ok it's good !