Boot problem with the command line

[final latch]

So i was installing arch with the help of this video: https://www.youtube.com/watch?v=FxeriGuJKTM&t=2448s along with a couple tweak.

Near the end of the setup i had to use mkinitcpio, but it was giving me an error bc of the vconnsole.conf not existing, according to this forum post: https://bbs.archlinux.org/viewtopic.php?id=310236 the fix was to just make the file using the touch cmd and that was what i did. After finishing the tutorial, ofc i tried booting and this is where i am now, the system boots yes, but it gives a timeout error since the root is locked or smth, btw i cannot chroot with the arch usb stick i had anymore and its just very weird, any thoughts?

Also the deviation were: using grub install with bios instead of uefi, making a swap partitions, using cfdisk and thats about it
When booting it goes rainbow static glitchy look -> timeouton the root partition -> emergency mode: "Cannot open acces to console, theroot account is locked"
If i press enter tries to reboot sys mng config and reprint the cannot open acces

[minor canyon]

It is generally not a good idea to follow tutorial videos because they cannot be updated if/when the process might change

Can we get a picture of the issue?

[final latch]

let mylogginn on my phone

[minor canyon]

"grub install with bios instead of uefi," - what's the motivation for this? Are you in a virtual machine?

Machines from the last 15 or so years are all UEFI so you should probably be using UEFI

[final latch]

Hwinfo tells me otherwise

Told*

[minor canyon]

What model is your machine?

[final latch]

Like i3 + gt 210 old

[minor canyon]

Please share the contents of /etc/mkinitcpio.conf

[final latch]

If usong it to learn installing arch

I cant

Or

Lwt me boot the installation drive

[minor canyon]

Can you check if there is a model number on a sticker on the bottom?

It'd be very unusual for a machine with an i3 series chip to not support UEFI.

[final latch]

Idk

Sgx is disabled also

[minor canyon]

Note that that part is an aside - bios/csm should work for you. I'm just recommending best practice

[minor canyon]

Seeing this file will hopefully show me what's wrong in your screenshot above

I'm looking specifically for the HOOKS="" part of that file

[final latch]

I added lvm2 and cryptsetup there if im not mistaken

[minor canyon]

Can I see? 😊

[final latch]

Ofc

[minor canyon]

That looks pretty OK

Can you share the output of mkinitcpio -P? Easiest way is with a tool called wgetpaste that you'll have to install

If you wgetpaste -c 'mkinitcpio -P' it will send your logs to the interwebs and you'll get a short link you can share here, so I can see the whole thing

[final latch]

Fstab

[final latch]

Ye

But where is that exactly

[minor canyon]

Before you get to this screen, does it ask you to decrypt?

[minor canyon]

Just in the pacman repos. pacman -S wgetpaste

It's just a little bash script

[final latch]

I cant ch root tho also i have lil drive but ima try

[final latch]

No just half quad output half rbg soup

And grub before it

[minor canyon]

OK that's good to know

[minor canyon]

mkinitcpio -P |& curl -F'file=@-' https://0x0.st is wgetpaste without having to install anything, if you need to do that

wgetpaste is just super duper convenient so it's my goto

This is what I am looking for

To ensure your mkinitcpio hooks are firing

[final latch]

they are

i know they are

well when i made it they did

the tutrial guy said to look for them and it did run em

i did see the hooks

[minor canyon]

HOOKS=(base udev autodetect microcode modconf kms keyboard keymap consolefont block encrypt lvm2 filesystems fsck) my hooks line for example

The only difference I have is no systemd stuff. You might want to try using my hooks line instead, see if it works for you

I am running an almost identical setup to yourself

[final latch]

https://bpa.st/5NNA

[minor canyon]

Ah you'd need a sudo on that mkinitcpio, but if you're sure the hooks are there, I believe you

[final latch]

IM NOT ChROOt I FORGOR

im ranit on the boot iso

hol up

[minor canyon]

Ah ok, gotcha

[minor canyon]

proof 😊

[final latch]

ialsohave a boot/EFI partition i wonder if that has any weird problems

i cant chroot noohohohoh

cant find zsh

but i can run zsh

[minor canyon]

That should be OK. /boot, /efi and /boot/efi are all working layouts

[final latch]

is it the sytems zsh

do i need to redoallthat work bruh

[minor canyon]

Have you run cryptsetp luksOpen to decrypt your disk?

[final latch]

i did

[minor canyon]

What's in /dev/mapper ?

[final latch]

that the first thing i did

lv_root and home

how would i mount the system wothout decrypting it

[minor canyon]

You can't. Until the volume is decrypted it's just a big pile of random bytes as far as the system is concerned

[minor canyon]

mount /dev/mapper/lv_root /mnt ?

[final latch]

shit

SHIT

i

bruh

its volgroup0-lv_home

WHAT DID I MOUNT WITH NO ERROR

[minor canyon]

That'll be your home partition I assume

[final latch]

but theyre mounted when i cjeck with lsblk tho

[minor canyon]

Share a pic if you like, I'm finding it hard to imagine what you mean

[minor canyon]

Looks OK to me. arch-chroot /mnt ?

[final latch]

im a dum dum

Chroot aint arch-chroot

Welp

Thre we go

Ima do the wgetpaste now

[minor canyon]

At a second look this is actually a little weird. Seems you have two EFI partitions mounted?

To /boot and /boot/EFI

[final latch]

I dunno man

[minor canyon]

That is probably confusing things. What I think is happening is that your mkinitcpio stuff is working fine, but when your system starts it is starting the one in the other place

[final latch]

Alr so https://bpa.st/RY7Q

[minor canyon]

Looks good to me. Try grub-mkconfig -o /dev/null and share its output please

[final latch]

I should mention that i have 2 kernels

Linux and linux lts

Theres. Awarning

[minor canyon]

That should be OK

[final latch]

I did mkcpio for both

[minor canyon]

Hmm that looks OK too. If you ls /boot/EFI, what does it contain?

[final latch]

Uhh

UHHH

Efi in efi

Cool

And other stuff

[minor canyon]

Hmm. I think that is confusing things. How would you feel about a nuclear option?

[final latch]

Reinstalling

Yes

[minor canyon]

Noooo not a reinstall

We can just nuke the boot stuff and do it from a blank slate

[final latch]

Makes sense to me alr

So just recursive deletion of the partitions

[minor canyon]

I'm just in the shop so gimme 10 mins and I'll walk you through it

[final latch]

Alr

Im gonna nuke the whole system at this point

Hey the boot partitions empty

Exception is EFI ofc

Ima read the arch wiki

ima try smth

What is i try to mount the sad2 to v
Boot

Also welcome back

[minor canyon]

I have returned!

umount -R /boot                    # unmount /boot/EFI and /boot
mount /dev/sda1 /boot                        # mount /boot
rm -rf /boot/*                     # be extremely careful typing this command out! Just want to clear out the contents of /boot
grub-install --efi-directory=/boot # install grub to /boot
pacman -Syu linux                  # reinstall your kernel and regenerate your initramfs (you can install lts the same way later)
grub-mkconfig -o /boot/grub/grub.cfg # reconfigure grub. It should pick up the kernel and initramfs you have just installed

That's what I would try in your situation

[final latch]

It is busy

What the star do ?

In the rm rf

[minor canyon]

* in linux is a wildcard most of the time

It grabs everything in that dir

[final latch]

Ah cool

[minor canyon]

to demo

[final latch]

Boot is already empty LOL

Weord

Vey weird tho

[minor canyon]

I think that's the core of what's wrong here - you have two places for boot stuff to go and so it's getting a bit confused

[final latch]

Also deos this mean i can get eid of sda2

[minor canyon]

It wouldn't be in use so you could do what you wanted with it

Did the video you linked suggest making two partitions like that?

[final latch]

Yea

Check it yousrlf

It seemed to work for others

[minor canyon]

It's not a setup Ive seen before 😄

[final latch]

Idkan he said he tested the process extensibly so yk

It must be good

Well i then again i didnt follow 1:1

[minor canyon]

Hm I've found the bit where he sets it up, but he doesn't say why he's doing that

That's another big problem with video tutorials

[final latch]

Yea

I realized that

But i mean its already an hour so

Ye

Well a series of videos does work tho

[minor canyon]

Anyhow, where are you at with this?

[final latch]

Grub install there aint no device supposedly

I mean it aint SPECIFIED

[minor canyon]

Someone else asked as well lol

[final latch]

Lol

[minor canyon]

Can you share what you ran and its output?

[final latch]

Installing i386-pc platform

And

Error install device isnt specified

[minor canyon]

Oh sorry I forgot you were bios/CSM 😭

[final latch]

Yk whats weird?

My mb is a b360m

AND IT AINT SUPPORT UEFI?

Like how bruh

[minor canyon]

It's from 2018, I am sure it does support UEFI

[final latch]

Like look at this shi

Uh

[minor canyon]

That aside, it should be grub-install /dev/sda then I think for bios https://wiki.archlinux.org/title/GRUB#Installation_2

Up to you if you want to carry on with bios/CSM or see if you can get your mobo in UEFI and follow the UEFI steps

Although I think that would involve repartitioning your disk as GPT unfortunately

[final latch]

I think i already did that the disk label right?

Gpt solaris

Dos

That stuff

[minor canyon]

UEFI usually uses GPT layouts while csm/bios uses dos

[final latch]

Its dos

[minor canyon]

Stick with that then I suppose

[minor canyon]

This should do the thing

[final latch]

Brother what is going on

Fat doesnt support wmbedding

Mkfs.what at this point

Cant even talk correclty

Dos acces

Dos r/o

[minor canyon]

I think you're mixing up UEFI and bios/csm instructions here. The EFI partition has to be FAT32 for UEFI setups, for dos it doesn't need to be FAT32

[final latch]

Id type is efi

[minor canyon]

In fact you don't even really need a separate boot partition for bios/csm, although it is nice for organisation reasons

[final latch]

I did read that in the wiki

Brotha im overwelmed

Ima continue tho

[final latch]

Ima change it to linux

[minor canyon]

Those partition type labels aren't super important really

[final latch]

Eh

Its still erroring

Ah

[minor canyon]

Share a pic if you likey

[final latch]

Make it ext4?

[minor canyon]

That would work

[final latch]

Fat doesnt support embedding

Tahts all

[minor canyon]

Ah ok

Make sure to remember to mark this partition as bootable in whatever disk management thing you're using

[final latch]

Did it

I still doesnt want too

WHY IS IT EXT2

Wth is this man

Like my man @minor canyon wtf

Average low level struggle

[minor canyon]

It would be grub-install /dev/sda, without the partition number

[final latch]

Please dont tell me

No way amn

Now pacman doesnt want to cooperate

[minor canyon]

I can't really help without seeing the issue

[final latch]

Temp files had an aneurism

[minor canyon]

Curious. What does mount have to say for your root partition?

Does it say it's ro ?

[final latch]

Wdym

My root is the installation root

Volgroup0-lv_root

[minor canyon]

Sure, but it says it's readonly

see how mine says "rw" for "read/write" ?

[final latch]

Why is it readinly all of the sudden

[minor canyon]

Dunno 😊

[final latch]

Ya

Im acheck gstab

F*

[minor canyon]

Tbh in this sort of weird situation i tend to just restart the iso

[final latch]

OH SHI

I coudve forgotten fstab

I mean we forgot fstab

[minor canyon]

The encrypt and mapper stuff happens before the fstab is used

[final latch]

Well yea but the fstab would mount sda2 to boot

We dont want that

Also lets change the device rw permission

so we use udev

[final latch]

Now reboot or?

[minor canyon]

Not sure where you're at

[final latch]

i finished the grub config

anfter i rebooted the arch iso installer drive usb stick

sry for taking so long

So i installled grub, made the config now what?

ah yes fstab

[final latch]

Hey n=man i have a new hypothesis

so what is the users is the problem and not grub

since the problems accualyseems to stem from the initrd.target program

so what if i go edit the initrd.target

alsothe problem seems to stem from the sulogin cmd

maybe force the login

or accualy the getpwnam

[minor canyon]

I'm not sure what you mean with that

users should not be involved, all this stuff is managed by the root user

[junior pewter]

From what I can see, you are using dm-crypt encryption and then LVM inside of that, and you are using systemd-based initramfs. You are also not using UEFI, so suppose that GPT partition automounting doesn't apply here. Could you please share your kernel command line parmeters?

Do you have the rd.luks.name parameter set? Are you getting the same error as earlier (timed out waiting for root device)?

From what I'm reading on the ArchWiki, it looks like it's also possible to specify this using /etc/crupttab.initramfs file.

[final latch]

I announce the fact that i, instead of using cool video tutorial, will now be using the holy bible (arch wiki) and the knowledge gained from the video to setup arch linux os, @minor canyon i thank you for all your help since you tried for multiple hours debugging with me the setup so shout out to you and have a wonderfull day.

[mystic turret]

mushroom.botherer received a thank you cookie!

[final latch]

As for tk-a thank for checking in but, for now the information wont be necesary

But definetly usefull ofc