#Installed Arch but Grub doesn't show on boot, the SSD with Arch on it does not show as a boot option
1 messages · Page 1 of 1 (latest)
do you know how to chroot? @vagrant coral
I'm going through archinstall for the third time but I can be In choot in around 2 mins, bear with
Also I've never seen it before, should Unified Kernel Images be on or off?
do you know if you need unified kernel images?
some mobo manufacturers are aholes and use their own UEFI that doesn't recognize certain kernels, only solution is the one mentioned
there's other uses for them but typically no, not something you use
I'll leave it off for now then and go from there, what do I do in Choot now btw?
it's not kernel related, but, it could be they need to do grub-install with the --removable flag at the end
wiki makes mention of Lenovo and Dell for the use of it if I recall correctly it's not useful info for this case I think anyways
This is where I'm at rn
lsblk -f
tell us which is your root and which is your esp (for grub)
.aw grub
that looks mounted to me
Unsure if that's clear enough
grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=GRUB --recheck
what mount command did you use for root?
it's also btrfs
Fixed the windows portion of it
how?
I used the archinstall setup
Ended up pulling out a 256gb sata ssd I had and used that
oh this is you selecting to be chrooted into it post archinstall but before you reboot?
Yep
can you edit your tags for this to say it's archinstall?
Oh yeah mb
it looks chrooted to me but then that prompt is deceiving
they just said they selected the chroot action post install
it's at the end of the archinstall script, last TUI option
@solar rain this means they rebooted
can you show us ls /boot/
yeah I think they ended up just reinstalling arch again when it didn't work though, otherwise they'd be able to provide the mount command they would've used to mount the system
if that's the case we are looking at something else, the install script does the grub-mkconfig part too
I don't know if the archinstall script will install grub with the --removable
but we could also look at boot options using efibootmgr
EFI amd-ucode.img grub initramfs-linux-fallback.img initramfs-linux-zen.img initramfs-linux.img vmlinuz-linux.img vmlinuz-linux-zen
and ls /boot/EFI
"BOOT"
it's interesting that there isn't a grub.cfg in /boot/ actually
wait no it's not
it'll be inside of /boot/grub
I'm silly
fonts grub.cfg grubenv locale themes x86_64-efi
hmmm
fair enough
.s ix
<command to print output> |& curl -F 'f:1=<-' ix.io
.s rs
<command to print output> |& curl --data-binary @- https://paste.rs
we lost the best one lol
efibootmgr |& curl --data-binary @- https://paste.rs
cam you give is the output of that please @vagrant coral
Yeah can do, bear with
I wonder if it's just a matter of changing your boot order, which, can be done with efibootmgr anyway
hmm, can you show me: ping archlinux.org
oh wait
there's a space
@-<SPACE>https://paste.rs
paste.rs is a simple, no-frills,
command-line driven pastebin service powered by the Rocket web
framework.
you've done it without a space
just do up arrow to get last command, and then you can edit it
it's not even there
which is, well, weird
sda1 is what you're using as boot, so, maybe lets rerun the grub install commands
So go back to installer?
do this one:
grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=GRUB --recheck
Oh aight
I mean I think manual installation is the way to go anyway
And then:
grub-mkconfig -o /boot/grub/grub.cfg
do we still want --removable
and then this one again
if it doesn't work I think efibootmgr should tell us, in which case we can just do it with --removable and see what happens
we can also just add the entry with efibootmgr that will do the trick
grub already uses it to make the entry
efibootmgr |& curl --data-binary @- https://paste.rs
efibootmgr output?
lets see what's there
you beat me to it
now we're cooking with gas
it's even set as the top boot order position
unless Legend see's a problem
no I see no issue, the boot order does and doesn't matter if the other items are not plugged in
it should boot if it's the only bootable device in use
So should I try boot and see what happens?
exit, umount -a /mnt shutdown -0 remove the iso and boot up
hmmm, odd, go back into the iso, and mount root and boot again?
this part is an easy solve from within Arch no need to chroot
but since we are going to chroot, might as well take care of it there
So turn it off, and load back up the iso right
any reason for the zen kernel?
Got recommended it over the base one due to apparently better performance in certain things
hmm, @solar rain any knowledge on that one?
Was something like "The normal kernel is designed for servers while the zen kernel is designed more so for home and game performance."
I need a wiki source for that one
My install guide was this tbh 💀
Remember Spartan: Microsoft Windows is Covenant malware.
Patreon: https://www.patreon.com/SyntheticSoundsmith
TikTok: https://www.tiktok.com/@thesyntheticsoundsmith
Instagram: https://www.instagram.com/syntheticsoundsmith/
► Music Credit: Jay-Lounge
Track Name: "Chill Lofi-Rain"
Music By:Jay-Lounge
https://soundcloud.com/jay-lounge
License f...
It worked before aswell on my old laptop
But yeah
marginal and not worth having installed for most people, but not a problem, once root and boot are remounted, hopefully just a matter of reinstalling the kernel
.aw installation_guide
this is now your installation guide
Understood
Master Chief can't do anything without Cortana, we can't trust him
Just to be sure though this is correct right
everything that was suggested previously we are doing again
yes but without doing the archinstall script
the problem of windows isn't a problem, it's just not setup yet, the problem of not being able to boot IS a problem
a problem that we will try to fix by mounting root, mounting boot, chrooting in, and THEN doing pacman -S linux-zen linux-zen-headers
grub-mkconfig -o /boot/grub/grub.cfg
yes
why the zen kernel?
already asked and answered above
because that's what the user has chosen to use
this?
mount -o subvol=@ /dev/sda2> /mnt
mount /dev/sda1 /mnt/boot
this is not a debate thread
I may know nothing on zen but it's officially supported so we go with that
these commands will mount your root subvolume and your esp (for your bootloader)
can you not? This is a support thread, user has made a choice, they can revise that later if they wish, you're just adding noise for them to read and that's NOT helpful. They want a bootable system first and foremost.
in fact, lets delete that.
#tech-general for debating the pros and cons of linux vs inux-zen.
fair
If your wanting them as separate commands, this is the first command reply.
we never chrooted, you missed a step
@vagrant coral it's pacman -Sy for the iso
@vagrant coral
you're jumping ahead
I want to make sure you've mounted the two partitions first, if you've done that, let me know
you don't bake the cake ingredients and then mix them, you mix them then bake them, the process has an order to it, right now you're not in your system you're in the ISO, let me know when you've mounted the partitions as I suggested above
I do apologize if I'm just being a dunce about this, but how do I know what ones root and boot?
which drive is it again?
sda 1 is boot and 2 is root
^^^
I gave the commands that I think should work, I'm assuming / is called subvol @, unless you or archinstall is being weird about it
umm
@vagrant coral you put a space between sda2 and >
Removed space and redid, still same message
@vagrant coral
@vagrant coral that command should ™️ be ran all at once
please read the wiki
oh sirry
no >
that's a typo
mount -o subvol=@ /dev/sda2 /mnt
and they should be run seperately
once root is mounted to /mnt then /mnt/boot exists, meaning sda1 can then be mounted there
And just to be sure, how can I confirm there mounted
lsblk -f
see now you're in your system and not the iso, how the mountpoint changes?
have a think on that 🙂
now pacman -S linux-zen linux-zen-headers and see if there are any errors
shouldn't it be sy?
no
It's finished running, it downloaded a few things and ended with "image generation successful"
no, they're chrooted
nope, that's wrong
edit /etc/default/grub so that os-prober is enabled
it should find the Win install, we are probably going to have to mount it anyways
it may or may not, mounting it makes it less likely to err, and if it still doesn't we need to boot into windows and disable fast start up, though that hopefully won't be needed
my solution has always been mount the boot Win partition and os-prober confirms it's available for grub
that's how I did it
So am I editing the file or
yes, it's the last line
remove the comment
the #
then save, then rerun grub-mkconfig -o /boot/grub/grub.cfg
At some point you want to add the windows partition to /etc/fstab
we can do that with a gui later
Why do we want to use a gui for something like that?
for nothing to go wrong?
that's all that's required
You advocate for things for the weirdest reasons
Done
I think they prefer gui more than terminal
lsblk again please
is the win install on the nvme?
mount /dev/nvme0n1p1 /mnt/win
rerun grub-mkconfig -o /boot/grub/grub.cfg
during that output it should like the Win .efi file, I can't recall what it's called, something along the lines of BOOTX64.efi
Permission denied, tried as sudo but says command isn't found
screenshot?
@vagrant coral you forgot the mount command
oh I thought this had already been done, whoops
been bouncing around between cooking, eating, feeding the dog, and this tread 😛
living the good life
boot into arch for now, that's where I've always done it
when you login, do we need to mount the win boot partition like we did above
re run the os-prober command with sudo this time
after that, I highly recommended installing a grub theme
No
that's not important at all
No
Just rerun grub-mkconfig command above
That will trigger os-prober
Now it's booting into windows instead of grub
save this for the very last step
how is this important?
That’s not functional though is it?
Just how it looks
it's optional
booting into their two OS' seems to be priority
oh boy
@hoary smelt with grub you never run os-prober as a command, you just install os-prober, enable it in /etc/default/grub and then rerun the mkconfig command
Is my install just botched?
you can
I check first with it make sure it's being found
Nope, just go into the iso, remount, chroot, and then check in efibootmgr to see which one is being selected and then put grub at the top
You see it in the output anyway- totally redundant
it's how I've always done it, dual booting for a long time now, you're probably right though
So I've done all the steps apart from efibootmgr, how could I check it?
Spat out a bunch of code and finished with "done"
there's no way I think it is what I think it is
open /etc/default/grub and add the # back to the last line
what..
it's gone again
it was just working that was the only change
now we have an actual problem
is can't be os-prober, but sure, try that if you want...
I mean that was the only change, hence my there's no way
just backtracking here that's all
the other change is that we've had a reboot
did the last grub-mkconfig look like this?
Yeah
that shouldn't be an issue, because that's just making the config
grub-install is the relevant command...
That's after I commented the thing again, re ran the command and did the efibootmgr
nothing you've done explains why it's disappeared
I guess we do --removable this time around
or do this
the mv part, we know it's installed
in bios is secureboot enabled?
If I remember right no. The ISO would refuse to boot with secure boot turned on.
Cause it wasn't signed or something like that
okay it isn't that then
I’m out of ideas now as to why it would and then wouldn’t show up seemingly just from rebooting
@opaque ruin boot manager shows up when installed according to efibootmgr- and then when the computer restarts it might show it once, but then after that not again…
the directory is wrong
You need to replace esp with the location of your EFI partition
That’s not really the issue though, even when done correctly it’s found grub, and then forgotten the partition exists from a bootable partition perspective
Yeah I know, I was just saying what was wrong with that part
@vagrant coral not an MSI motherboard is it?
Nah, it's an Asus board
A b550
I think we try this and reboot a few times makes sure it sticks
@vagrant coral sorry
Nah it's all good :)
You could try and see if another bootloader like systemd-boot works, although I doubt it's a bootloader issue
If worst comes to worst I might just wipe the drive completely and try do a manual install instead of using the archlinux installer
I don’t think it’s an issue with arch-install as we manually did grub-install