#arch-root fails and not enough size for pacstrap base

70 messages · Page 1 of 1 (latest)

velvet rose
#

Having some issues with recovering system after crashed update.

I have decrypted the disk with cryptsetup open /dev/nvme0n1p2 descrypted --type luks Mounted both main disk partition and EFI partition to /mnt successfully

When i attempt to do sudo arch-chroot /mnt

I get chroot: failed to run /bin/bash : No such file or directory

I tried pacstrap /mnt base linux linux-firmware

But it says I don't have enough space in disk

I'm a bit at the limit of my knowledge so any help is appreciated

upper hemlock
#

let me see your lsblk output

#

also if possible. outside chroot. install and enable sshd while in the iso and ssh into your pc (even from windows) so you can manage and copy and paste term input output

#

what i am suspecting is you mounted somthing like your boot to mnt first then your root. you have to mount your root partition to /mnt first. then your boot/efi and home next.

#

or you mounted the wrong parts and assumed it was the other one. eg mounting your 100mb or so boot part, to just /mnt

velvet rose
upper hemlock
#

let me see the output of lsblk and df -h

velvet rose
upper hemlock
#

and df -h ?

velvet rose
upper hemlock
#

weird im not seeing your p2 in df -h

#

anyways no clue lol. just curious really. try redownloading and reflashing the iso? and before chroot pacman -S archlinux-keyring.

velvet rose
upper hemlock
velvet rose
#

I unmounted everything from /mnt and only mounted the decrypted mapping

#

Now it shows up

#

But i still need to mount the EFI partition, right?

upper hemlock
#

eg if boot is empty the mount your boot part to /boot. if its not the mount your boot part to /boot/efi

#

me i didnt create a seperate boot part in the normal sense. my boot directory is just apart of the root part. and whats in my boot part gets mounted in /boot/efi

velvet rose
#

I had the efi folder in /boot

#

So i mounted to it, i still cant chroot to mnt

upper hemlock
#

oh. unmount everything again. then run dmesg. mount just your root. run dmesg again.

cold viper
# velvet rose

what have you got p1 and p2 mounted to the same place?

velvet rose
cold viper
#

/mnt for root, /mnt/boot or /mnt/boot/EFI or /mnt/boot/efi for boot

upper hemlock
cold viper
#

.aw installation_guide

tawdry oceanBOT
cold viper
#

Is it a different page you're using?

velvet rose
#

Meant arch-chroot wiki

cold viper
#

huh?

#

link me to the page?

velvet rose
#

I already have arch installed. I was updating and it crashed mid update. I'm attempting to recover

upper hemlock
#

if you mounted wrong like this and ran commands. you most certainly fucked it up more.

cold viper
cold viper
#

because "not enough space"

#

probably because p1 is mounted to /mnt

upper hemlock
#

o ok. i figured it may have overwritten the linux img.

cold viper
#

just umount /mnt, remount root to /mnt, mount p1 to /mnt/esp, and retry

upper hemlock
#

also if your decrypt keys are stored in boot. your encryption does nothing.

#

unless you encrypt boot.

#

so i read from a comment of a encrypted installation guide

velvet rose
cold viper
#

obviously mounting your encrypted root won't do anything

velvet rose
cold viper
velvet rose
velvet rose
cold viper
#

it's btrfs

#

so

#

you need a different mount command for your root anyway

#

btrfs subvols mean I believe -t subvol=@

velvet rose
#

Oh ok, do you mind typing the whole command so i dont mess up 🙏

cold viper
#

mount -t subvol=@ /dev/mapper/decrypted /mnt I assume, I don't know if that's right for the decrypted part, I'm basing that on what you've put there

#

I'll double check that though

#

might be -o and not -t

#

check the manual I guess

velvet rose
#

-o worked

#

Arch-chroot works 👍🏻

#

Now do i do pacman -Syu
Or do i use pacstrap?