1

I was in the process to install Fedora 22-3 on an Acer desktop with Windows 8 to create a dual-boot system. I believe to have followed reasonable guidelines on how to do this. (I reached up to point 9 there before getting into troubles). After a not so succint description, I have three questions (for the moment).


In summary, I switched on the legacy boot mode in the BIOS, put the flash drive on top of the boot order, started Fedora from the live-USB and began the installation from the icon in that 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 (probably believing that I was about to encrypt solely the partition or a user profile). All in all, I 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 -- but I am also aware the first question is why the computer does what it does, rather than why it didn't do what I wanted it to do.


The problem is here. At start up, an icon with lock and text box appears in a rather user-unfriendly manner since it does not offer any textual cue on what that bother is about. By pressing escape it turns back to text mode, where the context becomes clear.

The system founds a device, realizes it is encrypted (with the lucks method) and asks for the passphrase. The computer does not accept the ones I input and, after three attempts, it concludes that the Cryptography Startup failed. (As an aside, at this stage the laptop does not turn on any led if caps-on is locked, but I have put this to the test too.)

Very slowly moves it on, and then it starts 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 if I am not wrong. Currently, I type reboot and it goes from text mode to a bare window with the Fedora logo. It then hangs. Then I power oof the laptop.


The basic need is to eventually circumvent and undo this encryption barrier because of the passphrase mismatch.

One complication is then that, if I try to boot again from the live-USB, it ignores the boot order (no further change made in the BIOS settings in the meantime) and jumps into the Fedora GRUB and then, back again, into the passphrase request. Seems weird.

Question 3: am I doing something plainly wrong here or is this consequential on the troubles above?

Thanks for dealing with this. Detailed instructions will be much appreciated. I would like to fix these issues first and, in a second step, remove cryptography and probably start with a fresh start.


Addendum

I felt I had to summarise the state of the play

  • 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 lucs 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.

closed as too broad by maxschlepzig, G-Man, Jeff Schaller, Isaac, telcoM May 28 '18 at 4:17

Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

  • An answer to the same question is in the making on a Fedora forum. Lest contributors to this one forum feel discouraged to drop their own ideas here, I will make sure that the two posts are cross-linked. – XavierStuvw Sep 9 '15 at 6:39
  • Following on the previous comment, the problem has been solved. Please visit the relevant Fedora forum post. – XavierStuvw Sep 25 '15 at 21:55
  • Would anyone like to answer the question here? – Jeff Schaller May 27 '18 at 18:33