Hi again.
Cyril Brulebois k...@debian.org (09/03/2010):
Using my d-i usb stick, I was hoping to recover from it by mounting
the crypted lvm through cryptsetup luksOpen … (which a quick google
suggests), but unfortunately I end up with cryptsetup telling me to
check for missing aes support in
Hi.
[Context: I ended up (twice) with an unbootable system, apparently
because dm-crypt wasn't included in the initramfs.]
Using my d-i usb stick, I was hoping to recover from it by mounting
the crypted lvm through cryptsetup luksOpen … (which a quick google
suggests), but unfortunately I end up
On Tuesday 09 March 2010, Cyril Brulebois wrote:
Also: Is there any way to make sure there's no (kernel) version
mismatch between *-modules packages in the future?
That still stands.
Problem is that if we ask to remove the loop-aes udebs for .30 for unstable
(which is the only real option
On Tuesday 09 March 2010, Cyril Brulebois wrote:
Using my d-i usb stick, I was hoping to recover from it by mounting
the crypted lvm through cryptsetup luksOpen … (which a quick google
suggests), but unfortunately I end up with cryptsetup telling me to
check for missing aes support in the
On Tuesday 09 March 2010, Frans Pop wrote:
On Tuesday 09 March 2010, Cyril Brulebois wrote:
Using my d-i usb stick, I was hoping to recover from it by mounting
the crypted lvm through cryptsetup luksOpen … (which a quick google
suggests), but unfortunately I end up with cryptsetup telling
On Tuesday 09 March 2010, Cyril Brulebois wrote:
Using my d-i usb stick, I was hoping to recover from it by mounting
the crypted lvm through cryptsetup luksOpen … (which a quick google
suggests), but unfortunately I end up with cryptsetup telling me to
check for missing aes support in the
Frans Pop elen...@planet.nl (09/03/2010):
Sorry for the separate replies...
As I pointed out in my first reply, aes_generic was indeed what I
wanted, an error message confused me; that's how I got to loop-aes.
For rescue help with encrypted LVM, see:
On Tuesday 09 March 2010, Cyril Brulebois wrote:
The outcome was quite surprising, but explained a lot: cryptsetup
wasn't actually installed on the target system…
Did you install the system using a daily image? If so, that's what you get
from using udebs from unstable ;-)
Fixed.
--
To
Frans Pop elen...@planet.nl (09/03/2010):
Did you install the system using a daily image? If so, that's what
you get from using udebs from unstable ;-)
I started with something like squeeze alpha1, but might have ended up
updating something on this stick afterwards. I don't remember well,
that
9 matches
Mail list logo
