You are not logged in.
I've read a lot of previous issue about that, but didn't found any solutions.
I've checked that uname -r and /proc/version is not matched with the kernel version that i've installed indeed uname -r and also /proc/version gives me
linux-6.2.10 instead of 6.2.11 .
I've also checked that /boot is mounted at the time of
pacman -Syu indeed
cat /proc/mounts | grep boot returns that /dev/sda1 is mounted in /boot as expected
When i downgrade to 6.2.10 version arch returns to boot, but i don't know how to do in order to upgrade kernel without breaking boot.
Down here i leave configuration of fstab:
# /dev/sda2
UUID=978f1226-b3c1-4d86-8f0d-39d99fe25782 / ext4 rw,relatime 0 1
# /dev/sda1
UUID=23B5-766D /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
# /dev/sda3
UUID=6eeb469d-2965-4e4d-a485-6a1ed4c609bf none swap defaults 0 0and of grub.cfg:
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}
set menu_color_normal=light-blue/black
set menu_color_highlight=light-cyan/blue
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_msdos
insmod ext2
set root='hd0,msdos2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 978f1226-b3c1-4d86-8f0d-39d99fe25782
else
search --no-floppy --fs-uuid --set=root 978f1226-b3c1-4d86-8f0d-39d99fe25782
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en-US
insmod gettext
fi
terminal_input console
terminal_output gfxterm
insmod part_msdos
insmod fat
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 23B5-766D
else
search --no-floppy --fs-uuid --set=root 23B5-766D
fi
insmod gfxmenu
loadfont ($root)/grub/themes/fallout-grub-theme-master/fixedsys-regular-32.pf2
insmod png
set theme=($root)/grub/themes/fallout-grub-theme-master/theme.txt
export theme
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=5
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/01_grub-customizer_menu_color_helper ###
### END /etc/grub.d/01_grub-customizer_menu_color_helper ###
### BEGIN /etc/grub.d/10_linux_proxy ###
menuentry "Arch Linux" --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-978f1226-b3c1-4d86-8f0d-39d99fe25782' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 978f1226-b3c1-4d86-8f0d-39d99fe25782
else
search --no-floppy --fs-uuid --set=root 978f1226-b3c1-4d86-8f0d-39d99fe25782
fi
echo 'Loading Linux linux ...'
linux /vmlinuz-linux root=UUID=978f1226-b3c1-4d86-8f0d-39d99fe25782 rw nvidia_drm.modeset=1 loglevel=3 quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux.img
}
submenu "Advanced options for Arch Linux"{
menuentry "Arch Linux, with Linux linux" --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-advanced-978f1226-b3c1-4d86-8f0d-39d99fe25782' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod fat
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 23B5-766D
else
search --no-floppy --fs-uuid --set=root 23B5-766D
fi
echo 'Loading Linux linux ...'
linux /vmlinuz-linux root=UUID=978f1226-b3c1-4d86-8f0d-39d99fe25782 rw nvidia_drm.modeset=1 loglevel=3 quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux.img
}
menuentry "Arch Linux, with Linux linux (fallback initramfs)" --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-fallback-978f1226-b3c1-4d86-8f0d-39d99fe25782' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod fat
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 23B5-766D
else
search --no-floppy --fs-uuid --set=root 23B5-766D
fi
echo 'Loading Linux linux ...'
linux /vmlinuz-linux root=UUID=978f1226-b3c1-4d86-8f0d-39d99fe25782 rw nvidia_drm.modeset=1 loglevel=3 quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux-fallback.img
}
menuentry "Arch Linux, with Linux linux-lts" --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-lts-advanced-978f1226-b3c1-4d86-8f0d-39d99fe25782' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod fat
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 23B5-766D
else
search --no-floppy --fs-uuid --set=root 23B5-766D
fi
echo 'Loading Linux linux-lts ...'
linux /vmlinuz-linux-lts root=UUID=978f1226-b3c1-4d86-8f0d-39d99fe25782 rw nvidia_drm.modeset=1 loglevel=3 quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux-lts.img
}
menuentry "Arch Linux, with Linux linux-lts (fallback initramfs)" --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-lts-fallback-978f1226-b3c1-4d86-8f0d-39d99fe25782' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod fat
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 23B5-766D
else
search --no-floppy --fs-uuid --set=root 23B5-766D
fi
echo 'Loading Linux linux-lts ...'
linux /vmlinuz-linux-lts root=UUID=978f1226-b3c1-4d86-8f0d-39d99fe25782 rw nvidia_drm.modeset=1 loglevel=3 quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux-lts-fallback.img
}
}
### END /etc/grub.d/10_linux_proxy ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows Boot Manager (on /dev/nvme0n1p1)' --class windows --class os $menuentry_id_option 'osprober-efi-705F-7D9D' {
insmod part_gpt
insmod fat
search --no-floppy --fs-uuid --set=root 705F-7D9D
chainloader /efi/Microsoft/Boot/bootmgfw.efi
}
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/31_uefi-firmware ###
if [ "$grub_platform" = "efi" ]; then
fwsetup --is-supported
if [ "$?" = 0 ]; then
menuentry 'UEFI Firmware Settings' $menuentry_id_option 'uefi-firmware' {
fwsetup
}
fi
fi
### END /etc/grub.d/31_uefi-firmware ###
### BEGIN /etc/grub.d/35_fwupd ###
### END /etc/grub.d/35_fwupd ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg
fi
### END /etc/grub.d/41_custom ###Last edited by madella (2023-04-17 07:26:28)
Offline
Virtually every single thread about this (and there are many) has a solution. It's almost always an issue with a /boot partition or a bootloader. What have you tried from your searches?
Online
Virtually every single thread about this (and there are many) has a solution. It's almost always an issue with a /boot partition or a bootloader. What have you tried from your searches?
https://bbs.archlinux.org/viewtopic.php?id=269588
https://bbs.archlinux.org/viewtopic.php?id=281748
https://bbs.archlinux.org/viewtopic.php?id=257054
https://bbs.archlinux.org/viewtopic.php?id=206473
I'm trying to figure out why pacman is not upgrading the kernel as expected. I won't reinstall kernel in live-iso chroot. I'm trying to do that with pacman.
Last edited by madella (2023-04-17 00:15:35)
Offline
OK, so you edited a whole lot of info into your post as I was replying.
If you unmount /boot, so you see the old kernel there? Is there a different grub.cfg there?
Online
if i unmount /boot, these are the file that i found:
drwxr-xr-x 2 root root 4096 Apr 17 03:22 .
drwxr-xr-x 17 root root 4096 Apr 17 02:38 ..
-rw-r--r-- 1 root root 0 Apr 17 01:22 BOOT_IS_NOT_MOUNTED
-rw------- 1 root root 72329000 Apr 17 01:59 initramfs-linux-fallback.img
-rw------- 1 root root 16392991 Apr 17 01:58 initramfs-linux.img
-rw-r--r-- 1 root root 12512192 Apr 17 00:27 vmlinuz-linux with no grub folder at all.
And the vmlinuz-linux link at the right version, with
file vmlinuz-linux i obtain:
/boot/vmlinuz-linux: Linux kernel x86 boot executable bzImage, version 6.2.11-arch1-1 (linux@archlinux) #1 SMP PREEMPT_DYNAMIC Thu, 13 Apr 2023 16:59:24 +0000, RO-rootFS, swap_dev 0XB, Normal VGA
Even if it that file should not be there, if i'm right
Excuse my wants to fix with pacman, but it's the only way to figure out how to do future kernel updates without breaking everything (and reinstall with live version)
(CHECK THAT YOUR CONFIG IS SIMILAR TO MINE BEFORE FOLLOWING MY STEPS)
0. umount /boot
1. removed every file exept BOOT_IS_NOT_MOUNTED (Windows' EFI is on another partition, so was not afraid of this) from unmounted /boot
1.1in order to do that i've done from super user
chattr -i /boot
cd /boot
rm vmlinuz-linux *.img
chattr +i /boot(i'll repeat myself, doublecheck before doing this command)
2. I've searched also in other location of / with:
sudo find / -name 'vmlinuz*' to find if there were other installation somewhere in order to clean the one not in /boot. (i found no other entries)
2. remounted /dev/sda1 to /boot
3. reinstalled last kernel (even if the one on unmounted boot was the right version of kernel... idk why my system is booting from that file, and after that why it was the wrong version anyway).
4. update grub
5. reboot and it works
I suggest to other people with my problem to remove entry CAREFULLY, double checking that boot is not mounted, otherwise you are going to break Arch boot and all other boot
I apologize for posting an already much discussed topic, but in any case I hadn't found a solution with that of the others
Last edited by madella (2023-04-17 08:00:15)
Offline
cat /proc/cmdlineBut you obviously updated the kerne w/o the /boot partition being mounted at some point.
Offline
cat /proc/cmdlineBut you obviously updated the kerne w/o the /boot partition being mounted at some point.
It was at the right point, and the /proc/cmdline give me always the older version
I don't understand where the version 6.1.10 binary was taken from.
Last edited by madella (2023-04-17 07:50:36)
Offline
and the /proc/cmdline give me always the older version
I actually wanted to see where you're booting from…
Offline
and the /proc/cmdline give me always the older version
I actually wanted to see where you're booting from…
it was this
BOOT_IMAGE=/vmlinuz-linux root=UUID=978f1226-b3c1-4d86-8f0d-39d99fe25782 rw nvidia_drm.modeset=1 loglevel=3 quietEDIT: In any case, aside from this oddity I wonder how all this could have happened, "simply" using pacman with a system booted correctly, and /boot correctly mounted
Last edited by madella (2023-04-17 08:07:09)
Offline
You're booting from the /boot partition but on Apr 17, 01:58 you updated the kernel w/o the boot partition mounted - for whatever reason, but that happened.
Offline
#Seth. Off topic a bit. How do so many folk get into the situation that they upgrade and "boot" is not mounted and then they are totally confused.??
I'm puzzled.
Offline
#Seth. Off topic a bit. How do so many folk get into the situation that they upgrade and "boot" is not mounted and then they are totally confused.??
I'm puzzled.
Last edited by madella (2023-04-17 16:14:52)
Offline
The individual case aside, usually some youtube tutorial will be at the other end of that question; resulting in a "bad" fstab (there's no requirement to mount /boot otherwise) and general confusion.
The first update then typically "breaks" the system.
@madella, did you maybe try to update the kernel from the chroot on Apr 17, 01:58 and at that point forgot to mount the /boot partition?
Are there any errors in the pacman log for the update that (originally) "broke" the system?
You could also inspect teh system journal for that boot to see what might have happened to the /boot partition.
All we know is that the kernel and initramfs didn't go onto the /boot partition but at some point falsely onto the root partition.
Offline
Thanks Seth.
#Madella, No expert here and no sarcasm intended. I just wanted to know how the problem arises so as to aware.
Offline
@madella, did you maybe try to update the kernel from the chroot on Apr 17, 01:58 and at that point forgot to mount the /boot partition?
I've never update kernel from chroot
Are there any errors in the pacman log for the update that (originally) "broke" the system?
You could also inspect teh system journal for that boot to see what might have happened to the /boot partition.
I'll do
@Madella, No expert here and no sarcasm intended. I just wanted to know how the problem arises so as to aware.
Ok, i apologize for this misunderstanding
Last edited by madella (2023-04-17 16:10:29)
Offline
Another thing we see is that people forget to mount their boot partition while setting things up, then mount it later not realizing that it's far too late and things were already set up there.
Last edited by Scimmia (2023-04-17 16:10:47)
Online
Another thing we see is that people forget to mount their boot partition while setting things up, then mount it later not realizing that it's far too late and things were already set up there.
Maybe yes, but not in this case, i've been using arch for at least a year, and the system never done that before. So i do not think that is something badly set
Last edited by madella (2023-04-17 16:13:49)
Offline