> 1) Partman does not add option "plain" for non LUKS devices in crypttab.
> This causes warnings at startup and when running update-initramfs:
I also experienced these warnings, but adding "plain" to crypttab didn't
help to suppress them, at least in my case.
The correct solution seems: tell the
On 26/09/2021 at 12:48, Pascal Hambourg wrote:
Package: partman-crypto
Version: 114
Tags: patch
<https://salsa.debian.org/installer-team/partman-crypto/-/merge_requests/4>
Hello d-i team,
I found several issues related to plain dm-crypt (i.e. non LUKS)
encrypted devices in partma
Your message dated Sat, 30 Oct 2021 18:30:54 +0200
with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org>
and subject line Mass-closing old grub-installer bugs
has caused the Debian Bug report #686955,
regarding grub-installer: Grub fails to install on dm-crypt on LVM on SATA
vm2 on
dm-crypt on raid
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea wha
Package: partman-crypto
Version: 114
Tags: patch
Hello d-i team,
I found several issues related to plain dm-crypt (i.e. non LUKS)
encrypted devices in partman.
1) Partman does not add option "plain" for non LUKS devices in crypttab.
This causes warnings at startup and when runn
Your message dated Mon, 2 Nov 2020 18:47:25 +0200
with message-id <95371f9a-427f-bc97-f9b7-0b29d3c47...@debian.org>
and subject line Fixed in previous upload
has caused the Debian Bug report #646704,
regarding live-installer: installer doesn't write /etc/crypttab for crypt+LVM
to be mar
Your message dated Fri, 7 Aug 2020 23:44:04 +0200
with message-id <20200807234404.35e377ed8bc47c218bcf5...@mailbox.org>
and subject line Re: Mass-closing old installation-report bugs --- round 4
has caused the Debian Bug report #823845,
regarding D-I testing Alpha5 amd64: LVM on DM-CRYPT:
Aurelien Jarno (2019-12-06):
> There should be no changes needed on the d-i side. libc6-udeb has a
> new dependency on libcrypt1-udeb. When packages get rebuilt against
> libxcrypt, they'll have a direct dependency on libcrypt1-udeb.
>
> There is a small impact on size (~100kB) as libxcrypt provi
On 2019-12-06 22:46, Cyril Brulebois wrote:
> Hi,
>
> Marco d'Itri (2019-10-07):
> > Dear debian-boot: for the benefit of the ftpmasters, please confirm that
> > you have no objections to src:libxcrypt generating a libcrypt1-udeb
> > package (initially in experi
Hi,
Marco d'Itri (2019-10-07):
> Dear debian-boot: for the benefit of the ftpmasters, please confirm that
> you have no objections to src:libxcrypt generating a libcrypt1-udeb
> package (initially in experimental) which will provide crypt(3)
> currently in the libc udeb.
Processing control commands:
> retitle -1 rescue-mode: should support plain dm-crypt encrypted disks
Bug #404261 [rescue-mode] rescue-mode: should support loop-aes and plain
dm-crypt encrypted disks
Changed Bug title to 'rescue-mode: should support plain dm-crypt encrypted
disks'
Control: retitle -1 rescue-mode: should support plain dm-crypt encrypted disks
Retitle bug, since loop-AES is no longer supported by the installer
Holger
--
Holger Wansing
PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
On Oct 07, Aurelien Jarno wrote:
Dear debian-boot: for the benefit of the ftpmasters, please confirm that
you have no objections to src:libxcrypt generating a libcrypt1-udeb
package (initially in experimental) which will provide crypt(3)
currently in the libc udeb.
> I guess we should k
tasks: [E]
Install boot loader:[O]
Overall install:[O]
Comments/Problems:
I performed a network booted, serial console installation, and
attempted to use the Network Console (SSH) option for finishing the
install. It seems that gen-crypt, used to set the shadow entry for
Hi,
After some digging and a lot of attempts to get it right I am giving up.
Maybe you could help me a bit.
I'd like to have a recipe that would make partman-auto create:
1) EFI system partition (use an existing one if present, without formatting it),
2) /boot partition
3) a container partition
stall.
=== Failed trials: Manual Partitioning ===
* 30 GB /sda1 => ext4 /boot [OK]
* 730 GB dm-crypt (default crypto settings, AES, key=256, ...), write zeros
(1.5 hours) and create /sda5_crypt [no errors]
* format /sda5_crypt format ext4 [no errors]
* LVM: assigning volume group vg0 to /s
Control: reassign -1 partman-base
Control: forcemerge 778773 -1
markermoniker (2014-11-29):
> Package: installation-reports
> Severity: important
>
> Dear Maintainer,
>
> While attempting to set up a system with an LVM inside an encrypted
> partition, the installer hangs while re-scanning the d
Processing control commands:
> reassign -1 partman-base
Bug #771485 [installation-reports] installation-reports: Installation disk scan
hangs at 81% with LVM inside crypt partition
Bug reassigned from package 'installation-reports' to 'partman-base'.
Ignoring request to
Package: installation-reports
Followup-For: Bug #771485
Dear Maintainer,
I can reproduce this bug in virtualbox. I have found a workaround which may
further clarify the original problem. Whenever I have multiple initialized
dm-crypt volumes and then write an LVM group configuration into one of
Hi,
I encountered the same issue when trying to setup LVM inside a crypt
partition. The reason for the hanging partitioner is a crashing
'parted_server' process:
kernel: [ 422.613251] parted_server[15630]: segfault at 8 ip
0040b4b1 sp 7fff35d63ee0 error 4 in parted_ser
Package: installation-reports
Severity: important
Dear Maintainer,
While attempting to set up a system with an LVM inside an encrypted
partition, the installer hangs while re-scanning the disks at 81%. I had
similar, but less thoroughly documented issues trying to work around it with a
Your message dated Fri, 24 Oct 2014 10:40:40 +
with message-id
and subject line Bug#656710: fixed in partman-crypto 77
has caused the Debian Bug report #656710,
regarding Consider adding support to preseed a dm-crypt passphrase
to be marked as done.
This means that you claim that the problem
On Sun, Sep 8, 2013 at 13:27:41 -0700, Joseph Skerik wrote:
> Package: installation-reports
> Severity: important
> Tags: d-i
>
> Dear Maintainer,
>
> Here's what I see:
> * fdisk tells me that I have partitions misaligned.
That's an fdisk bug AFAIK.
> * Disk preparation during install (forma
Package: installation-reports
Severity: important
Tags: d-i
Dear Maintainer,
Here's what I see:
* fdisk tells me that I have partitions misaligned.
* Disk preparation during install (format/erase) took 36 hours for one 750GB
disk in an inexpensive laptop. The disk is mechanical and not super fa
I've also faced the same issue and it's resolved using the patch attached.
--
Regards,
Prathibha
C-DAC
Chennai
lvm_crypt.patch
Description: Binary data
Package: debian-installer
Severity: normal
This appears to be a regression bug. I have a Dell Inspiron 1720 (circa 2008)
which I previously used as a work laptop. The drive was configured as follows:
sda
sda1
ext3 filesystem (for /boot)
sda2
physical
I'd like to work on this bug. Do we have recent wheezy rc images which I
can use to reproduce & fix this bug?
--
Regards,
Dmitrijs.
signature.asc
Description: OpenPGP digital signature
tag 646704 - confirmed
thanks
usage of the tag 'confirmed' is reserved for the maintainer to indicate
that he could reproduce it, not users (re)reporting it.
--
Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
Email: daniel.baum...@progress-technologies.net
Internet:
Processing commands for cont...@bugs.debian.org:
> tag 646704 - confirmed
Bug #646704 [live-installer] live-installer: installer doesn't write
/etc/crypttab for crypt+LVM
Removed tag(s) confirmed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
6
Processing commands for cont...@bugs.debian.org:
> reassign 646704 live-installer
Bug #646704 [debian-installer] debian-installer: installer doesn't write
/etc/crypttab for crypt+LVM
Bug reassigned from package 'debian-installer' to 'live-installer'.
Ignoring reques
reassign 646704 live-installer
retitle 646704 live-installer: installer doesn't write /etc/crypttab for
crypt+LVM
tags 646704 +confirmed
thanks
Hi,
I was able to reproduce this issue with the current stable live cd,
debian-live-6.0.4-amd64-rescue.iso, however it does not occur with
d
Lennart> I have no crypt at all and am not interested in getting my life that
Lennart> complicated. :)
Oh, oh well. I can get it to work without crypto; it's the crypto that
breaks things.
Lennart> I don't see how grub could deal with crypt. Does it do that?
On my non-RAI
RAID drive, but it still fails to find the
> encrypted LVM (Auto-detection of a filesystem of /dev/mapper/waif-root
> failed). Do you have any cryptdevice lines in your /etc/default/grub,
> or /boot/grub/grub.cfg, or some customisation in /etc/grub.d?
I have no crypt at all and am not i
> # cat /boot/grub/device.map
> (hd0) /dev/disk/by-id/md-uuid-5847a5f9:19773d99:f13783a1:b611c764
Ok, so doing something similar on my machine again has the effect of
successfully locating the RAID drive, but it still fails to find the
encrypted LVM (Auto-detection of a filesystem of /dev/mapp
ed to partition this as
> before (small /boot, then a large dm-crypt partition on which I put LVM,
> then splitting the LVM into swap and root partitions). Again, grub
> tries to install to /dev/hda1 and fails, but this time when I reboot to
> the wheezy rescue mode, things are much more
/md126; with some false starts I've managed to partition this as
before (small /boot, then a large dm-crypt partition on which I put LVM,
then splitting the LVM into swap and root partitions). Again, grub
tries to install to /dev/hda1 and fails, but this time when I reboot to
the wheez
g
> to preserve dual boot with an existing Windows install). Used manual
> partitioning,
> having booted installer with "dmraid=true" kernel flag. Set up a small
> partition
> for /boot, and then a large dm-crypt partition, on which I created an LVM
> containing
> &
th "dmraid=true" kernel flag. Set up a small
partition
for /boot, and then a large dm-crypt partition, on which I created an LVM
containing
"swap" and "root". Install failed when trying to install Grub (I think it
tried to
install to hda1 or something like that).
Package: debian-installer
Version: testing
Severity: important
Dear Maintainer,
* What led up to the situation?
I tried installing Debian using the partition layout provided in the
gentoo wiki:
http://en.gentoo-wiki.com/wiki/Root_filesystem_over_LVM2,_DM-Crypt_and_RAID
* What exac
Package: debian-installer
Severity: grave
Justification: renders package unusable
I installed today a debian stable with debian-6.0.3-rescue-amd64.
I tried to use crypt+LVM, with / and /home in a Volume Group on a
crypted partition (/dev/sda6).
Hower the installation finishes well, boot on the
work for me
because i only have my /home and swap encrypted. My password prompt doesn't
timeout.
I have also seen suggestions of modifying a "mkinitcpio.conf" file to
include usb keyboard support, but I don't think the debian deployment of
dm-crypt uses this file.
Processing commands for cont...@bugs.debian.org:
> reassign 566497 partman-crypto
Bug #566497 [debian-installer] install: Please support reusing existing
crypt-lvm partitions
Bug reassigned from package 'debian-installer' to 'partman-crypto'.
Bug No longer marked as f
reassign 566497 partman-crypto
forcemerge 566497 451535
thanks
Quoting Vagrant Cascadian (vagr...@debian.org):
> Package: debian-installer
> Version: 6.0.1a
> Severity: normal
>
> many thanks for debian-installer!
>
> i wanted to set up multiple version of debian on an existing LVM volume group
Package: debian-installer
Version: 6.0.1a
Severity: normal
many thanks for debian-installer!
i wanted to set up multiple version of debian on an existing LVM volume group
on an existing encrypted partition, but unfortunately debian-installer didn't
seem to support re-using an already existing enc
Your message dated Sat, 22 Jan 2011 17:17:39 +
with message-id <1295716659.2505.210.camel@eeepc.Belkin>
and subject line
has caused the Debian Bug report #505099,
regarding installation-reports: [RC1 TEST] Thinkpad T61 ; netboot-install ;
crypto-root (dm-crypt)
to be marked as done.
Your message dated Wed, 08 Sep 2010 03:58:31 +
with message-id
and subject line Closing old installation report #496727
has caused the Debian Bug report #496727,
regarding partman fails with LVM over dm-crypt over RAID with the lenny beta2
d-i
to be marked as done.
This means that you claim
Your message dated Wed, 8 Sep 2010 00:04:32 +1000
with message-id <20100907140432.ga2...@debian.org>
and subject line Re: Bug#593492:
has caused the Debian Bug report #593492,
regarding debian-installer: Unable to install debian using RAID5, dm-crypt, LVM
to be marked as done.
This means th
I second this wish. I'm triple-booting Debian Lenny(13G), Debian
Squeeze(13G) and Ubuntu Karmic(20G),
all on the same encrypted LVM.
I currently use Qemu to create install to a Qemu image file from which I
copy the install logical
volume, but I have to use a different LVM volume name to access
Package: debian-installer
Severity: normal
I am unable to install lenny (5.0.5), i386 using RAID5, dm-crypt and LVM.
I got
/dev/sda (2TB)
/dev/sdb (2TB)
/dev/sdc (2TB)
and want to install the system unsing RAID5.
I use:
/dev/sda1 (256MB)
/dev/sdb1 (256MB)
/dev/sdc1 (256MB)
/dev/sda2 (about
Hello,
yes you're right. My patch is a quick hack and not good enought for the
debian distribution ...
I will try to rewrite it for better handle the multi crypted partitions.
A question for that. Is it possible do get a true or false value
without any user input in the debian-installer?
I think l
##
> > # Disk Partitioning/Boot loader
> > ####
> >
> > # dm-crypt passphrase
> > d-i partman-crypto/passphrase passwordThis_is_a
> > very_long_and_secret_passphrase!
> > d-i partman-crypto/passphrase-again passwordThis_
On Friday 10 July 2009, Gabriel wrote:
> The 'problem' with this way of preseeding is, if you want to use
> two seperate crypted partitions you cannot use two different
> passphrases.
Why do you say "cannot"? Wouldn't both partitions just get the same
passphrase with your changes? I don't think t
but I don't see what it could harm.
>
> This probably deserves a small addition to the installation manual
> too, at least adding the following to the example preseed file...
>
>
> CC'ing Frans to get advice about documenting the new "feature".
>
###
of the dm-crypt
passphrase failed
Quoting Gabriel Sailer (gabriel.sai...@gmx.net):
> Many thanks for this Information.
> If i rebuild the udeb package and i delete the two "db_fset ..." lines
> should the preseeding work for the passphrase?
You probably down't even
On Thursday 28 May 2009, Gabriel Sailer wrote:
> If i rebuild the udeb package and i delete the two "db_fset ..." lines
> should the preseeding work for the passphrase?
If you also remove the lines that unset the "seen" flag, probably yes. But
you'll have to try it to be sure.
--
To UNSUBSCRI
ne of
them). After delivering the laptops and before working, the user
_must_ set his own passphrase and _must_ delete the "installation
passphrase".
I haven't found an other solution to use dm-crypt on nearly the full
disk (it is not possible to crypt the partitions after the ins
Processing commands for cont...@bugs.debian.org:
> severity 530784 wishlist
Bug#530784: partman-crypto: preseeding of the dm-crypt passphrase failed
Severity set to `wishlist' from `normal'
> retitle 530784 Consider adding support to preseed a dm-crypt passphrase
Bug#530784
severity 530784 wishlist
retitle 530784 Consider adding support to preseed a dm-crypt passphrase
thanks
On Wednesday 27 May 2009, Gabriel Sailer wrote:
> i tried to install about 20 laptops full preseeded with crypted
> root and swap (and a normal /boot). The installation work but
>
On Monday 25 May 2009, Gabriel wrote:
> I did not find any information about a solution for problem.
Please file a bug report against partman-crypto for this issue, so we can
better track the discussion.
Provide at least the following information:
- the exact image you are using (full URL of the
Hello,
i tried to install about 20 laptops full preseeded with crypted
root and swap (and a normal /boot). The installation work but
without accepting my preseeded partman-crypto/passphrase (and
partman-crypto/passphrase-again).
I use 'd-i preseeded partman-crypto/passphrase password ' and the same
Hello,
i tried to install about 20 laptops full preseeded with crypted
root and swap (and a normal /boot). The installation work but
without accepting my preseeded partman-crypto/passphrase (and
partman-crypto/passphrase-again).
I use 'd-i preseeded partman-crypto/passphrase password ' and the same
Package: debian-installer
Version: nightly build ~ 20081202
Severity: normal
When using nightly build of d-i from around 20081202 and using dm-crypt with
LVM and XFS on top of this I run into a grave warning. When mounting the XFS
partition after rebooting the system told me that XFS will
Your message dated Sun, 30 Nov 2008 23:17:34 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#506068: fixed in rescue 1.19
has caused the Debian Bug report #506068,
regarding rescue mode doesn't load dm-crypt
to be marked as done.
This means that you claim that the probl
package: rescue-mode
version: lenny rc1
The lenny rc1 netinst image rescue mode detects my encrypted partition,
and asks for my passphrase, but doesn't decrypt the partition. This
works fine with my lenny beta 2 CD. I opened a console in rc1 and tried
to modprobe dm-crypt and it wouldn
tem:[O]
Clock/timezone setup: [O]
User/password setup:[O]
Install tasks: [O]
Install boot loader:[O]
Overall install:[O]
Comments/Problems:
- Netboot works fine.
But the netboot images seems older that CD 29-Oct instead of 04-Nov
- Crypto-root (dm-crypt) works :
package: partman-crypto-dm
I wanted to install a system with dm-crypt. So, I have created some
partitions and a non-encrypted partition for /boot.
By mistake,I've mixed-up swap and /boot: I defined /boot on an encrypted
partition. DI told me that was wrong, so I reconfigured the encr
roblem i reported has to do with misbehavior during the partman.
> It tried to create a partition table on the crypted volume (over
> RAID), rather than letting me use it directly as an LVM PV.
>
Is it actually creating the partition on the crypt disk or is it
pretending to do so for the p
On Thu 2008-08-28 11:40:51 -0400, Jérémy Bobbio wrote:
> On Tue, Aug 26, 2008 at 09:45:33PM -0400, Daniel Kahn Gillmor wrote:
>> Image version: lenny d-i beta2
>> FWIW, this arrangment (LVM over dm-crypt over RAID) seems like a
>> reasonable common one, so it should be easy
On Tue, Aug 26, 2008 at 09:45:33PM -0400, Daniel Kahn Gillmor wrote:
> Image version: lenny d-i beta2
> FWIW, this arrangment (LVM over dm-crypt over RAID) seems like a
> reasonable common one, so it should be easy to configure from d-i.
See the wiki page about the issue [1].
d via partman.
At this point, i was returned to the main partman screen, but if i
select the md1_crypt device to try to make it an LVM2 physical volume,
partman instead offers to put a partition table on the device, which
doesn't make any sense. Perhaps dm-crypt over RAID devices are
somehow no
Your message dated Tue, 05 Aug 2008 17:17:02 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#393728: fixed in partman-md 42
has caused the Debian Bug report #393728,
regarding dm-crypt on raid does not play nicely
to be marked as done.
This means that you claim that the p
Your message dated Tue, 05 Aug 2008 17:17:02 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#393728: fixed in partman-md 42
has caused the Debian Bug report #393728,
regarding root on ext3 over lvm over dm-crypt over raid 1 fails to boot
to be marked as done.
This means th
On Thu, May 15, 2008 at 08:23:32PM +0200, Lurkos wrote:
The same problem is present also with Etch.
Feel free to ask if you need more details.
How much memory did you allocate to the virtual machine which was
running the installer? crypto increases the memory usage of the
installer quite a bi
On Thursday 15 May 2008, Lurkos wrote:
> The same problem is present also with Etch.
> Feel free to ask if you need more details.
Please send the file /var/log/syslog for the installation after you have
returned to the menu after the error. To get the syslog you can use the
option "Save debug lo
The same problem is present also with Etch.
Feel free to ask if you need more details.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ler - Boot Fails USB boot, with RAID1,
DM-Crypt and LVM for root
On Thursday 08 May 2008, David Thornton wrote:
> On my home server, I am using Debian Installer (lenny amd64) to
create:
> * EM64T Asus PK5 SE motherboard, 2 x SATA 500gb drives.
> * USB Boot Partition
> * R
On Thursday 08 May 2008, David Thornton wrote:
> On my home server, I am using Debian Installer (lenny amd64) to create:
> * EM64T Asus PK5 SE motherboard, 2 x SATA 500gb drives.
> * USB Boot Partition
> * RAID1 Root
> * DM Crypt Root (LUKS)
> * LVM on top
>
Crypt Root (LUKS)
* LVM on top
Every combination works except the one above (i.e. Root RAID or Root DM
Crypt)
It looks like the cryptsetup is not being run from the initrd...
The RAID1 comes up alright... Then it can't find the LVMs (of course)
and the rest craps out.
I can
On Friday 01 February 2008, Frans Pop wrote:
> On Friday 01 February 2008, Jerome Despatis wrote:
> > I have this bug with a fresh etch install today
> >
> > Is this bug resolved in lenny ?
>
> AFAIK it is not.
See this page for additional information and workaround:
http://wiki.debian.org/DebianI
On Friday 01 February 2008, Jerome Despatis wrote:
> I have this bug with a fresh etch install today
>
> Is this bug resolved in lenny ?
AFAIK it is not.
Cheers,
FJP
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Tue, November 14, 2006 14:01, Mario Schubert said:
> On Tuesday 14 November 2006 09:48, you wrote:
>> The problem is a disagreement between partman-md and
>> partman-crypto which results in a bogus /etc/fstab on the target fs and
>> after that everything goes downhill (see #393728 for more detai
Processing commands for [EMAIL PROTECTED]:
> reassign 398464 partman-crypto
Bug#398464: root on ext3 over lvm over dm-crypt over raid 1 fails to boot
Bug reassigned from package `cryptsetup' to `partman-crypto'.
> forcemerge 393728 397872 398464
Bug#393728: dm-crypt on raid does
reassign 398464 cryptsetup
thanks
also sprach Mario Schubert <[EMAIL PROTECTED]> [2006.11.13.2314 +0100]:
> device-mapper: ... initialised ...
> Volume group "vg0" not found
> No cryptroot configured, skipping
cryptroot is defined to run after lvm, for whatever reason. The
cryptsetup people can
Processing commands for [EMAIL PROTECTED]:
> reassign 398464 cryptsetup
Bug#398464: root on ext3 over lvm over dm-crypt over raid 1 fails to boot
Bug reassigned from package `installation-reports' to `cryptsetup'.
> thanks
Stopping processing here.
Please contact me if you
d the rest.
The rest is RAID1, then encrypted with dm-crypt, then lvm and finally a root
volume with ext3.
I was able to configure it with the installer, but the reboot failed. I think
the devices are set up in the wrong order.
Thank you for your help.
reassign 394136 cryptsetup
retitle 394136 Add support for multiple device setup in initramfs
tags 394136 +d-i
thanks
On Fri, October 20, 2006 12:32, Miroslav Kure said:
> On Fri, Oct 20, 2006 at 10:50:34AM +0200, David Härdeman wrote:
>>
>> I'm fairly certain this is a bug in the cryptsetup initra
Processing commands for [EMAIL PROTECTED]:
> reassign 394136 cryptsetup
Bug#394136: LVM root on multiple dm-crypt partitions
Bug reassigned from package `partman-crypto' to `cryptsetup'.
> retitle 394136 Add support for multiple device setup in initramfs
Bug#394136: LVM root on m
On Thursday 19 October 2006 18:55, Miroslav Kure wrote:
> Begin: Running /scripts/local-top ...
> Volume group "vg" not found
> Enter LUKS passphrase:
> key slod 0 unlocked.
> Command succesfull.
> Couldn't find device with uuid
> 'DZ9wMr-ECxI-boX4-wmr8-v07z-Ni2E-bb30fy'. Couldn't f
On Fri, Oct 20, 2006 at 10:50:34AM +0200, David Härdeman wrote:
>
> I'm fairly certain this is a bug in the cryptsetup initramfs scripts. It
> might need some changes to partman-crypto as well though.
>
> Could you please provide me with the contents of /etc/crypttab and
> /etc/fstab from the rea
Package: partman-crypto
Hi,
I installed rom today's i386 netinst (20061016) with the following
setup:
/dev/hda1 16MB /boot
/dev/hda2 500MB physical volume for encryption
/dev/hdb1 516MB physical volume for encryption
Both crypto partitions were setup for dm-crypt. On the top of thes
00MB physical volume for raid
>
> RAID 1 was created from /dev/hda2 and /dev/hdb2 and on the top of it
> dm-crypt partition was created with all defaults.
>
> After returning from "Configure encrypted volumes" the new device
> md0_crypt was created as expected, but there w
On Tue, Oct 17, 2006 at 08:47:37PM +0200, David Härdeman wrote:
>
> Could you post the contents of /conf/conf.d/cryptroot in the initramfs
> image? (boot with the "break" argument and you'll be dropped into a
> shell so you can inspect the contents of the initramfs image).
Um, the directory /co
On Tue, Oct 17, 2006 at 05:35:24PM +0200, Miroslav Kure wrote:
The installation then proceeded like usual, but after the reboot to
the real system
Begin: Loading MD modules ...
md: driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
md: raid1 personality registered for leve
n the top of it
dm-crypt partition was created with all defaults.
After returning from "Configure encrypted volumes" the new device
md0_crypt was created as expected, but there was no "partition" inside
it to use.
I had to press enter on the md0_crypt device itself and it
Your message dated Wed, 11 Oct 2006 21:35:12 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#392248: partman-crypto: Fails to load modules for manual
dm-crypt
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been deal
Package: partman-crypto
Severity: normal
Hello again,
I used manual partitioning, and created one large
dm-crypt partiton, and when I went to configure it I got
An Error occured while configuring encrypted volumes
The configuration has been aborted.
The log said
Check kernel for
system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: debian-installer
Severity: important
Installed using latest daily D-I netinst. I tried to create the
following structure:
sda (ext3 /boot, crypt (lvm (ext3 /, swap) ) )
That is, root/swap on top of LVM
Package: debian-installer
Severity: important
Installed using latest daily D-I netinst. I tried to create the
following structure:
sda (ext3 /boot, crypt (lvm (ext3 /, swap) ) )
That is, root/swap on top of LVM on top of crypt. However, D-I is a
little too smart for itself, detected that a
Processing commands for [EMAIL PROTECTED]:
> reassign 381981 partman-crypto
Bug#381981: crypto installation report (root on dm-crypt, loop-AES)
Bug reassigned from package `installation-reports' to `partman-crypto'.
> retitle 381981 Configuration fails with blowfish / 448 bits
Bu
reassign 381981 partman-crypto
retitle 381981 Configuration fails with blowfish / 448 bits
block 381981 by 381973
thanks
On Tue, Aug 08, 2006 at 05:30:41AM +0200, Max Vozeler wrote:
> 1. For dm-crypt I could choose the blowfish cipher with a
> keysize of 448 bits. The blowfish kernel
1 - 100 of 126 matches
Mail list logo
