You are not logged in.

#1 2017-11-17 10:49:22

guiguibo
Member
Registered: 2012-10-13
Posts: 6

Grub/kernel fails to found encrypted disk after update

Hi,

I just updated my kernel and I now have the following issue after rebooting (the hard disk is encrypted):
The grub boots correctly, but it doesn't promt anymore for the password to decrypt the disk

The messages are the following:
:: running hook [udev]
:: Triggering uevents...
:: running hook [keymap]
:: Loading keymap...done.
:: running hook [encrypt]
Waiting 10 seconds for device /dev/disk/by-uuid/UUIDCYPHEREDPARTITION
# usually the password is promted here, but not anymore sad
Waiting 10 seconds for device /dev/disk/by-uuid/UUIDPARTITION
ERROR: device 'UUID=UUIDPARTITION' not found. Skipping fsck
:: mounting 'UUID=UUIDPARTITION' on real root
mount: /new_root: can't find UUID=UUIDPARTITION.

The uuid are still correct (checked on another linux) and I am able to decrypt the partition manually

What should I do ?

Offline

#2 2017-11-17 11:07:43

lo1
Member
Registered: 2017-09-25
Posts: 584

Re: Grub/kernel fails to found encrypted disk after update

Please use code tags, post output from

lsblk -O
cat /etc/fstab
cat /etc/mkinitcpio.conf

Offline

#3 2017-11-17 12:14:56

guiguibo
Member
Registered: 2012-10-13
Posts: 6

Re: Grub/kernel fails to found encrypted disk after update

lsblk -O

NAME           KNAME MAJ:MIN FSTYPE      MOUNTPOINT             LABEL UUID                                   PARTTYPE PARTLABEL PARTUUID                             PARTFLAGS  RA RO RM HOTPLUG MODEL            SERIAL                 SIZE STATE OWNER GROUP MODE       ALIGNMENT MIN-IO OPT-IO PHY-SEC LOG-SEC ROTA SCHED    RQ-SIZE TYPE  DISC-ALN DISC-GRAN DISC-MAX DISC-ZERO WSAME WWN                RAND PKNAME HCTL       TRAN   SUBSYSTEMS          REV VENDOR
sdd            sdd     8:48                                                                                                                                                    128  0  1       1 Ext SSD          171259400249         238,5G runni root  disk  brw-rw----         0    512      0     512     512    1 deadline     128 disk         0        0B       0B         0    0B                       1        12:0:0:0   usb    block:scsi:usb:pci 0    SanDisk 
├─sdd1         sdd1    8:49  ext3        /media/user/79828ee       79828eee-fbed-4ea2-b8a7-19d4eb79988c   0x83               3f446b63-01                                    128  0  1       1                                         100M       root  disk  brw-rw----         0    512      0     512     512    1 deadline     128 part         0        0B       0B         0    0B                       1 sdd                      block:scsi:usb:pci      
└─sdd2         sdd2    8:50  crypto_LUKS                              3b656068-1b9f-4e3b-af5b-3db18c252f6f   0x83               3f446b63-02                                    128  0  1       1                                       219,6G       root  disk  brw-rw----         0    512      0     512     512    1 deadline     128 part         0        0B       0B         0    0B                       1 sdd                      block:scsi:usb:pci      
  └─luks-3b656068-1b9f-4e3b-af5b-3db18c252f6f
               dm-3  252:3   ext4        /media/user/83168b2       83168b27-9ae0-4386-8ffc-b7bc7c734b50                                                                     128  0  0       0                                       219,5G runni root  disk  brw-rw----         0    512      0     512     512    1              128 crypt        0        0B       0B         0    0B                       0 sdd2                     block                   

/etc/fstab

# 
# /etc/fstab: static file system information
#
# <file system>	<dir>	<type>	<options>	<dump>	<pass>
UUID=83168b27-9ae0-4386-8ffc-b7bc7c734b50	/         	ext4      	rw,relatime,stripe=8191,data=ordered	0 1

UUID=79828eee-fbed-4ea2-b8a7-19d4eb79988c       /boot     	ext3      	rw,relatime,data=ordered	0 2

/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 udev autodetect modconf block  keymap filesystems encrypt keyboard fsck"

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

# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""

/boot/grub/grub.conf memuentry part

menuentry 'Arch Linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-83168b27-9ae0-4386-8ffc-b7bc7c734b50' {
	load_video
	set gfxpayload=keep
	insmod gzio
	insmod part_msdos
	insmod ext2
	set root='hd0,msdos1'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1  79828eee-fbed-4ea2-b8a7-19d4eb79988c
	else
	  search --no-floppy --fs-uuid --set=root 79828eee-fbed-4ea2-b8a7-19d4eb79988c
	fi
	echo	'Chargement de Linux linux…'
	linux	/vmlinuz-linux root=UUID=83168b27-9ae0-4386-8ffc-b7bc7c734b50 rw cryptdevice=/dev/disk/by-uuid/3b656068-1b9f-4e3b-af5b-3db18c252f6f:cryptroot
	echo	'Chargement du disque mémoire initial…'
	initrd  /initramfs-linux.img
}

Offline

#4 2017-11-17 12:29:22

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 11,783
Website

Re: Grub/kernel fails to found encrypted disk after update

You haven't merged your pacnew files, which may or may not be causing you problems. I would start by handling those.

https://wiki.archlinux.org/index.php/Pa … nd_Pacsave

Then regenerate your initramfs.


Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

#5 2017-11-17 12:41:59

lo1
Member
Registered: 2017-09-25
Posts: 584

Re: Grub/kernel fails to found encrypted disk after update

HOOKS="base udev autodetect modconf block  keymap filesystems encrypt keyboard fsck"

Try putting "encrypt" hook before "filesystems" in your mkinitcpio.conf, according to the wiki. Try following that order becuase it seems to matter.
Then run

sudo mkinitcpio -p linux

Also, i don't know if it's relevant but there's a double space between "block" and "keymap", fix it wink

Offline

Board footer

Powered by FluxBB