severity 554506 grave
thanks
raising the severity since this issue leaves the system unbootable
after installation.
mike
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
i've run into this issue as well while attempting to install a new
squeeze instance in a virtualbox vm. if you're having trouble
reproducing the problem, the following steps should be able to
reproduce it:
1. use a recent image such as [0], and start the installation
2. once you get to partitio
On Sun, Jun 20, 2010 at 14:54 +0200, Jonas Meurer wrote:
[...]
> i just tried to reproduce the bug, and failed. can you confirm, that
> this bug no longer applies? otherwise please give exact information
> about your system: /etc/fstab, /etc/crypttab, and from inside the
> initramfs: /conf/conf.d/c
hey Philip, Wolodja, Christoph, Denis, Riku and Matúš,
It's hard to track this bug, and to be honest I'm not even sure whether
all of you spotted the same bug. Thus it would be helpful if you could
try to reproduce the bug once again with preliminary cryptsetup packages
that I prepared. You can
hey Riku,
On 24/06/2010 Riku Voipio wrote:
> On Thu, Jun 24, 2010 at 11:58:08AM +0300, Riku Voipio wrote:
> > -crypttab-
> > hda2_crypt /dev/hda2 none luks
> > --
>
> switching this from hda2->sda2 makes it now boot. hrmh. Still, the
> error message remains.
which error message do you mean?
vol
Hi,
Running squeeze, encountered this bug after an upgrade of udev from
157-1 to 158-1 was done and the initrd was rebuilt.
The root device to unlock is defined by '/dev/disks/by-uuid/' in crypttab.
After failing to unlock the root device busybox drops in and I was
able to check nodes under /dev
On Thu, Jun 24, 2010 at 11:58:08AM +0300, Riku Voipio wrote:
> -crypttab-
> hda2_crypt /dev/hda2 none luks
> --
switching this from hda2->sda2 makes it now boot. hrmh. Still, the
error message remains.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "uns
Hi,
I have now with lenny->squeeze upgrade:
volume group "aardvark" not found
skipping volume group aardvark.
cryptsetup: lvm device name (/dev/hda1 does not begin with /dev/mapper/".
-fstab-
/dev/mapper/aardvark-root / ext3 errors=remount-ro,noatime,nodiratime 0 1
--
-crypttab-
hda2_crypt /dev
hey again,
On 25/02/2010 Jonas Meurer wrote:
> On 05/11/2009 Max Vozeler wrote:
> > We recently changed d-i to use UUID in crypttab entries,
> > which is likely to be causing this problem.
> >
> > Jonas, do you think the initramfs script can be adapted to
> > allow UUID or should partman-crypto g
hey,
On 05/11/2009 Max Vozeler wrote:
> On Thu, Nov 05, 2009 at 12:44:36AM +0100, Philip Frei wrote:
> > volume group "debian" not found.
> > skipping volume group debian.
> > unable to find LVM volume debian/root
> > volume group "debian" not found.
> > cryptsetup: lvm device name (dev/disk/by-uu
I had the same problem with a new installation of debian sqeeze. Even if
i recreate the missing directory "/dev/disk/by-uuid" and the symlinks
for the lvm and crypto devices, it does not work.
Only the change from uuid to device names at the file "/etc/crypttab"
worked for me. I do not know, w
Package: cryptsetup
Version: 2:1.1.0~rc2-1
Severity: normal
I can confirm this bug on my platform, but I am not sure if it is
related to UUIDs. I only run into this issue if I set my SATA controller
to operate in AHCI mode and it works fine when I use the "Compatibility"
mode. The same bug also oc
Package: cryptsetup
Version: 2:1.0.7-2
Severity: important
I installed today's testing netinstall image on a new laptop with lvm
an crypto root.
After the first boot it can't find the root volume:
volume group "debian" not found.
skipping volume group debian.
unable to find LVM volume debian/roo
13 matches
Mail list logo
