Thanks for your response. This is the result of luksDump on the container:
# cryptsetup luksDump /dev/FINALFRONTIER_VG/HOME_LV
Device /dev/FINALFRONTIER_VG/HOME_LV is not a valid LUKS device.
I will try to find the time to recreate the entire scenario. Do you think the current container I'm able to open is at risk of corruption as well?
On Tue, Aug 19, 2014 at 3:51 PM, Arno Wagner <arno@xxxxxxxxxxx> wrote:
I Have no idea about what the problem may be, but just a
few days ago, Jeff Esquivel was also reporting problems with
a LUKS container that suddenly became unopenable under
Ubuntu 14.04 and we were unable to determine the cause.
He did create the container under Ubuntu and a few days
later it refused to open, just like yours.
I suspect something in Ubuntu 14.04 may indeed corrupt
LUKS key-slots (or salt values). It would not
be the first time that Ubuntu messes up handling LUKS
containers. That possibility is also one reason why a
header-backup is so important.
I find it especially troubling that this affects only
one of your two containers and that the Fedora 20 that
was fine before now fails to open the LIKS containers.
That can basically only happen on some header or key-slot
corruption.
Could you post the output of luksDump for the container
that you cannot open? (This does not compromise your security.)
There may be some similar patterns in the salts to the ones
Jeff posted.
If you have a spare disk and time, could you try the following:
Recreate a partition setup similar to yours using Fedora 20,
make header-backups (see FAQ) and then see whether the switch
to Ubuntu 14.04 kills one or both LUKS containers. Then make
new header backups and compare them. If they are not
bit-identical, we have something we can look at.
Arno
> _______________________________________________
On Mon, Aug 18, 2014 at 22:58:49 CEST, John Wells wrote:
> Guys,
>
> I have an odd problem. I had two luks partitions...both created upon
> install on Fedora 20.
>
> Last week, I switched to Ubuntu 14.04. However, anticipating problems, I
> *made sure Ubuntu did nothing with these partitions*. No mounting, nothing.
>
> Now, when I boot into Ubuntu, I can mount one manually and my data is
> there. However, the other partition tells me "not a valid LUKS device". So,
> thinking it might be a problem with Ubuntu, I downloaded the Fedora 20 live
> cd, booted up and tried it there. Shockingly, in Fedora 20, *both*
> partitions give the "not a valid LUKS device" error, and neither can be
> mounted.
>
> The partition I can mount from Ubuntu is MORE_VG-MORE_LV in the output
> below. The partition I can't mount from either distro now is
> FINALFRONTIER_VG-HOME_LV.
>
> Here's what things like like from Ubuntu (note, /dev/MORE_VG-MORE_LV is
> mounted successfully on /home...this is one of the partitions in question):
>
> # lsblk
> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
> sda 8:0 0 37.3G 0 disk
> ├─sda1 8:1 0 100M 0 part
> └─sda2 8:2 0 37.2G 0 part
> sdb 8:16 0 1.8T 0 disk
> └─sdb1 8:17 0 1.8T 0 part
> └─md0 9:0 0 1.8T 0 raid1
> └─MORE_VG-MORE_LV (dm-1) 252:1 0 800G 0 lvm
> └─cryptdevice (dm-7) 252:7 0 800G 0 crypt /home
> sdc 8:32 0 1.8T 0 disk
> └─sdc1 8:33 0 1.8T 0 part
> └─md2 9:2 0 1.8T 0 raid1
> ├─FINALFRONTIER_VG-HOME_LV (dm-2) 252:2 0 698.5G 0 lvm
> ├─FINALFRONTIER_VG-SWAP_LV (dm-3) 252:3 0 22.4G 0 lvm [SWAP]
> ├─FINALFRONTIER_VG-OPT_LV (dm-4) 252:4 0 139.7G 0 lvm /opt
> ├─FINALFRONTIER_VG-VMS_LV (dm-5) 252:5 0 102.5G 0 lvm /vms
> └─FINALFRONTIER_VG-DATA_LV (dm-6) 252:6 0 279.4G 0 lvm /data
> sdd 8:48 0 1.8T 0 disk
> └─sdd1 8:49 0 1.8T 0 part
> └─md2 9:2 0 1.8T 0 raid1
> ├─FINALFRONTIER_VG-HOME_LV (dm-2) 252:2 0 698.5G 0 lvm
> ├─FINALFRONTIER_VG-SWAP_LV (dm-3) 252:3 0 22.4G 0 lvm [SWAP]
> ├─FINALFRONTIER_VG-OPT_LV (dm-4) 252:4 0 139.7G 0 lvm /opt
> ├─FINALFRONTIER_VG-VMS_LV (dm-5) 252:5 0 102.5G 0 lvm /vms
> └─FINALFRONTIER_VG-DATA_LV (dm-6) 252:6 0 279.4G 0 lvm /data
> sde 8:64 0 167.7G 0 disk
> ├─sde1 8:65 0 3G 0 part /boot
> ├─sde2 8:66 0 12G 0 part
> └─sde3 8:67 0 152.8G 0 part
> └─SSDROOT_VG-ROOT_LV (dm-0) 252:0 0 97.7G 0 lvm /
> sdf 8:80 0 1.8T 0 disk
> └─sdf1 8:81 0 1.8T 0 part
> sr0 11:0 1 1024M 0 rom
>
> # blkid
>
> /dev/sda1: LABEL="System Reserved" UUID="4884488784487988" TYPE="ntfs"
> /dev/sda2: UUID="2CC04A94C04A63E4" TYPE="ntfs"
> /dev/sdb1: UUID="96b277d2-a5fa-1d13-fc5d-40a17ee26d57"
> UUID_SUB="1f3e63f5-7f25-4139-a708-efd1dfee3d0a" LABEL="pragdesk:0"
> TYPE="linux_raid_member"
> /dev/sdc1: UUID="d2d341dc-e3a8-c880-3856-e56702f6ab33"
> UUID_SUB="100a43fb-5c9d-045a-2f03-daedfb9a4c6d" LABEL="pragdesk:2"
> TYPE="linux_raid_member"
> /dev/sdd1: UUID="d2d341dc-e3a8-c880-3856-e56702f6ab33"
> UUID_SUB="fdac08d6-8629-d95f-c18c-a0e3c4b3ef31" LABEL="pragdesk:2"
> TYPE="linux_raid_member"
> /dev/sde1: UUID="ffdcd97d-6352-45b1-89ea-ec18d1476097" TYPE="ext2"
> /dev/sde3: UUID="Rj1Rkx-YUX1-GV38-15ix-upRW-ocbF-0lY1lb" TYPE="LVM2_member"
> /dev/sdf1: UUID="96b277d2-a5fa-1d13-fc5d-40a17ee26d57"
> UUID_SUB="45ee2620-9ba3-3ac9-4b1c-fe4d87599db3" LABEL="pragdesk:0"
> TYPE="linux_raid_member"
> /dev/md0: UUID="mZufjx-oWfV-YuZ0-gHat-7cim-skJV-Mc9elZ" TYPE="LVM2_member"
> /dev/md2: UUID="Em7bB4-ijwz-YdmO-dBCi-e3N6-EzaA-hX50vJ" TYPE="LVM2_member"
> /dev/mapper/SSDROOT_VG-ROOT_LV: UUID="7a56249a-63ac-4239-a874-7aa8c2f33195"
> TYPE="ext4"
> /dev/mapper/MORE_VG-MORE_LV: UUID="6cc188db-ccdb-4c8f-97b2-e41198ec6e44"
> TYPE="crypto_LUKS"
> /dev/mapper/FINALFRONTIER_VG-SWAP_LV:
> UUID="55232f85-5753-4de8-bdf5-0df3067f35eb" TYPE="swap"
> /dev/mapper/FINALFRONTIER_VG-OPT_LV:
> UUID="d9fe324e-abe7-47e0-80c8-7f2e29011249" TYPE="ext4"
> /dev/mapper/FINALFRONTIER_VG-VMS_LV:
> UUID="e0f5ed2a-6382-43c1-88d9-74da4aa440c0" TYPE="ext4"
> /dev/mapper/FINALFRONTIER_VG-DATA_LV:
> UUID="23d38b64-99b2-42b8-8064-4468f0f71b1c" TYPE="ext4"
> /dev/mapper/cryptdevice: UUID="4de2ef32-9894-4bb4-bf64-ced1b312796d"
> TYPE="ext4"
>
> Note how FINALFRONTIER_VG-HOME_LV doesn't appear in the output of blkid.
>
> # blkid /dev/dm*
> /dev/dm-0: UUID="7a56249a-63ac-4239-a874-7aa8c2f33195" TYPE="ext4"
> /dev/dm-1: UUID="6cc188db-ccdb-4c8f-97b2-e41198ec6e44" TYPE="crypto_LUKS"
> /dev/dm-3: UUID="55232f85-5753-4de8-bdf5-0df3067f35eb" TYPE="swap"
> /dev/dm-4: UUID="d9fe324e-abe7-47e0-80c8-7f2e29011249" TYPE="ext4"
> /dev/dm-5: UUID="e0f5ed2a-6382-43c1-88d9-74da4aa440c0" TYPE="ext4"
> /dev/dm-6: UUID="23d38b64-99b2-42b8-8064-4468f0f71b1c" TYPE="ext4"
> /dev/dm-7: UUID="4de2ef32-9894-4bb4-bf64-ced1b312796d" TYPE="ext4"
>
> # dpkg -l | grep cryptsetup
> ii cryptsetup 2:1.6.1-1ubuntu1
> amd64 disk encryption support -
> startup scripts
> ii cryptsetup-bin 2:1.6.1-1ubuntu1
> amd64 disk encryption support -
> command line tools
> ii libcryptsetup4 2:1.6.1-1ubuntu1
> amd64 disk encryption support -
> shared library
>
> I do note that Ubuntu uses 1.6.1, while Fedora 20 uses 1.6.2 (see below
> output).
>
> Did the Ubuntu 14.04 install somehow corrupt my FINALFRONTIER_VG-HOME_LV
> partition? Could the version differences be causing this? Is all my data
> there lost? I do have backups for the *really* important stuff, but there's
> about 72 hours of coding in there I'd really like to get back if possible.
>
> Any help is greatly appreciated. I'm pasting similar output from the Fedora
> 20 live session below for your reference as well.
>
> Thanks,
> John
>
> ------------------------------ FROM FEDORA 20 ------------------------------
> # lsblk
> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
> sda 8:0 0 37.3G 0 disk
> ├─sda1 8:1 0 100M 0 part
> └─sda2 8:2 0 37.2G 0 part
> sdb 8:16 1 14.6G 0 disk
> ├─sdb1 8:17 1 953M 0 part
> /run/initramfs/live
> ├─sdb2 8:18 1 4.9M 0 part
> └─sdb3 8:19 1 19.7M 0 part
> sdc 8:32 0 1.8T 0 disk
> └─sdc1 8:33 0 1.8T 0 part
> sdd 8:48 0 1.8T 0 disk
> └─sdd1 8:49 0 1.8T 0 part
> └─md127 9:127 0 1.8T 0 raid1
> ├─FINALFRONTIER_VG-HOME_LV 253:5 0 698.5G 0 lvm
> ├─FINALFRONTIER_VG-SWAP_LV 253:6 0 22.4G 0 lvm
> ├─FINALFRONTIER_VG-OPT_LV 253:7 0 139.7G 0 lvm /tmp/opt
> ├─FINALFRONTIER_VG-VMS_LV 253:8 0 102.5G 0 lvm
> └─FINALFRONTIER_VG-DATA_LV 253:9 0 279.4G 0 lvm
> sde 8:64 0 1.8T 0 disk
> └─sde1 8:65 0 1.8T 0 part
> └─md127 9:127 0 1.8T 0 raid1
> ├─FINALFRONTIER_VG-HOME_LV 253:5 0 698.5G 0 lvm
> ├─FINALFRONTIER_VG-SWAP_LV 253:6 0 22.4G 0 lvm
> ├─FINALFRONTIER_VG-OPT_LV 253:7 0 139.7G 0 lvm /tmp/opt
> ├─FINALFRONTIER_VG-VMS_LV 253:8 0 102.5G 0 lvm
> └─FINALFRONTIER_VG-DATA_LV 253:9 0 279.4G 0 lvm
> sdf 8:80 0 167.7G 0 disk
> ├─sdf1 8:81 0 3G 0 part
> ├─sdf2 8:82 0 12G 0 part
> └─sdf3 8:83 0 152.8G 0 part
> └─SSDROOT_VG-ROOT_LV 253:3 0 97.7G 0 lvm
> sdg 8:96 0 1.8T 0 disk
> └─sdg1 8:97 0 1.8T 0 part
> └─md126 9:126 0 1.8T 0 raid1
> └─MORE_VG-MORE_LV 253:4 0 800G 0 lvm
> sr0 11:0 1 1024M 0 rom
> loop0 7:0 0 8K 1 loop
> loop1 7:1 0 1.2M 1 loop
> └─live-osimg-min 253:2 0 4G 1 dm
> loop2 7:2 0 886.8M 1 loop
> loop3 7:3 0 4G 1 loop
> ├─live-rw 253:0 0 4G 0 dm /
> ├─live-base 253:1 0 4G 1 dm
> └─live-osimg-min 253:2 0 4G 1 dm
> loop4 7:4 0 512M 0 loop
> └─live-rw 253:0 0 4G 0 dm /
> [root@localhost]# cryptsetup luksDump /dev/MORE_VG/MORE_LV
> Device /dev/MORE_VG/MORE_LV is not a valid LUKS device.
> [root@localhost]# cryptsetup luksDump /dev/FINALFRONTIER_VG/HOME_LV
> Device /dev/FINALFRONTIER_VG/HOME_LV is not a valid LUKS device.
>
> # blkid
>
> /dev/sdb1: UUID="2013-12-12-00-56-55-00"
> LABEL="Fedora-Live-Desktop-x86_64-20-1" TYPE="iso9660" PTUUID="5513338d"
> PTTYPE="dos" PARTUUID="5513338d-01"
> /dev/sda1: LABEL="System Reserved" UUID="4884488784487988" TYPE="ntfs"
> PARTUUID="9ff59ff5-01"
> /dev/sda2: UUID="2CC04A94C04A63E4" TYPE="ntfs" PARTUUID="9ff59ff5-02"
> /dev/sdb2: SEC_TYPE="msdos" LABEL="EFI" UUID="7E31-E62C" TYPE="vfat"
> PARTUUID="5513338d-02"
> /dev/sdb3: UUID="11c76dff-3163-3083-8cec-c9045139ec1b" LABEL="Fedora Live"
> TYPE="hfsplus" PARTUUID="5513338d-03"
> /dev/loop0: TYPE="squashfs"
> /dev/loop1: TYPE="DM_snapshot_cow"
> /dev/loop2: TYPE="squashfs"
> /dev/loop3: LABEL="_Fedora-Live-Des"
> UUID="24375583-5faa-4172-8345-5dff1a0e89e5" TYPE="ext4"
> /dev/loop4: TYPE="DM_snapshot_cow"
> /dev/mapper/live-rw: LABEL="_Fedora-Live-Des"
> UUID="24375583-5faa-4172-8345-5dff1a0e89e5" TYPE="ext4"
> /dev/mapper/live-base: LABEL="_Fedora-Live-Des"
> UUID="24375583-5faa-4172-8345-5dff1a0e89e5" TYPE="ext4"
> /dev/mapper/live-osimg-min: LABEL="_Fedora-Live-Des"
> UUID="24375583-5faa-4172-8345-5dff1a0e89e5" TYPE="ext4"
> /dev/sdc1: UUID="96b277d2-a5fa-1d13-fc5d-40a17ee26d57"
> UUID_SUB="1f3e63f5-7f25-4139-a708-efd1dfee3d0a" LABEL="pragdesk:0"
> TYPE="linux_raid_member" PARTUUID="c8aa8e9b-01"
> /dev/sdd1: UUID="d2d341dc-e3a8-c880-3856-e56702f6ab33"
> UUID_SUB="100a43fb-5c9d-045a-2f03-daedfb9a4c6d" LABEL="pragdesk:2"
> TYPE="linux_raid_member" PARTUUID="0004869f-01"
> /dev/sde1: UUID="d2d341dc-e3a8-c880-3856-e56702f6ab33"
> UUID_SUB="fdac08d6-8629-d95f-c18c-a0e3c4b3ef31" LABEL="pragdesk:2"
> TYPE="linux_raid_member" PARTUUID="000956e0-01"
> /dev/sdf1: UUID="ffdcd97d-6352-45b1-89ea-ec18d1476097" TYPE="ext2"
> PARTUUID="00005669-01"
> /dev/sdf2: PARTUUID="00005669-02"
> /dev/sdf3: UUID="Rj1Rkx-YUX1-GV38-15ix-upRW-ocbF-0lY1lb" TYPE="LVM2_member"
> PARTUUID="00005669-03"
> /dev/sdg1: UUID="96b277d2-a5fa-1d13-fc5d-40a17ee26d57"
> UUID_SUB="45ee2620-9ba3-3ac9-4b1c-fe4d87599db3" LABEL="pragdesk:0"
> TYPE="linux_raid_member" PARTUUID="bde5c281-01"
> /dev/md127: UUID="Em7bB4-ijwz-YdmO-dBCi-e3N6-EzaA-hX50vJ"
> TYPE="LVM2_member"
> /dev/md126: UUID="mZufjx-oWfV-YuZ0-gHat-7cim-skJV-Mc9elZ"
> TYPE="LVM2_member"
> /dev/mapper/SSDROOT_VG-ROOT_LV: UUID="7a56249a-63ac-4239-a874-7aa8c2f33195"
> TYPE="ext4"
> /dev/mapper/FINALFRONTIER_VG-SWAP_LV:
> UUID="55232f85-5753-4de8-bdf5-0df3067f35eb" TYPE="swap"
> /dev/mapper/FINALFRONTIER_VG-OPT_LV:
> UUID="d9fe324e-abe7-47e0-80c8-7f2e29011249" TYPE="ext4"
> /dev/mapper/FINALFRONTIER_VG-VMS_LV:
> UUID="e0f5ed2a-6382-43c1-88d9-74da4aa440c0" TYPE="ext4"
> /dev/mapper/FINALFRONTIER_VG-DATA_LV:
> UUID="23d38b64-99b2-42b8-8064-4468f0f71b1c" TYPE="ext4"
>
> # blkid /dev/dm*
> /dev/dm-0: LABEL="_Fedora-Live-Des"
> UUID="24375583-5faa-4172-8345-5dff1a0e89e5" TYPE="ext4"
> /dev/dm-1: LABEL="_Fedora-Live-Des"
> UUID="24375583-5faa-4172-8345-5dff1a0e89e5" TYPE="ext4"
> /dev/dm-2: LABEL="_Fedora-Live-Des"
> UUID="24375583-5faa-4172-8345-5dff1a0e89e5" TYPE="ext4"
> /dev/dm-3: UUID="7a56249a-63ac-4239-a874-7aa8c2f33195" TYPE="ext4"
> /dev/dm-6: UUID="55232f85-5753-4de8-bdf5-0df3067f35eb" TYPE="swap"
> /dev/dm-7: UUID="d9fe324e-abe7-47e0-80c8-7f2e29011249" TYPE="ext4"
> /dev/dm-8: UUID="e0f5ed2a-6382-43c1-88d9-74da4aa440c0" TYPE="ext4"
> /dev/dm-9: UUID="23d38b64-99b2-42b8-8064-4468f0f71b1c" TYPE="ext4"
> /dev/dm-0: LABEL="_Fedora-Live-Des"
> UUID="24375583-5faa-4172-8345-5dff1a0e89e5" TYPE="ext4"
> /dev/dm-1: LABEL="_Fedora-Live-Des"
> UUID="24375583-5faa-4172-8345-5dff1a0e89e5" TYPE="ext4"
> /dev/dm-2: LABEL="_Fedora-Live-Des"
> UUID="24375583-5faa-4172-8345-5dff1a0e89e5" TYPE="ext4"
> /dev/dm-3: UUID="7a56249a-63ac-4239-a874-7aa8c2f33195" TYPE="ext4"
> /dev/dm-6: UUID="55232f85-5753-4de8-bdf5-0df3067f35eb" TYPE="swap"
> /dev/dm-7: UUID="d9fe324e-abe7-47e0-80c8-7f2e29011249" TYPE="ext4"
> /dev/dm-8: UUID="e0f5ed2a-6382-43c1-88d9-74da4aa440c0" TYPE="ext4"
> /dev/dm-9: UUID="23d38b64-99b2-42b8-8064-4468f0f71b1c" TYPE="ext4"
>
> # rpm -qa | grep cryptsetup
> cryptsetup-1.6.2-1.fc20.x86_64
> cryptsetup-libs-1.6.2-1.fc20.x86_64
> dm-crypt mailing list
> dm-crypt@xxxxxxxx
> http://www.saout.de/mailman/listinfo/dm-crypt
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@xxxxxxxxxxx
GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718
----
A good decision is based on knowledge and not on numbers. - Plato
_______________________________________________
dm-crypt mailing list
dm-crypt@xxxxxxxx
http://www.saout.de/mailman/listinfo/dm-crypt
_______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt
