[WORKAROUND-FOUND] Peppermint 7 ... full disk encryption

[PCNetSpec]

Well let's try to keep encryption first eh as itMUST be working if you can boot recovery mode

Okay does the system have an active internet connection in recovery mode ?

If so, open a terminal and run these commands in sequence:

Code: [Select]

sudo apt-get updatethen

Code: [Select]

sudo apt-get upgradethen

Code: [Select]

sudo apt-get dist-upgradeonce completed, see if the system will reboot normally.

If not, boot into recovery mode again and try installing the 4.7.2 kernel via these instructions...

Open a terminal and run these commands in sequence:

Code: [Select]

mkdir ~/Desktop/kernel-4.7.2then

Code: [Select]

cd ~/Desktop/kernel-4.7.2then

Code: [Select]

wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7.2/linux-headers-4.7.2-040702-generic_4.7.2-040702.201608201334_amd64.debthen

Code: [Select]

wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7.2/linux-headers-4.7.2-040702_4.7.2-040702.201608201334_all.debthen

Code: [Select]

wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7.2/linux-image-4.7.2-040702-generic_4.7.2-040702.201608201334_amd64.debthen

Code: [Select]

sudo dpkg -i *.debthen REBOOT normally and see if it'll boot properly

Once rebooted, check which kernel you're using with

Code: [Select]

uname -a

[Gre9J]

 I appreciate all your help. Yes, agreed, encryption does appear to be working in recovery mode .. it's just not prompting me for the key during normal boot.

OK, first three commands seem to execute successfully.  I reboot and it still hangs at 'Starting Up', so back to recovery mode. Now I notice Update Manager is offering a few updates so I install these too before reboot  .. still hangs.

Commands to install kernel 4.7.2 appear to run successfully, so reboot .. and it still hangs at 'Starting Up'. Back to dear-old recovery mode .. output from 'uname -a' is:

Code: [Select]

Linux greg-Aspire-E5-573 4.7.2-040702-generic #201608201334 SMP Sat Aug 20 17:37:03 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

[AndyInMokum]

Hi Gre9J, for future reference, could you please remember to encapsulate terminal outputs with the Insert, Code # function.  For extra long outputs, please use the Spoiler, Sp function.  Don't combine the functions.  Only use one or the other  .  These preserve the original format of the output.  This makes it easier for future visitors to relate to their own issues.  These functions are found in the forum editor, above the,  Embarrassed and  the Cry emoticon respectively.  Use the Preview button to see how it'll look in the forum.  This time, I've done it for you - many thanks  .

[PCNetSpec]

Can you post the output from

Code: [Select]

inxi -Fwhilst running in recovery mode.

and post the contents of your

Code: [Select]

pluma /etc/fstaband

Code: [Select]

pluma /boot/grub/grub.cfg
Meanwhile I'll try an encrypted install in a VM

[Gre9J]

Hello AndyInMokum  Please accept my apology for that. Thanks for fixing it on this occasion.

[Gre9J]

Here's the outputs PCNetSpec:

Spoiler (click here to view / hide)

[close]

[PCNetSpec]

Okay all "recovery mode" options have the "nomodeset" kernel boot parameter set .. normal boots do not.

Shall we try adding "nomodedset" to the regular kernel boot line ?

Open a terminal and run:

Code: [Select]

sudo pluma /etc/default/grubfind the line that reads

Code: [Select]

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"and change it to read

Code: [Select]

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset"SAVE the file and exit pluma

Back in the terminal run:

Code: [Select]

sudo update-grubWhen that completes, reboot to test.

If that works .. does it leave you with a low screen resolution ?

[AndyInMokum]

Hello AndyInMokum  Please accept my apology for that. Thanks for fixing it on this occasion.

No problem, you weren't expected to know automatically  .

[Gre9J]

PCNetSpec I regret to report that after editing grub according to your instruction I'm still hanging at 'Starting Up' .. still no prompt for the encryption key.

Here's the content of my current /etc/default/grub:

Spoiler (click here to view / hide)

[close]

[PCNetSpec]

Can you post the contents of:

Code: [Select]

pluma /boot/grub/grub.cfgagain please.

[Gre9J]

My pleasure 

Spoiler (click here to view / hide)

[close]

[PCNetSpec]

can you test something for me

boot normally and wait until the PC appears to freeze .. give it a few more seconds, then try typing in your encryption key and then hit enter.

did it boot ?

Here's the reason I ask
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1370707
it may be the $vt_handoff parameter that's blocking displaying of the key entry dialog .. we can fix this, but it would be nice to know if that's what it is.

[Gre9J]

Sorry PCNetSpec, no luck with that.

While trying your suggestion I noticed something has changed. It now echoes whatever I type to the screen. For example hitting ESC, then Alt-SysRq R E I S U produces this:



I don't know if that's relevent. Maybe a result of the new kernel?

[PCNetSpec]

Okay try this

Boot to the GRUB menu .. leave the top option selected and hit the "E" key to edit .. find the line

linux   /vmlinuz-4.7.2-040702-generic root=/dev/mapper/peppermint--vg-root ro  quiet splash nomodeset $vt_handoff

and change it to

linux   /vmlinuz-4.7.2-040702-generic root=/dev/mapper/peppermint--vg-root ro

Now hit Ctrl+X or F10 to continue booting

what happened ? .. did it boot, or maybe give us a clue where it's hanging ?

[Gre9J]

Doing that looks similar to recovery mode. Lots of scrolling text until it prompts for the encryption key. I enter it, then, more scrolling text before I arrive at the desktop.

I wish I could buy you a beer, or, two or three or four or five  I really appreciate your help, enthusiasm and dedication.

I'm about to go offline for the night. Tomorrow I'm out of town for the best part of the day, so it will probably be 24 hours before I get back to this.