Hello,

I have not reproduced this problem myself but it seems likely that it
exists.  I am writing here to be sure that nothing is overlooked and
to give people who might have this problem a reference.

This is a companion problem to bug #918590 and am told related to
a problem fixed in Buster RC 1.

grub-installer/grub-mkconfig can fail when in rescue mode in the installed
system's chroot because of a long LVM related timeout.  The workaround
is reportedly something like:

# mkdir /mnt/hostlvm
# mount --bind /run/lvm /mnt/hostlvm
# chroot /mnt
# ln -s /hostlvm /run/lvm

See:
https://wiki.archlinux.org/index.php/GRUB#Device_/dev/xxx_not_initialized_in_udev_database_even_after_waiting_10000000_microseconds
and
https://bbs.archlinux.org/viewtopic.php?pid=1820949#p18209

Hey Karl,

Karl O. Pinc <kop@karlpinc.com> (2019-11-07):

Thanks for filing this bug report; I'll try and keep that in mind while
preparing updates for buster, using the throw away VMs to test this.
I'll adjust bug metadata accordingly when I get to it.

Also, I suppose bind-mounting /run entirely would be sufficient.



Cheers,