You are not logged in.

#1 2018-04-27 01:33:19

strugart
Member
From: argentina
Registered: 2013-10-03
Posts: 10
Website

[RESOLVED]boot problems after kernel update

Hi. I did search this issue but alas I think is strange enough. The problem is that everytime i update the kernel grub finds the wrong initramfs to boot (the one before last). Now the mkinitcpio finish fine and the boot partition is mounted.
If I try rebooting after doing this systemd cant find the crypto module and cant boot the efi partition. If i go to a chroot enviroment mkinitcpio finds the before last version (as grub did, like somehow mkinitpcio did not commit the change on disk or dont have permissions to write) but if I reinstall the kernel in the chroot with pacman -S and i reboot it boots ok.
Any ideas?

Last edited by strugart (2018-04-29 14:22:08)

Offline

#2 2018-04-27 17:26:11

mrunion
Member
From: Jonesborough, TN
Registered: 2007-01-26
Posts: 1,938
Website

Re: [RESOLVED]boot problems after kernel update

More details please.

I assume you are using UEFI? It sounds like you don;t have the /boot path correctly mounted when doing an upgrade. Search on that and you will find copious amounts of help.


Matt

"It is very difficult to educate the educated."

Offline

#3 2018-04-28 12:21:24

strugart
Member
From: argentina
Registered: 2013-10-03
Posts: 10
Website

Re: [RESOLVED]boot problems after kernel update

yes I am using UEFI. That is the thing, when i searched i found /boot mounted issues (which makes sense), but in this case the /boot path is ok. That is way I called a strange issue.

Offline

#4 2018-04-28 14:11:20

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,427

Re: [RESOLVED]boot problems after kernel update

Post

mount
lsblk -f
tree /boot #Needs the tree package

during this apparently correct setup

Offline

#5 2018-04-29 12:43:23

strugart
Member
From: argentina
Registered: 2013-10-03
Posts: 10
Website

Re: [RESOLVED]boot problems after kernel update

V1del wrote:

Post

mount
lsblk -f
tree /boot #Needs the tree package

during this apparently correct setup

mount command:
https://ptpb.pw/jvtL

lsblk -f command

NAME   FSTYPE LABEL  UUID                                 MOUNTPOINT
sda                                                       
└─sda1 btrfs  data00 e7a236ff-76d1-4580-93c2-bea570abf5aa /run/media/strugart/data00
sdb                                                       
├─sdb1 vfat          565D-62E7                            /boot/efi
├─sdb2 swap          b3932f98-be2b-414a-aa83-dd23d13ca4da [SWAP]
└─sdb3 ext4          e623387a-5dfa-478f-8971-2499cb053b35 /
sdc                                                       
└─sdc1 ext4          00bf74f3-c50b-4abc-8594-614b939489ce /home
sdd                                                       
└─sdd1 ext4          4f10a40c-081f-4ff7-a55e-39cc1523b8bc /var

tree /boot
https://ptpb.pw/YCg-

As you can see is a correct setup, because it boot outside of this issue. No need for more snarky mentions

Last edited by strugart (2018-04-29 12:44:22)

Offline

#6 2018-04-29 14:42:07

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,427

Re: [RESOLVED]boot problems after kernel update

That does indeed look alright at first glance, sorry for the snark it wasn't intended, though I certainly see that it can be perceived as such.

If you have this resolved, would you mind posting how you solved it? It might help future searchers.

Offline

#7 2018-04-29 15:04:14

strugart
Member
From: argentina
Registered: 2013-10-03
Posts: 10
Website

Re: [RESOLVED]boot problems after kernel update

V1del wrote:

That does indeed look alright at first glance, sorry for the snark it wasn't intended, though I certainly see that it can be perceived as such.

If you have this resolved, would you mind posting how you solved it? It might help future searchers.

As metioned in a previous post i did a big update after my system being down for a few months. That of course lead to a few bugs and quirks. Debugging suchs issues lead to a broken grub install (it can be seen in the tree command, there are two grub.efi files). So when mkinitcpio did the write of a new initramfs it was seen by only one of the grub files. removing everything in the boot partition, reinstalling grub and the last kernel fixed the issue.

Offline

Board footer

Powered by FluxBB