You are not logged in.
Hello,
I have a Dell Latitude 7430. I have installed Arch on it, using an encrypted root parition.
After completing installation (wheres I must obviously have forgotten something) the UEFI tells me, that there is no disc installed in the laptop.
After booting again from usb, decrypting (cryptsetup open /dev/nvme0n1p3 root), mounting (mount /dev/mapper/root /mnt) and chrooting into the installation (arch-chroot /mnt), I cannot find any obvious mistake. So kindly asking for support.
While being chrooted:
lsblk -f
sda (usb drive)
nvme0n1 1.8T disk (the only drive in the Laptop)
-nvme0n1p1 1G /boot
-nvme0n1p2 16g (swap)
-nvme0n1p3 1.8t
--root //boot/loader/entries/arch.conf
title Arch Linux
linux /vmlinuz-linux
initrd /intel-ucode.img
initrd /initramfs-linux.img
options cryptdevice=UUID=15...0757c:cryptroot root=/dev/mapper/cryptroot/boot/loader/entries/arch-fallback.conf
title Arch Linux Fallback
linux /vmlinuz-linux
initrd /intel-ucode.img
initrd /initramfs-linux-fallback.img
options cryptdevice=UUID=15...0757c:cryptroot root=/dev/mapper/cryptrootoutput of bootctl:
ystem:
Firmware: n/a (n/a)
Firmware Arch: x64
Secure Boot: disabled (unknown)
TPM2 Support: yes
Measured UKI: no
Boot into FW: supported
Current Boot Loader:
Product: n/a
Features: - Boot counting
- Menu timeout control
- One-shot menu timeout control
- Default entry control
- One-shot entry control
- Support for XBOOTLDR partition
- Support for passing random seed to OS
- Load drop-in drivers
- Support Type #1 sort-key field
- Support @saved pseudo-entry
- Support Type #1 devicetree field
- Enroll SecureBoot keys
- Retain SHIM protocols
ESP: n/a
File: --n/a
Random Seed:
System Token: set
Exists: Yes
Available
Firmware: n/a
Firmware Arch: x64
Secure Boot: disabled (unknown)
TPM2 Support: no
Measured UKI: no
Boot into FW: supported
Available Boot Loaders on ESP:
ESP: /boot (/dev/disk/by-partuuid/5c7c94b1-a0e8-47e4-8202-4e5ebcc59d66)
File: |-/EFI/systemd/systemd-bootx64.efi (systemd-boot 255.5-4-arch)
`-/EFI/BOOT/BOOTX64.EFI (systemd-boot 255.5-4-arch)
Boot Loaders Listed in EFI Variables:
Title: Linux Boot Manager
ID: 0x0001
Status: active, boot-order
Partition: /dev/disk/by-partuuid/5c7c94b1-a0e8-47e4-8202-4e5ebcc59d66
File: -/EFI/systemd/systemd-bootx64.efi
Boot Loader Entries:
$BOOT: /boot (/dev/disk/by-partuuid/ff...)
token: arch
Default Boot Loader Entry:
type: Boot Loader Specification Type #1 (.conf)
title: Arch Linux
id: arch.conf
source: /boot//loader/entries/arch.conf
linux: /boot//vmlinuz-linux
initrd: /boot//intel-ucode.img
/boot//initramfs-linux.img
options: cryptdevice=UUID=...:cryptroot root=/dev/mapper/cryptrootWould be thankfully for suggestions.
Edit: The Linux Boot Manager is listed in the UEFI, whereas I have to admit that this laptop has the most complex UEFI I've ever come across. I have disabled secure boot right fom the beginning but now also disabled "Microsoft UEFI CA". Furthermore in Storage I changed the SATA/NVMe Operation mode from "Raid on" to AHCI/NVMe. However, this doesn't seem to have an effect.
Last edited by funkaddict (2024-05-07 18:59:42)
Offline
I just checked my installation and my first line is:
Firmware: UEFI 2.70 (American Megatrends 5.19)and Inoticed this difference from your setup
Current Boot Loader:
Product: systemd-boot 255.5-4-archthen this one
ESP: /dev/disk/by-partuuid/1e6abd64-da46-4992-abe0-16e2c9e85a61
File: └─/EFI/BOOT/BOOTX64.EFIPlease note that I'm not running any kind of encryption. BTW, did you issue a "bootctl install" at the end of the installation?
Last edited by fmc000 (2024-05-07 16:55:41)
Linux user since 1996. Currently running Arch on an I7 11th gen laptop with root on zfs with continuous snapshots and replication.
Offline
I just checked my installation and my first line is:
Firmware: UEFI 2.70 (American Megatrends 5.19)
Yes right. I edited this. I was taking the bootctl from my current system (from which I am writing this) and altering as it is shown on the screen on the computer where I am trying to install Arch.
and Inoticed this difference from your setup
Current Boot Loader: Product: systemd-boot 255.5-4-archthen this one
ESP: /dev/disk/by-partuuid/1e6abd64-da46-4992-abe0-16e2c9e85a61 File: └─/EFI/BOOT/BOOTX64.EFIPlease note that I'm not running any kind of encryption. BTW, did you issue a "bootctl install" at the end of the installation?
I am not completely understanding, where the problem might be here?
In the meanwhile, I did some further trials in the UEFI (BIOS) config. As said above its hillariously complex. Now I got systemd-boot to show the different options to start either Arch, or Arch-Fallback. So far so good. So it seems it was an UEFI-related issue. However, now I am running into the following prompt. I guess I have a problem with regards to encryption configuration:
A password is required to access the volume:
Command requires device and mapped name as argumentsThis is described on stackexchange. I am trying to figure out the problem with the cryptdevice configuration now
Offline
Okay, I found the issue. It was a simple typo in the
/boot/loader/entries/arch.confHowever, I think it will take me a while to tune this system to where I want to get. Especially the UEFI with its thousand functions, will cost quite some time to invest.
Thank you fmc000 for your thoughts!
Last edited by funkaddict (2024-05-07 19:00:39)
Offline