Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
[SOLVED] Buster systems updating to different kernels
[SOLVED] Buster systems updating to different kernels
I have three systems running Buster. All are updated regularly with "apt upgrade". One of them is on kernel-image 4.14 the other two updated to kernel-image 4.15 sometime ago. What gives? I was under the impression the default kernel would be 4.14 since that's LTS.
Last edited by MH on 2018-04-13 08:07, edited 4 times in total.
DOS > Windows > Corel > RH > Libranet > Xandros > SuSE > Debian:KDE
"It is hard to free fools from the chains they revere." --Voltaire
"It is hard to free fools from the chains they revere." --Voltaire
Re: Buster systems updating to different kernels
Post the output of
on all boxes. I bet the one running 4.14 doesn't have the kernel metapackage.
Code: Select all
apt-cache policy linux-image-amd64
Re: Buster systems updating to different kernels
Here's the output:4D696B65 wrote:Post the output ofon all boxes. I bet the one running 4.14 doesn't have the kernel metapackage.Code: Select all
apt-cache policy linux-image-amd64
linux-image-amd64:
Installed: (none)
Candidate: 4.15+91
Version table:
4.15+91 500
500 http://mirror.applebred.net/debian buster/main amd64 Packages
OK so the "metapackage" is not installed. I wasn't even aware there was such a thing. Seems odd to me that it installed itself on two of my three systems but not the third. In any case, I installed it and my system updated to 4.15. Thanks for the clue.
DOS > Windows > Corel > RH > Libranet > Xandros > SuSE > Debian:KDE
"It is hard to free fools from the chains they revere." --Voltaire
"It is hard to free fools from the chains they revere." --Voltaire
Re: Buster systems updating to different kernels
OK. Now things are getting really weird. I installed the metapackage and my system automatically installed the new kernel image (4.15). I thought I was good to go, but after a reboot I found I was still running 4.14.
I ran dpkg-reconfigure and got an error about missing headers, so I installed the headers. Rebooted and I'm still running 4.14. Checked aptitude for broken packages and found none. Checked for installed kernels and it lists both 4.14 and 4.15 as installed. Ran update-grub and rebooted. Grub sees both kernels and all looks good. I reboot and 4.15 still does not show up in grub and uname -r confirms the system is booting to 4.14.
I ran dpkg-reconfigure and got an error about missing headers, so I installed the headers. Rebooted and I'm still running 4.14. Checked aptitude for broken packages and found none. Checked for installed kernels and it lists both 4.14 and 4.15 as installed. Ran update-grub and rebooted. Grub sees both kernels and all looks good. I reboot and 4.15 still does not show up in grub and uname -r confirms the system is booting to 4.14.
DOS > Windows > Corel > RH > Libranet > Xandros > SuSE > Debian:KDE
"It is hard to free fools from the chains they revere." --Voltaire
"It is hard to free fools from the chains they revere." --Voltaire
- sunrat
- Administrator
- Posts: 6412
- Joined: 2006-08-29 09:12
- Location: Melbourne, Australia
- Has thanked: 116 times
- Been thanked: 462 times
Re: Buster systems updating to different kernels
Do a full upgrade and see if it fixes it:
Code: Select all
apt update && apt full-upgrade
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ” Remember to BACKUP!
Those who have lost data
...and those who have not lost data YET ” Remember to BACKUP!
- Head_on_a_Stick
- Posts: 14114
- Joined: 2014-06-01 17:46
- Location: London, England
- Has thanked: 81 times
- Been thanked: 132 times
Re: Buster systems updating to different kernels
Did you check the "Advanced Options" sub-menu?MH wrote:4.15 still does not show up in grub
Are you sure that GRUB is reading grub.cfg on your Debian system?
deadbang
Re: Buster systems updating to different kernels
Did that previously then repeated. Problem remains. I also purged all 4.15 header files and reinstalled. Problem remains. It seems to be a grub problem.sunrat wrote:Do a full upgrade and see if it fixes it:Code: Select all
apt update && apt full-upgrade
DOS > Windows > Corel > RH > Libranet > Xandros > SuSE > Debian:KDE
"It is hard to free fools from the chains they revere." --Voltaire
"It is hard to free fools from the chains they revere." --Voltaire
Re: Buster systems updating to different kernels
I cannot find grub.cfg anywhere on the system.Head_on_a_Stick wrote:Did you check the "Advanced Options" sub-menu?MH wrote:4.15 still does not show up in grub
Are you sure that GRUB is reading grub.cfg on your Debian system?
DOS > Windows > Corel > RH > Libranet > Xandros > SuSE > Debian:KDE
"It is hard to free fools from the chains they revere." --Voltaire
"It is hard to free fools from the chains they revere." --Voltaire
- Head_on_a_Stick
- Posts: 14114
- Joined: 2014-06-01 17:46
- Location: London, England
- Has thanked: 81 times
- Been thanked: 132 times
Re: Buster systems updating to different kernels
How about /boot/grub/grub.cfg?
The `update-grub` wrapper script directs grub-mkconfig's output to that file.
You could try issuing
Replace X with the letter assigned to your main drive (`lsblk` is your friend here), *do not* append a partition number.
Perhaps run `update-grub` again afterwards and check /boot/grub/grub.cfg before rebooting.
The `update-grub` wrapper script directs grub-mkconfig's output to that file.
You could try issuing
Code: Select all
# grub-install /dev/sdX
Perhaps run `update-grub` again afterwards and check /boot/grub/grub.cfg before rebooting.
deadbang
Re: Buster systems updating to different kernels
I copy my primary drive to an identical backup drive. There was some kind of conflict between the BIOS and GRUB. This was caused by a change in the BIOS boot order. What I don't understand is how/why a drive OTHER THAN than the drive mounted as the system drive was getting the kernel update. In any case, swapping the drives and changing the BIOS boot order solved the problem.Head_on_a_Stick wrote:How about /boot/grub/grub.cfg?
The `update-grub` wrapper script directs grub-mkconfig's output to that file.
You could try issuingReplace X with the letter assigned to your main drive (`lsblk` is your friend here), *do not* append a partition number.Code: Select all
# grub-install /dev/sdX
Perhaps run `update-grub` again afterwards and check /boot/grub/grub.cfg before rebooting.
DOS > Windows > Corel > RH > Libranet > Xandros > SuSE > Debian:KDE
"It is hard to free fools from the chains they revere." --Voltaire
"It is hard to free fools from the chains they revere." --Voltaire
Re: [SOLVED] Buster systems updating to different kernels
Depending on the way you copy the drive/partition, you may need to change the UUIDs to make them unique using tune2fs.
You also might have to sync /boot/grub/grub.cfg on the different drives and do grub-update on all drives.
The problem is that when drives/partitions with same UUIDs exist, only the first one to be discovered in the hardware recognition process will be recognized.
This could explain all the problems you described.
You also might have to sync /boot/grub/grub.cfg on the different drives and do grub-update on all drives.
The problem is that when drives/partitions with same UUIDs exist, only the first one to be discovered in the hardware recognition process will be recognized.
This could explain all the problems you described.