Installing Debian 9 (Stretch) RC4 with full disk encryption.

Help with issues regarding installation of Debian
Post Reply
Message
Author
toopho
Posts: 18
Joined: 2009-02-08 12:08

Installing Debian 9 (Stretch) RC4 with full disk encryption.

#1 Post by toopho »

I have a ThinkPad T500 with libreboot and I am trying to install Debian 9 (Stretch) Release candidate 4 following all the instructions in the Libreboot documentation to install Debian encrypted with full disk encryption. After the installation, the system boots, but it doesn't get to the desktop environment.

I go to boot the system and with “grub> cryptomount -a” I enter the passphrase and after more than one minute (very long time and I don't know why) it is accepted, then I change the third line in the documentation from

<<grub> linux /vmlinuz root=/dev/mapper/matrix-rootvolcryptdevice=/dev/mapper/matrix-rootvol:root>>

to

<<grub> linux /vmlinuz root=/dev/mapper/matrix rootvolcryptdevice=/dev/mapper/matrix-rootvol:root>>

that is, I remove the first hyphen that appears in that line of the documentation. And after booting the system and some output, it gets to the following lines:

Code: Select all

Begin: Mounting root file system … Begin: Running /scripts/local-top … WARNING: Failed to connect to lvmetad. Falling back to device scanning. 
  Volume group “matrix” not found
  Cannot process volume group matrix
[      2.693881] device-mapper: uevent: version 1.0.3
[      2.693881] device-mapper: ioctl: 4.35.0-ioctl (2016-06-23) initialised: dm-develatredhatcom
Please unlock disk sda1_crypt:
(I enter the passphase there and it continues as follows)

Code: Select all

[  143.846160] NET: Registered protocol family 38
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  Reading all physical volumes. This may take a while...
  Found volume group “matrix” using metadata type lvm2
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  2 logical volume(s) in volume group “matrix” now active
cryptsetup (sda1_crypt): unknown fstype, bad password or options?
Device-mapper: remove ioctl on sda1_crypt failed: Device or resource busy
(and that last line repeats 25 times in about 2 seconds)

Code: Select all

Device-mapper: remove ioctl on sda1_crypt failed: Device or resource busy
Device sda1-crypt is still in use.
Please unlock disk sda1_crypt: Device sda1_crypt already exists.
(I enter again the passphase there and instantly continues as follows)

Code: Select all

cryptsetup (sda1_crypt): cryptsetup failed, bad password or options?
Please unlock disk sda1_crypt: Device sda1_crypt already exists.
(And again I enter the passphase one more time there and instantly continues as follows)

Code: Select all

cryptsetup (sda1_crypt): cryptsetup failed, bad password or options?
cryptsetup (sda1_crypt): maximum number of tries exceeded
cryptsetup: going to sleep for 60 seconds...
done.
Begin: Running /scripts/local-premount … [ 1009.924016] raid6: sse2x1   gen() 2577 MB/s
[ 1009.992011] raid6: sse2x1     xor()    2701 MB/s
[ 1010.060026] raid6: sse2x2     gen()   3577 MB/s
(more lines of output that I have omitted here)
[ 1010.380000] Btrfs loaded, crc32c=crc32c-generic
Scanning for Btrfs filesystems
[ 1010.953680] BTRFS: device fsid bc8a5713-52bc-4913-5a7-9ca951a167e6 devid 1 transid 11771 /dev/mapper/matrix-rootvol
[ 1009.965844] PM: Starting manual resume from disk
done.
Begin: Waiting for root file system … Begin: Running /scripts/local-block … done.
Begin: Running /scripts/local-block … done.
(This line is repeated 28 times)
Begin: Running /scripts/local-block … done.
done.
Gave up waiting for root file system device. Common problems:
-Boot args (cat /proc/cmdline)
-Check rootdelay (did the system wait long enough?)
-Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/mapper/matrix does not exist. Dropping to a shell!
(and then BusyBox comes up)

Post Reply