Arch Linux

xra1n

Member

Registered: 2022-02-06

Posts: 2

[SOLVED] A start job running for /dev/mapper/root (/ 1min 30s)

I am trying to install a system with a encrypted root partition

I am dual booting with Windows
I am using systemd-boot as my bootloader

Welcome to Linux!
...
[ *** ] A start job is running for /dev/mapper/root (1min 21s / 1min 30s)

And after 1min 30s I get "Timed out waiting for device /dev/mapper/root"

Output of lsblk -f

NAME        FSTYPE      FSVER LABEL       UUID                                 FSAVAIL FSUSE% MOUNTPOINTS

nvme0n1                                                                                       
├─nvme0n1p1 vfat        FAT32             B6C7-9D36                                           
├─nvme0n1p2                                                                                   
├─nvme0n1p3 ntfs                          72AAC473AAC4357F                                    
├─nvme0n1p4 ntfs                          549E37F99E37D1EA                                    
└─nvme0n1p5 crypto_LUKS 2                 9ec096e2-a8be-4d15-bfe1-376734e8242b                

cat /etc/mkinitcpio.conf

# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES=(piix ide_disk reiserfs)
MODULES=()

# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image.  This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=()

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way.  This is useful for config files.
FILES=()

# HOOKS
# This is the most important setting in this file.  The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
##   This setup specifies all modules in the MODULES setting above.
##   No raid, lvm2, or encrypted root is needed.
#    HOOKS=(base)
#
##   This setup will autodetect all modules for your system and should
##   work as a sane default
#    HOOKS=(base udev autodetect block filesystems)
#
##   This setup will generate a 'full' image which supports most systems.
##   No autodetection is done.
#    HOOKS=(base udev block filesystems)
#
##   This setup assembles a pata mdadm array with an encrypted root FS.
##   Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
#    HOOKS=(base udev block mdadm encrypt filesystems)
#
##   This setup loads an lvm2 volume group on a usb device.
#    HOOKS=(base udev block lvm2 filesystems)
#
##   NOTE: If you have /usr on a separate partition, you MUST include the
#    usr, fsck and shutdown hooks.
HOOKS=(base systemd autodetect keyboard modconf block sd-encrypt filesystems fsck)

# COMPRESSION
# Use this to compress the initramfs image. By default, zstd compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="zstd"
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"

# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=()

cat /boot/loader/entries/arch.conf

title Arch Linux
linux /vmlinuz-linux
initrd /intel-ucode.img
initrd /initramfs-linux.img
options rd.luks.name=/9ec096e2-a8be-4d15-bfe1-376734e8242b=root root=/dev/mapper/root nowatchdog loglevel=3

If anyone has any ideas on what I've done wrong, or ideas on how to troubleshoot this, I would be really grateful!

Last edited by xra1n (2022-02-06 15:59:05)

xra1n

Member

Registered: 2022-02-06

Posts: 2

Re: [SOLVED] A start job running for /dev/mapper/root (/ 1min 30s)

Fixed I had a typo on bootloader config