Grub on efi

[whole girder]

I ran:
grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=Arch
In attempt to install grub when grub install sdb but the disk isnt gpt formated and it does not need to be

So im getting a error that my partition isnt efi for some reason, maybe some incorrect mounting or smthin

[raw compass]

replace /dev/sda1 with your boot partition

also, make sure that your boot partition is mounted to /boot in the first place

[whole girder]

I already installed basic utils onto those three partitions

how would restarting affect it

[whole girder]

also im installing in sdb

[raw compass]

wdym restarting

[raw compass]

doesn't matter

where did you get that from

oh the lsblk

i didnt say format sda1

[edgy monolith]

wait sdb1 is windows

and you said their boot partition nevermind

[whole girder]

sda is my virtual machine drive

here is where arch will be

uhh

it should be fat32 the boot

not vfat

[edgy monolith]

fat32 is vfat

[raw compass]

fat32 is vfat though

[whole girder]

oh

[raw compass]

regardless

now you know the issue

[raw compass]

see here

[whole girder]

so my boot is fat32, which is correct, its mounted under boot

uh

[raw compass]

but it's not mounted to /boot

[edgy monolith]

you have it mounted at /boot/efi

[raw compass]

it's mounted to /boot/efi

in this case

just replace /boot with /boot/efi when running the command

[whole girder]

mount /dev/sdb6 /boot

?

and umount /dev/sdb6 /boot/efi

correct?

[raw compass]

no

[raw compass]

see here

[whole girder]

we are talking about sdb6 right?

the fat32 one

oh wait

i see

grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=Arch

thanks

ill try it

[edgy monolith]

Just so you know, bootloader id is optional

[whole girder]

https://tenor.com/view/huh-meme-confused-gif-24780938

[edgy monolith]

Make sure you booted the ISO in UEFI mode, and not using CSM

[raw compass]

so is efi

[whole girder]

Why isnt there a UEFI mode

[raw compass]

boot the iso as efi then

[whole girder]

what

[hasty flint]

This is what arch iso looks like when you boot from BIOS / CSM

[raw compass]

because you can't switch to efi after opening the menu

[whole girder]

So do I have to reinstall arch and mount my disks to mnt

*partitions

[raw compass]

what why

[whole girder]

Well I accidently selected bios in the menu and i cant switch to UEFI now?

like

what can i do now

[hasty flint]

You will need to go to the firmware setup utility to configure your firmware to boot the ISO in the UEFI environment.

[whole girder]

is there any posts about this or anything on the wiki

walking me through thre steps

would be more appreciated tho

[hasty flint]

The firmware setup utility is usually accessed by pressing F2, F12 or ESC during early start up, depending on the manufacturer.

[whole girder]

Im installing arch from virtualbox

[hasty flint]

Here is an example of what they look like

[whole girder]

would I be able to go to the firmware setup in virtualbox

[hasty flint]

no

[hasty flint]

EFI is not enabled by default in Virtualbox

You need to enable it in the Virtual Machine Settings view.

[whole girder]

oh there is a setting for it

[whole girder]

yeah i remmebered

[whole girder]

sdb7 isnt appearing as swap

[hasty flint]

stat /sys/firmware/efi/efivars

[whole girder]

btw im chrooted in

[whole girder]

what did that do?

uhh it still did not make the partition i wanted too a swap

i tried reswapping it

[hasty flint]

To check if you are using UEFI

Use swapon to activate Swap.

[whole girder]

ah it worked now or some reason

oh

i did wrong command earlier

INSTALLED FINALLY

Soo

It installed

I tried ti set up the config

I rebooted the system

I can't see it

Arch isn't appearing

[whole girder]

Since I mounted at /boot/efi do I make the grub configuration file there?

[hasty flint]

Grub reads its configuration from /boot/grub/grub.cfg by default

[whole girder]

So why isn't it appearing in the bootloader list

[hasty flint]

/boot/grub/grub.cfg does not correspond to UEFI boot entries.

[hasty flint]

Please post the output of command

efibootmgr

[whole girder]

Oh, I can add boot options if I wanted, pressing f2 into the BIOS screen I can add a boot option

[whole girder]

Chrooted in ?

[hasty flint]

No need.

[raw compass]

not chrooted, i dont think efibootmgr is installed anyway

[raw compass]

@whole girder did you run the command

[late relic]

why are you in your systems boot manager?

[whole girder]

@raw compass @late relic @hasty flint

What the hell happened

[whole girder]

it cant access tty

I triied this

uhh how do i rebuild my kernal

cfdisk, lsblk, parted are broken

nano is working

[edgy monolith]

you're not going to be able to do much from the emergency shell chroot

I would recommend booting into the arch iso

[whole girder]

I made a new vm and now im back

so my arch system is not showing up in the BIOS boot (f12)

[whole girder]

I figured it out

https://unix.stackexchange.com/questions/430606/arch-linux-boot-loader-not-showing-as-boot-option

grub-install --target=x86_64-efi --efi-directory=/boot/efi --removable

The --removable flag

[raw compass]

your root partition must be wrong

oh ok

do you still need help

[whole girder]

Yep, i installed the system and it's showing up as a boot option but

[whole girder]

It's like this

Not corrupted but somethings broken

What is rootfs's disk utility?

It booted me in the emergency cli known as rootfs and I need to see my disks

*partitions

[raw compass]

ls output?

then send ls new_root output

as i said root partition must be wrong

/sbin/init is the thing you save on your root partition that __init__ializes the system

[whole girder]

Do I need to fix via pacstrap

But I'm not on tty so I doubt I can use the command

[raw compass]

doubt it

@whole girder grub thinks your root partition is /dev/sda5, but it probably isn't; you gotta fix that

i am not sure how because i don't use grub

but you could press e and replace

[whole girder]

OH WAIT

I think I might know

So

The more partitions and disks your system has access too

The partition naming scheme changes

So what if, when I installed it on a vm there was just sda and sdb. When I boot up stuff could have moved

So I need to see a list of the partitions from the systems perspective

[raw compass]

um

wha

[whole girder]

When you mount a disk/partition to a device its label changes

I mounted my main disk to my vm

So it was labeled as sdb5 but when I boot into my main disk there is only sda

I think

I dunno how to list my partitions

[raw compass]

disks and partitions are devices so idk what you mean

[raw compass]

check their uuids

[whole girder]

How do I do that?

In rootfs

[raw compass]

cant, needs iso

[whole girder]

Ok so

I got the correct fstab

Wait

[whole girder]

Oh you gotta be fuckig kidding me
When I booted into my ventoy usb
The drive names were moved around
Like
When you mount a disk it's Givin a new name like sdb
And when you tell the computer to look for sdb when you boot, it can't find it, that'd because sdb is sda
FUCK

[hasty flint]

If your machine has more than one SATA, SCSI or IDE disk controller, the order in which their corresponding device nodes are added is arbitrary. This may result in device names like /dev/sda and /dev/sdb switching around on each boot, culminating in an unbootable system, kernel panic, or a block device disappearing

[whole girder]

So it is a problem, I don't think its due to multiple diffrent controllers but components being added from other disks to their corresponding controllers

So how can I fix it

[hasty flint]

I don't think its due to multiple diffrent controllers but components being added from other disks to their corresponding controllers
The order in which their corresponding device nodes are added is arbitrary
So how can I fix it
Please see to "Persistent block device naming"
https://wiki.archlinux.org/title/Persistent_block_device_naming

[whole girder]

I understand some of it

How to use it in the context of what I'm doing is a bit difficult

Umm

How exactly would I go about this

[hasty flint]

Could you please brief me about your objectives?

[whole girder]

In my fstab file i could have it use a persistent naming scheme instead so that when i boot up into arch from my core computer it does not try and look for a partition that does not exist

[hasty flint]

It is explained here: https://wiki.archlinux.org/title/Fstab#Identifying_file_systems

Please make sure that your kernel command also uses a persistent naming scheme.
You can check the current kernel cmdline with cat /proc/cmdline

[whole girder]

in the terminal its hard to copy and paste things like UUIDS

wait ima check if there is a way for my to copy and paste

[whole girder]

LABEL=ESP         /boot        vfat          defaults         0      2
LABEL=System      /            ext4          defaults         0      1
LABEL=Data        /home        ext4          defaults         0      2
LABEL=Swap        none         swap         defaults         0      0```

can I use that

like

I dont think anything needs to be altered

[raw compass]

yo im back

holy put it perfectly

[whole girder]

hey

[whole girder]

UUID=CBB6-24F2                            /boot vfat   defaults  0      2
UUID=0a3407de-014b-458b-b5c1-848e92a327a3 /     ext4   defaults  0      1
UUID=b411dc99-f0a0-4c87-9e05-184977be8539 /home ext4   defaults  0      2
UUID=f9fe0b69-a280-415d-a03a-a32752370dee none  swap   defaults  0      0```

How do i format blkid to look like this ^

like sdb5 to 7 are my main stuff

but i dont see a system UUID bit

[edgy monolith]

you can just use genfstab to setup a fstab

[whole girder]

not if i want Persistent block device naming

it does not boot if i dont have that

because the block names and shit change depending on where i boot

when i put in my ventoy drive, the ventoy drive is sda while my arch drives in sdb

[edgy monolith]

you can tell genfstab to use uuids or labels

[whole girder]

some times is nvme0...

[whole girder]

how?

[edgy monolith]

-U for UUIDs and -L for Labels

[whole girder]

which do you recommend

[edgy monolith]

UUIDs tend to be the most unique

[whole girder]

It seems like the same

[raw compass]

huh

[whole girder]

Read up a little bit

[raw compass]

i havent slept at all last night i can barely talk

[whole girder]

im trying to make a fstab witch unique identifiers

so like

not use system assigned partition nameds

perferably UUIDs