You are not logged in.

#1 2019-07-04 16:22:03

jiv222
Member
Registered: 2019-01-14
Posts: 54

New install won't boot

Hello, I've been trying to get my new arch install to boot, but no matter what I do, I cant seem to figure out why my BIOS can't find anything to boot.

I've followed this guide for installing LVM on LUKS.
https://wiki.archlinux.org/index.php/Dm … VM_on_LUKS

I may be missing a very simple step; I haven't installed arch in a while.

A quick summary of what I've done to install the system and bootloader:

- Create two partitions (Linux Filesystem for nvme0n1p2, ESP on nvme0n1p1)
- Format ESP as FAT32.
- Setup and open luks container on nvme0n1p2
- setup lvm (root, home, swap)
- mount and install base system
- genfstab -U /mnt >> /mnt/etc/fstab
- setup locale, timezone, hwclock
- add encrypt and lvm2 hooks to mkinitcpio.conf (after block, before filesystem)
- verify booted in UEFI mode, and that /boot is mounted to nvme0n1p1
- bootctl install
- create entry at /boot/loader/entries/
- Add kernel options

 options cryptdevice=UUID=<UUID>:MyVol root=/dev/mapper/MyVol-root

Am I missing something obvious??

In the Dell logs, it says there is no bootable device found, but I am not sure why it cannot find my systemd-boot installed on nvme0n1p1. This partition isn't encrypted, but when I try to boot, it doesnt even prompt to decrypt anything, but instead boots straight into the UEFI firmware settings..

Any help would be great, let me know if any further info would be helpful in helping me.

Thanks!

Offline

#2 2019-07-04 17:20:47

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,426
Website

Re: New install won't boot

Paste your bootctl entry and the output of blkid: and don't obfuscate the UUIDs.


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#3 2019-07-05 07:06:04

jiv222
Member
Registered: 2019-01-14
Posts: 54

Re: New install won't boot

Here's the boot loader entry. Its path is

/boot/loader/entries/arch-linux.conf

https://pastebin.com/P75in9e2

Here is the output of blkid.
https://pastebin.com/5sf9EHne

Offline

#4 2019-07-05 07:17:13

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 25,423

Re: New install won't boot

If I'm interpreting you right you aren't even getting to systemd-boot? What is the output of

efibootmgr -v
bootctl status

?

Offline

#5 2019-07-05 14:28:05

jiv222
Member
Registered: 2019-01-14
Posts: 54

Re: New install won't boot

V1del wrote:

If I'm interpreting you right you aren't even getting to systemd-boot? What is the output of

efibootmgr -v
bootctl status

?

I'm even more confused now.. I woke up and turned my laptop on, and systemd-boot came up, followed by the prompt to decrypt luks partition.  Everything booted perfectly, but after rebooting, it refuses to boot.  Whether I manually select Linux Boot Manager or not, it fails to boot immediately and brings me to the uefi firmware.

Here is the output of efibootmgr -v
https://pastebin.com/22mHnegM
I suppose I should probably clean out some of those entries.

And here is the output of bootctl status:
https://pastebin.com/K0jztzyL

Offline

#6 2019-07-07 16:56:00

jiv222
Member
Registered: 2019-01-14
Posts: 54

Re: New install won't boot

In the output of bootctl status, should a ESP be listed under the current boot loader? The only other thing I can think of would be that all the extra entries are causing some kind of confusion on boot.

Like I said, the system can boot. I just dont know why it doesn't find my bootloader?

Any help would be great, even if it's just pointing out something obvious I'm missing. Thanks

Offline

Board footer

Powered by FluxBB