Update:
I've made some progress, but I still haven't solved the problem. I modified the /etc/initramfs-tools/conf.d/cryptroot file again, so it says:
Code: Select all
CRYPTOPTS=target=sda5_crypt,source=/dev/sda5,lvm=LogicalVolumesOnEncryptedPartition-Root
The boot sequence starts up the same:
Code: Select all
Volume group "LogicalVolumesOnEncryptedPartition" not found
Skipping volume group LogicalVolumesOnEncryptedPartition
Unable to find LVM volume LogicalVolumesOnEncryptedPartition/Root
Then it asks for the passphrase, and OMG, it actually loads the volumes!
Code: Select all
Unlocking the disk /dev/sda5 (cryptroot)
Enter passphrase:
Reading all physical volumes. This may take a while...
Found volume group "LogicalVolumesOnEncryptedPartition" using metadata type lv
m2
3 logical volumes(s) in volume group "LogicalVolumesOnEncryptedPartition" now a
ctive
cryptsetup: cryptroot set up successfully
INIT: version 2.88 booting
Using makefile-style concurrent boot in runlevel S.
Starting the hotplug events dispatcher: udevd.
Synthesizing the initial hotplug events...done.
Waiting for /dev to be fully populated...udevd[600]: failed to execute '/lib/ude
v/mtp-probe' 'mtp-probe /sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.2 4 3'
: No such file or directory
udevd[601]: failed to execute '/lib/udev/mtp-probe' 'mtp-probe /sys/devices/pci0
000:00/0000:00:1a.0/usb3/3-1/3-1.3 3 4': No such file or directory
Note that the mtp-probe errors happen with the LiveCD too. So far, so good...
Code: Select all
done.
Setting parameters of disc: (none).
Setting system clock.
Setting preliminary keymap...done.
Checking root file system...fsck from util-linux-ng 2.17.2
/dev/mapper/LogicalVolumesOnEncryptedPartition-Root: Superblock last mount time is in the future.
(by less than a day, probably due to the hardware clock being incorrectly set) FIXED.
/dev/mapper/LogicalVolumesOnEncryptedPartition-Root: Superblock last mount time is in the future.
(by less than a day, probably due to the hardware clock being incorrectly set) FIXED.
/dev/mapper/LogicalVolumesOnEncryptedPartition-Root: clean, 163740/1310720 files, 1073274/5242880 blocks
done.
Finally, it loaded my root filesystem! But wait...now it's trying to unlock my drive again, when it's already unlocked!
Code: Select all
Starting early crypto disks...sda5_crypt (starting)...
Unlocking the disk /dev/sda5 (sda5_crypt)
Enter passphrase:
Cannot use device /dev/sda5 which is in use (already mapped or mounted).
Unlocking the disk /dev/sda5 (sda5_crypt)
Enter passphrase:
Cannot use device /dev/sda5 which is in use (already mapped or mounted).
On the third try, I may have made a typo, or it may have just decided to do something differently:
Code: Select all
Unlocking the disk /dev/sda5 (sda5_crypt)
Enter passphrase:
failed.
done.
Cleaning up ifupdown....
Loading kernel modules...done.
Setting up networking....
Setting the system clock.
Setting up LVM Volume Groups Reading all physical volumes. This may take a while...
Found volume group "LogicalVolumesOnEncryptedPartition" using metadata type lvm2
3 logical volume(s) in volume group "LogicalVolumesOnEncryptedPartition" now active
.
Starting remaining crypto disks...sda5_crypt (starting)...
Unlocking the disk /dev/sda5 (sda5_crypt)
Enter passphrase:
Cannot use device /dev/sda5 which is in use (already mapped or mounted).
Unlocking the disk /dev/sda5 (sda5_crypt)
Enter passphrase:
After the fourth and fifth password prompts, I headed off to bed.
This morning, that screen was still up, and I entered the passphrase one more time...and lo and behold, it actually booted and got me to the login screen! I tried the same process again, and I can eventually get to the login screen after about 7 password attempts (the second time required at least one more try, so typos are probably factoring in somewhere).
Of course, everything is STILL not correct even after logging in: I am now able to log in, but the Disk Utility shows my
LVM volumes (dm-1, dm-2, and dm-3 for root, swap, and data, respectively) as unformatted drives. I can access their data, but I can't imagine this won't have any ill effects. The OS should really be recognizing their formatting (ext4 for root, swap for swap, and ext3 for my data partition).
In case it matters, my fstab is as follows (note that on Ubuntu, the same LUKS/
LVM setup worked without a hitch):
Code: Select all
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
/dev/mapper/LogicalVolumesOnEncryptedPartition-Root / ext4 errors=remount-ro 0 1
/dev/sda3 /boot ext4 defaults 0 2
/dev/mapper/LogicalVolumesOnEncryptedPartition-Swap none swap sw 0 0
/dev/mapper/LogicalVolumesOnEncryptedPartition-Data /home/user/data ext3 auto,user,exec,rw,async,nodev,nosuid,relatime 0 2
(Sorry if the tabs make it hard to read in a browser.)
Note that my data partition is meant to mount at /home/user/data. (It's basically a separate home without all of the dot folders. I let each distro keep its own dot folders to avoid conflicts and problems, and for the few I need to be persistent, I symlink them to a directory inside my data partition.)
I'm assuming the OS isn't properly recognizing my logical volumes due to the screwy boot sequence which my setup took before finally letting me log in...and that boot sequence is unnecessarily arduous. I have a feeling the shutdown sequence will be equally screwy as wel...so how do I fix my boot sequence and get
LVM/LUKS operating as it should?