I found a temporary solution that seems ok for now. This article walks through the addition of an initramfs hook to add the necessary kernel modules and and executables to the initramfs image so that the boot process can deal with lvm thinpools and thinvolumes.
Then update the initramfs image:
# chmod 755 /etc/initramfs-tools/hooks/thin-provisioning-tools
# update-initramfs-tools -u
After reboot, things work as expected. I expect the thin-provisioning-tools package should be updated to make these changes. What is the right way to report this as an issue with this package?
I found a temporary solution that seems ok for now. This article walks through the addition of an initramfs hook to add the necessary kernel modules and and executables to the initramfs image so that the boot process can deal with lvm thinpools and thinvolumes.
http:// askubuntu. com/questions/ 673815/ how-do- i-start- my-laptop- with-root- partition- on-lvm2- thin-pool
To recap, create file /etc/initramfs- tools/hooks/ thin-provisioni ng-tools:
#!/bin/sh
PREREQ="lvm2"
prereqs()
{
echo ""
}
case $1 in
prereqs)
prereqs
exit 0
;;
esac
. /usr/share/ initramfs- tools/hook- functions
copy_exec /usr/sbin/ thin_check thin_repair thin_restore
copy_exec /usr/sbin/thin_dump
copy_exec /usr/sbin/
copy_exec /usr/sbin/
copy_exec /sbin/dmeventd
manual_add_modules dm_thin_pool
Then update the initramfs image: tools/hooks/ thin-provisioni ng-tools initramfs- tools -u
# chmod 755 /etc/initramfs-
# update-
After reboot, things work as expected. I expect the thin-provisioni ng-tools package should be updated to make these changes. What is the right way to report this as an issue with this package?