Your message dated Mon, 7 Jun 2010 19:32:18 +0200
with message-id <20100607173218.ga13...@galadriel.inutil.org>
and subject line Re: Seems to be resolved already
has caused the Debian Bug report #576635,
regarding Unable to access an encrypted root partition after a failed resume
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 what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
576635: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576635
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.32-3-amd64
Version: 2.6.32-9
Severity: important
I set up unstable on a new laptop last week, using the same
configuration that I had on my last laptop: a single LVM physical
volume, encrypted (with the configuration created by the installer),
divided into two logical volumes, one for swap and one for the root
partition. /boot, obviously, isn't on that partition.
This morning, I tried to unhibernate the laptop for the second or
third time ever. I entered my password and the screen blanked, but this
time I was unlucky and it didn't come back (I was starting to hope
hibernate would actually work ... oh well). So after giving it a good
five minutes to do something, I finally just killed the power and
rebooted.
After the reboot, the initrd wouldn't accept my encryption passphrase.
More specifically: it would unlock the partition, then announce that it
couldn't find a filesystem on the device. I've booted the Squeeze live
CD on the laptop, and it appears that the initrd was correct. I can
unlock the partition by hand, but pvdisplay insists that the unencrypted
device is not an LVM physical volume. Nor does it appear to be a
filesystem of any normal sort. I'm not sure what sort of horrible thing
happened to it at this point.
I'm currently trying to hook the laptop in question up to the network
so I can grab an image of the block device for analysis, in the hope
that I can eventually figure out how to get my data off it (I'd like to
get a working system on the laptop soon so I can use it one the bus).
Obviously, I'd appreciate any suggestions you can give me with regard to
tracking down what happened and/or repairing the system.
Daniel
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-2-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
Version: 2.6.32-15
On Sun, Jun 06, 2010 at 04:10:14PM +0300, Oren Held wrote:
> I'm using now linux-image-2.6.32-5-amd64 (v2.6.32-15), and I do not
> experience this bug anymore
Thanks, marking as fixed.
Cheers,
Moritz
--- End Message ---
