Bug#863843: bugs.debian.org: Encrypted partition not accessible after resume

[garjola]

On Fri 02-Jun-2017 at 19:03:13 +0200, garj...@garjola.net wrote: 
> On Thu 01-Jun-2017 at 23:58:43 +0200, Ben Hutchings  
> wrote: 
>> On Thu, 2017-06-01 at 23:36 +0200, garj...@garjola.net wrote:
>>> On Thu 01-Jun-2017 at 00:15:29 +0200, Ben Hutchings >> .uk> wrote: 
>>> > Control: tag -1 moreinfo
>>> > 
>>> > On Wed, 31 May 2017 21:34:59 +0200 Garjola Dindi 
>>> > wrote:
>>> > [...]
>>> > > For several weeks now I have been having issues after resume (both
>>> > 
>>> > from RAM or from disk): my /home seems not to be accessible (at least
>>> > for writing). This does not happen every time, but more something like
>>> > once every 10 or 20 resume cycles.
>>> > [...]
>>> > 
>>> > Please send the messages that appear in the kernel log when you resume.
>>> > (Run 'dmesg' as root to show the kernel log.)
>>> > 
>>> > Ben.
>>> 
>>> Hi,
>>> 
>>> The problem appeared again. I ran dmesg and piped the output to a file
>>> (in one of the non encrypted partitions) just after the problematic
>>> resume, but after reboot (to be able to send this message), the file was
>>> gone.
>>> 
>>> Below is the output of dmesg after a fresh reboot and one successful
>>> suspend/resume cycle. I dont't know if is is useful, since the problem
>>> has not happened since the reboot.
>> [...]
>>
>> I really need to see what happens in the failing case.
>>
>> Ben.
>
> Hi,
>
> Here goes the output of dmesg after a failing resume. I have used a usb
> stick to save the output of dmesg so that I could send it to you. This
> is the sdc device which appears at the end of the log.
>
> Thanks.
>
[...]

Hi, 

Today, after a failed resume I noticed that hard reset with the power button 
tries to shutdown and I could see messages like (copied from a picture of the 
screen, since I don't know how to capture this info):

Timed out stopping /dev/disk/by-id/dm-uuid_CRYPT-LUKS1-..-sda5_crypt.
Timed out stopping /sys/devices/virtual/block/dm-0.
Timed out stopping /dev/disk/by-id/dm-name-sda5_crypt.
Timed out stopping /dev/dm-0.

And also:
(1 of 3) A stop job is running for /dev/mapper/sda5_crypt
(2 of 3) A stop job is running for Disk Manager

Then:

Failed unmounting /boot
Failed unmounting /home

Again, I am attaching the output of dmesg:

[0.00] Linux version 4.9.0-3-amd64 (debian-ker...@lists.debian.org) 
(gcc version 6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.30-1 
(2017-06-04)
[0.00] Command line: BOOT_IMAGE=/vmlinuz-4.9.0-3-amd64 
root=UUID=98ae6177-1de0-4af2-b905-687df457f1ca ro quiet
[0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point 
registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
[0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[0.00] x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]:   64
[0.00] x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]:   64
[0.00] x86/fpu: Enabled xstate features 0x1f, context size is 960 
bytes, using 'compacted' format.
[0.00] x86/fpu: Using 'eager' FPU context switches.
[0.00] e820: BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009dbff] usable
[0.00] BIOS-e820: [mem 0x0009dc00-0x0009] reserved
[0.00] BIOS-e820: [mem 0x000e-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0xc70fafff] usable
[0.00] BIOS-e820: [mem 0xc70fb000-0xc7c7efff] reserved
[0.00] BIOS-e820: [mem 0xc7c7f000-0xc7e7efff] ACPI NVS
[0.00] BIOS-e820: [mem 0xc7e7f000-0xc7efefff] ACPI data
[0.00] BIOS-e820: [mem 0xc7eff000-0xc7ef] usable
[0.00] BIOS-e820: [mem 0xc7f0-0xcc7f] reserved
[0.00] BIOS-e820: [mem 0xf800-0xfbff] reserved
[0.00] BIOS-e820: [mem 0xfd00-0xfe7f] reserved
[0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved
[0.00] BIOS-e820: [mem 0xfed0-0xfed00fff] reserved
[0.00] BIOS-e820: [mem 0xfed1-0xfed19fff] reserved
[0.00] BIOS-e820: [mem 0xfed84000-0xfed84fff] reserved
[0.00] BIOS-e820: [mem 0xfedf-0xfee00fff] reserved
[0.00] BIOS-e820: [mem 0xff70-0x] reserved
[0.00] BIOS-e820: [mem 0x0001-0x0008317f] usable
[0.00] NX (Execute Disable) protection: active
[0.00] SMBIOS 2.7 present.
[0.00] DMI: HP HP EliteBook 840 G3/8079, BIOS N75 Ver. 01.13 11/01/2016
[0.00] e820: 

Bug#863843: bugs.debian.org: Encrypted partition not accessible after resume

[garjola]

On Thu 01-Jun-2017 at 23:58:43 +0200, Ben Hutchings  
wrote: 
> On Thu, 2017-06-01 at 23:36 +0200, garj...@garjola.net wrote:
>> On Thu 01-Jun-2017 at 00:15:29 +0200, Ben Hutchings > .uk> wrote: 
>> > Control: tag -1 moreinfo
>> > 
>> > On Wed, 31 May 2017 21:34:59 +0200 Garjola Dindi 
>> > wrote:
>> > [...]
>> > > For several weeks now I have been having issues after resume (both
>> > 
>> > from RAM or from disk): my /home seems not to be accessible (at least
>> > for writing). This does not happen every time, but more something like
>> > once every 10 or 20 resume cycles.
>> > [...]
>> > 
>> > Please send the messages that appear in the kernel log when you resume.
>> > (Run 'dmesg' as root to show the kernel log.)
>> > 
>> > Ben.
>> 
>> Hi,
>> 
>> The problem appeared again. I ran dmesg and piped the output to a file
>> (in one of the non encrypted partitions) just after the problematic
>> resume, but after reboot (to be able to send this message), the file was
>> gone.
>> 
>> Below is the output of dmesg after a fresh reboot and one successful
>> suspend/resume cycle. I dont't know if is is useful, since the problem
>> has not happened since the reboot.
> [...]
>
> I really need to see what happens in the failing case.
>
> Ben.

Hi,

Here goes the output of dmesg after a failing resume. I have used a usb
stick to save the output of dmesg so that I could send it to you. This
is the sdc device which appears at the end of the log.

Thanks.

[4.490217] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[4.511012] :00:16.3: ttyS0 at I/O 0x3080 (irq = 19, base_baud = 115200) 
is a 16550A
[4.511185] Linux agpgart interface v0.103
[4.557309] tpm_tis 00:0b: 1.2 TPM (device-id 0x1B, rev-id 16)
[4.941311] tpm tpm0: A TPM error (7) occurred attempting to read a pcr value
[4.941368] tpm tpm0: TPM is disabled/deactivated (0x7)
[4.941507] AMD IOMMUv2 driver by Joerg Roedel 
[4.941508] AMD IOMMUv2 functionality not available on this system
[4.941793] i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 
0x60,0x64 irq 1,12
[4.943323] i8042: Detected active multiplexing controller, rev 1.1
[4.943926] serio: i8042 KBD port at 0x60,0x64 irq 1
[4.943929] serio: i8042 AUX0 port at 0x60,0x64 irq 12
[4.943953] serio: i8042 AUX1 port at 0x60,0x64 irq 12
[4.943973] serio: i8042 AUX2 port at 0x60,0x64 irq 12
[4.943991] serio: i8042 AUX3 port at 0x60,0x64 irq 12
[4.944404] mousedev: PS/2 mouse device common for all mice
[4.98] rtc_cmos 00:03: RTC can wake from S4
[4.944999] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
[4.945080] rtc_cmos 00:03: alarms up to one month, y3k, 242 bytes nvram, 
hpet irqs
[4.945086] intel_pstate: Intel P-state driver initializing
[4.945356] intel_pstate: HWP enabled
[4.945520] ledtrig-cpu: registered to indicate activity on CPUs
[4.945776] NET: Registered protocol family 10
[4.945987] mip6: Mobile IPv6
[4.945988] NET: Registered protocol family 17
[4.945990] mpls_gso: MPLS GSO support
[4.946163] microcode: sig=0x406e3, pf=0x80, revision=0x94
[4.946222] microcode: Microcode Update Driver: v2.01 
, Peter Oruba
[4.946333] registered taskstats version 1
[4.946346] zswap: loaded using pool lzo/zbud
[4.970449] input: AT Translated Set 2 keyboard as 
/devices/platform/i8042/serio0/input/input0
[4.993615] tpm tpm0: A TPM error (7) occurred attempting to read a pcr value
[4.993708] ima: No TPM chip found, activating TPM-bypass!
[4.996949] rtc_cmos 00:03: setting system clock to 2017-06-01 21:20:08 UTC 
(1496352008)
[4.997131] PM: Checking hibernation image partition 
/dev/mapper/pc--117--162--vg-swap_1
[4.997139] PM: Hibernation image not present or could not be loaded.
[4.999349] Freeing unused kernel memory: 1392K (b711e000 - 
b727a000)
[4.999350] Write protecting the kernel read-only data: 12288k
[4.999759] Freeing unused kernel memory: 1996K (88494720d000 - 
88494740)
[5.001549] Freeing unused kernel memory: 1244K (8849476c9000 - 
88494780)
[5.005189] x86/mm: Checked W+X mappings: passed, no W+X pages found.
[5.057319] random: systemd-udevd: uninitialized urandom read (16 bytes read)
[5.057384] random: systemd-udevd: uninitialized urandom read (16 bytes read)
[5.057391] random: systemd-udevd: uninitialized urandom read (16 bytes read)
[5.057400] random: systemd-udevd: uninitialized urandom read (16 bytes read)
[5.058066] random: udevadm: uninitialized urandom read (16 bytes read)
[5.058090] random: udevadm: uninitialized urandom read (16 bytes read)
[5.058872] random: udevadm: uninitialized urandom read (16 bytes read)
[5.058906] random: udevadm: uninitialized urandom read (16 bytes read)
[5.058936] random: udevadm: uninitialized 

Bug#863843: bugs.debian.org: Encrypted partition not accessible after resume

[garjola]

On Thu 01-Jun-2017 at 00:15:29 +0200, Ben Hutchings  
wrote: 
> Control: tag -1 moreinfo
>
> On Wed, 31 May 2017 21:34:59 +0200 Garjola Dindi 
> wrote:
> [...]
>> For several weeks now I have been having issues after resume (both
> from RAM or from disk): my /home seems not to be accessible (at least
> for writing). This does not happen every time, but more something like
> once every 10 or 20 resume cycles.
> [...]
>
> Please send the messages that appear in the kernel log when you resume.
> (Run 'dmesg' as root to show the kernel log.)
>
> Ben.

Hi,

The problem appeared again. I ran dmesg and piped the output to a file
(in one of the non encrypted partitions) just after the problematic
resume, but after reboot (to be able to send this message), the file was
gone.

Below is the output of dmesg after a fresh reboot and one successful
suspend/resume cycle. I dont't know if is is useful, since the problem
has not happened since the reboot.

Thanks.


[0.00] Linux version 4.9.0-3-amd64 (debian-ker...@lists.debian.org) 
(gcc version 6.3.0 20170425 (Debian 6.3.0-16) ) #1 SMP Debian 4.9.25-1 
(2017-05-02)
[0.00] Command line: BOOT_IMAGE=/vmlinuz-4.9.0-3-amd64 
root=UUID=98ae6177-1de0-4af2-b905-687df457f1ca ro quiet 
resume=/dev/mapper/pc--117--162--vg-swap_1
[0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point 
registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
[0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[0.00] x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]:   64
[0.00] x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]:   64
[0.00] x86/fpu: Enabled xstate features 0x1f, context size is 960 
bytes, using 'compacted' format.
[0.00] x86/fpu: Using 'eager' FPU context switches.
[0.00] e820: BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009dbff] usable
[0.00] BIOS-e820: [mem 0x0009dc00-0x0009] reserved
[0.00] BIOS-e820: [mem 0x000e-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0xc70fafff] usable
[0.00] BIOS-e820: [mem 0xc70fb000-0xc7c7efff] reserved
[0.00] BIOS-e820: [mem 0xc7c7f000-0xc7e7efff] ACPI NVS
[0.00] BIOS-e820: [mem 0xc7e7f000-0xc7efefff] ACPI data
[0.00] BIOS-e820: [mem 0xc7eff000-0xc7ef] usable
[0.00] BIOS-e820: [mem 0xc7f0-0xcc7f] reserved
[0.00] BIOS-e820: [mem 0xf800-0xfbff] reserved
[0.00] BIOS-e820: [mem 0xfd00-0xfe7f] reserved
[0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved
[0.00] BIOS-e820: [mem 0xfed0-0xfed00fff] reserved
[0.00] BIOS-e820: [mem 0xfed1-0xfed19fff] reserved
[0.00] BIOS-e820: [mem 0xfed84000-0xfed84fff] reserved
[0.00] BIOS-e820: [mem 0xfedf-0xfee00fff] reserved
[0.00] BIOS-e820: [mem 0xff70-0x] reserved
[0.00] BIOS-e820: [mem 0x0001-0x0008317f] usable
[0.00] NX (Execute Disable) protection: active
[0.00] SMBIOS 2.7 present.
[0.00] DMI: HP HP EliteBook 840 G3/8079, BIOS N75 Ver. 01.13 11/01/2016
[0.00] e820: update [mem 0x-0x0fff] usable ==> reserved
[0.00] e820: remove [mem 0x000a-0x000f] usable
[0.00] e820: last_pfn = 0x831800 max_arch_pfn = 0x4
[0.00] MTRR default type: write-back
[0.00] MTRR fixed ranges enabled:
[0.00]   0-9 write-back
[0.00]   A-B uncachable
[0.00]   C-F write-protect
[0.00] MTRR variable ranges enabled:
[0.00]   0 base 00E000 mask 7FE000 uncachable
[0.00]   1 base 00D000 mask 7FF000 uncachable
[0.00]   2 base 00CC00 mask 7FFC00 uncachable
[0.00]   3 base 00CA00 mask 7FFE00 uncachable
[0.00]   4 disabled
[0.00]   5 disabled
[0.00]   6 disabled
[0.00]   7 disabled
[0.00]   8 disabled
[0.00]   9 disabled
[0.00] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WC  UC- WT  
[0.00] e820: last_pfn = 0xc7f00 max_arch_pfn = 0x4
[0.00] Base memory trampoline at [884280097000] 97000 size 24576
[0.00] Using GB pages for direct mapping
[0.00] BRK [0x6c7b2e000, 0x6c7b2efff] PGTABLE
[0.00] BRK [0x6c7b2f000, 0x6c7b2] PGTABLE
[0.00] 

Bug#863843: bugs.debian.org: Encrypted partition not accessible after resume

[Ben Hutchings]

On Thu, 2017-06-01 at 23:36 +0200, garj...@garjola.net wrote:
> On Thu 01-Jun-2017 at 00:15:29 +0200, Ben Hutchings  .uk> wrote: 
> > Control: tag -1 moreinfo
> > 
> > On Wed, 31 May 2017 21:34:59 +0200 Garjola Dindi 
> > wrote:
> > [...]
> > > For several weeks now I have been having issues after resume (both
> > 
> > from RAM or from disk): my /home seems not to be accessible (at least
> > for writing). This does not happen every time, but more something like
> > once every 10 or 20 resume cycles.
> > [...]
> > 
> > Please send the messages that appear in the kernel log when you resume.
> > (Run 'dmesg' as root to show the kernel log.)
> > 
> > Ben.
> 
> Hi,
> 
> The problem appeared again. I ran dmesg and piped the output to a file
> (in one of the non encrypted partitions) just after the problematic
> resume, but after reboot (to be able to send this message), the file was
> gone.
> 
> Below is the output of dmesg after a fresh reboot and one successful
> suspend/resume cycle. I dont't know if is is useful, since the problem
> has not happened since the reboot.
[...]

I really need to see what happens in the failing case.

Ben.

-- 
Ben Hutchings
The most exhausting thing in life is being insincere. - Anne Morrow
Lindberg



signature.asc
Description: This is a digitally signed message part

Bug#863843: bugs.debian.org: Encrypted partition not accessible after resume

[Ben Hutchings]

Control: tag -1 moreinfo

On Wed, 31 May 2017 21:34:59 +0200 Garjola Dindi 
wrote:
[...]
> For several weeks now I have been having issues after resume (both
from RAM or from disk): my /home seems not to be accessible (at least
for writing). This does not happen every time, but more something like
once every 10 or 20 resume cycles.
[...]

Please send the messages that appear in the kernel log when you resume.
(Run 'dmesg' as root to show the kernel log.)

Ben.

-- 
Ben Hutchings
Lowery's Law:
    If it jams, force it. If it breaks, it needed replacing anyway.



signature.asc
Description: This is a digitally signed message part

Bug#863843: bugs.debian.org: Encrypted partition not accessible after resume

[Don Armstrong]

Control: reassign -1 src:linux
Control: severity -1 normal
Control: tag -1 moreinfo

On Wed, 31 May 2017, Garjola Dindi wrote:
> I am using Debian Stretch on a laptop with a HDD (/dev/sda) and an SSD
> (/dev/sdd). My swap and home partitions are encrypted with lvm. The
> ouput of lsblk is:
> 
> NAME  MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
> sda 8:00 931.5G  0 disk  
> ├─sda1  8:10   243M  0 part  /boot
> ├─sda2  8:20 1K  0 part  
> └─sda5  8:50 931.3G  0 part  
>   └─sda5_crypt254:00 931.3G  0 crypt 
> ├─pc--117--162--vg-root   254:10 893.6G  0 lvm   /home
> └─pc--117--162--vg-swap_1 254:20  37.7G  0 lvm   [SWAP]
> sdb 8:16   0   477G  0 disk  
> └─sdb1  8:17   0   477G  0 part  /
> 
> For several weeks now I have been having issues after resume (both
> from RAM or from disk): my /home seems not to be accessible (at least
> for writing). This does not happen every time, but more something like
> once every 10 or 20 resume cycles.
> 
> At first, I thought this was related to an initramfs-tools (0.129)
> update where it was mentioned that the RESUME variable had to be set
> in the configuration, but this should only affect resuming from disk.
> I however tried to set this to different values (the /dev/XXX, auto,
> none) but nothing changes with my issue.
> 
> Since I also have a warning at boot time saying "Failing to connect to
> lvmetad" I set use_lvmetad = 0 in /etc/lvm/lvm.conf. Again, nothing
> changes.

You've filed this bug against bugs.debian.org which is the pseudopackage
for reporting bugs which affect the bug tracking system itself, not for
bugs which the underlying package is unclear.

I've reassigned it to the linux source package, but you'll need to
provide more information before the maintainers of that package will be
able to help.

In this particular case, I'm suspecting that /home or possibly swap is
getting mounted read only, but the output of dmesg; when you have a
failure will provide more information. [Along with the precise kernel
version and whether this happens on newer kernels (4.11.0-trunk is in
experimental) too.]



-- 
Don Armstrong  https://www.donarmstrong.com

"In my many years I have come to a conclusion that one useless man is
a shame, two is a law firm, and three or more is a congress."
 -- John Adams

Bug#863843: bugs.debian.org: Encrypted partition not accessible after resume

[Garjola Dindi]

Package: bugs.debian.org
Severity: serious
Justification: 4

Dear Maintainer,

Hi,

I am using Debian Stretch on a laptop with a HDD (/dev/sda) and an SSD 
(/dev/sdd). My swap and home partitions are encrypted with lvm. The ouput of 
lsblk is:

NAME  MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sda 8:00 931.5G  0 disk  
├─sda1  8:10   243M  0 part  /boot
├─sda2  8:20 1K  0 part  
└─sda5  8:50 931.3G  0 part  
  └─sda5_crypt254:00 931.3G  0 crypt 
├─pc--117--162--vg-root   254:10 893.6G  0 lvm   /home
└─pc--117--162--vg-swap_1 254:20  37.7G  0 lvm   [SWAP]
sdb 8:16   0   477G  0 disk  
└─sdb1  8:17   0   477G  0 part  /

For several weeks now I have been having issues after resume (both from RAM or 
from disk): my /home seems not to be accessible (at least for writing). This 
does not happen every time, but more something like once every 10 or 20 resume 
cycles.

At first, I thought this was related to an initramfs-tools (0.129) update where 
it was mentioned that the RESUME variable had to be set in the configuration, 
but this should only affect resuming from disk. I however tried to set this to 
different values (the /dev/XXX, auto, none) but nothing changes with my issue.

Since I also have a warning at boot time saying "Failing to connect to lvmetad" 
I set use_lvmetad = 0 in /etc/lvm/lvm.conf. Again, nothing changes.

My /etc/crypttab reads as follows:
sda5_crypt UUID=11a52b25-26f4-41ae-b52e-2aa5d0a4d35d none luks

which seems OK since
ls -l /dev/disk/by-uuid/
total 0
lrwxrwxrwx 1 root root 10 May 31 10:45 11a52b25-26f4-41ae-b52e-2aa5d0a4d35d -> 
../../sda5
lrwxrwxrwx 1 root root 10 May 31 10:45 136599d4-9b3b-4a74-a0dc-6bc48fb227f3 -> 
../../sda1
lrwxrwxrwx 1 root root 10 May 31 10:45 2b70ec10-751f-4670-8000-1c59d7307f29 -> 
../../dm-2
lrwxrwxrwx 1 root root 10 May 31 10:45 98ae6177-1de0-4af2-b905-687df457f1ca -> 
../../sdb1
lrwxrwxrwx 1 root root 10 May 31 10:45 d3415b5d-e1fe-4ce6-98c8-a8645f358524 -> 
../../dm-1

Thanks

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64
 (x86_64)

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)