| View previous topic :: View next topic |
| Author |
Message |
schmittlauch
n00b
Joined: 12 Sep 2014
Posts: 23
|
 Posted: Fri Oct 17, 2014 9:23 pm Post subject: Cryptsetup luksOpen doesn't work anymore with 3.16 |
 |
|
I have 2 btrfs volumes encrypted with LUKS aes-xts-plain64 which are automatically decrypted and mounted during boot in my initramfs genrated by genkernel-next. This works like a charm with gentoo-sources-3.14.14, but after upgrading to gentoo-sources-3.16.6-gentoo it doesn't:
I am prompted to enter my LUKS password, but after entering it and pressing return nothing happens. Though it still seems to get the characters I entered as it complains about a wrong password when not entering the correct one. But if I enter the correct password, nothing happens.
I built my initramfs with | Code: | | genkernel --luks --btrfs --install initramfs |
My 3.14.14 config: http://pastebin.com/ZKUjinmq
kernel commandline: | Code: | | /vmlinuz-3.14.14-gentoo debug verbose ro rootflags=subvol=gentoo_root crypt_roots=/dev/sda3 crypt_roots=/dev/sdb1 root=UUID=0cd6d909-dba3-4542-a3b3-bffa16f6ce78 init=/usr/lib/systemd/systemd root_trim=yes rootfstype=btrfs |
My 3.16.6 config: http://pastebin.com/8CPaz25X
kernel commandline: | Code: | | /vmlinuz-3.16.6-gentoo debug verbose ro rootflags=subvol=gentoo_root crypt_roots=/dev/sda3 crypt_roots=/dev/sdb1 root=UUID=0cd6d909-dba3-4542-a3b3-bffa16f6ce78 init=/usr/lib/systemd/systemd root_trim=yes rootfstype=btrfs |
Any ideas why cryptsetup doesn't do anything? If not, how can I get more logs?
Regards, schmittlauch |
|
| Back to top |
|
 |
Roman_Gruber
Advocate
Joined: 03 Oct 2006
Posts: 3846
Location: Austro Bavaria
|
| Posted: Sat Oct 18, 2014 6:12 pm Post subject: |
|
|
Most probably the initramfs / busybox is screwed up.
I gave up on the kernel upgrade path with any costs. I stick to plain old stable release, long term supported 3.10 kernel branch.
Since i do that no hassles at all with the kernel
Your best choice is to insert breaks / steppoints / step through the init system and find the bug or use maybe genkernel-next or make your own initramfs to boot from |
|
| Back to top |
|
|
schmittlauch
n00b
Joined: 12 Sep 2014
Posts: 23
|
| Posted: Sat Oct 18, 2014 9:30 pm Post subject: |
|
|
| I already use genkernel-next (as I'm running systemd). How can I insert stepbreaks into initrd to find out what's wrong? |
|
| Back to top |
|
|
schmittlauch
n00b
Joined: 12 Sep 2014
Posts: 23
|
| Posted: Sun Oct 19, 2014 3:42 pm Post subject: |
|
|
| I tried booting the 3.16.6 kernel with the 3.14.14 initrd which worked together with the 3.14.14 kernel, but it didn't work. So this appears to be a kernel issue. Shall I report a bug? |
|
| Back to top |
|
|
BlueFusion
Guru
Joined: 08 Mar 2006
Posts: 371
|
| Posted: Mon Oct 20, 2014 4:14 am Post subject: |
|
|
dm-crypt/LUKS + btrfs rootfs works fine for me with 3.16.6. 3.17, however, I'm having serious issues with....randomly stops being able access the disks.
| Code: | title Gentoo Linux 64-bit (3.16.6)
root (hd0,0)
kernel /kernel-genkernel-x86_64-3.16.6-gentoo root=/dev/ram0 init=/linuxrc crypt_root=/dev/sdb2 real_rootflags=nodiscard,compress,noatime,device=/dev/sdc,device=/dev/sdd,device=/dev/sde,subvol=@rootfs vga=775 scandelay=0
initrd /initramfs-genkernel-x86_64-3.16.6-gentoo |
I don't use genkernel with the --btrfs option (infact, didn't know such option existed).
I suspect it' a systemd problem. I'm using OpenRC.
_________________
i7-940 2.93Ghz | ASUS P6T Deluxe (v.1) | 24GB Triple Channel RAM | nVidia GTX660
4x 4TB Seagate NAS HDD (Btrfs raid5) | 2x 120GB Samsung 850 EVO SSD (Btrfs raid1) |
|
| Back to top |
|
|
Roman_Gruber
Advocate
Joined: 03 Oct 2006
Posts: 3846
Location: Austro Bavaria
|
| Posted: Mon Oct 20, 2014 8:50 am Post subject: |
|
|
| schmittlauch wrote: | | I tried booting the 3.16.6 kernel with the 3.14.14 initrd which worked together with the 3.14.14 kernel, but it didn't work. So this appears to be a kernel issue. Shall I report a bug? |
report it to systemD !! BC kernel + init + userspace => and as the forum is full with systemd bugs, they are first to fix their stuff
Anyway you use critical, unproven and unstable components. An unstable file system on a stable encryption with a highly buggy init implementation, see this forum for bugs regarding this stuff compared to good stable openrc. Next you use the newest untested kernel and therefore run into more problems. You may have less hassles using a proven file system like ext with luks on the long term kernel supported named 3.10 from kerne.org.
If you really care for your data / security using such unproven software will cause you lots of headache. See it as hint / advise / my personal opinion. |
|
| Back to top |
|
|
Princess Nell
l33t
Joined: 15 Apr 2005
Posts: 916
|
| Posted: Wed Nov 05, 2014 8:39 pm Post subject: |
|
|
I have a vaguely similar problem. An external USB HDD with a cryptsetup-encryted ext4 filesystem doesn't even register when plugged in. Kernel version is 3.16.5, and downgrading to 3.14.14 works.
This is not a generic problem with USB - other devices work just fine. |
|
| Back to top |
|
|
Princess Nell
l33t
Joined: 15 Apr 2005
Posts: 916
|
| Posted: Thu Nov 06, 2014 11:27 pm Post subject: |
|
|
| Funny that, it works today. No explanation. |
|
| Back to top |
|
|
|
Kernel & Hardware
