Help answer threads with 0 replies.
Go Back > Forums > Linux Forums > Linux - Distributions > Ubuntu
User Name
Ubuntu This forum is for the discussion of Ubuntu Linux.


  Search this Thread
Old 07-04-2018, 07:35 PM   #1
Registered: Oct 2014
Distribution: Slackware, Proxmox, Debian, CentOS, Ubuntu MATE
Posts: 773

Rep: Reputation: Disabled
initrd not building correctly

I am trying to install Ubuntu MATE 16.04 into a LUKS partition.

I am not using the defaults from the installer. I manually created two partitions, an ext2 /boot and a LUKS/ext4 system partition. With the installer I select the Something else option.

I manually select the partitions and I am not using LVM.

I am able to install with no problems. I do not reboot but instead, run some mount --bind commands and chroot into the new system. I verify the fstab. Tweak /etc/default/grub with GRUB_ENABLE_CRYPTODISK=y. I then run update-grub and update-initramfs -u -v.

All seems to go well.

Upon rebooting, the system shows a Press any key to continue message and then fails to prompt for a LUKS passphrase. The boot process drops to an initramfs shell. The ALERT error message is the UUID of the LUKS partition does not exist. Of course, the partition does exist and I can boot into a Live ISO and mount the partition.

I am unable to manually run cryptsetup at the (initramfs) prompt. Exploding the initrd shows no cryptsetup command in sbin.

Seems the initrd is not building correctly. Any ideas how to resolve?

Thanks again.

P.S. I performed the steps on one other system and was successful. I have compared config files, grub.cfg, etc. I have been testing this with both bare metal and VMs. I have browsed hundreds of tutorials and threads looking for a clue.

Edit: Possibly I have narrowed this to two issues. One, CRYPTSETUP=y needs to be set in /etc/environment and two, /etc/initramfs-tools/conf.d/cryptroot must be manually created. The Press any key to continue message is caused by a broken cryptomount -u entry in grub.cfg that should not exist. Looks like grub-mkconfig and update-initramfs are broken.

Edit: Looks like /etc/initramfs-tools/hooks/cryptsetup might be needed, chmod +x, containing:


Last edited by upnort; 07-05-2018 at 06:33 PM.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Building the initrd before installation. stf92 Slackware 20 05-29-2018 03:13 AM
[SOLVED] initrd not being read correctly by grub? chexmix Slackware 19 05-13-2016 06:28 AM
Building initrd.img with dracut-network dazdaz Linux - Networking 0 01-18-2013 11:44 AM
initrd issue, building new kernel jcas1411 Slackware 7 12-03-2010 09:33 PM
Necessity of initrd in building a kernel? Erik_the_Red Linux - Newbie 3 08-13-2005 09:53 PM > Forums > Linux Forums > Linux - Distributions > Ubuntu

All times are GMT -5. The time now is 01:06 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration