From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gmazyland@gmail.com>
Received: from mail.saout.de ([127.0.0.1])
 by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 0pCreNuhWUVh for <dm-crypt@saout.de>;
 Sat, 20 Jul 2013 22:06:15 +0200 (CEST)
Received: from mail-ee0-x233.google.com (mail-ee0-x233.google.com
 [IPv6:2a00:1450:4013:c00::233])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mail.saout.de (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Sat, 20 Jul 2013 22:06:15 +0200 (CEST)
Received: by mail-ee0-f51.google.com with SMTP id e52so2975606eek.38
 for <dm-crypt@saout.de>; Sat, 20 Jul 2013 13:06:15 -0700 (PDT)
Message-ID: <51EAEDB4.1090407@gmail.com>
Date: Sat, 20 Jul 2013 22:06:12 +0200
From: Milan Broz <gmazyland@gmail.com>
MIME-Version: 1.0
References: <CACxrqpCg4zP-G0ufRz2rSafqqX1mw=5JjSWw=nfjaQ0QEw-CBQ@mail.gmail.com>
In-Reply-To: <CACxrqpCg4zP-G0ufRz2rSafqqX1mw=5JjSWw=nfjaQ0QEw-CBQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] ing rootfs without initramfs
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt/>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: ebelcrom ebelcrom <ebelcrom@googlemail.com>
Cc: dm-crypt@saout.de

On 07/20/2013 09:36 PM, ebelcrom ebelcrom wrote:

> I played around with dm-crypt without using initramfs for
> en-/decryption of my root file system. The rootfs is encrypted plain
> with cryptsetup and the key is stored at the disk containing the
> rootfs between MBR and the partition. The kernel parameter given to
> it from the bootloader is configured as it should be (cryptdevice,
> cryptkey, root mapper). The disk driver (loaded before) is built-in
> as well as dm-crypt (loaded after). The message I got at boot time is
> this (cr_rootfs is the encrypted rootfs):
> 
> VFS: Cannot open root device "mapper/cr_rootfs" or
> unknown-block(0,0)
> 
> According to some hints in the web there is no need to have an
> initramfs. Is that true? If yes what are the steps to get there and
> what should I keep into account?

I think the only possibility is to use GRUB2 which should understand
LUKS directly and boot from it. (Not sure about plain dmcrypt device).

I do not think you can create device-mapper block device without
initramfs (there were some patches to add some kernel options
but IIRC it never reached upstream).

Milan