Testing: Bootloader, grub: Can't find UUID

[jtagcat]

Booted ISO from https://github.com/archlinux/archinstall/actions/runs/835197079
9be01c2510970a4a36676e6afb3b1783 archlinux-2021.05.12-x86_64.iso (https://github.com/archlinux/archinstall/actions/runs/835198909 didn't manage to launch archinstall at all, slice error somewhere)

Result

There were quite a few 'unsupported log type' messages during the install. Nothing fatal shown to the user.

GRUB seemed fine, yet when selecting the (default) boot option, this is the output:

Starting version 240.2-2-arch


ERROR: device 'UUID=3620d4ba-foo-blah-baz-bong490' not found. Skipping fsck.
mount:/new_root:can't find UUID=3620d4ba-foo-blah-baz-bong490.
You are now being dropped into an emergency shell.
sh: can't access tty: job control turned off
[rootfs ]#

So, likely problems asking for decryption passwd and switching to actual root.

Logfile

Disk states before installing: {'blockdevices': [{'name': 'loop0', 'fstype': 'squashfs', 'fsver': '4.0', 'label': None, 'uuid': None, 'fsavail': '0', 'fsuse%': '100%', 'mountpoint': '/run/archiso/airootfs', 'type': 'loop', 'size': '651.7M'}, {'name': 'sda', 'fstype': None, 'fsver': None, 'label': None, 'uuid': None, 'fsavail': None, 'fsuse%': None, 'mountpoint': None, 'type': 'disk', 'size': '931.5G', 'children': [{'name': 'sda1', 'fstype': 'vfat', 'fsver': 'FAT32', 'label': None, 'uuid': '2051-7564', 'fsavail': None, 'fsuse%': None, 'mountpoint': None, 'type': 'part', 'size': '100M'}, {'name': 'sda2', 'fstype': None, 'fsver': None, 'label': None, 'uuid': None, 'fsavail': None, 'fsuse%': None, 'mountpoint': None, 'type': 'part', 'size': '16M'}, {'name': 'sda3', 'fstype': 'ntfs', 'fsver': None, 'label': None, 'uuid': 'ECBA58C8BA5890C6', 'fsavail': None, 'fsuse%': None, 'mountpoint': None, 'type': 'part', 'size': '930.9G'}, {'name': 'sda4', 'fstype': 'ntfs', 'fsver': None, 'label': None, 'uuid': '9EE690C4E6909DD9', 'fsavail': None, 'fsuse%': None, 'mountpoint': None, 'type': 'part', 'size': '499M'}]}, {'name': 'sdb', 'fstype': 'iso9660', 'fsver': 'Joliet Extension', 'label': 'ARCH_202105', 'uuid': '2021-05-12-10-34-33-00', 'fsavail': None, 'fsuse%': None, 'mountpoint': None, 'type': 'disk', 'size': '14.4G', 'children': [{'name': 'sdb1', 'fstype': 'iso9660', 'fsver': 'Joliet Extension', 'label': 'ARCH_202105', 'uuid': '2021-05-12-10-34-33-00', 'fsavail': '0', 'fsuse%': '100%', 'mountpoint': '/run/archiso/bootmnt', 'type': 'part', 'size': '720M'}, {'name': 'sdb2', 'fstype': 'vfat', 'fsver': 'FAT16', 'label': 'ARCHISO_EFI', 'uuid': '019B-8A6E', 'fsavail': None, 'fsuse%': None, 'mountpoint': None, 'type': 'part', 'size': '67M'}]}]}
Deprecated level detected in log message, please use new logging.<level> instead for the following log message:
Disk states before installing: {'blockdevices': [{'name': 'loop0', 'fstype': 'squashfs', 'fsver': '4.0', 'label': None, 'uuid': None, 'fsavail': '0', 'fsuse%': '100%', 'mountpoint': '/run/archiso/airootfs', 'type': 'loop', 'size': '651.7M'}, {'name': 'sda', 'fstype': None, 'fsver': None, 'label': None, 'uuid': None, 'fsavail': None, 'fsuse%': None, 'mountpoint': None, 'type': 'disk', 'size': '931.5G', 'children': [{'name': 'sda1', 'fstype': 'vfat', 'fsver': 'FAT32', 'label': None, 'uuid': '2051-7564', 'fsavail': None, 'fsuse%': None, 'mountpoint': None, 'type': 'part', 'size': '100M'}, {'name': 'sda2', 'fstype': None, 'fsver': None, 'label': None, 'uuid': None, 'fsavail': None, 'fsuse%': None, 'mountpoint': None, 'type': 'part', 'size': '16M'}, {'name': 'sda3', 'fstype': 'ntfs', 'fsver': None, 'label': None, 'uuid': 'ECBA58C8BA5890C6', 'fsavail': None, 'fsuse%': None, 'mountpoint': None, 'type': 'part', 'size': '930.9G'}, {'name': 'sda4', 'fstype': 'ntfs', 'fsver': None, 'label': None, 'uuid': '9EE690C4E6909DD9', 'fsavail': None, 'fsuse%': None, 'mountpoint': None, 'type': 'part', 'size': '499M'}]}, {'name': 'sdb', 'fstype': 'iso9660', 'fsver': 'Joliet Extension', 'label': 'ARCH_202105', 'uuid': '2021-05-12-10-34-33-00', 'fsavail': None, 'fsuse%': None, 'mountpoint': None, 'type': 'disk', 'size': '14.4G', 'children': [{'name': 'sdb1', 'fstype': 'iso9660', 'fsver': 'Joliet Extension', 'label': 'ARCH_202105', 'uuid': '2021-05-12-10-34-33-00', 'fsavail': '0', 'fsuse%': '100%', 'mountpoint': '/run/archiso/bootmnt', 'type': 'part', 'size': '720M'}, {'name': 'sdb2', 'fstype': 'vfat', 'fsver': 'FAT16', 'label': 'ARCHISO_EFI', 'uuid': '019B-8A6E', 'fsavail': None, 'fsuse%': None, 'mountpoint': None, 'type': 'part', 'size': '67M'}]}]}
Deprecated level detected in log message, please use new logging.<level> instead for the following log message:
You can skip selecting a drive and partitioning and use whatever drive-setup is mounted at /mnt (experimental)
BlockDevice(/dev/sda) contains the following partitions:
 Partition(path=/dev/sda1, size=100M, fs=vfat)
 Partition(path=/dev/sda2, size=16M, fs=None) (Filesystem not supported)
 Partition(path=/dev/sda3, size=930.9G, fs=ntfs) (Filesystem not supported)
 Partition(path=/dev/sda4, size=499M, fs=ntfs) (Filesystem not supported)
 * Passwords did not match * 
Disk states before installing: {'blockdevices': [{'name': 'loop0', 'fstype': 'squashfs', 'fsver': '4.0', 'label': None, 'uuid': None, 'fsavail': '0', 'fsuse%': '100%', 'mountpoint': '/run/archiso/airootfs', 'type': 'loop', 'size': '651.7M'}, {'name': 'sda', 'fstype': None, 'fsver': None, 'label': None, 'uuid': None, 'fsavail': None, 'fsuse%': None, 'mountpoint': None, 'type': 'disk', 'size': '931.5G', 'children': [{'name': 'sda1', 'fstype': 'vfat', 'fsver': 'FAT32', 'label': None, 'uuid': '2051-7564', 'fsavail': None, 'fsuse%': None, 'mountpoint': None, 'type': 'part', 'size': '100M'}, {'name': 'sda2', 'fstype': None, 'fsver': None, 'label': None, 'uuid': None, 'fsavail': None, 'fsuse%': None, 'mountpoint': None, 'type': 'part', 'size': '16M'}, {'name': 'sda3', 'fstype': 'ntfs', 'fsver': None, 'label': None, 'uuid': 'ECBA58C8BA5890C6', 'fsavail': None, 'fsuse%': None, 'mountpoint': None, 'type': 'part', 'size': '930.9G'}, {'name': 'sda4', 'fstype': 'ntfs', 'fsver': None, 'label': None, 'uuid': '9EE690C4E6909DD9', 'fsavail': None, 'fsuse%': None, 'mountpoint': None, 'type': 'part', 'size': '499M'}]}, {'name': 'sdb', 'fstype': 'iso9660', 'fsver': 'Joliet Extension', 'label': 'ARCH_202105', 'uuid': '2021-05-12-10-34-33-00', 'fsavail': None, 'fsuse%': None, 'mountpoint': None, 'type': 'disk', 'size': '14.4G', 'children': [{'name': 'sdb1', 'fstype': 'iso9660', 'fsver': 'Joliet Extension', 'label': 'ARCH_202105', 'uuid': '2021-05-12-10-34-33-00', 'fsavail': '0', 'fsuse%': '100%', 'mountpoint': '/run/archiso/bootmnt', 'type': 'part', 'size': '720M'}, {'name': 'sdb2', 'fstype': 'vfat', 'fsver': 'FAT16', 'label': 'ARCHISO_EFI', 'uuid': '019B-8A6E', 'fsavail': None, 'fsuse%': None, 'mountpoint': None, 'type': 'part', 'size': '67M'}]}]}
Deprecated level detected in log message, please use new logging.<level> instead for the following log message:
You can skip selecting a drive and partitioning and use whatever drive-setup is mounted at /mnt (experimental)
BlockDevice(/dev/sda) contains the following partitions:
 Partition(path=/dev/sda1, size=100M, fs=vfat)
 Partition(path=/dev/sda2, size=16M, fs=None) (Filesystem not supported)
 Partition(path=/dev/sda3, size=930.9G, fs=ntfs) (Filesystem not supported)
 Partition(path=/dev/sda4, size=499M, fs=ntfs) (Filesystem not supported)
 * Selected option "[B[B[A[A[B[B[B[B0" does not exist in available options * 
-- Guided template chosen (with below config) --
{
    "!encryption-password": "******",
    "!root-password": "******",
    "audio": "pipewire",
    "bootloader": "grub-install",
    "filesystem": "btrfs",
    "harddrive": {
        "model": "WDC_WDS100T2B0B",
        "path": "/dev/sda",
        "size": "931.5G"
    },
    "hostname": "proxynode",
    "kernels": [
        "linux"
    ],
    "keyboard-language": "et-nodeadkeys",
    "mirror-region": {
        "Estonia": {
            "https://mirror.cspacehostings.com/archlinux/$repo/os/$arch": true
        }
    },
    "nic": {
        "NetworkManager": true,
        "nic": "Use NetworkManager to control and manage your internet connection"
    },
    "packages": [],
    "profile": {
        "path": "/usr/lib/python3.9/site-packages/archinstall-2.2.0-py3.9.egg/archinstall/profiles/desktop.py"
    },
    "superusers": {
        "jc": {
            "!password": "******"
        }
    },
    "timezone": "Europe/Tallinn",
    "users": {}
}
Wiping BlockDevice(/dev/sda) by using partition format 1
Using and formatting the entire BlockDevice(/dev/sda).
Adding partition to BlockDevice(/dev/sda)
Adding partition to BlockDevice(/dev/sda)
Set the root partition Partition(path=/dev/sda2, size=931G, fs=btrfs) to use filesystem btrfs.
Partition Partition(path=/dev/sda1, size=512M, fs=vfat, rel_mountpoint=/boot) is a boot partition and has content inside.
Did not format Partition(path=/dev/sda1, size=512M, fs=vfat, rel_mountpoint=/boot) because .safe_to_format() returned False or .allow_formatting was False.
Encrypting Partition(path=/dev/sda2, size=931G, real_device=/dev/sda, fs=btrfs, rel_mountpoint=/) (This might take a while)
Formatting /dev/sda1 -> vfat
Formatting /dev/mapper/luksloop -> btrfs
Mounting Partition(path=/dev/mapper/luksloop, size=-1, real_device=/dev/sda2, fs=btrfs) to /mnt
Mounting Partition(path=/dev/sda1, size=512M, fs=vfat, rel_mountpoint=/boot) to /mnt/boot
Waiting for automatic mirror selection (reflector) to complete.
A new package mirror-list has been created: /etc/pacman.d/mirrorlist
Installing packages: ['base', 'base-devel', 'linux-firmware', 'linux', 'btrfs-progs']
A new package mirror-list has been created: /mnt/etc/pacman.d/mirrorlist
Installing packages: ('grub',)
Adding bootloader grub-install to Partition(path=/dev/sda1, size=-1, fs=vfat, mounted=/mnt/boot)
Installing packages: ('grub',)
Installing packages: ('efibootmgr',)
Installing packages: ('networkmanager',)
Enabling service NetworkManager.service
This audio server will be used: pipewire
Installing packages: ['pipewire', 'pipewire-alsa', 'pipewire-jack', 'pipewire-media-session', 'pipewire-pulse', 'gst-plugin-pipewire', 'libpulse']
Installing network profile Profile(desktop)
Installing packages: ['nano', 'vim', 'openssh', 'htop', 'wget', 'iwd', 'wireless_tools', 'wpa_supplicant', 'smartmontools', 'xdg-utils']
Installing network profile Profile(sway)
Installing packages: ['sway', 'swaylock', 'swayidle', 'waybar', 'dmenu', 'light', 'grim', 'slurp', 'pavucontrol', 'alacritty']
Installing packages: ['mesa', 'xf86-video-amdgpu', 'xf86-video-ati', 'libva-mesa-driver', 'vulkan-radeon']
Creating user jc
Setting password for jc
Enabling sudo permissions for jc.
For post-installation tips, see https://wiki.archlinux.org/index.php/Installation_guide#Post-installation
Updating /mnt/etc/fstab
Some required steps were not successfully installed/configured before leaving the installer:
 - bootloader
Detailed error logs can be found at: /var/log/archinstall
Submit this zip file as an issue to https://github.com/archlinux/archinstall/issues

Side complaint

315 commits to master since this release

..but, but I want to install Arch with the installer. Release seems quite outdated.

[dylanmtaylor]

Can you try with this ISO? @Torxed just pushed a bunch of dual-boot and formatting-related changes.

https://github.com/archlinux/archinstall/actions/runs/843294880

[Torxed]

All of the latests ISO's also contains lsblk output in the log to help identify where exactly the installer made an error. Most likely a mixup in PARTUUID vs disk UUID. Which isn't ideal obviously.

But most likely it's a mixup in /boot/loader/entries/<date>.conf and lsblk -o+PARTUUID,UUID,TYPE /dev/sda for some reason.

Regarding:

Release seems quite outdated.

We release with one months cycle, since Arch Linux builds it's ISO's every month. In between those releases, there might be hundreds of debug commits, so the commit amount doesn't really speak for anything :)

[jtagcat]

Can you try with this ISO? @Torxed just pushed a bunch of dual-boot and formatting-related changes.

archlinux/archinstall/actions/runs/843294880

Issue persists.

[Torxed]

Check, can you output the contents of /boot/loader/entries/<date>.conf and lsblk -o+PARTUUID,UUID,TYPE /dev/sda for us?

[jtagcat]

(Booting from a live fedora stick.)
After opening the LUKS partition, /boot on there is empty. The first partition, the EFI partition is attached.

lsblk:

NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT PARTUUID                             UUID                                 TYPE
sda      8:0    0 931.5G  0 disk                                                                                      disk
├─sda1   8:1    0   512M  0 part            889ae77c-be67-45ce-89e5-7bfcde473d8a 4934-0A56                            part
└─sda2   8:2    0   931G  0 part            a5d63405-9ebd-4d2c-a4c7-3bbce4058d11 4def279c-7284-4fce-9cb4-8c5d94079778 part

https://sh.c7.ee/wgZRd/EFI.tgz (63M) [tree] https://sh.c7.ee/dJLEH/install.log

[fluffydino]

I have this issue too.

[dylanmtaylor]

(Booting from a live fedora stick.) After opening the LUKS partition, /boot on there is empty. The first partition, the EFI partition is attached.

lsblk:

NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT PARTUUID                             UUID                                 TYPE
sda      8:0    0 931.5G  0 disk                                                                                      disk
├─sda1   8:1    0   512M  0 part            889ae77c-be67-45ce-89e5-7bfcde473d8a 4934-0A56                            part
└─sda2   8:2    0   931G  0 part            a5d63405-9ebd-4d2c-a4c7-3bbce4058d11 4def279c-7284-4fce-9cb4-8c5d94079778 part

https://sh.c7.ee/wgZRd/EFI.tgz (63M) [tree] https://sh.c7.ee/dJLEH/install.log

/boot should be a separate partition and have its own files in it.

[Torxed]

(Booting from a live fedora stick.) After opening the LUKS partition, /boot on there is empty. The first partition, the EFI partition is attached. lsblk:

NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT PARTUUID                             UUID                                 TYPE
sda      8:0    0 931.5G  0 disk                                                                                      disk
├─sda1   8:1    0   512M  0 part            889ae77c-be67-45ce-89e5-7bfcde473d8a 4934-0A56                            part
└─sda2   8:2    0   931G  0 part            a5d63405-9ebd-4d2c-a4c7-3bbce4058d11 4def279c-7284-4fce-9cb4-8c5d94079778 part

https://sh.c7.ee/wgZRd/EFI.tgz (63M) [tree] https://sh.c7.ee/dJLEH/install.log

/boot should be a separate partition and have its own files in it.

I think we only use one partition when GRUB is used?

[Ulimn]

I also ran into this issue. I don't know if this is useful info but after that I tried the same config but chose the systemd-boot instead of GRUB and it works that way.

[jtagcat]

I chose not to comment yesterday, iirc, I tried and failed with systemd-boot as well.

[KenVanHoeylandt]

I have this 100% of the time with archlinux-2021.08.01-x86_64.iso on VirtualBox 6.1.26. Options in archinstall:

• /dev/sda is empty, and I let archinstall do its thing with it.
• Main mount point is an ext4 partition with full disk encryption
• Bootloader is Grub
• Type of install is desktop with Gnome
• No root user, 1 admin user, no regular user
• Locale: US keyboard, NL local settings

Edit: I can confirm this 100% certainly related to the full disk encryption. I ran the installation process once more without that feature, and now it runs fine.

[Torxed]

I have this 100% of the time with archlinux-2021.08.01-x86_64.iso on VirtualBox 6.1.26. Options in archinstall:

• /dev/sda is empty, and I let archinstall do its thing with it.
• Main mount point is an ext4 partition with full disk encryption
• Bootloader is Grub
• Type of install is desktop with Gnome
• No root user, 1 admin user, no regular user
• Locale: US keyboard, NL local settings

Edit: I can confirm this 100% certainly related to the full disk encryption. I ran the installation process once more without that feature, and now it runs fine.

Could you attach or post the log file, to see what commonalities this shares with the above post? Sorry for the late response here, I dealt with some stuff in my private life that delayed my activity.

I have a sneaky suspicion that there are three separate issues in this thread that might have caused this similar issues:

1. Partial package installation (usually resulting in Failed to strap in packages: 256 which indicates failed installs)
2. Running out of disk space on the boot partition, partially creating what's needed to boot but not everything
3. RAID setups of any kind (this one is more rare, but usually manifests in a bootable system that hangs on waiting for luksdev)

But I can't confirm this without some more information, could you post lsblk -o+PARTUUID,UUID,TYPE as well as the /boot/loader/entries/<date>.conf? It would be very helpful.

[svartkanin]

@Torxed I think we could close this for now, given the recent updates to the partition classes and logic this might have been addressed with it

[svartkanin]

@Torxed shall we close this?