Re: Bricked system after migrating to thin LVMs

2020-11-25 Thread Ed Greshko
On 25/11/2020 16:42, Sreyan Chakravarty wrote: On Tue, Nov 24, 2020 at 6:12 PM Ed Greshko mailto:ed.gres...@greshko.com>> wrote: Well, the module is located here in my f32 systems. [egreshko@f32k ~]$ locate dm-thin-pool /usr/lib/modules/5.8.13-200.fc32.x86_64/kernel/drivers/md/dm-

Re: Bricked system after migrating to thin LVMs

2020-11-25 Thread Sreyan Chakravarty
On Tue, Nov 24, 2020 at 6:12 PM Ed Greshko wrote: > Well, the module is located here in my f32 systems. > > [egreshko@f32k ~]$ locate dm-thin-pool > > /usr/lib/modules/5.8.13-200.fc32.x86_64/kernel/drivers/md/dm-thin-pool.ko.xz > > /usr/lib/modules/5.8.14-200.fc32.x86_64/kernel/drivers/md/dm-thin

Re: Bricked system after migrating to thin LVMs

2020-11-25 Thread Sreyan Chakravarty
On Tue, Nov 24, 2020 at 9:23 PM Roger Heflin wrote: > If you have a "rescue" option in grub then boot it, the rescue install > should be built with hostonly=no and is expected to include all > drivers including that one. I verified on one of my machines that one > is included in my rescue. The

Re: Bricked system after migrating to thin LVMs

2020-11-24 Thread Roger Heflin
If you have a "rescue" option in grub then boot it, the rescue install should be built with hostonly=no and is expected to include all drivers including that one. I verified on one of my machines that one is included in my rescue. The normal initrd is hostonly=yes and only includes the critical

Re: Bricked system after migrating to thin LVMs

2020-11-24 Thread Ed Greshko
On 24/11/2020 20:19, Sreyan Chakravarty wrote: I think I have found the problem: Nov 24 10:44:00 localhost.HPNotebook dracut-initqueue[861]: Scanning devices dm-0  for LVM logical volumes vgfedora/fedora Nov 24 10:44:00 localhost.HPNotebook dracut-initqueue[886]: inactive '/dev/vgfedora/pool00

Re: Bricked system after migrating to thin LVMs

2020-11-24 Thread Sreyan Chakravarty
Ok, I think I have found the problem: Nov 24 10:44:00 localhost.HPNotebook dracut-initqueue[861]: Scanning devices dm-0 for LVM logical volumes vgfedora/fedora Nov 24 10:44:00 localhost.HPNotebook dracut-initqueue[886]: inactive '/dev/vgfedora/pool00' [929.75 GiB] inherit Nov 24 10:44:00 localho

Bricked system after migrating to thin LVMs

2020-11-24 Thread Sreyan Chakravarty
Hi, I have cloned my original root LVM, and then migrated to the newer thin LVMs using partclone. Both backup and restore went off without causing any problems. But when I am now trying to boot into my system, it asks for the encryption LUKS passphrase but after that I am getting: