[SOLVED]System doesn't mount boot after update

[old cypress]

Hi, so I've done full system update after a around month of not doing so, and at first it crashed mid thing, but I booted to cli and finished rest no problem. Now when I boot I get error that /boot couldn't be mounted and idrk what to do. I have a backup on raid1 partition but idk how to get to it, or I can do it other way? I'll send pictures soon. Also as far as I see internet doesn't work too

[signal glacier]

drop to a shell and run systemctl status boot.mount please

send a picture here, do not type it out

[old cypress]

I was about to do it hehe

[signal glacier]

go into the iso, mount your partitions, chroot in, and then regen your kernel images with mkinitcpio -P

[old cypress]

So I need a pendrive with arch,m

[signal glacier]

yes

[old cypress]

Okay, will any of data be lost?

[signal glacier]

no

[old cypress]

Okay great thanks I'll try it soon and let you know

[old cypress]

When I'll be booted into iso can you assist me a little? I am pretty much new into it and don't know a lot

[signal glacier]

read off of the wiki

https://wiki.archlinux.org/title/File_systems#Mount_a_file_system

https://wiki.archlinux.org/title/Chroot

[old cypress]

Do I mount / or other drives too

Cus I have more than one

[signal glacier]

you mount your root partition and esp partition

home is not needed

[old cypress]

Okay

[signal glacier]

mounting will be different depending on what filesystem you're using, if btrfs first mount the toplevel subvolume and then list out the available subvolumes on that mount point

additionally if using an encrypted root, first open it with cryptsetup then mount /dev/mapper/*

[old cypress]

I didn't try yet, I was downloading ISO

[signal glacier]

worked? @old cypress

[old cypress]

Im stuck on mounting, it says that it can't find it in fstab

[old cypress]

Sorry if i'm doing something wrong

[signal glacier]

Is this BTRFS?

And you're doing it wrong

That's not how you chroot

... chroot

[tacit patio]

#11522 📣 https://discovery.endeavouros.com/system-rescue/arch-chroot/2022/12/

[old cypress]

Yes

[old cypress]

I was told to first mount then chroot? Unless I understand wrong

I didn't get to that step yet

[signal glacier]

You're mounting it the wrong way
Read that article

BTRFS uses subvolumes, which you have to mount

.aw BTRFS

[tacit patio]

Btrfs

https://wiki.archlinux.org/title/Btrfs

[old cypress]

Okay I'll read the article rq sorry I didn't know

[signal glacier]

You don't mount BTRFS like ext4

Different filesystems

[old cypress]

So I follow this?

[old cypress]

It says unknown parameter 'subvol'

[signal glacier]

Yes

[signal glacier]

Read it again, it literally tells how to chroot BTRFS

Arch installed with archinstall uses same subvolumes configuration as EndeavourOS

Use lsblk -f to check your configuration

[old cypress]

Yes, and I need to mount / before chroot, right?

I get that error while trying to mount / like in the guide

[signal glacier]

You're doing it wrong

I already said how to proceed

[old cypress]

Maybe im reading wrong part of the article, but I type the exact command they're telling me to and I get that error

[signal glacier]

It literally says mount -o something

[old cypress]

And im doing literally that

[signal glacier]

Check dmesg

It depends on your BTRFS subvol layout

Also use latest arch iso

[old cypress]

I have latest iso, downloaded yesterday

[signal glacier]

lsblk -f helps

[old cypress]

Not sure how to check it, unless I am not seeing something in lsblk -f, cus I tried mounting nvme0n1p2 but get an error too

[old cypress]

This is dmesg for this

And similar error for when I try to mount nvme0n1p2 but it also says no such file or directory

[signal glacier]

Why it's targeting ext4 when it's BTRFS

Be sure what filesystem you're using

[old cypress]

I am sure

[old cypress]

It wasn't subvol=@ but subvol=/

Apparently restoration completed, I exited from chroot, rebooted to arch but still it can't mount /boot on startup

Same error as earlier

Earlier I mean first screenshot

[old cypress]

Okay @signal glacier so I mounted both as in the guide Hazel send, ran mkinitcpio -P rebooted to OS but it still is dead (image 1 is after mkinitcpio-P, image 2 after boot)

[old cypress]

From what I see it sometimes works sometimes not?

[old cypress]

Ngl idk what to do

[old cypress]

I did what I was told to do but still the same error on boot

[signal glacier]

like i said

mount both partitions

[signal glacier]

you forgot to mount your esp partition here

[old cypress]

I did, I mounted nvme0n1p2 and nvme0n1p1

[signal glacier]

show me

mount both. chroot in, run mkinitcpio -P, and then lsblk -f, and ls -l /boot

[old cypress]

Ok

[old cypress]

Please

[signal glacier]

whats in /efi?

is that xboodldr?

ls -lR /efi pls

kay my suspicions are you're mounting your esp to the wrong place and you don't actually have xbootldr

you should exit chroot and mount your esp partition to /mnt/boot instead

and then chroot in, regen kernel images

then show me:

cat /etc/fstab
ls -l /boot

[signal glacier]

you only need to mount the root subvolume, whether that being the toplevel one or not

so:

mount -o subvol=@ /dev/nvme0n1p2 /mnt

and then you would mount your esp here

[signal glacier]

well now we see

you're mounting your esp partition to the wrong place

[signal glacier]

do this

and the message below

[old cypress]

Esp being nvme0n1p1?

[signal glacier]

yes

it needs to be remounted to /mnt/boot

since kernel images get generated in /boot

[old cypress]

Oh, okay, I followed what Hazel send me

[signal glacier]

atleast in the default mkinitcpio.conf rpesetr

preset*

[signal glacier]

they only taught you how to mount your btrfs partition, not esp

esp you should know where to mount if you installed manually

[old cypress]

It's in the guide to mount under /mnt/efi

[signal glacier]

that's only for pure uki/efistub setups, and/or xbootldr

[signal glacier]

well that's not the archwiki sorry not osrry

[old cypress]

I'll unmount it and mount under where you said

[signal glacier]

don't follow 3rd party guides

biggest mistake

[old cypress]

I mean it was linked in this conversation so I thought it's fine

[signal glacier]

where exactly?

[signal glacier]

@signal glacier don't link this, it's spreading misinformation

it's completely wrong as well, from a first glance

[old cypress]

Why when I do this I get an error no such file or directory but when I replace @ with / it mounts?

[signal glacier]

missing that subvolume

/ is the toplevel subvolume in btreefs

@ is where your root would live if you had followed the default layout

[signal glacier]

mkinitcpio -P

and you'll be good

just rerun ls -hR /boot after so i can sanity check it

[old cypress]

Check top unless I misspelled it

[signal glacier]

oh

[old cypress]

(also is the image quality good)

[signal glacier]

update your kernel with:

pacman -Syu linux

this will trigger initramfs creation

which is what mkinitcpio -P does

[old cypress]

All 84 packages?

[signal glacier]

well first

have you done the manual intervention?

for linux-firmware

https://archlinux.org/news/linux-firmware-2025061312fe085f-5-upgrade-requires-manual-intervention/

this

if not, cancel out of that upgrade and:

pacman -Rdd linux-firmware && pacman -Syu linux linux-firmware

[old cypress]

I did

[signal glacier]

kay

then proceed

with the update

and if there are any warnings or errors, send a picture here

[old cypress]

Errors occured no packages were updated, and a bunch of X exist in filesystem

I'll send pic in a sec

[signal glacier]

pacman -Syu --overwrite='*'

[signal glacier]

run this as typed

--overwrite='*' two single quotes with an asterisk

[old cypress]

Again non valid kernel errors

[signal glacier]

show

[signal glacier]

same as here?

[signal glacier]

did your kernel get updated?

pacman -Q linux

[signal glacier]

send output of this

[old cypress]

linux 6.15.6.arch1-1

[signal glacier]

mkinitcpio -p linux

does that work

[old cypress]

-p or -P?

[signal glacier]

lowercase

[old cypress]

No

[signal glacier]

weird that it's pointing to that, does exiting chroot and re entering work? if not then try a reboot

remount,rechroot,and re mkinitcpio -P

[signal glacier]

for reboot only

[signal glacier]

actually how old is that image

ls -lh /boot

[old cypress]

So first exit chroot, try this and if same error reboot, remount, chroot and this again?

[signal glacier]

ignore that for now

i want to check the age of that kernel image

[old cypress]

In chroot right?

[signal glacier]

yes

[signal glacier]

the kernel image is a month old

pacman -Syu linux

[signal glacier]

good

now reboot into the installation

unplug usb

[old cypress]

Can I keep it plugged just change boot order?

[signal glacier]

you can change boot order on cli with efibootmgr

[old cypress]

In bios

[signal glacier]

but just unplug for now

and see if it owrks

[old cypress]

Ok

When I input my password I get send back to this screen, error was before I did anything

[signal glacier]

unrelated to this thread, make a new one and ping me there so i can help you with that

for now mark this thread as solved

... solved

[tacit patio]

#17640 📣 If there is nothing else that we can do for you, please close this thread by adding "[SOLVED]" to the title.

• You can do this on desktop by clicking the three dots on the top right of the page, and pressing "Edit Post".
• You can also do this on Android / iOS by long tapping your post in the text channel list, and tapping "Edit Post".

Your title should be like so: https://media.discordapp.net/attachments/1377138685538992252/1394893287667667035/image.png?ex=6878771b&is=6877259b&hm=e490049052812fd977384de338fa0f0c0634c50ed75a6f5a00bc7c7a847ff278&=&format=webp&quality=lossless&width=628&height=122
Thank you

[old cypress]

Okay

[SOLVED]System doesn't mount boot after update

Done?

[signal glacier]

it's not misinformation. it works here fine, always did, and was written by endeavourOS devs.
I use it as template and reminder.

it is

i have listed my reasons in a separate channel

3rd party guide
which is only meant for uki/efistub setups and/or xbootldr

kernel images always go in /boot so mounting esp to /mnt/efi will cause issues, unless the user has modified /etc/mkinitcpio.d/linux.preset or any of the other preset files to point images to /efi instead of /boot

if xbootldr, the bootloader will live in /efi so it's fine to mount to /mnt/efi

even if it does mention this way (/boot/efi not /efi), it's still wrong as stated in the specification and totally deprecated, also this completely varies on the users setup, a noob is not going to know where their esp partition gets mounted to and will just mount it to /mnt/efi blindly

https://uapi-group.org/specifications/specs/boot_loader_specification/#mount-points

[signal glacier]

@signal glacier