#[SOLVEN]Can't boot into system

1 messages · Page 1 of 1 (latest)

dry prism
#

Hello, I need help. When I tried to boot into system, endeavour popped out with emergency mode. I tried arch-chroot but it didn't help. After some more digging I found out that EFI partition isn't mounted and it's folder is empty

dusty gorge
#

@dry prism get into a chroot first please

dry prism
#

I used arch-chroot but it didn't help

violet nimbus
#

if you're asking for help do as they say

dry prism
#

Well, it's too late. I already started reinstalling system

violet nimbus
#

ok

dry prism
#

Update, I can't boot again into system

#

No options appear in systemd-boot

#

Only boot into firmware settings

#

And EFI is again empty and unmounted

dry prism
dusty gorge
#

@dry prism can you take a photo of you in the chroot please

dry prism
#

Lemme just log into discord real quick

dusty gorge
#

@dry prism mount /dev/sdXY /mnt

dry prism
#

that command is for mounting main partion?

dusty gorge
#

yes

#

The chroot target should be a directory which contains a file system hierarchy.

dry prism
#

and where should i mount it?

dusty gorge
#

For an existing installation, you need to mount existing partitions into /mnt yourself:

dry prism
#

its mounted

dusty gorge
#

do you have swap?

dry prism
#

no swap partions

dusty gorge
#

you have an NVMe drive /dev/nvme0nXpY.

dry prism
#

yes

dusty gorge
#

If you have any discrete partitions, mount them too.

dry prism
#

i only have unmounted on this drive efi

dusty gorge
#

Run arch-chroot with the new root directory as first argument

#

arch-chroot /path/to/new/root

dry prism
#

is this new root directory from system or just completly new?

dusty gorge
#

@dry prism new

dry prism
#

can it be second drive?

dusty gorge
#

try it and see

dry prism
#

nope, it doesnt work

#

[[email protected] ~]$ sudo arch-chroot /run/media/liveuser/02bf0480-a98b-4d52-8263-69f4cb82cc8a/
mount: /run/media/liveuser/02bf0480-a98b-4d52-8263-69f4cb82cc8a//proc: mount point does not exist.
dmesg(1) may have more information after failed mount system call.
==> ERROR: failed to setup chroot /run/media/liveuser/02bf0480-a98b-4d52-8263-69f4cb82cc8a/

dusty gorge
#

no nee for the sudo if you are in root

dry prism
#

nope, second driive doesnt work

#

[root@EndeavourOS ~]# arch-chroot /run/media/liveuser/02bf0480-a98b-4d52-8263-69f4cb82cc8a/
==> ERROR: Can't create chroot on non-directory /run/media/liveuser/02bf0480-a98b-4d52-8263-69f4cb82cc8a/

#

and in my main system partion file appears when i use arch-chroot on it

#

Generated by NetworkManager

nameserver 192.168.5.1