Welcome, Guest. Please login or register.
Did you miss your activation email?

Author Topic: [EN] initramfs won't handle encrypted LV  (Read 5529 times)

WhiteDwarf

  • Guest
[EN] initramfs won't handle encrypted LV
« on: 2013/02/07, 16:06:14 »
Quote from: Bequimão
Das Problem hatte ich doch auch schon, und es liegt vor dem Öffnen der /root-partition

http://forum.siduction.org/index.php?msg=23397#23397

Bitte gib die englischen Originalfehlermeldungen an, so daß kein Ratespiel entsteht.

Grüße,
Bequimão

Dear all,
for making sure everybody who is interested in this issue, I will hopefully explain a little bit more clear about my setup.

Aim is to setup siduction 2012.2 on a laptop with encryprted LV / VG according to siduction manual. I have done it with aptosid on 3 Laptops years ago.
With the last "dist-upgrade" on one of this laptops,I received the message during "update-grub": "core.img" is to big, can't be installed on MBR of /dev/sda. And it also failed to install into a logical volume.
So I decided to switch completly from aptosid to siduction.

I installed installed Siduction 2012.2 with following LV/VG setup on disk /dev/sda and everything was working well.

This is the LV-Setup:
Code: [Select]
root@spica:/home/markus# lvdisplay
  --- Logical volume ---
  LV Path                /dev/crypt_spica/swap
  LV Name                swap
  VG Name                crypt_spica
  LV UUID                m1gKh1-CrA9-ANAD-x13p-pWxh-DOuJ-9B6Epo
  LV Write Access        read/write
  LV Creation host, time ,
  LV Status              available
  # open                 2
  LV Size                2,00 GiB
  Current LE             512
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:3
   
  --- Logical volume ---
  LV Path                /dev/crypt_spica/root
  LV Name                root
  VG Name                crypt_spica
  LV UUID                rt8M3l-HwsN-j0kR-Ihf3-foCe-B9lg-rdwOXq
  LV Write Access        read/write
  LV Creation host, time ,
  LV Status              available
  # open                 1
  LV Size                30,00 GiB
  Current LE             7680
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:4
   
  --- Logical volume ---
  LV Path                /dev/crypt_spica/home
  LV Name                home
  VG Name                crypt_spica
  LV UUID                O1HCCv-tG7w-HXi5-GhVt-1jf2-Bi2O-r1l20r
  LV Write Access        read/write
  LV Creation host, time ,
  LV Status              available
  # open                 1
  LV Size                42,28 GiB
  Current LE             10823
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:5
   
  --- Logical volume ---
  LV Path                /dev/spica/boot
  LV Name                boot
  VG Name                spica
  LV UUID                A3lgeV-1Olh-XGm7-mkD9-gxJh-a967-EzGDw9
  LV Write Access        read/write
  LV Creation host, time ,
  LV Status              available
  # open                 1
  LV Size                252,00 MiB
  Current LE             63
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:0
   
  --- Logical volume ---
  LV Path                /dev/spica/crypt
  LV Name                crypt
  VG Name                spica
  LV UUID                zkCfkW-7p1c-5c2D-wGHv-Bhj9-wHQt-k5PVLQ
  LV Write Access        read/write
  LV Creation host, time ,
  LV Status              available
  # open                 1
  LV Size                74,28 GiB
  Current LE             19016
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:1
For having newest packages and firmware for ipw2200, i have made a "apt-get update" and "apt-get dist-upgrade".
Then I received the "update-grub" message, described above once more. For me, it looks like the easiest way seems to downgrade the grub packages to version 1.99 with apt-get install packageXY=version.
It run smoothly through with no error messages.
For being sure, I have made an "update-grub" once more.

But after rebooting the system it stops during boot and is going into initramfs shell.

"vgchange -ay" in the console will activate 2 logical volumes: spica-boot and spica-crypt
"cryptsetup luksOpen /dev/mapper/spica-crypt cryptroot" activates the password sequence and granted access to the crypted LV
"vgchange -ay" will activate now another 3 logical volumes: crypt_spica-root, crypt_spica-home,  crypt_spica-swap

Now I can exit initramfs and the system is booting into runlevel 5.

In "etc/default/grub" I have added a rootdelay of 5 and made "update-grub", but still the same problem during boot.

I tried to pick out the messages as follows:
syslog:
Code: [Select]
Feb  7 10:39:02 spica /USR/SBIN/CRON[18170]: (root) CMD (  [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -depth -mindepth 1 -maxdepth 1 -type f -ignore_readdir_race -cmin +$(/usr/lib/php5/maxlifetime) ! -execdir fuser -s {} 2>/dev/null \; -delete)
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sda1
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/10freedos on mounted /dev/mapper/crypt_spica-home
Feb  7 10:41:06 spica 10freedos: debug: /dev/mapper/crypt_spica-home is not a FAT partition: exiting
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/10qnx on mounted /dev/mapper/crypt_spica-home
Feb  7 10:41:06 spica 10qnx: debug: /dev/mapper/crypt_spica-home is not a QNX4 partition: exiting
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/20macosx on mounted /dev/mapper/crypt_spica-home
Feb  7 10:41:06 spica macosx-prober: debug: /dev/mapper/crypt_spica-home is not an HFS+ partition: exiting
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/20microsoft on mounted /dev/mapper/crypt_spica-home
Feb  7 10:41:06 spica 20microsoft: debug: /dev/mapper/crypt_spica-home is not a MS partition: exiting
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/30utility on mounted /dev/mapper/crypt_spica-home
Feb  7 10:41:06 spica 30utility: debug: /dev/mapper/crypt_spica-home is not a FAT partition: exiting
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/40lsb on mounted /dev/mapper/crypt_spica-home
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/70hurd on mounted /dev/mapper/crypt_spica-home
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/80minix on mounted /dev/mapper/crypt_spica-home
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/83haiku on mounted /dev/mapper/crypt_spica-home
Feb  7 10:41:06 spica 83haiku: debug: /dev/mapper/crypt_spica-home is not a BeFS partition: exiting
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/90linux-distro on mounted /dev/mapper/crypt_spica-home
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/90solaris on mounted /dev/mapper/crypt_spica-home
Feb  7 10:41:06 spica os-prober: debug: /dev/mapper/crypt_spica-swap: is active swap
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/10freedos on mounted /dev/mapper/spica-boot
Feb  7 10:41:06 spica 10freedos: debug: /dev/mapper/spica-boot is not a FAT partition: exiting
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/10qnx on mounted /dev/mapper/spica-boot
Feb  7 10:41:06 spica 10qnx: debug: /dev/mapper/spica-boot is not a QNX4 partition: exiting
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/20macosx on mounted /dev/mapper/spica-boot
Feb  7 10:41:06 spica macosx-prober: debug: /dev/mapper/spica-boot is not an HFS+ partition: exiting
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/20microsoft on mounted /dev/mapper/spica-boot
Feb  7 10:41:06 spica 20microsoft: debug: /dev/mapper/spica-boot is not a MS partition: exiting
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/30utility on mounted /dev/mapper/spica-boot
Feb  7 10:41:06 spica 30utility: debug: /dev/mapper/spica-boot is not a FAT partition: exiting
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/40lsb on mounted /dev/mapper/spica-boot
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/70hurd on mounted /dev/mapper/spica-boot
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/80minix on mounted /dev/mapper/spica-boot
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/83haiku on mounted /dev/mapper/spica-boot
Feb  7 10:41:06 spica 83haiku: debug: /dev/mapper/spica-boot is not a BeFS partition: exiting
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/90linux-distro on mounted /dev/mapper/spica-boot
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/90solaris on mounted /dev/mapper/spica-boot
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/mapper/spica-crypt
Feb  7 10:41:06 spica 50mounted-tests: debug: /dev/mapper/spica-crypt is a LUKS partition; skipping

messages:

Code: [Select]
Feb  7 10:12:44 spica os-prober: debug: os detected by /usr/lib/os-probes/50mounted-tests
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sda1
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/10freedos on mounted /dev/mapper/crypt_spica-home
Feb  7 10:41:06 spica 10freedos: debug: /dev/mapper/crypt_spica-home is not a FAT partition: exiting
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/10qnx on mounted /dev/mapper/crypt_spica-home
Feb  7 10:41:06 spica 10qnx: debug: /dev/mapper/crypt_spica-home is not a QNX4 partition: exiting
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/20macosx on mounted /dev/mapper/crypt_spica-home
Feb  7 10:41:06 spica macosx-prober: debug: /dev/mapper/crypt_spica-home is not an HFS+ partition: exiting
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/20microsoft on mounted /dev/mapper/crypt_spica-home
Feb  7 10:41:06 spica 20microsoft: debug: /dev/mapper/crypt_spica-home is not a MS partition: exiting
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/30utility on mounted /dev/mapper/crypt_spica-home
Feb  7 10:41:06 spica 30utility: debug: /dev/mapper/crypt_spica-home is not a FAT partition: exiting
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/40lsb on mounted /dev/mapper/crypt_spica-home
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/70hurd on mounted /dev/mapper/crypt_spica-home
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/80minix on mounted /dev/mapper/crypt_spica-home
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/83haiku on mounted /dev/mapper/crypt_spica-home
Feb  7 10:41:06 spica 83haiku: debug: /dev/mapper/crypt_spica-home is not a BeFS partition: exiting
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/90linux-distro on mounted /dev/mapper/crypt_spica-home
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/90solaris on mounted /dev/mapper/crypt_spica-home
Feb  7 10:41:06 spica os-prober: debug: /dev/mapper/crypt_spica-swap: is active swap
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/10freedos on mounted /dev/mapper/spica-boot
Feb  7 10:41:06 spica 10freedos: debug: /dev/mapper/spica-boot is not a FAT partition: exiting
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/10qnx on mounted /dev/mapper/spica-boot
Feb  7 10:41:06 spica 10qnx: debug: /dev/mapper/spica-boot is not a QNX4 partition: exiting
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/20macosx on mounted /dev/mapper/spica-boot
Feb  7 10:41:06 spica macosx-prober: debug: /dev/mapper/spica-boot is not an HFS+ partition: exiting
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/20microsoft on mounted /dev/mapper/spica-boot
Feb  7 10:41:06 spica 20microsoft: debug: /dev/mapper/spica-boot is not a MS partition: exiting
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/30utility on mounted /dev/mapper/spica-boot
Feb  7 10:41:06 spica 30utility: debug: /dev/mapper/spica-boot is not a FAT partition: exiting
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/40lsb on mounted /dev/mapper/spica-boot
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/70hurd on mounted /dev/mapper/spica-boot
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/80minix on mounted /dev/mapper/spica-boot
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/83haiku on mounted /dev/mapper/spica-boot
Feb  7 10:41:06 spica 83haiku: debug: /dev/mapper/spica-boot is not a BeFS partition: exiting
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/90linux-distro on mounted /dev/mapper/spica-boot
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/mounted/90solaris on mounted /dev/mapper/spica-boot
Feb  7 10:41:06 spica os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/mapper/spica-crypt
Feb  7 10:41:06 spica 50mounted-tests: debug: /dev/mapper/spica-crypt is a LUKS partition; skipping
Feb  7 10:41:06 spica os-prober: debug: os detected by /usr/lib/os-probes/50mounted-tests
dmesg:
Code: [Select]
.
[    0.000000] pcpu-alloc: [0] 0 [0] 1
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 257681
[    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.7-6.towo-siduction-686 root=/dev/mapper/crypt_spica-root ro rootdelay=5 quiet rootdelay=5
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
.
.
.
[  215.950422] Adding 2097148k swap on /dev/mapper/crypt_spica-swap.  Priority:-1 extents:1 across:2097148k
[  215.967817] EXT4-fs (dm-4): re-mounted. Opts: (null)
[  216.836896] EXT4-fs (dm-4): re-mounted. Opts: errors=remount-ro
[  217.651772] fuse init (API version 7.20)
[  219.159324] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: errors=remount-ro
[  219.261545] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: errors=remount-ro
[  220.962901] RPC: Registered named UNIX socket transport module.
[  220.962907] RPC: Registered udp transport module.
[  220.962910] RPC: Registered tcp transport module.
[  220.962912] RPC: Registered tcp NFSv4.1 backchannel transport module.
[  221.006380] FS-Cache: Loaded
[  221.076521] FS-Cache: Netfs 'nfs' registered for caching
[  221.151584] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[  221.226148] 8139too 0000:02:01.0 eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
Sorry, for maybe too long code messages, but for now I dont know further.

I see the problem is that the encrypted LV is not recognized.

It would be nice if you could help.
Thanks and regards,
Markus
« Last Edit: 2013/11/10, 02:27:35 by ayla »

WhiteDwarf

  • Guest
initramfs won't handle encrypted LV
« Reply #1 on: 2013/02/07, 16:08:05 »
Code: [Select]
root@spica:/home/markus# ls -al /dev/disk/by-uuid
insgesamt 0
drwxr-xr-x 2 root root 140 Feb  7 11:45 .
drwxr-xr-x 5 root root 100 Feb  7 11:40 ..
lrwxrwxrwx 1 root root  10 Feb  7 11:45 0f6bce1f-6c1f-472c-9efd-558bb628bf3e -> ../../dm-5
lrwxrwxrwx 1 root root  10 Feb  7 11:40 131fae7f-72e4-4760-9107-fdc4e0c89671 -> ../../dm-0
lrwxrwxrwx 1 root root  10 Feb  7 11:45 5a8fe144-5178-4216-8a98-6d25d22765da -> ../../dm-4
lrwxrwxrwx 1 root root  10 Feb  7 11:40 79229db4-d606-4f32-9230-713af7e67e1e -> ../../dm-1
lrwxrwxrwx 1 root root  10 Feb  7 11:45 bbf43211-5015-40f8-8377-67d91718be00 -> ../../dm-3


grub.cfg

Code: [Select]
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Debian GNU/Linux, mit Linux 3.7-6.towo-siduction-686' --class debian --class gnu-linux --class gnu --class os {
load_video
insmod gzio
insmod lvm
insmod part_msdos
insmod ext2
set root='(spica-boot)'
search --no-floppy --fs-uuid --set=root 131fae7f-72e4-4760-9107-fdc4e0c89671
echo 'Linux 3.7-6.towo-siduction-686 wird geladen …'
linux /vmlinuz-3.7-6.towo-siduction-686 root=/dev/mapper/crypt_spica-root ro rootdelay=5 quiet rootdelay=5
echo 'Initiale Ramdisk wird geladen …'
initrd /initrd.img-3.7-6.towo-siduction-686
}


cryptab, was empty in the past and has worked well, now I have tried the following:
 
Code: [Select]
# <target> <source> <key> <options>
cryptroot /dev/spica-crypt 79229db4-d606-4f32-9230-713af7e67e1e none luks


fstab
Code: [Select]

UUID=131fae7f-72e4-4760-9107-fdc4e0c89671     /boot                ext4         defaults,relatime,errors=remount-ro           0    2  
UUID=bbf43211-5015-40f8-8377-67d91718be00     none                 swap         sw                                            0    0  
UUID=5a8fe144-5178-4216-8a98-6d25d22765da     /                    ext4         defaults,relatime,errors=remount-ro           0    1  
UUID=0f6bce1f-6c1f-472c-9efd-558bb628bf3e     /home                ext4         defaults,relatime,errors=remount-ro           0    2  

192.168.1.12:/media              /multimedia          nfs          nfsvers=3,rsize=65536,wsize=65536,tcp,noatime,intr
192.168.1.12:/backup             /backup              nfs          nfsvers=3,rsize=65536,wsize=65536,tcp,noatime,intr

Offline michaaa62

  • User
  • Posts: 299
initramfs won't handle encrypted LV
« Reply #2 on: 2013/02/07, 19:25:52 »
Please delete the content of the crypttab, if it was working fine before. This file is essential to additional partitions for encrypted media or some eccentric partition setup.

This is my boot line with all the options to get an encrypted partition booted
Code: [Select]
linux /vmlinuz-3.7-6.towo-siduction-amd64 root=/dev/mapper/medion_cryptVG-root ro cryptopts=source=UUID=1fabb8ab-34ec-4fba-a12f-b9e18c0fb70c,target=crypt,lvm=medion_cryptVG-root quiet splashNote:
The forum software truncates the UUID in the boot line.
1fabb8ab-34ec-4fba-a12f-b9e18c0fb70c is the UUID of the raw partition, that is holding the LV, aka. /dev/sda5 on my PC, but there is no UUID for your raw partition shown in the output!?
 lvm=medion_cryptVG-root is the name of the LV to be used as root partition.

I must admit, i never tried to boot from an encrypted /boot/-partition, which seem to be your setup.

hefee

  • Guest
initramfs won't handle encrypted LV
« Reply #3 on: 2013/02/07, 20:07:16 »
michaaa62: with a good /etc/cryptab you don't need these fancy grub parameters :) But these boot parameters can help to boot into the system :) I do also have an encrypted system and my boot line looks like this:

Code: [Select]

linux   /vmlinuz-3.7-6.towo-siduction-amd64 root=/dev/mapper/vtabin-root ro quiet


My guess ist that there is a file in the dir /etc/initramfs-tools/conf.d. These files can work against the default UUIDs. And are not needed anymore for booting.
Please show us the files it that directory:
Code: [Select]

ls /etc/initramfs-tools/conf.d

Offline michaaa62

  • User
  • Posts: 299
initramfs won't handle encrypted LV
« Reply #4 on: 2013/02/07, 20:34:08 »
Thanks for letting me know!  :oops:  :)

WhiteDwarf

  • Guest
initramfs won't handle encrypted LV
« Reply #5 on: 2013/02/08, 09:31:59 »
The boot-partion is not encrypted:

LV1 is spica-boot, not encrypted
LV2 is spica-crypt, entcrypted, holding inside /dev/crypt_spica/root, /dev/crypt_spica/home and /dev/crypt_spica/swap

in the /dev/mapper are these files located as:
Code: [Select]
root@spica:/home/markus# ls /dev/mapper
control    crypt_spica-home  crypt_spica-swap  spica-crypt
cryptroot  crypt_spica-root  spica-boot

In the past it had worked without cryptab entry, but there was alrays a warning during "update-grub" like "no valid final line..". Sorry but i can't recall the exact sentence anymore.
Code: [Select]
root@spica:/home/markus# ls /etc/initramfs-tools/conf.d
resume

root@spica:/home/markus# cat /etc/initramfs-tools/conf.d/resume
UUID=bbf43211-5015-40f8-8377-67d91718be00

I have taken a picture from the bootsequence, because in this early stage of booting the system, no log file is active.
It seems, the bootprocess is not using or skipping dm-crypt for open the encrypted LV spica-crypt.


I very appreciate your help, thanks.

Markus

WhiteDwarf

  • Guest
initramfs won't handle encrypted LV
« Reply #6 on: 2013/02/08, 16:22:45 »
so, sorry, but i gave up and reinstalled siduction freshly, because im lacking of time. I´m an old guy you know.
I have done no dist-ugrade so far. I'm afraid of running into same problems as above.
For now it´s not really important for me to beeing uptodate, as long I can work with the laptop.

Here are the configs for my correct working setup. All was generated automatically by this superb distro.

grub.cfg
Code: [Select]
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Debian GNU/Linux, mit Linux 3.6-9.towo-siduction-686' --class debian --class gnu-linux --class gnu --class os {
insmod gzio
insmod lvm
insmod part_msdos
insmod ext2
set root='(spica-boot)'
search --no-floppy --fs-uuid --set=root a89ae50b-21d5-46f7-ab85-57c27b8e7ba5
echo 'Linux 3.6-9.towo-siduction-686 wird geladen …'
linux /vmlinuz-3.6-9.towo-siduction-686 root=/dev/mapper/crypt_spica-root ro cryptopts=source=/dev/mapper/spica-crypt,target=cryptroot,lvm=crypt_spica-root quiet
echo 'Initiale Ramdisk wird geladen …'
initrd /initrd.img-3.6-9.towo-siduction-686
}
### END /etc/grub.d/10_linux ###

cryptab is empty  :)

fstab:
Code: [Select]
UUID=a89ae50b-21d5-46f7-ab85-57c27b8e7ba5     /boot                ext4         defaults,relatime,errors=remount-ro           0    2  
UUID=bbf43211-5015-40f8-8377-67d91718be00     none                 swap         sw                                            0    0  
UUID=4a321b7d-5d55-492a-a232-8d7154f46e48     /                    ext4         defaults,relatime,errors=remount-ro           0    1  
UUID=0f6bce1f-6c1f-472c-9efd-558bb628bf3e     /home                ext4         defaults,relatime,errors=remount-ro           0    2  

192.168.1.12:/media              /multimedia          nfs          nfsvers=3,rsize=65536,wsize=65536,tcp,noatime,intr
192.168.1.12:/backup             /backup              nfs          nfsvers=3,rsize=65536,wsize=65536,tcp,noatime,intr

Thanks for supporting me so far.

Best Regards,
Markus

Offline devil

  • Administrator
  • User
  • *****
  • Posts: 4.844
initramfs won't handle encrypted LV
« Reply #7 on: 2013/02/08, 16:56:33 »
You can always put grub2 on hold and dist-upgrade happily. With
Code: [Select]
apt-mark hold <package> that is no problem at all.

greetz
devil

Offline michaaa62

  • User
  • Posts: 299
initramfs won't handle encrypted LV
« Reply #8 on: 2013/02/08, 17:11:10 »
Looks good, is /boot a seperate partiton or (part of) a LVM?

WhiteDwarf

  • Guest
initramfs won't handle encrypted LV
« Reply #9 on: 2013/02/11, 18:18:43 »
@devil
thanks for the hint, I will do it.

@michaaa67,
yes /boot is a separate partition and is not encrypted.

Now, all is working fine. :D

Thanks and very best regards,

Markus

hundix

  • Guest
initramfs won't handle encrypted LV
« Reply #10 on: 2013/03/14, 18:25:23 »
The same problem here. Solution new install and grub-legacy on hold. But how long?