Kernel from OMV 5.x is not upgraded after running omv-release-upgrade command

godzinilla · 16. Juni 2022

Code

linux-image-amd64:
  Installed: (none)
  Candidate: 5.16.12-1~bpo11+1
  Version table:
     5.16.12-1~bpo11+1 500
        100 http://httpredir.debian.org/debian bullseye-backports/main amd64 Packages
     5.10.120-1 500
        500 http://security.debian.org/debian-security bullseye-security/main amd64 Packages
     5.10.106-1 500
        500 http://deb.debian.org/debian bullseye/main amd64 Packages
     5.10.70-1~bpo10+1 -1
        100 /var/lib/dpkg/status

Alles anzeigen

ryecoaaron · 16. Juni 2022

That looks good too. Now, sudo apt-get install linux-image-amd64

godzinilla · 16. Juni 2022

Zitat von ryecoaaron

That looks good too. Now, sudo apt-get install linux-image-amd64

Finally something has changed:

Code

root@baranki:~# sudo apt-get install linux-image-amd64
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  linux-image-5.16.0-0.bpo.4-amd64
Suggested packages:
  linux-doc-5.16 debian-kernel-handbook
Recommended packages:
  apparmor
The following NEW packages will be installed:
  linux-image-5.16.0-0.bpo.4-amd64 linux-image-amd64
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 67.9 MB of archives.
After this operation, 452 MB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://httpredir.debian.org/debian bullseye-backports/main amd64 linux-image-5.16.0-0.bpo.4-amd64 amd64 5.16.12-1~bpo11+1 [67.9 MB]
Get:2 http://httpredir.debian.org/debian bullseye-backports/main amd64 linux-image-amd64 amd64 5.16.12-1~bpo11+1 [1,500 B]
Fetched 67.9 MB in 2s (45.0 MB/s)
Selecting previously unselected package linux-image-5.16.0-0.bpo.4-amd64.
(Reading database ... 88732 files and directories currently installed.)
Preparing to unpack .../linux-image-5.16.0-0.bpo.4-amd64_5.16.12-1~bpo11+1_amd64.deb ...
Unpacking linux-image-5.16.0-0.bpo.4-amd64 (5.16.12-1~bpo11+1) ...
Preparing to unpack .../linux-image-amd64_5.16.12-1~bpo11+1_amd64.deb ...
Unpacking linux-image-amd64 (5.16.12-1~bpo11+1) ...
Setting up linux-image-5.16.0-0.bpo.4-amd64 (5.16.12-1~bpo11+1) ...
I: /vmlinuz is now a symlink to boot/vmlinuz-5.16.0-0.bpo.4-amd64
I: /initrd.img is now a symlink to boot/initrd.img-5.16.0-0.bpo.4-amd64
/etc/kernel/postinst.d/dkms:
dkms: running auto installation service for kernel 5.16.0-0.bpo.4-amd64:.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.16.0-0.bpo.4-amd64
/etc/kernel/postinst.d/zz-update-grub:
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.16.0-0.bpo.4-amd64
Found initrd image: /boot/initrd.img-5.16.0-0.bpo.4-amd64
Found linux image: /boot/vmlinuz-5.10.0-0.bpo.9-amd64
Found initrd image: /boot/initrd.img-5.10.0-0.bpo.9-amd64
done
Setting up linux-image-amd64 (5.16.12-1~bpo11+1) ...

Alles anzeigen

And in the OMV/Kernel menu:

Code

root@baranki:~# sudo update-grub
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.16.0-0.bpo.4-amd64
Found initrd image: /boot/initrd.img-5.16.0-0.bpo.4-amd64
Found linux image: /boot/vmlinuz-5.10.0-0.bpo.9-amd64
Found initrd image: /boot/initrd.img-5.10.0-0.bpo.9-amd64
done

And now I am sucessfuly botted to the new kernel

Old kernels may be safely removed now, right?

What about the proxmox Kernel available from OMV/Kernel menu? Is it better?

ryecoaaron · 16. Juni 2022

Zitat von godzinilla

Old kernels may be safely removed now, right?

Yes.

Zitat von godzinilla

What about the proxmox Kernel available from OMV/Kernel menu? Is it better?

It is basically the Ubuntu LTS kernel. I run it on every amd64 system of mine. So, yes, I think it is better. If you use zfs, it definitely is.

Clusters · 17. Juni 2022

I have the same issue, but I'm a bit confused what grub has to do with that. Would it be possible to summarize what actual steps led to your success?
I've not changed anything with grub what-so-ever, but my boot disk isn't sda. It's sdb for an unknown reason.

godzinilla · 17. Juni 2022

Zitat von ryecoaaron

Yes.

It is basically the Ubuntu LTS kernel. I run it on every amd64 system of mine. So, yes, I think it is better. If you use zfs, it definitely is.

Thank you for your advice and your help I am really appreciate that! I will try the proxmox sonn too

Zitat von Clusters

I have the same issue, but I'm a bit confused what grub has to do with that. Would it be possible to summarize what actual steps led to your success?
I've not changed anything with grub what-so-ever, but my boot disk isn't sda. It's sdb for an unknown reason.

I have messed up my grub somewhere between upgrading of a system and installing nvidia drivers. We have just verifying if grub is correct.

Look at the post #6 of this thread:

Zitat von donh

Make sure the the files in /etc/apt/sources.list and /etc/apt/sources.list.d/ refer to bullseye and not buster,
apt clean all
apt update
apt dist-upgrade
If that doesn't get it.
apt install linux-headers-5.16.0-0.bpo.4-amd64 linux-headers-5.16.0-0.bpo.4-common linux-kbuild-5.16

Alles anzeigen

If it did not work for you, the sudo apt-get install linux-image-amd64 finally helped me.

Kernel from OMV 5.x is not upgraded after running omv-release-upgrade command

Jetzt mitmachen!

Tags