LinuxQuestions.org
Support LQ: Use code LQ3 and save $3 on Domain Registration
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 12-01-2013, 04:48 AM   #1
Phorize
Member
 
Registered: Sep 2005
Location: UK
Distribution: Slackware
Posts: 217

Rep: Reputation: 23
Trouble shooting boot failure with uefi+lvm on luks


Hi all. I have a machine with the following configuration:

/dev/sda1 EFI partition
/dev/sda2 ext2 partition mounting /boot
/dev/sda3 luks partioning containing lv group with separate swap, home and root partitions.

The boot currently fails when elilo starts-it's expecting to find /dev/crypt/root but that's not mounted.

I built an initrd.gz (using output from mkinitrd_command_generator.sh)-it installed to /boot

In the absence of documentation that sets out exactly how elilo expects to handle invoking the initrd.gz I assumed that I needed to ensure that /boot was unencrypted so that the initrd could handle the fully encrypted /dev/sda3.

elilo.conf in /boot/efi/EFI/slackware has the initrd set to /boot/initrd.gz and the kernel set to /boot/vmlinuz-generic-3.10.17

This is probably obvious to those of you who have played around with elilo and encrypted partitions, but having looked at the elili documentation, the rest of the stuff on rodsbooks and the uefi/dmcrypt docs on in the slackware tree I am well and truly stumped.

What do we think?
 
Old 12-01-2013, 08:51 AM   #2
tux_dude
Member
 
Registered: Dec 2008
Distribution: Slackware64 Current
Posts: 226

Rep: Reputation: 33
What was the mkinitrd command used and the content of /etc/crypttab?
 
Old 12-02-2013, 02:56 PM   #3
mostlyharmless
Senior Member
 
Registered: Jan 2008
Distribution: Slackware 14.1 (multilib) with kernel 3.15.5
Posts: 1,533
Blog Entries: 12

Rep: Reputation: 171Reputation: 171
Quote:
I built an initrd.gz (using output from mkinitrd_command_generator.sh)-it installed to /boot
Yes, I had the same problem; I had to manually modify the mkinitrd command. You can see what I did in my blog, hope it's helpful: http://www.linuxquestions.org/questi...rmless-386558/
 
Old 12-02-2013, 03:52 PM   #4
metageek
Member
 
Registered: Jun 2007
Location: manchester, uk
Distribution: Slackware
Posts: 118

Rep: Reputation: 23
Quote:
Originally Posted by Phorize View Post
I built an initrd.gz (using output from mkinitrd_command_generator.sh)-it installed to /boot
Most likely you will have to add -L to the command line suggested by mkinitrd_command_generator.sh . This has been a problem that has affected many.
 
Old 12-02-2013, 06:35 PM   #5
natharran
Member
 
Registered: Jul 2012
Location: Czech Republic
Distribution: Slackware64 14.1
Posts: 34

Rep: Reputation: Disabled
Quote:
Originally Posted by Phorize View Post
I built an initrd.gz (using output from mkinitrd_command_generator.sh)-it installed to /boot
In my experience, mkinitrd_command_generator.sh doesn't usually give very good advice (well, it probably does on very standard installations, but I have always had to modify the suggested command due to encryption and other funny things).

Based on your post I would guess that the correct command could be
Code:
mkinitrd -c -k <your kernel> -m <all colon separated modules you need, especially your root filesystem> -f <your root filesystem> -r /dev/crypt/root -C /dev/sda3 -L -u
You may also try to move your kernel and initrd.gz to the EFI partition and adjust the elilo.conf accordingly (perhaps it's not necessary, I don't know whether elilo can look to other partitions with different filesystems directly but it's where I have my boot data and all works well).

Hope some of this helps you .
 
Old 12-04-2013, 02:33 PM   #6
Phorize
Member
 
Registered: Sep 2005
Location: UK
Distribution: Slackware
Posts: 217

Original Poster
Rep: Reputation: 23
OK, this one was strange. There was nothing wrong with the mkinitrd options-it was correct for all the necessary modules, the relevant partitions and encryption. The elilo.conf gave the correct location for the kernel and the initrd.gz. I don't see anything wrong with the partitioning-you can't mount the the efi partition unless /boot is accessible, so that's OK. I've never played around with elilo before so it might be that I'm missing something obvious, i just can't see that though. I decided to call it a day and revert to lilo/mbr-perhaps I'll revisit this when 14.2 comes out

Thank you all for your offers of help. It's always good to know that the LQ Slackware community has got your back.

Last edited by Phorize; 12-04-2013 at 02:35 PM. Reason: To say thanks!
 
  


Reply


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
[SOLVED] Cannot see /dev/sda1 boot in LUKS - LVM setup hua Slackware 4 09-29-2012 08:30 AM
[SOLVED] partial boot, mount invalid argument, lvm on luks BashTin Slackware 2 05-22-2012 06:20 PM
Trouble booting new Slack 13. LVM on Luks BashTin Slackware 8 10-22-2011 07:56 PM
LUKS LVM with usb token at boot mrmnemo Ubuntu 3 02-26-2011 08:35 AM
[SOLVED] Combining LUKS and LVM... LILO fails to boot STDOUBT Slackware - Installation 4 06-10-2010 09:58 PM


All times are GMT -5. The time now is 09:03 PM.

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