LEAD ME DOWN ANOTHER RABBIT HOLE WITH OBTUSE NON-EXPLANATIONS, I DARE YOU MOTHERFUCKERS

oh you just gotta append some initrd= options to the boot loader or whatever, tehee :troll:

WELL HOW THE FUCK DO I DO THAT?? I WILL FIND YOU

You are viewing a single thread.
View all comments View context
2 points

The drive name in boot menu is determined by what you use in grub-install --target=x86_64-efi --efi-directory=esp --bootloader-id=GRUB the GRUB at the end gives it the name and the esp is the directory with boot files, typically /boot. If you like Manjaro, I would probably try to stick with Arch if you want to know your system, it is pretty good distro and AUR is much better there.

permalink
report
parent
reply
1 point
*

Thanks for the info, it did indeed change the drive name. Tried redoing the whole arch install, but it’s still giving me a “no such device” and “unknown filesystem” when I try to boot. Seems like the UUID is wrong or something

permalink
report
parent
reply
2 points

Hard to tell what is wrong from that. I would guess that you skipped some part of the grub configuration. Make sure you do the grub-install above and grub-mkconfig -o /boot/grub/grub.cfg (or wherever your efi directory is). Plus make sure your disk is formatted with GPT (if you are using fdisk just make sure you start with g command that will create new GPT partition table).

Btw this all assumes you are using GRUB, but if you don’t have any reason not to I would recommend using it, it is the most common bootloader.

(Btw I have to say Arch installation guide seems to be much less straightforward than I remember)

permalink
report
parent
reply
1 point
*

I think I did all those things. Gonna Do it again from scratch to make sure I did the GPT partition scheme properly. e: same error, I’m gonna try asking some arch forum

What’s weird is that the grub rescue says “no such device” and a UUID that doesn’t correspond to any device in the computer, and I double checked that the UUIDs in the grub.cfg are correct. Also, after rebooting, the grub.cfg can no longer be found in the grub folder (created it with grub-mkconfig -o /boot/grub/grub.cfg while chrooted)

permalink
report
parent
reply
1 point

But shouldn’t that be stored on the drive I’m installing the OS on? I figured it would be cleared when formatting

permalink
report
parent
reply
2 points

As far as I understand, when you use this command, it also writes to memory on the motherboard itself. So even formatting won’t do anything. The boot option will not work, but it will still be there.

Btw just out of curiosity where did you find mention of initrd options in arch installation guide, I just took a quick look and didn’t see it there.

permalink
report
parent
reply
1 point