Bug 983833 - dm-thin-pool not loaded by initrd, after cryptsetup
Summary: dm-thin-pool not loaded by initrd, after cryptsetup
Status: RESOLVED DUPLICATE of bug 983221
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Bootloader (show other bugs)
Version: Current
Hardware: x86-64 Other
: P5 - None : Critical (vote)
Target Milestone: ---
Assignee: Jiri Srain
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-06-08 18:35 UTC by Thiago Macieira
Modified: 2016-06-08 19:09 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Thiago Macieira 2016-06-08 18:35:45 UTC 
Evironment: system with at least one filesystem on an LVM Thin Pool (as recommended by snapper for ext4 snapshotting). It's not the root filesystem (fortunately).

Situation: when booting, the system halts for 90 seconds waiting for lvm2-activation-early.service and lvm2-activation.service to finish, which failed. After that, systemd drops me to an emergency shell because it couldn't mount all filesystems.

The reason is that dm-thin-pool.ko was not loaded, so vgchange could not activate the Thin Pool LVs. In that emergency shell, if I run
  modprobe dm-thin-pool && vgchange -ay

Then the boot proceeds normally.

This began happening around the time kernel 4.6.0-1-default was released. It did not happen on May 24 and it definitely did not on May 17.

Workaround: edit /etc/default/grub and add
 rdloaddriver=dm-thin-pool
to GRUB_CMDLINE_LINUX_DEFAULT.
Comment 1 Martin Pluskal 2016-06-08 19:09:32 UTC 
Likely same issue as boo#983221

*** This bug has been marked as a duplicate of bug 983221 ***