Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Fedora 22, disk-encryption passphrase, POST failure, dracut

I was in the process to install Fedora 22-3 on a brand-new Acer desktop (Aspire V11 Touch aka V3 112P P2E7) running on with Windows 8 to create a dual-boot system.

On installing Fedora

I am new to Fedora but not to installing dual-boot systems. I have followed these guidelines on how to do this, up to early point 9 there.

In summary, I switched on the legacy boot mode in the BIOS, put the Flash drive (USB FFD) on top of the boot sequence, started Fedora from the live-USB and began the installation from the icon in the desktop environment. Using the attending GUI I have reclaimed the disk space necessary for the installation from the existing data partition (easy for tell from the disproportionately large size).

Additionally/regretfully I chose to encrypt the disk with the luks method (probably believing that I was about to encrypt solely the partition or a user profile). I then selected one passphrase (for the encryption) and two passwords (for root and the user, having administrative rights). I am convinced to have carefully selected the password to be strong and memorable, although the evidence is that something went wrong there (too).

Start-up trouble 1

At start up, a bare and unfriendly dialogue box with a lock icon and text box shows up. By hitting escape it turns back to text mode, where the context becomes clear.

The system founds a device, realizes it is encrypted and asks for the passphrase. The computer does not accept the ones I type in and, after three attempts, it concludes that the Cryptography Startup failed.

Exceedingly slowly moves it on to the Dracut Emergency Shell. It suggests to save some log files saved in a USB and attach them to a bug report.

Question 1 How do I export a report file to a removable device with dracut? Just to see if there's some devil in the details, beside misapplications on my part.

Question 2 how do I turn off the system cleanly with dracut? shutdown does not exist there. Currently, I type reboot and it goes from text mode to a bare window with the Fedora logo. It then hangs on indefinitely. Then I power off the laptop. At any rate this suggest that dracut requires specific skills.

Just for the sake of narrative, I repeated the passphrase input step upon fastidiously mimicking obvious typos and mistakes to bridge the gap between memory and experience. To no avail though. As an aside, at this stage the keyboard does not signal if caps-on is locked.

Start-up trouble 2

One complication is then that, if I try to boot again from the live-USB, it ignores the boot order while I made no further change made in the BIOS settings in the meantime.

I double-checked the boot sequence: only the Windows Boot Manager is gone, which possibly can be expected as a temporary situation -- see guideline above.

Back to the main point, the boot process directly jumps into the Fedora GRUB and then, back again, into the passphrase request. This is a vicious loop. I have checked on another computer that the live-USB still works properly.

In summary

BIOS. Current setting: legacy mode. Boot priority order: USB FFD, HDD, ATAPI CDROM, Network Boot, USB HDD, USB CDROM. Oddity: priority order respected before installation with live USB, ignored after installation (it jumps into the Fedora GRUB insensitively)

POST. Bare and unfriendly password dialogue, skipped with ESC. Then request for passphrase for (whole?) disk, passphrase mismatch and fall-back on Dracut Emergency Shell. There, lack of skills on how to save and export report information.

Problem: how to work around the passphrase lock-out if the computer persistently reboots from the hard drive, that is locked?

Additional info: Possible data loss is no issue here (new laptop). If possible, though, I would like to rescue as much as possible of the existing situation in order to minimize further exposure to even worse quagmires.